Your data.
Last updated 20 November 2026. This page says what Verityped does with your data today. If that changes, for example when documents can be published or shared, this page changes first.
Who is responsible
Jeffrey Humble, Peschkestr. 5, 12161 Berlin, Germany. Email: support@pigrosoft.com.
In short
Verityped uses no advertising and no tracking. We count visits with a small counter of our own that sets no cookies and cannot tell who you are. The only cookie is the one that keeps you signed in, and you only get it if you sign in. If you do not sign in, what you write stays in your own browser. If you sign in, your documents are locked in your browser with your fingerprint or face, or a passphrase only you know, before they are saved to your account, so we cannot read what you write, and no one at Verityped has a way to.
Hosting
The site runs on Cloudflare (Cloudflare, Inc., USA), which also provides the domain’s DNS. When you open a page, Cloudflare processes technically necessary access data such as your IP address in server logs. Our account database is a Cloudflare D1 database that we asked to be placed in Western Europe. Documents saved to an account are kept in a Cloudflare R2 bucket restricted to the European Union. Cloudflare may process data outside the EU under the safeguards it describes in its privacy policy and data processing terms. The legal basis is our legitimate interest in running a secure website (Art. 6(1)(f) GDPR). Fonts and images are served from this site, and no third-party services are loaded. The visitor counter (next section) is our own and runs on Cloudflare too.
Visitor counter
We count visits with a small counter of our own, made by Pigrosoft and run on Cloudflare. When a page loads, your browser sends a request to stats.pigrosoft.com with the address of the page you opened and, if your browser shares it, the name of the website that sent you here. The counter mixes your IP address and browser type with the site name and a secret code that is replaced every day, and keeps only the result for that day, so that you are not counted twice. It then adds one to the day’s total, to the count for the page, to the count for the referring website, and to the count for your country (a two-letter code from Cloudflare, with no city or region). The counter sets no cookies, stores no IP address, stores nothing in your browser, and deletes the previous day’s results and secret code when a new day starts. The counts cannot be tied to a person. It does not run on or read anything you write in the editor, only the page address. We use the numbers to see how many people use Verityped and which pages they read. The legal basis is our legitimate interest in knowing that (Art. 6(1)(f) GDPR), and you can object at any time by writing to support@pigrosoft.com.
Inside the editor we also keep anonymous counts of which features get used, so that we know what is worth improving. When you start a document, type for the first time, have a paste refused, drag a passage to a new place, apply formatting, open the writing history, turn the typing sound on, check a file, download a .typed file or pair a new device, your browser tells our server the name of that event, and we add one to the day’s total for it. When you stop typing, we also add one to a band for how long the sitting lasted, such as under a minute or five to fifteen minutes. Nothing else is sent: no text, no title, no document, no account, no cookie and no ID, and we do not store your IP address or browser type for this. The event names come from a fixed list on our server, and it ignores anything else. Nothing is sent if your browser sends Do Not Track or Global Privacy Control, or if you have turned off the counter with #toggle-counter. For signed-in accounts we also know, as before, when the account was made, when you last signed in and when each locked document was last saved, and we use those to see how many writers come back. The legal basis is again our legitimate interest in knowing how the product is used (Art. 6(1)(f) GDPR).
What you write
If you are not signed in, your documents, and the record of how you typed them, are saved only in your browser on your own device. They are not sent to us, we cannot see or recover them, and clearing your browser data deletes them. A .typed file, or the backup file you can download from the documents page, exists only when you download one, and the backup is plain text, so keep it as carefully as you would keep the writing itself. Your browser also stores your documents and settings in its local storage because the editor cannot work without it, so no consent is needed for that (§ 25(2) no. 2 TDDDG).
If you sign in, each document is also saved to your account so that it is backed up and available on your other devices. Before a document leaves your browser it is locked with a key that is made in your browser and protected by your fingerprint or face, or by a passphrase you choose. Our server never receives the key, the passphrase or your fingerprint. What we store is scrambled text: the writing, the typing history, the title, the folder and the excerpt are all inside it, and we cannot open it, not through the website, not through the database and not by looking at our own storage. The server also refuses to store a document that is not locked. We can see only that your account holds a number of locked documents, how large each one is, when it was last saved, and whether it is in your trash. We also hold your key in locked form, which is no use to anyone without your fingerprint, passphrase or recovery code.
There are three ways to open your documents, and all three stay with you. The first is your fingerprint or face, set up as a passkey on your device. Your device makes the passkey’s secret and it never leaves the device, and we store only a copy of your key that this secret can open. The second is a recovery code, a short code you are shown once when you set up and keep yourself, for the day you lose your devices. The third is a passphrase, which is optional where a fingerprint works and the way in on browsers that cannot use one. You can turn the fingerprint lock off only once a passphrase is set, so that you are never left with the recovery code alone.
A device you already use can also open your documents on a new one. The new device shows a code, you check that the same code appears on the old device and approve it there, and the old device passes the key across sealed so that only the new device can open it. We relay that sealed key for a few minutes and delete it, and we cannot read it.
We cannot reset any of these for you or recover your documents, because we have nothing to recover them with. Signing in by email proves the account is yours, but it does not open your documents. If you lose every device, the recovery code and any passphrase, nobody can open the copies on your account, including us. Your documents in your browsers and any files you saved are not affected. You can then start again, which deletes the copies on your account and saves the documents still in your browser again under a new lock.
If you use a passphrase, a short or common one is easier to guess for someone who somehow got hold of the stored data, so a few unrelated words in a row is better than one. The page that does the locking is code we send to you each time you open it, so what protects you is that the code runs in your browser and that this page says how it works. If publishing or sharing a document is ever added, it will be something you choose to do for that document, and this page will say so first.
Deleting a document from your trash for good removes its copy from your account too. To delete your account and every locked copy with it, write to us. The legal basis is Art. 6(1)(b) GDPR, because saving your documents is the service you asked for. The locked copies sit in storage that Cloudflare keeps inside the European Union.
Writing assistants
While you write, the page looks for a short list of known writing assistants, such as Grammarly and LanguageTool, in your browser. If it sees one, it adds the tool’s name to that document’s typing history, which is part of the .typed file and is shown to anyone you send the file to. The page learns nothing else about your browser or other extensions, and nothing is blocked.
Signing in
If you sign in, we ask for your email address and send you a link that works once and expires after 15 minutes. We keep your email address, the time you signed up and the time you last signed in, so that the same address always reaches the same account. Signing in sets one cookie, vt_session. It keeps you signed in for up to 30 days, can only be read by our server, and is deleted when you sign out. It is strictly necessary for signing in, so it needs no consent (§ 25(2) no. 2 TDDDG). On our side we keep only a scrambled version of the sign-in link and of the session code, so a leak of the database could not be used to sign in as you.
To stop abuse, we count sign-in link requests per email address and per IP address for an hour. The counts are deleted within two days. The legal basis for the account is Art. 6(1)(b) GDPR, because you asked us to provide it, and for the abuse counts Art. 6(1)(f) GDPR.
Sign-in links are sent by our email provider Brevo (Sendinblue GmbH, Germany, part of Brevo), who delivers them for us and processes your email address for that purpose only. To delete your account and everything we hold about it, write to support@pigrosoft.com from the address you signed in with.
Writing to us
If you use the contact form or email us, we receive what you type, including your name, email address and organization if you give them. The form passes the message to our inbox through Brevo, and nothing is stored on this website. We use it only to reply, and delete it when it is no longer needed. The legal basis is Art. 6(1)(b) or (f) GDPR, depending on whether you are asking about our service or something else.
Your rights
You have the right to access, correction, deletion, restriction of processing, data portability and objection, and the right to complain to a data protection authority. The authority responsible for us is the Berliner Beauftragte für Datenschutz und Informationsfreiheit. To use any of these rights, write to support@pigrosoft.com.
No automated decisions
We do not profile you, and we do not make automated decisions about you. Verityped does not score writing or estimate whether it was written by AI.