Halaman ini belum tersedia dalam bahasa Anda. Anda membaca teks bahasa Inggris.
Glossary
Data residency
Data residency is the question of which country the machines physically holding your data stand in.
What residency means
Residency is a question about location and nothing else: the disk holding a record sits in a building, and that building sits in a country.
It is asked most often in a contract, where one side wants to know which legal system can reach the records without asking anyone.
Three neighbouring questions
The three get used as though they meant one thing, and a contract falls apart at exactly the seam between them.
Residency
Where the data physically sits, building and country included.
Sovereignty
Whose law can reach it, which is not always the law of the country it sits in.
Localisation
A rule requiring certain data to stay inside a border rather than merely start there.
Where the data lives in this trade
Three places, and the one people ask about first turns out to be the smallest of the three by a wide margin.
Your own machine
The profile directory holds cookies, storage and the browser databases, written where you are sitting.
A folder you chose
The synchronised folder a session archive travels through, kept wherever its provider keeps it.
Our server
The account, the plan, your machines, the workspace log and profile settings mirrored while you are signed in.
The largest part stays with you
The heavy data belongs to the browser itself, and it is written into the app data directory on the machine in front of you.
That directory is not fixed either: a path named on launch wins over the default, so the whole working set can live on a disk you picked and carry with you.
What the server is told
While you are signed in, profile settings are mirrored so a second machine and your teammates see one list: the profile identifier, name, group, scenario, template and generation, proxy, tags and notes.
What is absent from that list matters more than what is on it. Cookies never leave, nor the sign-in pair saved beside a profile, nor a byte of the databases the browser keeps.
Where a session archive goes
The session of a profile leaves the machine by one road only: a folder you point the app at yourself, and the archive leaves encrypted.
Whatever service keeps that folder decides the residency of that copy, and the passphrase that opens it stays behind on your own machine. Beside the archive lies an open marker with the time, the size and the machine name.
What this does not do
- It does not let you pick a country for the server. There is no region setting, and mirrored settings live wherever the service runs.
- It does not manage the folder for you. The service behind it decides where its copy sits and how long a deleted file lingers there.
- It does not tell you where a proxy carries your traffic. An address registered in one country may leave through machines in another.
- It does not reach the copy a site keeps. Residency here covers your side of the visit, and the other side keeps its own records.
Check it
Each line here is a file you can open, and most carry a stand that fails when the claim stops being true.
- A session archive goes only to the folder you point at, and the passphrase does not travel with it
- apps/desktop/src/lib/sessionSync.js
- No call that mirrors profile settings carries the sign-in pair
- apps/desktop/test/login-stays-local.js
- A data directory named at launch wins over the default
- apps/desktop/test/data-dir-explicit.js
- An exported script leaves its values behind, and a launch entry holds a name and a time
- apps/desktop/test/выгрузка-без-секретов.js · apps/server/src/profiles/profiles.service.ts
Questions
- Do my cookies ever reach your server?
- No. They live in the profile directory on the machine you are sitting at, and no call carries them away from it.
- Where does the synchronised copy live?
- Wherever the folder you chose lives. The app writes two files per profile into it: an encrypted archive, and an open marker carrying the time, the size and the machine name.
- Can I keep everything on an external disk?
- Yes. A data directory named at launch wins over the app default, and everything the browser writes then goes there.
- Is the fingerprint stored in a database somewhere?
- No. It is derived at launch from the template, the profile identifier and the generation, and no column anywhere holds the result.
- What does the server learn about a launch?
- That a profile was started, by whom and when. What was opened inside the window is not recorded at all.
See what is stored and where
The security page names the directory, the folder and the fields, with a file behind every line.