Guide
Deleting your account
You can delete your Layerbase account yourself, from the dashboard, without contacting support. It cancels your billing and tears down every live cloud resource you own. This page explains exactly what happens, what gets erased, and what is kept.
How to delete
Open your cloud dashboard, go to Settings, and find the Danger Zone. Click Delete my account, then type your exact account email into the confirmation box. The button stays disabled until the email matches, so there is no way to delete by a single misclick.
The dialog also offers an optional, unchecked-by-default box: Also permanently erase all my backups. This cannot be restored by anyone, including Layerbase support. Leave it unchecked to keep the default behavior, where your backups are retained and support can restore your account. Check it only if you want your backups erased for good. When it is checked you must type a second confirmation word, ERASE, in addition to your email before the button enables. This double confirmation exists because erasing backups is immediate and cannot be undone by anyone.
There is no undo button in the dashboard. Confirming starts the teardown right away and signs you out.
What happens when you confirm
Billing stops first. Any active subscription is canceled immediately, so you are not charged again while the rest of the teardown runs. Cancellation here is not the graceful end-of-period cancel you get from the plan page: deleting your account revokes the subscription outright.
Then your cloud resources are purged across every server that holds your data. Running clients lose their connection at once, since the live databases are being torn down. The purge takes roughly 20 to 60 seconds depending on how many databases and backups you have. It runs on the server, so it finishes even if you close the tab.
What is erased
The purge removes every live resource tied to your account, on every active cloud server:
- - Every cloud database you own (containers, volumes, and routing).
- - Your API keys.
- - The DNS records for your databases.
- - Connected integration state, including preview-branch mappings and stored integration tokens.
What is kept (default)
If you leave the erase-backups box unchecked, self-serve deletion is a soft purge: the live side is torn down, but your backups are retained in full, along with a minimal cloud account record. Layerbase is built to never silently drop your data, so nothing in your backup history is deleted as part of deleting your account this way.
Because your backups and a minimal record are kept, an administrator can reinstate an account that was deleted by mistake, unless you have asked us for full erasure. If that happens, contact support and we can restore it. This is a manual recovery, not a self-serve one.
The same applies in reverse. If your account was already deleted this way and you now want the retained backups gone, email ops@layerbase.com and we will run the full erasure once we have verified the request. It is a verified, human-confirmed path rather than an automatic one, because erasing the last backup cannot be undone.
Asking us to erase everything
You can ask for full erasure at any point, whether or not you have already deleted your account. Email ops@layerbase.com from the address on the account. We verify that the request really comes from the account owner, then mark the account for erasure. From that moment every deletion path runs the full erasure, so there is no way for the account to be half-deleted by mistake afterwards.
Full erasure goes further than the backup erasure in the delete dialog. Alongside every backup on every server, we remove the records elsewhere in our systems that name you: support requests and any files attached to them, bug reports filed with your contact address, team invitations to and from you, your teams and plan records, marketing and conversion rows including the ad click identifiers attached to your signup, abuse-ledger entries, credit grants, app subscriptions, your avatar image, the cached network-registry lookup for the IP address you signed up from, your saved SSH keys, workspace access requests, your workspace GitHub connections and the repository access tokens issued through them, and the diagnostic data our internal logging and debugging tools hold about you.
Workspace records are deleted when the workspace is already gone. A workspace whose machine is still running out its paid term is scrubbed instead: its name, your SSH key, the agents you chose and their sign-in details, your workspace instructions, and the credentials it used to reach us are removed, and we keep only what we need to bill and shut down the machine when its term ends.
When the erasure finishes, we email a confirmation to the address on the account so you know it is done and on what date.
One record is kept: your email address, the date you asked, and the date we erased. We keep it because it is the only way we can show that your request was honoured and when, and so that a later request for the same address is not mistaken for a first one. GDPR Art 17(3)(e) allows this narrow retention for the establishment, exercise or defence of legal claims. It is deleted automatically 90 days after the erasure.
One more entry is kept, and it holds only your email address: a marketing suppression entry, whose sole purpose is to guarantee we never send you marketing again. Unlike the erasure record it has no expiry, because an opt-out we forget is not an opt-out. Unsubscribing creates the same entry, and it is removed only if you explicitly opt back in.
After a full erasure, signing in again with the same Google or GitHub account does not bring the old account back. It creates a brand new, empty account instead. This is deliberate: the erased account no longer exists, so there is nothing to restore it to.
Erasing your backups (optional)
If you check Also permanently erase all my backups and type the ERASE confirmation, deletion runs the full erase instead of the soft purge. Every backup is deleted immediately, including the most recent copy, along with the minimal ownership record we normally keep.
This is irreversible. Once your backups are erased, no one can restore your account, including Layerbase support. There is no grace period and no recovery window: the erase happens as soon as you confirm. Choose this only if you are certain you want your data gone for good, for example to exercise a right-to-erasure request. If you are unsure, leave the box unchecked and your backups stay restorable.
Delete an account vs cancel a plan
These are different actions. Canceling your plan keeps your account and databases and just drops you to Free-tier limits at the end of the paid period. Deleting your account removes the account and its databases entirely. If you only want to stop paying, cancel your plan instead of deleting.