Published policy
Closing access and deleting data are tracked separately.
This English policy is operational information, not legal advice. Immediate access denial protects the account first; erasure or anonymisation then follows the applicable workflow and lawful retention exceptions.
1. How to request closure
An authenticated developer may request closure through DELETE /v1/account. If you cannot authenticate, email [email protected] from the account address. We may request proportionate identity evidence and will never ask you to email a password or API key.
Account closure and a privacy erasure request are related but not identical. You may request access, correction, restriction, portability, objection, or erasure without closing the account where applicable.
2. Immediate account effect
When a valid closure request is accepted, AddBrains immediately marks the account unavailable, denies developer access, revokes every active API key, invalidates sessions and unused verification, bootstrap, recovery, and reset credentials, prevents an old link from reactivating the account, and stops queued credential messages where technically possible.
“Immediate” describes loss of access, not deletion of every legally retained record. Any unconsumed entitlement, refund, chargeback, or legal claim is handled through a separately tracked case.
3. Tracked erasure and anonymisation
Closure creates a durable erasure case with an identifier, request source, verification state, due and review state, affected data categories, exceptions, actions, reviewer, and completion timestamp. Personal data that is no longer needed and is not subject to an exception is erased or irreversibly anonymised without undue delay.
If a request is complex or an applicable rule permits more time, AddBrains notifies the requester and explains the reason rather than silently leaving the case open. The confirmation states what was erased, anonymised, or retained and why.
4. Records that may remain
AddBrains may retain only the minimum ledger, payment, tax, refund, chargeback, fraud, security, audit, and legal-claims evidence required by law or needed to establish, exercise, or defend rights. Access is restricted and ordinary product use remains impossible. Where feasible, retained records replace direct identifiers with internal or pseudonymous references.
Closure does not erase an immutable accounting entry, payment evidence, or security record when the law requires it to remain. See the Privacy Notice for the processing and retention map.
5. Prompts and outputs
AddBrains does not retain prompt or output content by default after fulfilment, so there should ordinarily be no stored prompt or output corpus to delete at closure. The erasure case still covers exceptional content deliberately supplied in a support case and personal data in usage or security metadata.
6. Confirmation and re-registration
AddBrains confirms that access is closed and later confirms erasure or anonymisation completion, or explains any continuing retention category. A new registration does not silently merge with a closed account or restore revoked credentials. Any lawful re-registration requires a new policy-evidence record.
Do not include a password, API key, payment-card data, or provider credential in a closure request.
7. Privacy rights and complaints
Contact [email protected] for a rights request or [email protected] for ordinary account support. We use proportionate identity verification and normally respond within one month, with any lawful extension explained. You may complain to the Commission for Personal Data Protection.
See Support and Privacy Requests for the safe request path.