Start with the exact document or control that applies to the account today. Record the operator, date, data category, stated purpose, recipient, retention boundary and available control. If the source does not answer one of those fields, write unknown. The purpose of this page is not to turn a policy into a trust badge. It is to make the next decision smaller, dated and reversible.
Candy AI's October 19, 2026 Privacy Notice describes processing that can include model improvement, quality analysis and human review in defined contexts. Those are vendor statements, not proof that a conversation is confidential, unseen or immediately erased.
What the official documents say—and what to do with it
This is a dated document review, not a private-account test. Each finding is limited to the public source and revision available on the checked date.
Operator and current notice
The Privacy Notice identifies EverAI Limited as controller and shows a revision date of October 19, 2026. The Terms show a September 22, 2026 revision.
Decision: Match the operator and date before relying on a policy excerpt or search snippet.
Chats, calls and outputs
The notice treats user prompts, messages or calls and generated outputs as Content data when they contain personal data.
Decision: Treat private chat and generated media as account data, not as an ephemeral or anonymous exchange.
Model improvement and review
The notice says de-identified or anonymized interactions may be used to prepare training datasets and may include human review. It separately describes human review of content flagged by moderation controls or users.
Decision: Do not promise that nobody can review content. Share less and keep credentials, documents and third-party secrets out.
Recipients
The notice lists hosting, moderation and third-party LLM providers or hosters among service-provider categories and says those parties may receive chatbot message content.
Decision: Read the live recipient section before entering intimate or identifying details.
Retention and deletion
The notice generally describes account-data retention for three years after last account activity, with stated alternatives, deletion requests and legal or financial exceptions. Financial records are described separately.
Decision: Account closure, chat deletion and a personal-data request are different actions; keep the confirmation for the route you use.
Rights and content removal
The Privacy Team route is [email protected] and the notice also names [email protected]. The separate removal policy covers AI-generated content that resembles a real person; it is not a universal account-deletion route.
Decision: Use the privacy route for data rights and the removal route for real-person resemblance concerns.
What to inspect before deciding
01operator and policy date□
02chats and generated outputs□
03model improvement and human review□
04service providers and message content□
05retention after account closure□
06rights and removal routes□
Unknown stays unknown. Recheck before sharing.The six fields below are deliberately narrow. Check them against the current notice, account screen or regulator guidance rather than relying on a search snippet. Save the checked date and the URL because wording, ownership and controls can change.
operator and policy date
Find the specific wording for operator and policy date. Separate a vendor statement from an independently verified fact, note any regional condition, and avoid extending the claim beyond the product and date named by the source.
chats and generated outputs
Find the specific wording for chats and generated outputs. Separate a vendor statement from an independently verified fact, note any regional condition, and avoid extending the claim beyond the product and date named by the source.
model improvement and human review
Find the specific wording for model improvement and human review. Separate a vendor statement from an independently verified fact, note any regional condition, and avoid extending the claim beyond the product and date named by the source.
service providers and message content
Find the specific wording for service providers and message content. Separate a vendor statement from an independently verified fact, note any regional condition, and avoid extending the claim beyond the product and date named by the source.
retention after account closure
Find the specific wording for retention after account closure. Separate a vendor statement from an independently verified fact, note any regional condition, and avoid extending the claim beyond the product and date named by the source.
rights and removal routes
Find the specific wording for rights and removal routes. Separate a vendor statement from an independently verified fact, note any regional condition, and avoid extending the claim beyond the product and date named by the source.
How to interpret a complete or incomplete card
A complete field means the source gives a usable answer; it does not mean the answer is favorable. A missing field is a decision constraint. Reduce the data you share, keep a permission off, delay payment, choose a different service or contact the operator through the official route. Do not fill a gap with marketing language from another page.
Compare like with like. A privacy notice, terms page, app permission and deletion control answer different questions. A strong account control cannot repair a vague collection purpose, and an encryption claim cannot explain retention. Keep each piece of evidence in its own column before reaching a conclusion.
Use low-risk fictional examples if a feature needs a prompt. Never upload a real person’s private image, reveal credentials or provoke harmful content merely to see what happens. This guide relies on public evidence and does not claim hands-on access to private account behavior.
What this page cannot promise
- It cannot certify that a provider, conversation or account is private or safe.
- It cannot prove unseen technical behavior from policy wording alone.
- It cannot replace legal advice, regulator guidance or emergency support.
- It does not convert a sponsored link into an endorsement or a product test.
Stop when the operator is unclear, the data requested exceeds the feature’s need, another person’s consent is missing, an adult boundary is ambiguous, or the exit route cannot be found. Preserve only the evidence you need and avoid creating additional sensitive copies.
A practical decision record
- Capture
Save the exact page, checked date and wording that supports the field.
- Classify
Label it vendor statement, account control, regulator guidance or independent standard.
- Constrain
Turn each unknown into a smaller permission, smaller disclosure or delayed purchase.
- Recheck
Review the evidence before sharing more data, renewing or changing the account.
Public evidence used for this question
- Candy AI privacy policy
Vendor-stated data collection, purposes, sharing, retention, rights and contact routes; notice revision October 19, 2026.
vendor policy · checked October 30, 2026 - Candy AI terms of service
Vendor-stated age, account, content-license, billing, conduct and termination boundaries; terms revision September 22, 2026.
vendor policy · checked October 30, 2026 - Candy AI content removal policy
Vendor-stated route for AI-generated content that resembles a real person; policy revision July 30, 2026.
vendor policy · checked October 30, 2026
Inspect the current documents before you continue
Candy AI is a sponsored destination and a labeled vendor case study. Verify the live terms, privacy notice and controls for your own account and region.
Visit Candy AI — sponsored