Help for owners
I am worried my AI tools are sending customer data to third parties
Short answer
Data typed into an AI tool leaves your systems and goes to the provider, and what happens next depends on the product and plan. OpenAI states API data is not used for training unless you opt in, and abuse logs are kept up to 30 days by default. Find out who uses what, set a simple rule, and avoid personal data where you can.
Does this sound like your situation?
- Staff paste customer emails or spreadsheets into a free chat tool.
- I do not know which AI tools my team uses.
- A plugin or app connected itself to my email or drive.
- A customer or contract asks how I handle their data with AI.
- My developer sends full records to an AI API and I never asked what is included.
Why does this happen?
Consumer tools and business APIs are different products
A free chat window, a paid team plan and the developer API each have their own terms. A rule that is true for one is not true for another, so you have to check the exact product.
API data and training
OpenAI states that data sent to its API is not used to train or improve its models unless you explicitly opt in.
Confirmed by developers.openai.com
Providers keep some logs
By default, OpenAI generates abuse monitoring logs for API usage and retains them for up to 30 days, longer if the law requires it. Approved customers can ask for Zero Data Retention or Modified Abuse Monitoring, and some features store application state until you delete it.
Confirmed by developers.openai.com
Staff do it to save time
Most leaks are not attacks. Someone pastes a complaint, a contract or a customer list into whichever tool is open, because nobody told them not to.
Connected apps get wide access
A browser add-on, a meeting recorder or an AI plugin can be allowed to read email, files or calendars. The permission is granted in one click and forgotten.
What can I do about it today?
- Ask your team what they useA short, friendly question with no blame: which AI tools, for what, with which accounts. You cannot make a rule without knowing.
- Write a one-page ruleSay which tools are approved, and that customer names, ID numbers, health or payment details must not be pasted into others.
- Review connected appsIn your email, drive and chat admin pages, look at which third-party apps have access, and remove ones nobody recognises. Removing access is reversible.
- Read the plan's data termsFor each approved tool, find its data page and note whether your data is used for training and how long it is kept.
- Check what your own apps sendIf a developer built AI into your product, ask which fields are sent to the provider and whether each is needed.
When should I bring someone in?
- You handle health, financial or other regulated customer data.
- A customer contract or auditor asks for written proof of how data is handled.
- You suspect data has already been shared that should not have been.
How do I handle it?
- Map the data flowI list every place where your data goes to an AI provider: which fields, from which system, under which account and settings.
- Send lessNames, numbers and other identifiers are removed or replaced before a request leaves your system, wherever the task allows.
- Use the provider's controlsI read the provider's data documentation, choose the settings that fit, and note which options need the provider's approval.
- Lock down keys and accessKeys live on the server, not in an app or a shared document, and access is limited by role.
- Write it downYou get a plain description of the flow that you can show a customer. Legal questions remain for your lawyer.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is it safe to use ChatGPT for work?
It depends on the product and plan and on what you paste. Check the exact terms of the one you use, and keep sensitive data out of tools you have not checked.
Does the provider read my data?
Providers describe retention and monitoring in their data pages. Read the page for your product rather than relying on general statements.
Is this legal advice?
No. For rules like data protection laws or sector requirements, ask a qualified lawyer.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.