Account lifecycle
What deletion, the org-wide data wipe, restore, and purge actually do.
Last verified: 31 July 2026
There are several destructive actions, and they do different things on different timelines. Read this before using any of them.
Deleting your account
Deleting your account does not delete anything straight away. It freezes the account, cancels billing, and schedules permanent deletion 30 days later.
The 30 days are a deliberate recovery window, not a processing delay.
- Immediately. Access is cut. You are locked out, as are your paired devices and any connected MCP clients. Billing is cancelled. Your indexed content still exists, untouched.
- During the 30 days. Your content is still there and the deletion can be undone by resubscribing.
- At day 30. The purge runs and permanently deletes your documents, text chunks, embeddings, permissions, conversations, messages, search history, and text extracted from your images. That list is exhaustive: nothing derived from your content survives it. This cannot be undone.
Nothing is recoverable after the purge. If you are unsure, resubscribe inside the 30 days rather than waiting to see what happens.
The active-subscription guard
An account that reaches its deletion deadline while holding an active subscription is restored rather than deleted. A subscription that is live at day 30 is treated as a signal that you did not mean to leave, and the purge does not run.
What survives the purge
One thing, and only one: a content-free record that an account existed and was deleted. It holds no documents, no messages, and no search history. The email address on it is erased after 90 days.
Wiping your data without deleting the account
A separate action wipes indexed content across the organisation while keeping the account itself: the organisation, your user, your subscription, and your sign-in account all survive. What goes is the indexed content.
This is organisation-wide, not personal, and it is restricted to an organisation admin. It removes indexed content for the whole organisation, not just for the person clicking it. Today an organisation is effectively a single user, but that will not stay true as team support lands.
Use this when you want to clear an index and start over – after connecting the wrong account, or before re-indexing with a narrower selection – without touching your subscription.
Disconnecting a single connector
Disconnecting one connector is the fastest and most surgical option, and unlike account deletion it takes effect immediately.
Connections → the source → Disconnect immediately and permanently deletes that connector's sources, documents, text chunks, embeddings, and permissions. There is no recovery window and no undo.
Your account survives, and every other connector on it is untouched – disconnecting Jira does not affect your GitHub content.
| Disconnect a connector | Delete your account | |
|---|---|---|
| Timing | Immediate | Freeze now, purge at day 30 |
| Scope | That connector's content | Everything |
| Recovery window | None | 30 days, by resubscribing |
| Account survives | Yes | No, after the purge |
| Billing | Unaffected | Cancelled immediately |
Cancellation is not deletion
Cancelling your subscription ends billing and locks features at period end. It does not freeze, schedule, or purge anything by itself. See plans and billing.
What the deletion paths do not remove
Operational and infrastructure records such as logs and billing records are kept, for operational and legal reasons. They contain no document content.
Everything derived from your content is removed by the paths above, including text extracted from your images.
Data export
Self-service data export is not implemented. The settings entry is a stub. There is no button that hands you your indexed documents, conversations, and settings today.
If you need your data out before deleting, email team@remly.it first and wait for a reply. Do not delete and then ask – deletion cuts your access immediately, even though your content survives for 30 days.
Related
- Plans and billing
- Privacy and security
- Integrations – disconnecting a single source