DRAFT — under the owner's review, not legal advice. Placeholders in ⟨angle brackets⟩ are decisions the owner has not taken yet.

Privacy Policy

Last updated 2026-09-10. Controller: ⟨the operator — the owner names the person or entity⟩, reachable at support@vflin-antik.com.

1. The principle

The cloud is built so that the server cannot read what it stores for you. Your profiles leave your computer as signed, encrypted blobs; the keys stay on your devices; your password is never sent — a check value derived from it on your device is.

measuredThe table below is not a promise: it is what was read back from the database of a running server after accounts were created from this site and from the desktop app.

2. What the server holds

in the clear	sealed (encrypted; the server cannot read it)	never received
your email address whether two-step verification is on a 16-byte login salt the ids and names of your signed-in devices, when each was added and last seen for each synced profile: its id, the ciphertext's size and hash, a version vector, the core version your plan and the payment provider's event ids for it team memberships and the public keys of members	the check value derived from your password (stored as an Argon2id hash of it) the two-step verification seed every profile's contents — cookies, storage, extensions, settings the keyring that opens them	your password your profiles' passphrase and recovery key the pages you visit, the proxies you use, the accounts you keep in profiles

3. Server logs and request data

The server logs each request's method, path, status and duration, and applies rate limits by IP address; when the site is served through Cloudflare, Cloudflare passes the visitor's IP to the server for that purpose and applies its own privacy terms to the traffic it handles. ⟨Log retention period — the owner decides; until then: logs are kept as the server's rotation keeps them and are not exported.⟩

4. This website

The site sets no tracking cookies and loads no third-party scripts, fonts or analytics; its Content Security Policy allows only its own origin. The cabinet keeps your sign-in token in your browser's session storage (or local storage if you tick "stay signed in") and a random device id in local storage — nothing else.

5. Payments

Paid plans are bought through a cryptocurrency payment provider on its own hosted page; we receive the provider's confirmation and its reference for the payment, not your wallet's details beyond what the provider reports. ⟨Provider name and its policy link — the owner confirms the provider.⟩

6. Your rights and the account's deletion

You can see everything the server holds about you in the cabinet: the account, its devices, its plan and its payment events.
You can delete the account from the cabinet. The server removes the account, its devices, the synced profiles' pointers and encrypted blobs, the subscription and team memberships. measuredDeletion was exercised against a live server. Payment history stays for the books, without a link to the account. Profiles on your own computers are untouched.
Requests that the cabinet cannot serve (a copy of your data in a file, a correction of the email) go to the support address; ⟨response time — the owner decides⟩.

7. Email

We send mail only to reset a password (a one-shot link valid for 30 minutes) and, ⟨if the owner decides so⟩, to announce material changes. ⟨The mail provider the owner chose, and its policy link.⟩

8. Changes

The date at the top moves when this policy changes; material changes are announced in the cabinet.

Decisions the owner has not taken

The controller: a person or a legal entity, the governing law, a postal address if the law requires one.
Log retention, and whether logs are ever exported.
The payment provider's name and the mail provider's name on this page.
A response time for data requests.

Terms · Refunds · What the server can and cannot see (technical) · Home