Rights & safeguards

Check rights before you check price

Separate ownership, privacy, contracts and platform rules before licensing an archive.

Sources and guidance · Reviewed October 2026
Technical export access is not permission to commercialise the exported content. Check contracts, copyright, privacy and collection restrictions separately.

Start with the system

Official-source export notes and distinctive rights questions for each platform.

18 platform guides

Platform preparation · 01

Slack data exports: preparation and rights review

Prepare Slack records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 02

Microsoft 365 data exports: preparation and rights review

Prepare Microsoft 365 records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 03

Google Workspace data exports: preparation and rights review

Prepare Google Workspace records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 04

Atlassian Jira and Confluence data exports: preparation and rights review

Prepare Atlassian Jira and Confluence records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 05

GitHub data exports: preparation and rights review

Prepare GitHub records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 06

GitLab data exports: preparation and rights review

Prepare GitLab records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 07

Notion data exports: preparation and rights review

Prepare Notion records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 08

Salesforce data exports: preparation and rights review

Prepare Salesforce records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 09

HubSpot data exports: preparation and rights review

Prepare HubSpot records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 10

Zendesk data exports: preparation and rights review

Prepare Zendesk records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 11

ServiceNow data exports: preparation and rights review

Prepare ServiceNow records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 12

Intercom data exports: preparation and rights review

Prepare Intercom records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 13

Zoom data exports: preparation and rights review

Prepare Zoom records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 14

QuickBooks data exports: preparation and rights review

Prepare QuickBooks records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 15

Xero data exports: preparation and rights review

Prepare Xero records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 16

NetSuite data exports: preparation and rights review

Prepare NetSuite records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 17

Figma data exports: preparation and rights review

Prepare Figma records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Platform preparation · 18

Linear data exports: preparation and rights review

Prepare Linear records for an AI data licensing review: export scope, content risks, provenance, and a bounded pilot.

Four separate permission checks

Ownership: who created the material and who owns the relevant rights? Privacy: what does the collection reveal about people, and what rules apply to reuse? Contracts: what did you promise customers, staff and suppliers? Platform terms: what restrictions apply to the way the data was obtained?

A positive answer in one column does not clear the others. Keep evidence and unresolved questions for each collection, not just a single yes/no answer for the company.

Prepare a rights register

For every data source, record its owner, collection route, applicable contract version, intended recipient and use, rights evidence, exclusions and reviewer. Attach references to documents rather than copying sensitive clauses into a public datasheet.

Make exclusions an operational step

Remove restricted data before generating samples. Preserve a manifest of exclusions and test that links or attachments have not reintroduced the same material. Sensitive content can appear in filenames, comments, embedded images, revision history and logs.

Get advice where uncertainty matters

Use qualified counsel for jurisdiction-specific legal questions, employee monitoring, regulated data, insolvency, international transfers and broad warranties. This site provides preparation guidance, not a legal clearance or a decision that any dataset is lawful to sell.