How to say no to an AI company that wants your data

When is no the right answer to an AI data request?#

No is the right answer to an AI data request whenever you cannot yet say what would be shared, under whose rights, and for what permitted use. Most cold requests arrive before any of that is known, so a decline is often the honest response rather than a defensive one.

Founders tend to judge the request on the merits of the offer. The better test is whether your own house is in order: do you know which systems hold the records, which customer contracts and vendor terms apply, and who can sign for the company? If any of those answers is unknown, the request is early for you, whatever it says about the requester.

What should a decline message include?#

A decline message should include thanks, a clear decision, no detail about your records, a deletion request for anything already received, and a statement about future contact. Leaving any of them out tends to invite the follow-up call you were trying to avoid.

Put the decision in the first two sentences. Requesters often read a hedged reply as an opening bid, and a vague not at this stage can turn into a recurring check-in sequence. If the answer is not now, say what would prompt you to reach out, in general terms.

• 1Thanks for the interest, in one line.
• 2The decision: not pursuing data licensing now, or not pursuing it with this requester.
• 3No description of systems, record counts, customers, years of history or what you think the records are worth.
• 4A request to delete any samples, screenshots or notes from earlier calls, with written confirmation.
• 5A reminder that confidentiality obligations already signed continue to apply, if there are any.
• 6Whether the requester may contact you again, and through whom.

Decline templates you can adapt#

Decline templates work best when you pick the version that matches your real position: not now with the door open, not on these terms, or a firm no. Edit the bracketed items, keep the length, and send from the executive who owns the decision rather than from a shared inbox.

Not now, door open: 'Thank you for reaching out about licensing records from [Company]. We have reviewed the request and are not pursuing data licensing at this time. If our position changes, [Name, title] will contact you directly, so there is no need to follow up. If you received any material from us in earlier conversations, please delete it and confirm by reply.'

Not on these terms: 'Thank you for the proposal. [Company] is not able to proceed on the terms described. We would consider licensing records only for a defined permitted use and a fixed term, with deletion at the end and no onward transfer. If that does not fit your plans, we will leave it here. Please delete any material you received from us and confirm by reply.'

Firm no: 'Thank you for your note. [Company] has decided not to license its records to [Requester], and we ask that you not contact our team about this again. Please delete any information you received from us and confirm in writing. Our [NDA or confidentiality terms] continue to apply.'

Internal note to file: 'Request from [Requester], received [date] through [channel]. Records requested: [description]. Declined because: [reason]. Revisit if: [trigger].' The internal note often matters more than the email, because it is what the next leadership team will find.

What should you never say when you decline?#

The most damaging thing to say when you decline is anything that describes what you hold. A sentence such as 'we have years of tickets but our contracts are messy' gives away your history, your record type and your weak point in one line.

Avoid naming a price you would accept, blaming a customer or employee for the decision, or promising the requester a first look if you ever proceed. A first-look promise can read as a soft exclusivity commitment, and a price hint anchors every later conversation, including ones with other parties.

Do not agree to a quick call to understand your concerns unless you want to reopen the decision. If the requester answers with a mutual NDA, you do not need to sign it to say no, because declining creates no obligation to negotiate.

What if you already shared samples or screens?#

Samples or screens shared before a decline should be treated as disclosed records, so ask for deletion and written confirmation. Early conversations often include a screen share of a help desk queue, a spreadsheet export or a handful of redacted tickets, and those copies outlive the call.

Check whether an NDA was signed and what its return-or-destroy clause says. Some NDAs let the recipient keep archival or backup copies, so note what may remain. If there was no NDA, the deletion request still documents that you objected to further use.

Then look inward. Find out who shared what, from which system, and whether customer or employee personal details were included. If personal details left the company, involve whoever handles privacy, because notice or contract obligations may apply depending on the data and the agreements involved.

Which changes justify revisiting the decision?#

A declined request deserves a second look only when something specific changes inside the company, not when the requester asks again. Tie each decline to a named trigger so the next conversation starts from a fact rather than from persistence.

If none of these triggers occurs, the decline stands. Repeated outreach from the same requester is not a trigger; it is a reason to check that your reply was clear.

Illustrative: a restoration contractor says not now#

Illustrative: a fictional water and fire restoration contractor, operating as a franchisee, receives an email from an AI startup asking for its job files, moisture readings, photo logs and adjuster correspondence. The owner has never checked whether the franchise agreement gives the franchisor control over job records, and many files include homeowner names and insurance claim details.

The owner sends the not-now template, asks the startup to delete a sample job file a project manager had already emailed, and receives written confirmation. The internal note lists two triggers: a reading of the franchise agreement's records clause with counsel, and a review of how homeowner details could be removed. Months later, with both answered, the owner runs a metadata-only fit check on the company's own terms instead of reopening the original thread.

How SourceX treats a no#

SourceX treats a no as a normal result, whether it comes at the first conversation or just before release. The supplier approves each step of the SourceX five-step transaction, so stopping needs no justification and creates no obligation to continue.

The fit check that opens the process collects metadata, such as system names, years of history and record families, rather than files. A company that stops there has described its systems in general terms but disclosed no records, which is the same position this article recommends for any decline.