Your data
What Alltra keeps, where each piece of it lives, and exactly what disabling or deleting removes.
5 min read
Alltra holds a trading record, which is worth being precise about — both because it is yours and because closing an account should not be a guess about what happens next. This page says what is stored, what is only in this browser, and what each of the two removal actions actually does.
What is stored on your account
- Executions — the individual fills, and the raw broker responses they were read out of. These are the source; everything else is built from them.
- Trades — derived from those fills rather than stored as the broker described them, along with the legs linking each trade to the fills behind it.
- Journal entries — and their revision history, because an editor that autosaves needs one.
- Tags, tag categories and their assignments — the vocabulary and what it is attached to.
- Attachments — the screenshots and chart images you have put on trades and entries.
- Your portfolio ledger — transactions, budget categories and their limits.
- Trading accounts and their connections — including broker credentials, encrypted at rest.
- Your profile and appearance — name, photo, timezone, theme, accent and colour trio.
A broker connection is read-only and Alltra refuses a credential that is not — for MetaTrader that means the investor password and never the master one. The check runs before the credential is transmitted anywhere, so a credential that could move money is rejected rather than stored. Credentials are also stripped from every log line by name.
What is kept in this browser instead
- Your theme, accent and colour trio — three cookies, a year each, so the page can be the right colour before it paints.
- Demo Mode — per browser rather than per account — on at work is not on at home.
- The Dollar / Private choice — read on the server so a shared screen is masked from the first frame.
- The account selection and the date range — both remembered rather than carried in a link, and both tied to the domain so they apply across every app.
Signing out clears three of these: the session, the refresh token, and the account selection this browser was carrying. Your theme, Demo Mode and the Dollar/Private setting stay, because they are preferences about this browser rather than about you.
Getting your data out
There is no export control in the product today. The Plans page lists exporting among what a membership includes, and the machinery for a daily-report export exists behind the scenes, but nothing in the interface reaches it yet — so there is no button to press and this guide will not pretend otherwise. If you need a copy of your data before that lands, ask in the Discord.
Disabling your account
Disabling gives you 30 days to change your mind. Nothing is removed in that window — not a trade, not a journal entry, not an attachment. That retention is the entire meaning of the 30 days, and it is why disabling is offered as something distinct from deleting rather than as a softer word for it.
Every session is ended, including the one you are using, so you are signed out immediately afterwards. Disabling a second time keeps the original window rather than extending it, so a stray second submit cannot quietly buy you another month.
Deleting your account
Deleting is irreversible and there is no recovery window behind it. The request marks the account deleted and ends every session at once; the erasure itself is handed to a background job that runs shortly afterwards, because removing years of executions inside a single request is the kind of operation that can time out halfway and leave an account neither alive nor gone.
What that job removes, in order:
- Every trade, the legs behind it, the executions those legs point at, and the raw broker payloads they were read from
- Account adjustments and equity points
- Portfolio transactions, budget expenses, budget categories and their limits
- Journal entries and every revision of them
- Tag assignments, tags and tag categories
- Your strategies, and any documents saved against them
- Attachments, rollups, sessions, refresh tokens and your trading accounts
- Then the account record itself, which takes anything still attached to it
One thing survives, deliberately: the security record that a deletion was requested and authorised. Its link back to you is cleared when your account row goes, so what remains is that a deletion happened and was authorised — not who it was. That is the record you want to exist if anyone ever asks whether it was.
Both are guarded twice
- Type the word — DISABLE or DELETE, exactly. It is uppercased as you type, so the only way to fail it is to type something else.
- Enter your current password — until both are right, the confirm control stays locked.
- Hold it, do not click it — the final control completes on a press-and-hold. The typed word proves you meant this account; the hold proves you meant it now.
Neither window closes on success and neither shows a confirmation, because both actions end every session you have — there is no page left underneath for a message to land on. You are taken to sign-in instead, which is the only honest end state.
Did this article answer your question?
Security and sessions
Changing your password, signing out, and how a session actually ends.
ReadGuide last updated