← Research

How to Opt Out of AI Training Without Assuming the Toggle Does Everything

Use a Training-Use Objection Packet to opt out of AI training in companion apps, check toggle scope and legal basis, and record the written outcome.

Quick answer: To opt out of AI training in a companion app, first separate training purposes from service delivery and safety filtering, locate the current privacy policy and stated legal basis, complete a structured Training-Use Objection Packet, use any visible toggle only for its documented scope, then send a concise written objection or erasure request. Record every response, note unresolved data uses, and follow up on exceptions. Jurisdiction, legal basis, and provider exceptions determine what actually changes. The process requires identifying each use, submitting verifiable identity proof when requested, and treating account deletion, chat deletion, and billing cancellation as distinct actions. No toggle or single request guarantees reversal of prior training.

Meet the companions

Choose your AI girlfriend

Pick your AI girlfriend

Click the button to view the full character lineup.

Hana Fujimoto AI girlfriend

Hana Fujimoto, 23

CutePink

Lifestyle Creator

Tokyo-born creator with a pixie cut and pastel-pink moods — cozy bedroom selfies and chat that starts shy then melts.

Start chatting
Elise Chen AI girlfriend

Elise Chen, 24

SleekBold

Pilates Instructor

Taipei-born pilates coach with long dark hair and window-light confidence — toned curves and DMs that go direct after class.

Start chatting
Sora Kim AI girlfriend

Sora Kim, 22

PlayfulSultry

Fashion Blogger

Seoul fashion blogger who turns her living room into a private shoot — stockings, lace, and couch poses meant only for you.

Start chatting
Rosie Hart AI girlfriend

Rosie Hart, 24

Soft

Florist

Rose-obsessed florist who turns bath nights into rituals — petals, steam, and shy smiles that melt fast.

Start chatting
Chloe Mercer AI girlfriend

Chloe Mercer, 23

PlayfulTeasing

Hotel Concierge

Auburn-haired concierge with a mischievous maid fantasy — stockings, vinyl, and couch poses meant only for you.

Start chatting
Emma Brooks AI girlfriend

Emma Brooks, 22

WarmFlirty

Interior Stylist

Cozy stylist with wavy brown hair and red-ribbon moods — mirror selfies and living-room heat after sunset.

Start chatting
Jade Monroe AI girlfriend

Jade Monroe, 26

EdgySultry

Cocktail Bartender

After-hours bartender with pool-table charisma — stockings, dim lights, and a smirk that dares him to stay.

Start chatting
Scarlett Voss AI girlfriend

Scarlett Voss, 25

BoldWild

Luxury Car Vlogger

Luxury car vlogger with handcuff fantasies and white-lace nights — adrenaline and intimacy in one breath.

Start chatting

Browse all companions →

Separate training from service delivery and safety use

“Training” is not a safe umbrella for every use of chat data. A policy may describe service delivery, safety or abuse prevention, analytics, product improvement and model training separately—or use different terms. Copy the provider's exact purpose, data category and stated legal basis into the packet. Do not infer model weights, embeddings or downstream use when the policy does not say so. A control labelled “Improve the model” establishes only the scope described beside that control.

Open the live Privacy Policy or Data Practices page and note its date, controller, jurisdiction, purpose, legal basis and request route. Do not assume that most companion apps rely on the same basis or lack the same security property. The ICO's right-to-object guidance explains a UK route and its limits; it does not create a universal result. If the policy is unclear, record “not stated” and ask the provider instead of completing the cell from another vendor's policy.

Complete the Training-Use Objection Packet

FieldReader entryEvidenceUnknown until response
Product and controllerCopy from live policyPolicy URL and dateWhether another entity controls a separate purpose
Exact processing purposeQuote or closely paraphrasePurpose sectionWhether the requested opt-out covers it
Stated legal basis and jurisdictionCopy only if statedPolicy sectionWhether the right applies to this user
Account controlExact toggle text or “not found”Screenshot and timestampServer-side effect beyond the label
Objection or erasure routeForm, email or account controlProvider instructionsIdentity check and exceptions
Requested scopeFuture use, specified data or erasureSent requestAccepted, refused, partial or pending
ConfirmationLeave blank before replyReference and responseRetained categories and purposes

The packet prevents a generic “opt me out” request from hiding several purposes. Supply only the account identifier and verification material the provider reasonably requests through its secure route; do not attach unrelated sensitive chat content.

Use a toggle only for the scope it names

If a training or improvement toggle exists, save its exact label and surrounding explanation before changing it. After the change, confirm only that the displayed state persisted. That is not proof of a backend outcome. If the provider says the setting applies only prospectively or excludes named purposes, copy that boundary into the packet. Installing or uninstalling an app or web shortcut is unrelated to the scope of this control.

AISoul provides a useful dated boundary check. Its public Privacy Policy, last updated June 28, 2026 and checked September 9, 2026, says messages may go to external AI providers to generate replies and that AISoul does not authorize public-model training where it can opt out. The page does not describe a user-facing training toggle or promise that every provider offers an opt-out. It directs location-dependent access, deletion, export and objection requests to its privacy contact. The supported conclusion is therefore “submit a purpose-specific request and await a written answer,” not “training is off” or “the policy proves prior data was reversed.” This public-page check is reproducible by comparing the AI Processing and Your Rights & Choices sections; it is not a backend test.

Send an objection or deletion request with minimum data

Use the provider’s form or published privacy contact. Identify the account, name the exact processing purpose being challenged and ask for a written statement of the result and any retained categories. Cite a legal right only after confirming the relevant jurisdiction and basis; do not combine UK GDPR and California language as if they were equivalent. Objection and erasure are distinct, so choose one or both deliberately and let the provider explain the route and verification required.

A concise request can state: “I am writing about account [identifier]. Your policy dated [date] describes [exact purpose]. Please tell me whether my data is used for that purpose, which control or request route applies to my account and jurisdiction, and what data or purposes remain if my request is accepted. Please provide the outcome and any exception in writing.” This is a factual enquiry template, not a claim that a particular right applies. Send it only through the published route. Do not include chat transcripts, government identity documents or payment details unless the provider’s secure verification process specifically requires appropriate material.

Record the response and unresolved uses

Record the date, reference, exact outcome and any named exceptions. Separate the provider’s acknowledgement from its substantive answer: an automated receipt proves delivery only. Use the response period stated by the provider or applicable authority rather than inventing a universal deadline. Silence is pending, not success. If the answer says a toggle was applied, ask which stated purposes it covers and from what point. If it says the request is refused or partial, record the cited basis and which categories remain. A policy revision after the request should be saved separately rather than overwriting the earlier version. Jurisdiction-specific regulator or legal guidance may be appropriate for a dispute, but this article cannot determine entitlement or outcome.

Questions about opting out of AI training

Is turning off chat history the same as opting out of training?

No. A history control describes visible or stored conversation behavior only to the scope stated by that provider. A training control or objection concerns a named processing purpose. Read both descriptions and ask the provider when the relationship is unclear; the absence of a toggle does not by itself determine whether a written objection is available or valid.

Can I object to AI training under UK GDPR?

The ICO right-to-object guidance explains the UK right and how the organisation’s purpose and legal basis affect it. That does not establish that a particular provider uses legitimate interests for training or that a specific user’s objection must succeed. Copy the provider’s own stated purpose and basis, then use the ICO’s current guidance or qualified advice for the reader’s circumstances. The ICO erasure guidance covers a separate right with its own limits.

Does deleting an account reverse training already completed?

Do not assume either outcome. Account deletion covers the categories and purposes stated by that provider, subject to its policy and applicable law. Whether prior training can be isolated or affected is a technical and legal question for the provider. Ask for a written explanation rather than asserting that weights are reversible or irreversible.

What information belongs in an opt-out request?

Include the account identifier, exact processing purpose, policy version and date, relevant jurisdiction and a request for a written outcome. Copy the legal basis only if the provider states it and the right is applicable. Provide the minimum verification material requested through the published secure route; no universal 30-day rule is asserted here.

Does AISoul promise that chats are never sent to external AI providers?

No. AISoul states it stores account, chat, usage, payment and technical data and uses external AI providers. It makes no E2EE or absolute-security claim. Chat deletion, account deletion, billing cancellation and a data-rights request remain separate actions unless the current policy explicitly combines them. Users should review the live AISoul Privacy Policy for the latest wording.

Rights evidence, jurisdiction limits and publisher disclosure

Evidence routes for reproducing this page's checks: AISoul Privacy Policy; AI chat-history deletion guide; personal-data minimisation guide.

The AISoul policy is dated June 28, 2026 and was checked September 9, 2026. The ICO sources define the UK objection and erasure boundaries; they do not guarantee eligibility or result in another jurisdiction. The linked internal pages cover history deletion and data minimisation as separate tasks. A vendor page proves only the vendor's published policy, not the actual effect of a control.

AISoul publishes these pages and has a commercial interest as an adults-only browser companion using one active fictional adult female character. All facts above are applied conservatively from the verified sources as of 2026-09-09. Users must verify live policy text for their account and jurisdiction; unknown elements require direct confirmation. No universal right is claimed, no reversal of completed training is promised, and no legal advice is given. The workflow remains a jurisdiction-aware request process only.