Questa pagina non è ancora nella sua lingua. Sta leggendo il testo in inglese.
Glossary
GDPR
GDPR is the European regulation that sets how personal data about a person may be collected, kept and erased.
What the regulation covers
Personal data is anything that points back to a living person: a name, an address, an identifier a device carries, or a record of something that person did.
The text is about handling rather than about storage alone, so it reaches collection, transfer and deletion in the same breath.
The words it uses
Four words carry most of the text, and every argument about it eventually comes back to one of them.
Personal data
Anything that identifies a person, directly or through something joined to it later.
Controller
Whoever decides why data is handled and by what means. The duties land here first.
Processor
Whoever handles it for the controller, under instructions rather than on their own account.
Lawful basis
The reason handling is allowed at all. Consent is one of six named in the text and not the default one.
What a person may ask for
The rights belong to the person the data is about, and they are exercised against whoever decided to collect it.
Access
A copy of what is held about them, and an account of where it came from.
Correction
A wrong record put right rather than argued about across a support queue.
Erasure
Deletion, in the cases where nothing else obliges the holder to keep the record.
Portability
The same data in a form a machine can read, so it can be carried somewhere else.
Objection
A stop on certain kinds of handling, including profiling built out of the records.
Where your account data actually sits
For this app the answer fits in a short table, and the middle column is the heavy one.
The things people worry about most are the things that never move off the machine at all. Of the sign-in pair the system seals the password only, and when it cannot seal a value the app writes it as it is rather than calling it sealed.
| What | On your machine | On the server |
|---|---|---|
| Cookies, storage and the browser databases | In the profile directory | Never sent |
| The sign-in pair saved with a profile | Beside the profile, with the password sealed | No column exists for it |
| Profile settings: name, group, scenario, template, proxy, tags, notes | Yes | Mirrored while you are signed in |
| The fingerprint a profile presents | Derived at launch | Stored nowhere |
| The account itself | The signed-in session | Your email, and the password as a hash |
Deleting has two steps
Deleting a profile closes its browser first and moves the row to the recycle bin. Nothing on the disk is erased at that point: the directory, the cookies and the saved sign-ins are all still there.
Deleting for good from the bin is the step that erases. It takes the browser directory, the extensions, the schedules, the counters, the launch entries that carried the name and the encrypted archive in your sync folder.
The bin does not empty itself on a timer. A profile waits there until you empty it, and until then its cookies and its saved sign-ins are still on the machine.
What the workspace log keeps
While you are signed in, actions are written to a log your workspace can read: a profile created, started, stopped or renamed, a proxy changed, a member removed.
An entry holds the action, the time, who did it and the profile it names. A sign-in and a newly registered machine also record the address and the country they came from. What happened inside the browser window is not in it.
What this does not do
- This page is not legal advice and does not claim compliance with anything. It says what is stored and where, and the conclusions about your own duties stay yours.
- It does not erase the workspace log along with a profile. The log exists so a team can see who did what, and an entry outlives the row it names.
- It does not remove an account from a screen. Profiles go to the recycle bin one by one or a whole selection at once, and the account itself is not among the things the app takes away.
- It does not reach what a site keeps on its own side. A page you opened has its own records of the visit, and nothing here touches them.
Check it
Each line here is a file you can open and, where a claim can be measured, a stand that fails when it stops being true.
- No call that mirrors settings carries the sign-in pair, and the table has no column for it
- apps/desktop/test/login-stays-local.js · apps/server/prisma/schema.prisma
- Every action the workspace log can record is named in one list
- apps/server/src/common/audit/audit.service.ts
- Deleting for good takes the counters and the launch entries, and clears the folder too
- apps/desktop/test/delete-leaves-nothing.js · apps/desktop/test/purge-clears-cloud.js
- A report for support carries no secret, and a shared script leaves its values behind
- apps/desktop/test/problem-report.js · apps/desktop/test/выгрузка-без-секретов.js
Questions
- Does the app send analytics anywhere?
- There is none in the app and none on this site: no tag manager, no session recorder, no foreign script. The free tools here measure inside your browser and make no request.
- Can I take my data out?
- Profile settings export to a file you choose. The app asks first whether the saved secrets travel with them or stay behind, and the file records which answer you gave.
- What leaves my machine when I ask for help?
- A report assembled locally, and only once you press send. Anything that looks like a secret is replaced by a mark, and the field name stays so you can see it was there.
- Do cookies from my profiles live anywhere else?
- Only where you send them yourself. They sit in the profile directory, and a session copy travels only through a folder you pointed the app at.
- Who in a team can see a profile?
- The members of that workspace, according to the role each of them was given. The role decides what a person may open and what they may change.
See what is stored and where
The security page walks the same ground in detail, with the file behind every line of it.