Isolated profiles

A profile is a browser session of its own, not a tab. It gets its own folder, and everything the engine keeps goes there: cookies, storage, cache and service workers.

Nothing crosses between two of those folders, because the engine never learns that the other one exists. A site you are logged into inside one profile sees nothing of the other.

• Its own folder

  Everything the engine keeps, from cookies and cache to service workers.

• Its own extensions

  Your enabled extensions load here only, next to a protection extension written for this profile.

• Its own proxy

  Address, credentials and exit country belong to the profile, not to the machine.

• Its own fingerprint

  It grows from the profile id.

• Its own open tabs

  After a crash the browser offers up to 30 of this profile's tabs back, and the offer stands for up to a week.

At creation you take a handful of decisions at once. There are five scenarios to choose from: privacy, e-commerce, social, ad accounts and freelance.

The app checks the opening address when you save, so a bad one fails in front of you rather than falling back to the scenario silently.

The list holds names, groups, proxies and login details for everything you own. It is never written over the old one, so a power cut in the middle of a save cannot leave you with half a list.

An unreadable file is not an empty one. The app copies a damaged list aside before anything can overwrite it.

1. 1

   Beside it, never over it

   The new content goes into a temporary file next to the real one, readable by your account only.

2. 2

   No space means a refusal

   No space left or a disk that went away aborts the whole write instead of passing for done.

3. 3

   All of it or none of it

   On disk you have either the whole old list or the whole new one, never half of either.

4. 4

   The access stays yours

   Only you can read this file after every write, and the new name survives a power cut.

Before it opens, a profile passes a sequence of gates, and each one is there because skipping it caused a specific harm. The ceiling on open profiles comes first, so nothing is spent on a profile that will not open.

1. 1

   Ceiling and seat

   A profile takes its seat in the same step that checks the limit, so eight parallel launches cannot all see the same zero.

2. 2

   Proxy or nothing

   A proxy that cannot be applied stops the launch, because going direct would show the site your real address.

3. 3

   Generation check

   A profile made by a newer fingerprint generation than this build understands refuses to open.

4. 4

   Busy lock

   The server marks the profile busy first, so a colleague cannot open the same account from another machine.

5. 5

   Session and exit

   The profile pulls a newer session from the sync folder if one is configured, and a failed IP change stops the launch.

6. 6

   Geo, extensions, protection

   The exit country sets the profile's clock and languages, and it gets a protection extension of its own.

A profile's fingerprint grows from its template, its id, its exit country and the engine version, and it is ready before the first page opens. ARMANOS Browser substitutes those values inside itself, so the first page script already sees the profile's machine.

The ceiling depends on your machine rather than being written down in advance. Three gigabytes go to the system and the app, the rest is divided one gigabyte per browser, and the result never leaves 4 and 32.

The limit is soft: it refuses to open one more and never closes what is already open. The app tells that refusal apart from a breakage, so bulk launches and schedules wait up to 30 minutes for a seat instead of failing the profile at once.

A deleted profile goes to the recycle bin. It drops out of every list and stops counting against your quota, and nothing on disk has been touched yet.

Delete permanently is the second button and it is meant literally. The profile's own browser closes first, because erasing under an open window is how erasing fails while the record disappears anyway.

If the browsing data on this disk could not be erased, you are told so.

• Browsing data

  Storage, cache, the name and credential caches, and the engine's own folder for this profile.

• Local choices

  Its extension selections, its schedules and its start page pass.

• Records that outlive it

  Its name in the launch notifications, its counters in the statistics and its daily action tallies.

• The cloud copy

  The sealed session bundle in the sync folder, so no second machine can bring the profile back.

The plan decides how many profiles you may hold at once. Extra profiles beyond a tier cost $2 each per month, and a team seat beyond the ones included costs $3 per month.

The server counts the real quota and the app shows it to you on screen. Launches go through it as well, not only creates, and offline you can still create for 24 hours after the last successful check.

An ordinary browser separates profiles for convenience, not for concealment. Cookies are kept apart and that is where it stops: the same screen, the same graphics card, the same fonts, the same address.

Incognito is forgetting rather than separation, a VPN moves the address and touches nothing else, and a virtual machine costs tens of gigabytes per identity. Here the storage, the exit, the claimed machine, the extensions and the daily limits all belong to one profile at once.