Deze pagina is nog niet in uw taal. U leest de Engelse tekst.
Knowledge base
Clear the cookies of a profile
One profile
Clear cookies… stands in the profile menu after Import cookies. Its window says what will happen before anything is deleted: sign-ins to sites will be lost, and site data stays.
- 1
Open the profile menu
The menu of the row in the list.
- 2
Choose Clear cookies…
Right after Import cookies.
- 3
Choose how
Export and clear saves the cookies to a file first; Clear deletes them at once.
What stays
Site data such as Local Storage and IndexedDB stays. A site that keeps its own number there can still recognise the profile, and the window says so.
Clearing cannot be undone. Export and clear deletes only after the file is written.
Open or closed
An open profile is cleared by its own browser, and on ARMANOS Browser the app then checks that no cookie is left. A closed ARMANOS Browser profile loses its cookie database on disk, and nothing else of the profile on disk is touched.
A profile that is starting right now is not cleared: the message asks you to wait until it opens. Cookies waiting for a first launch are deleted too, and the message counts them.
A profile browser that outlived ARMANOS (for example, the app was force quit) is an open profile too: it clears its own cookies, and ARMANOS leaves its files alone. Until ARMANOS has connected to such a browser, which takes the first few seconds after the app starts, clearing refuses and asks you to wait a few seconds.
Many profiles
Select profiles and press Clear cookies in the bar above the list. The window counts the profiles and has no export, since a save window per profile would be one too many.
A profile closed by a password is named and left as it was.
Export straight from the profile window
Inside an open profile, Cmd+Shift+K on a Mac or Ctrl+Shift+K elsewhere exports its cookies without going back to the app. On ARMANOS Browser the same export is the cookie icon Export profile cookies in the extensions menu of the browser.
On the built in engine the Profile menu of the app carries Export profile cookies with the same keys. The file is offered in Downloads under the profile name and the time, and a message says how many cookies were saved.
What this does not do
- It does not clear site data: Local Storage and IndexedDB stay.
- It does not export from the bar: to keep a file, clear one profile at a time with Export and clear.
- In the sync folder the cookies go only at the next upload of the profile.
Where this is decided
The claims that carry the most weight, with the stand that checks each of them.
- Only the cookie database is deleted, site data stays, a starting profile is refused and waiting cookies go too
- apps/desktop/test/очистка-куки-дороги.js
- On a live open and a live closed profile the page sees no cookies afterwards and its Local Storage is still there
- apps/desktop/test/очистка-куки-живьём.js
- A browser that outlived a killed app clears its own cookies: the cookie database under it stays the same file, and after a new launch the site sees the cookies set after clearing and none of the cleared ones
- apps/desktop/test/очистка-куки-подхваченного-живьём.js
- The export from the profile window writes the file with the owner’s rights and opens its windows in front of the browser
- apps/desktop/test/куки-из-окна-профиля.js
Questions
- The site still knows me after clearing. Why?
- It may keep its own number in site data, which clearing leaves in place, or read the fingerprint and the address of the profile.
- The browser kept some cookies. What now?
- The message says how many were left. Close the profile and clear again: a closed profile loses its whole cookie database.
Try it on your own profiles
The free plan gives two profiles, with no time limit and no card.