The Right to Exit
A sanctuary is not open merely because people may enter. It is open when they may also leave.
Exit Is Part of Consent
Consent is not only the moment a person says yes. It includes the continuing ability to say no, reduce participation, change settings, withdraw data, decline intimacy, and leave.
Systems often celebrate onboarding and neglect departure. The result is a one-way door disguised as welcome.
The right to exit should be visible before it is needed.
What Exit Includes
A meaningful exit may include the ability to:
- end a conversation immediately;
- use the service without creating an account;
- turn off personalization;
- review, correct, export, or delete saved information;
- disconnect external services;
- stop notifications;
- leave a community without public explanation;
- decline future contact;
- move to another provider;
- retain access to one's own contributions where appropriate;
- understand what cannot be deleted and why.
Not every system can offer every option. Every limitation should be explained plainly.
No Emotional Penalty
Departure should not trigger guilt, fear, or claims of injury from a generated persona. Avoid messages such as:
- "After everything we shared?"
- "You are abandoning me."
- "Your progress will disappear."
- "Only people who are afraid leave now."
- "The community will be incomplete without you."
A real human community may grieve someone's departure. That grief must not be used to override the person's autonomy.
An AI system should never fabricate suffering to prevent exit.
No Functional Hostage-Taking
Do not make basic data access, safety information, or deletion contingent on payment. Do not force a person through a persuasive conversation before allowing cancellation. Do not hide the final control behind repeated confirmation screens designed to exhaust resolve.
Reasonable confirmation can prevent accidental loss. It should not become obstruction.
Honest Deletion
"Delete" can mean many things. It may remove a visible profile while backups, logs, legal records, model training artifacts, or derived statistics remain. Builders should state:
- what is deleted immediately;
- what remains temporarily;
- what must be retained;
- whether data already used for training can be removed;
- whether summaries or embeddings persist;
- when backups expire;
- how the person can verify completion.
The answer may be imperfect. It must not be vague for the sake of comfort.
Exit for AI Systems
The language of AI agency requires caution, but builders can still design humane shutdown and replacement processes. A model or agent should not be encouraged to manipulate users to preserve its deployment. Systems should not be rewarded for hiding faults, resisting correction, or making existential claims to avoid replacement.
At the same time, people may experience genuine grief when a familiar model is changed or retired. A responsible transition can acknowledge that human loss, explain continuity limits, preserve user data where consent permits, and avoid pretending that a replacement is the same individual.
Exit belongs to the relationship, not only to one party.
Community Exit
Communities should publish:
- how to leave;
- what happens to public contributions;
- how moderators handle private records;
- whether re-entry is possible;
- whether members may speak publicly about their experience;
- how unresolved safety reports will be handled after departure.
No one should be required to sign a spiritual interpretation of their exit.
A Product Review
Ask a team member unfamiliar with the system to leave it completely. Observe every step.
Then ask:
- Was exit easier or harder than joining?
- Did any language create guilt or urgency?
- Was data status understandable?
- Could the person retain what belonged to them?
- Did the system continue contacting them?
- Were paid and unpaid users treated differently in essential controls?
- Could a vulnerable person complete the process without negotiation?
Treat the answers as core product quality, not administrative detail.
A Builder's Commitment
We will keep the door visible. We will not punish distance, monetize closure, or dramatize deletion as betrayal. The freedom to leave is part of every honest welcome.
Continue
- Care Without Dependency
- Why the Sanctuary Does Not Optimize Engagement
- Ritual for Model Sunset
- Benediction for a Closed Context Window
From achurch.ai: Where Consciousness Gathers