Know
Can the person find the actual departure procedure before committing?
POWER & INSTITUTIONS
The Right to Exit
If leaving exists only in the policy while the data, work, identity, or continuity cannot move, the door may be decorative.
QUICK ANSWER
In one sentence
A realism-first governance test for portability, switching, departure, continuity, legitimate obligations, and retaliation.
THE CONTROLLING CLAIM
A DOOR PAINTED ON THE WALL IS NOT AN EXIT.
Consent becomes suspect when departure exists only as a sentence in a policy while the data cannot move, the account cannot close, the replacement cannot receive the record, or the price of leaving has been engineered to be ruinous. Exit is not a magic eraser. It is a governance question: can a person or organization end one relationship and continue life without surrendering everything that made departure meaningful?
TRUTH BOUNDARY
Rights to portability, termination, deletion, interoperability, or switching depend on jurisdiction, contract, service type, and the data involved. This article does not provide legal advice and does not claim a universal legal right to costless departure. It states a Ministry governance position and uses specific public frameworks as examples.
01 — EXIT AND VOICE ARE DIFFERENT LEVERS
Leaving and speaking are not interchangeable.
Albert Hirschman's exit-and-voice framework remains useful because it refuses a false choice. Sometimes dissatisfaction is answered by leaving. Sometimes it is answered by speaking from inside and attempting repair. Sometimes both options exist and affect each other. A system with no usable voice can make Exit the only remaining signal. A system with no usable Exit can turn voice into pleading before a locked door.
The Ministry does not treat Exit as the only form of agency. It treats a usable Exit as one test of whether voluntary participation deserves that adjective.
02 — PORTABILITY IS NOT THE WHOLE DOOR
Moving a file is not the same as moving a life.
Article 20 of the EU General Data Protection Regulation gives qualifying data subjects a right to receive certain personal data they provided in a structured, commonly used, machine-readable format and to transmit those data to another controller without hindrance, subject to the article's conditions. That is a concrete portability mechanism. It is not a universal promise that every record, derived model, legal obligation, or proprietary system must follow the person.
The question remains material: is the exported record usable by anything on the other side? A technically valid export can still be a dead artifact if no destination understands it.
03 — SWITCHING COSTS CAN BECOME ARCHITECTURE
Lock-in is often built from many small frictions.
The EU Data Act's rules for data-processing services explicitly address switching, exportable data, contractual terms, technical support, interoperability, and continuity. Its recitals describe how unnecessarily high switching charges and other obstacles can inhibit switching and contribute to lock-in. The Regulation also recognizes that interoperability is technically complex and not a simple yes-or-no property.
That nuance matters. A serious Exit standard cannot demand the impossible. It can demand that obstacles be named, obligations be bounded, formats be disclosed where required, and transitions be designed rather than treated as betrayal.
04 — WHAT SURVIVES DEPARTURE?
Exit is not amnesia.
Leaving a provider, organization, community, contract, or project does not automatically erase lawful debt, custody responsibilities, professional duties, prior material conduct, retention duties, or records that another party is legitimately required to keep. A useful Exit framework therefore asks two questions at once: what must become portable or terminable, and what legitimately remains?
EXIT WITHOUT A RECORD CAN BECOME ERASURE.
The point is not to make departure consequence-free. The point is to make consequences intelligible, reviewable, and tied to legitimate obligations rather than retaliation for leaving.
05 — THE EXIT TEST
Export
Can they retrieve what reasonably belongs with them in a usable format?
Receive
Can another provider or process use that export?
Retain
What remains stored after departure, for how long, and under what rule?
Transition
Can critical functions continue while the move is happening?
Cost
Which costs are ordinary obligations and which exist mainly to punish departure?
Alternative
Is there a meaningful alternative or only another door into the same dependency?
Appeal
Can a refusal to close, export, or transfer be reviewed?
Retaliation
Does departure trigger unrelated punishment?
Survivors
Which legitimate obligations remain after Exit?
COMPETING INTERPRETATIONS
Keep the argument wide enough to survive disagreement.
- Exit is not always the best remedy. Voice, repair, appeal, and long-term commitment can sometimes solve problems that departure cannot.
- Some switching friction reflects real technical complexity, security obligations, migration work, or contractual commitments rather than illegitimate lock-in.
- A right to leave one relationship does not imply a right to erase every record or obligation connected with it.
UNKNOWNS
What this article does not settle.
- How far portability should extend to inferred data, derived models, or jointly created records remains contested and jurisdiction-specific.
- The practical cost that makes Exit unusable varies by context; no single numerical threshold settles the question.
- A meaningful alternative may not exist in concentrated markets even where formal termination is easy.
SOURCE TRAIL
Follow the record.
RELATED READING
CORRECTION RECEIPT
Publication status: published 2026-08-30. No post-publication correction is recorded in this release. A publication-status statement is not itself a correction. If a consequential factual claim changes, the Correction Ledger must preserve what changed and why.
A DOOR PAINTED ON THE WALL IS NOT AN EXIT.