The question is not "is it private" but "private from whom, and for how long." A tool can promise not to train on your content while still retaining it for thirty days for abuse monitoring, and a tool can retain nothing while still sending it to a subprocessor in another jurisdiction. These are different promises, and the marketing pages tend to merge them.
What follows is based on published policy documents as of October 2026. Policies change, and the binding document is the one you signed — treat this as a map of what to look for, then verify against your own agreement.
The four questions to ask any tool
- Is my content used for training? Usually a plan-tier distinction. Consumer plans frequently opt you in by default; business tiers generally opt you out contractually.
- How long is it retained? Even with training disabled, most providers keep logs for a period — commonly thirty days for abuse investigation, sometimes longer.
- Can a human read it? Some services retain the right to review flagged conversations. Enterprise agreements often remove this.
- Where does it go? Subprocessors and regions matter for any text covered by data-residency obligations.
If a vendor's policy page does not answer all four, ask directly and get it in writing before pasting anything sensitive.
How the tiers generally differ
| Tier | Typical training default | Typical retention |
|---|---|---|
| Free / consumer | Often included; opt-out available in settings | Retained for a defined period, sometimes indefinitely until deleted |
| Pro / individual paid | Usually excluded, but verify — this varies | Commonly around 30 days for abuse monitoring |
| Team / business | Excluded contractually | Shorter, with admin controls and deletion |
| Enterprise | Excluded, with zero-retention options | Configurable, sometimes none |
The practical consequence: the same tool can be safe for one team and not another depending on the plan. Check the tier you are actually paying for, not the headline promise.
Four categories never to paste
- Identifying customer data — names, contact details, account records, anything under a privacy commitment you made to someone else.
- Unpublished financials — results, forecasts, pricing decisions before disclosure.
- Regulated records — health, legal, employment files, anything with a statutory handling requirement.
- Credentials and keys — API keys, tokens, connection strings, internal URLs. Assume anything pasted is no longer secret.
Each of these creates an obligation you cannot retract once the text has left your systems. The risk is rarely the model — it is the retention, the logs, and the people with access to them.
What "zero retention" does and does not cover
Enterprise agreements sometimes offer zero-retention processing: the request is handled and not stored. Worth understanding the boundaries of that promise. It usually covers the provider's own storage, not your browser history, your company's endpoint logging, third-party integrations you enabled, or screenshots taken by anyone else. It also typically excludes the abuse-monitoring carve-out, which is why the retention period matters even when training is disabled.
A workable policy for a small team
- Decide the tier first, then the tool — the data terms sit at plan level
- Write down the four categories and circulate them; assume people will paste them otherwise
- Use placeholders in reusable templates: [CLIENT NAME], not the actual client
- Turn off chat history where the option exists, and review it quarterly
- For regulated work, use a business tier with contractual terms rather than a consumer login
The last point is the one most often skipped, and it is where the actual exposure sits. A consumer subscription used for client work is a policy problem waiting to be discovered.
Check the tier, not the logo
Data handling differs by plan. Confirm which terms you are on before the draft contains anything you could not publish.
Try Rytr →Frequently Asked Questions
Do AI writing tools train on my drafts?
It depends on the plan. Consumer tiers often include training by default with an opt-out; business and enterprise tiers typically exclude it contractually. Check the terms for the tier you pay for.
Does deleting a chat remove it from the model?
Deleting removes it from your account and from future training runs. It does not retroactively remove influence from a model that was already trained on it.
Is the paid version private?
Private is the wrong word. Paid tiers usually remove training and shorten retention, but they are not a confidentiality agreement unless the contract says so.
Can employees paste client data?
Not without checking your own commitments. If your client agreement restricts subprocessors, pasting that data into a consumer tool likely breaches it.
What is the safest thing to paste?
Text you would be comfortable publishing. If it would cause a problem on the front page, it does not belong in the prompt.
How often do these policies change?
Often enough that a quarterly review is worth it. Providers revise retention periods and subprocessor lists without much notice.