Tej strony nie ma jeszcze w Twoim języku. Czytasz tekst angielski.
Offline
Your profiles live on this disk
- The profile directory on this computer
- Where cookies and logins are kept
- 24 hours from the last answer
- Work with the server out of reach
- Every 5 minutes
- How often the app asks while signed in
- Two profiles, no time limit, no card
- With no account at all
What sits on your computer
A profile is a whole browser directory: cookies, local storage, saved logins, history and the databases the engine writes. All of it is on this disk and none of it is uploaded by itself.
You can open that directory yourself: ~/Library/Application Support/@armanos/desktop on macOS, %APPDATA%\@armanos\desktop on Windows, ~/.config/@armanos/desktop on Linux.
Stays here
Cookies and site data, the profile's login pair, its one time code key, history, downloads and any fingerprint value you set by hand.
Mirrored while you are signed in
Settings only: name, folder, scenario, template, proxy, tags, notes and which extensions are switched on.
Derived, never stored
The fingerprint. It is computed at launch from the profile id, so the values themselves are never kept unless you set one by hand. The template and the generation they are computed from do travel.
A day without the server
While you are signed in the app asks your account a short question every five minutes. The day is counted from the last answer it received, not from the moment the cable came out.
A short drop in the middle of a working day therefore costs nothing at all. Past twenty four hours out of reach the app waits for one check to go through before it opens anything new.
| What you do | Within the day | After the day ends |
|---|---|---|
| Opening a profile | Opens as usual | The button dims and names the reason |
| Creating or editing a profile | Saved here, sent later | Waits for one answer |
| Flows and warm-up | Run as usual | A run ends before it opens a window |
| A schedule that comes due | Fires | Passed over and named, never stored up |
| Checking a proxy | Goes out through the proxy | The same, and never through us |
| Browsers already open | Keep working | Keep working until you close them |
A clock wound backwards ends the day sooner
An edit made offline waits by the field
Rename a profile with no connection, and the new name is on this disk at once. The app marks that field as not sent yet and carries on.
Only marked fields travel afterwards. A field a colleague changed on another machine still comes down, because your stale copy of it was never waiting to be sent.
The mark is set before the request
A sync running at that same moment cannot paint over what you just typed.
Waiting fields leave on their own
They go up at the next start of the app, and with your next edit of that profile.
A refusal is not silence
A change the account did not accept says so on screen, and that profile counts as out of step until it goes through.
A profile made offline keeps its identity
A fingerprint here is derived from the profile id, so a new id would mean the same accounts arriving from a different machine. A profile born on this disk goes up to your account under the id it was born with.
Signing in never wipes what only this machine holds. Profiles made while you were signed out are kept, sent to your account unless another account has been on this computer, and counted on screen if sending did not work.
Two accounts on one computer
The app remembers which account these profiles were last checked against. Sign in with a different one and the first account's rows move to the recycle bin, while their cookies and saved logins stay on the disk.
Signing back in with the first account brings the rows back. Nothing travels the other way once this machine has been seen under another account: profiles you made for yourself are held back rather than pushed into an employer's account, and a held profile stays on this computer for good, because nothing sends it up later.
Signed out is a working state
With no account the app opens and runs on the free floor of two profiles, with no time limit and no card. There is no day to count here, because there is nothing to ask.
What you give up is what an account provides: settings mirrored to a second machine, the lock that keeps two colleagues off one profile, and folders shared with a team.
Who else can read these files
The app's own files that hold a secret are written so that only their owner can read them. That is what matters when a copy leaves the folder: a backup, a synced cloud directory, an archive sent to a colleague.
On macOS and Linux those permissions are the protection. On Windows they are decided by access lists the app does not reach, and what stands there is your user account: another user cannot enter your profile folder without administrator rights.
What this does not do
- It is not an offline licence. The day runs from the last answer the server gave, and once the server cannot be reached past that day, nothing new opens until a check goes through.
- A profile created with no connection is not promised a place in your account. The quota is the server's to count, and it can refuse on return: the profile stays here and is counted on screen.
- Owner only permissions are real on macOS and Linux. On Windows they change nothing, and the protection there is your user account, not the file.
- Local is not a backup. A dead disk takes the profiles with it unless their sessions went to a folder of yours.
How to check
Every claim above has a file and a stand you can run.
- The day runs from the last answer, and a clock wound back cuts it short
- apps/desktop/src/lib/license.js · apps/desktop/test/session-restore.js
- Signing in keeps what only this machine holds, and a profile keeps its id
- apps/desktop/src/main/main.js · apps/desktop/test/sync-preserves-local.js
- An edit that did not reach the account is kept and sent again
- apps/desktop/src/lib/profiles.js · apps/desktop/test/отметка-не-отправлено-по-полям.js
- A second account moves rows and leaves the data
- apps/desktop/src/lib/accountSwitch.js · apps/desktop/test/смена-аккаунта-не-стирает-сессии.js
- A file holding a secret is written for its owner alone
- apps/desktop/src/lib/secureFile.js · apps/desktop/test/secrets-on-disk.js
Questions
- Can I work with the network unplugged?
- For a day from the last answer your account gave: profiles open, flows run and edits are saved here. Past that it waits for one check.
- Does closing the app reset that day?
- No. It is written down and read back at the next start, so the app opens as you left it.
- What happens if I move the machine clock back?
- The last check then sits in the future, and that counts as no check at all. The day ends sooner, not later.
- Do my cookies ever reach your server?
- No. Only the settings of a profile are mirrored, and that record has no place for cookies, a login pair or a one time code key.
- I signed in with another account and my profiles vanished.
- Their rows are in the recycle bin, because they belong to the account you signed out of. The cookies and logins are untouched, and signing back in returns them.
See it with the network unplugged
Install ARMANOS and pull the cable out.