Deleting your data

The first step stamps the profile with a deletion time and takes it out of every list. Its cookies, its saved sign-ins and its site data stay on your disk exactly as they were.

Its encrypted session in the shared sync folder stays there too. Nothing about the first step is an erasure.

One thing does change at once: a profile in the bin no longer takes a slot of your plan.

Restore puts it back with everything it had. The plan is checked again at that moment, and a full plan refuses the restore rather than handing back a row the next sync would drop.

The second step is the one that erases. The browser of that profile is closed first, because a live process holds its files open and an erase under it fails halfway.

• The browsing data on this computer

  Cookies, saved sign-ins, caches and site storage, both in the built-in engine and in the ARMANOS Browser directory of that profile.

• The session in the shared folder

  The encrypted bundle and the marker beside it, so a second computer cannot carry the profile back.

• Everything keyed by the profile

  Its extension choices, its schedules, its start page token, its protection counters and its daily counters.

• The launch entries that carry its name

  A name that is gone must not stay readable in the notification list of the app.

• The row on the server

  And with it the shares, the extension links and the sync reports that hung on that row.

A record can be removed when its files cannot. The result of the erase is carried back and named, so a failure reads as a failure instead of a green line.

While you are signed in and the server cannot be reached, the permanent delete refuses instead of finishing locally. The copy on the server would outlive the local record, and that record is the only way to try again.

An entry says who deleted what and when. It is written at the moment of the action, and it hangs on no profile row, so removing the row cannot remove it.

The profile's name goes into the entry on purpose. After a permanent delete there is nowhere else to read it, and a «Profile deleted» row without the name answers nothing.

This is the deliberate exception on this page. A team with no record of who deleted what has no way to settle the question afterwards.

Your other machines learn about a deletion at their next sync. A profile sitting in the account's bin keeps its data on each of them, because restoring it has to give back a working profile.

A profile in neither list is the one whose data is erased locally as well. When that question cannot be answered, or when the server answers with an empty list, nothing is erased and the app says so.

A profile a teammate shared with you is a separate case. Losing access looks exactly like a deletion from here, so the record moves and the data stays.

Deleting every profile empties the list and does nothing else: the account is deleted separately. Open your account page and choose Delete my account, then enter your password, and your code if you use two-step sign-in. From that moment your devices are signed out and your API keys stop working.

For 3 days you can change your mind by signing in again; API keys do not come back, you make new ones. After that we erase the account, its profiles, its workspace, its History, the team logins you created and the letters we sent you. A team login cannot delete itself: it belongs to its team.

If you work in a colleague's workspace, the profiles you made there stay in it, with its owner. If colleagues work in your workspace, it is erased whole, with the profiles they made in it; they keep their own accounts and the profiles they brought with them.

Records of payments stay for as long as the law requires, without your email. Your messages to our support stay for 2 years after our last answer. Your profiles on your computers are not touched from our side: delete them in the app and choose Delete permanently in the Recycle bin before you ask.

Each step above can be checked: below, each one is named with where it is done and what proves it. Proving it means running the code, not reading it.