Deleting your account / starting from scratch
Deleting your Omniscio account and starting over: what is removed in the cloud straight away versus cleared on this computer at the next launch, exporting first, the only-owner block on shared workspaces, signing back in afterwards, and the smaller resets that clear one app's data instead.
On this page
Status: shipped. Settings → Accounts → Delete my account. Requires typing
DELETEto confirm. Only appears when you are signed in.
What it is
The self-service way to remove your Omniscio account and clear the copy of your data on this computer. It is the "I want to start over from nothing" action.
It does two separate things, and they happen at different times:
| What | When |
|---|---|
| Your Omniscio account in the cloud is deleted | Immediately |
| The data on this computer is cleared | The next time you open Omniscio |
The second step is staged rather than immediate because the local database is open and in use while the app is running — it cannot be deleted from underneath itself. So Omniscio writes a marker, and on the next launch it clears everything before your settings or the database are loaded, then starts you at a fresh setup.
Where to find it
Before you delete
- What you published is taken down first. Before your account is touched, Omniscio takes down every link you published and asks Forms to close your published forms and erase their answers and uploads from the Forms service. This runs first because it uses your sign-in, which the deletion removes. If any of it cannot be done (Forms is turned off, or the sharing service cannot be reached), nothing is deleted and the message names what is still online. Turn Forms on or fix the connection, then try again. Forms you never published stay on this computer until the local clear-out.
- Forms published from another computer are erased too. Right after your account is deleted, the Omniscio servers erase every form your account owns, wherever it was published: its public page comes down first, then its answers and uploaded files. If the Forms service cannot be reached at that moment, the servers retry every day until it is done; your account deletion itself is not held up.
- Export your data first if you want a copy. There is an Export your data link right in the delete card, which takes you to Settings → Backup & Restore. The export covers your local data; Team Chat messages live in the cloud and are not included.
- If you are the only owner of a shared workspace, deletion is blocked. Add another owner, or delete the workspace, then try again. There is a Manage your workspaces link in the same card. Contact support if you need a workspace reassigned.
Just want to clear one app's data?
Deleting your account is the whole-install option. Smaller, targeted resets exist:
- Supermail — Settings → Danger zone → Reset account data deletes the mail Omniscio has synced and re-syncs it from scratch, keeping your account, mailbox and settings.
- Signing out (Supermail Settings → Account → Sign out, or the account menu) returns you to the sign-in screen and deletes nothing. Your connected services (Google, Dropbox, OneDrive, Slack, Discord, Composio, Telegram, SMS, Zoom and Granola) are set aside for you and stop while nobody is signed in; sign back in as yourself and they come back without connecting again. If someone else signs in on that computer, they get none of them, and yours stay set aside for you until you sign back in. A Fathom key is the one exception: signing out forgets it.
Erase all local data (no screen for it yet)
The deepest local reset is erase all local data: it wipes the personal data Omniscio holds on this computer — the records behind your projects and sessions, the files and folders it keeps for you, and anything plugins have stored. It is irreversible: no backup is taken and nothing can be brought back afterwards, so export first (Settings → Backup & Restore).
Some of that data is held open while the app runs — the agents' browser profiles, the AI engines' folders, the logs, a few caches and the files your plugins saved. Those are removed the next time Omniscio starts, before anything else runs, and the erase result says restart to finish. Anything you add to those particular folders before you restart goes with them.
Your plugins stay installed. What each one saved in its own folder is removed, so a plugin starts empty; if a plugin had downloaded a program into that folder, it downloads it again the next time it needs it. Marketplace plugins you had opened for review are removed entirely.
It leaves your account, your Team Chat cloud data and the billing/usage ledger alone — but it is not purely local: it also takes down every share link you have published, pulling the files behind them so those public links stop working. Re-publishing the same link cannot bring them back.
Once the erase has confirmed that its database step returned, anything after it that could not be finished is reported instead of a clean wipe. The report names each part it knows about — archived messages, published links, files or folders still open in another program, saved settings, your coaching notes, an unencrypted copy of your Tasks board, or erased data that may stay readable in the database's working files — and asks you to run it again, which is safe to repeat. If the erase cannot confirm that its database step finished, it cannot tell what was already erased: it shows only the general "the wipe could not complete" message, and running it again is the next step.
There is no Settings screen for it yet. It runs only through Omniscio's CLI (the local command door, on by default), and only with your approval:
- Preview it. Ask an agent, or call
POST /privacy/erase-allwith{"confirm":"ERASE-ALL-LOCAL-DATA","dryRun":true}. That reports what would go, surface by surface, and deletes nothing. - Ask for the real wipe. The same call without
dryRun(the confirm word is still required) does not run immediately: it lands in your inbox as an approval card reading Erase ALL local personal data (irreversible, cannot be undone). - Approve it in the inbox. Only then does the wipe run.
Nothing can approve that card for you: the gate has no off switch in Settings, so an AI or a script cannot self-approve a wipe of your own data. Your account and the billing/usage ledger are not touched — deleting your account is the separate control above. Take your published links into account before you run it: they go dead.
How it behaves
What gets deleted
In the cloud, straight away: your sign-in account, your profile, your user-scoped records, and your Team Chat messages. You are also removed from any shared workspace.
On this computer, at the next launch: the whole local database and your settings file, together with the automatic backup copies Omniscio keeps of both on this computer. That covers every project, every session and its full conversation history, quick replies, recipes and automations, saved logins, notes, and any attachments or reports saved on disk. Your Tasks files are deleted too: the plain-text copy of your task list and the files Export JSON wrote, including the older copies kept in Omniscio's data folder before each account had its own.
Your screen recordings go too — including recordings you have moved to another folder (the recordings location in Settings → Screen Recorder). In a folder you chose yourself, Omniscio removes only the recordings it made there. Anything else you keep in that folder is left exactly as it is, and the folder itself is never deleted.
What is kept after deletion
A few records survive so billing, support and security keep working. None of them is your Team Chat or session content, but they are not nothing — here is what is kept:
- Spend and usage ledger — how much was spent and when, with the account link stripped:
the cost-ledger rows are anonymised (the account id is replaced with a shared placeholder), so
the amounts remain for reconciliation but no longer point at you
(
saas-api/src/billing/postgres-credit-store.ts). - Support and helpdesk conversations, and bug reports — the conversation, including what you
wrote, is kept for the operator; the identity stamp attached to it (your name, email and account
id) is replaced with a removed marker. This scrub is best-effort and does not rewrite anything
you typed into the message body (
firebase/functions/src/global-auth/user-erasure.ts). - A privileged-action audit trail — a security trail of admin actions is not removed when
you delete your account. It keeps your account id (never your name; an email address is stored
only as a scrambled digest) and, for some admin actions, the IP address used. The in-app trail
is on a two-year window (
firebase/functions/src/global-auth/audit.ts). - This computer's coding-spend ledger — how much each coding session cost and when, kept on
purpose so your all-time Spend view survives a reset. It carries no message content, but it
still holds your account id (
src/main/services/privacy/erasure-registry.ts).
Signing back in afterwards
Signing in again with the same Google (or GitHub) account creates a brand-new, empty account. It does not restore anything: the old account is gone and this computer has been cleared.
If you sign back in before restarting — in the same app session — you may still see your old projects, because the local clear-out has not run yet. It will run the next time you open Omniscio.
If you deleted your account with an older version
Older versions staged the clear-out but never actually ran it on a normal start, so the data on this computer may still be there. Because you may have kept using it since, it is never erased without asking. The first time you open a version with the fix, before anything else loads, Omniscio asks once: Erase your data on this computer?, with the date the account was deleted.
- Erase my data clears this computer exactly as described above.
- Keep my data (or closing the question) keeps everything and cancels the old request for good. You will not be asked again.
- If the question cannot be shown at all, nothing is erased and it is asked again next time.
Your cloud account was already deleted either way.
If something goes wrong
- "You are the last owner…" — expected. See Before you delete above.
- "Nothing was deleted. Omniscio stopped before deleting your account because these are still online: …": the take-down could not finish, so the account and your data are untouched. The message says what is still online and what to do.
- "Your published links and forms were taken down, but your account was not deleted: …": the take-down worked but the account deletion itself failed (for example the last-owner block). Your links and forms are already down; fix the reason given and try again.
- "…the data on this computer could not be cleared" — the cloud account was deleted,
but the local clear-out could not be staged (a permissions or disk problem). Your local
data is still there, and reinstalling Omniscio does not remove it — a reinstall or
upgrade deliberately keeps your history. To remove it by hand, uninstall Omniscio and
answer Yes to "Also delete Omniscio's data?" (that prompt defaults to No, and
a silent or automatic uninstall skips it entirely). macOS and Linux installs have no
removal prompt at all: delete the app's data folder yourself —
%APPDATA%\omniscioon Windows,~/Library/Application Support/omniscioon macOS,~/.config/omniscioon Linux. Data you relocated with theDATA_DIRsetting lives outside that folder and must be deleted by hand too. The other way out is simply to restart: the clear-out retries on each launch (next bullet). - You restarted and your old data is still there — the clear-out reports a problem in the app log rather than failing silently, and it retries on each launch. If another program (an antivirus scan, for example) was holding the database file, the clear-out stops and tries again next time rather than reporting done. Check Settings → Diagnostics.
Related
- Cross-Device Sync — if sync was on, other signed-in machines each clear themselves the same way when you sign out or delete there.
- Backup Mirror — backups made before deletion still contain your data until they age out. Deleting your account does not reach into an existing backup.
Last verified 2026-11-19