Guide · 6 min read
Is it safe to give an AI data buyer access to your Slack and email?
Assess the actual access requested, the preparation process and the consequences if records are exposed or reused beyond the agreed purpose. A scoped export can reduce access, but security controls and contractual promises do not eliminate every risk.
Read-only export or live tool access?
A one-time, scoped, read-only export limits what a buyer can see. Connector access depends on its permissions and lifetime; check both rather than assuming access is limited to a one-time export. Prefer exports where possible, and if you connect tools, scope permissions narrowly and revoke them after delivery.
Who de-identifies the data, and where?
Some buyers de-identify inside your environment before anything leaves (Scale AI says it does), others after transfer. De-identification inside your environment is the stronger position. NIST’s SP 800-188 is a useful reference for de-identification methods.
What happened in the Mercor security incident?
In April 2026 Mercor confirmed it was one of thousands of companies affected by a supply-chain attack involving the open-source LiteLLM library (Business Insider). Meta paused its work with Mercor (WIRED) and at least seven class actions followed, which Mercor disputes (WSJ). The lesson for sellers: ask about dependency and vendor security, not only the buyer’s own systems.
What should you ask every buyer?
Buyer security questions
- Is data encrypted in transit and at rest?
- Where is raw data stored, in which region, and for how long?
- Who can access raw, identified data?
- What de-identification method is used, and can we review a sample?
- Which attestations do you hold (for example SOC 2 Type II), who audited you and for which period?
- How fast will you notify us of an incident?
- Will you delete raw data after de-identification and certify it?
- Can our data be resold or relicensed?
Worked example: setting up a safe transfer (fictional)
Tallowmere Billing, a fictional 120-person SaaS company, refuses a live Zendesk connector and instead provides a scoped, read-only export of 2016 to 2025 tickets with payment fields removed.
The buyer de-identifies inside a workspace Tallowmere controls, Tallowmere reviews 200 sample tickets, and the contract requires deletion of the raw export within 30 days of acceptance, with a signed certificate.
When not to do it
- Do not grant ongoing admin access to production tools for a one-time license.
- Do not rely on a security badge on a website; ask for the report, the auditor and the period.
Sources
- Scale AI data partnership
- NIST SP 800-188: De-identifying government datasets
- WIRED on Mercor
- Business Insider on Mercor
Content revised November 1, 2026. Buyer profiles show program review dates; historical reporting is identified separately.
Figures are each buyer’s published range or reported values, labelled as such, and are not offers. This is general information, not legal advice. QuoteMyData may be paid by buyers when a deal closes; see our disclosure.
