Privacy policy
What information this website handles, and what it does not.
Last updated: November 4, 2026
This policy explains what Zortex collects when you read the website, join the waitlist or use the publishing studio.
Readers
Reading the website requires no account. The server receives the ordinary request data every website receives: your IP address, the page requested, the time, and your browser’s user-agent string. These appear in server logs used for operation and security and are not combined with other data or sold. No advertising pixels or third-party fonts are loaded. Our hosting and security providers, Railway and Cloudflare, handle this request data only to deliver and protect the website. Pages with the waitlist form also load Cloudflare Turnstile, a security check that tells people from automated signups; it runs in your browser and Cloudflare receives the signals it needs for that check, including your IP address.
Visit measurement
To understand interest in Zortex we count visits to the homepage and to journal articles and the install page on our own server. No reader cookie is set. For each visit we record the day, which kind of page it was, and any campaign labels in the link you followed (utm_source, utm_medium, utm_campaign). To estimate how many different visitors came on a given day, the server combines your IP address and browser user-agent with a random value that is replaced every day, and stores only the resulting one-way code. Those codes are deleted the following day and the daily value is discarded, so visits on different days cannot be linked to each other or back to you. We keep only the daily totals.
The install page also reports a short allow-listed action name when someone opens its Autopilot instructions, copies the install command or follows the npm package link. Our server sends aggregate page and action events, coarse campaign labels, and no IP address, user-agent, email or page content to the Zortex team’s hosted PostHog project. All anonymous website events use one aggregate identifier, so these totals are not presented as people or accounts.
Waitlist
What we collect. If you join the waitlist we store the email address you enter, when you joined, the page you joined from, the journal article that led you there (its address on this site only), any campaign labels from the link you followed, the version of the offer and wording you saw, and, if you choose to answer it, what you would most like to use Zortex for. We do not store full referring web addresses.
Why. To send you an early-access invite when Zortex is ready and occasional updates while we build it, and to understand how much interest there is and where it comes from. Joining does not create an account, reserve a place or give you a position in a queue.
Email. When you join, we send one confirmation email from hello@zortex.me with a link to confirm your address. You are only on the list once you open it and press Confirm; until then we send you nothing else. If you never confirm, we keep the unconfirmed entry and never email it again unless you ask for a new link. A new link can be requested only a few times a day for the same inbox. The email goes through Proton Mail, our email provider, which handles your address only to deliver it. After you confirm, we will email your early-access invite and occasional updates. Every email has an unsubscribe link, and replying reaches us directly.
Security checks. To stop automated signups and people signing others up, the form uses Cloudflare Turnstile, and we limit how often one network can submit it and how many confirmation emails one inbox can receive. These limits are kept as one-way hashes, not as addresses, and expire within a day.
Who can see it. Only the people who administer this website, after signing in to its private studio. They can export the list as a file for their own use. We do not sell or share the list.
How long we keep it. Until early access opens, and for as long as you stay on the list after that. You can leave at any time, and we delete your entry when you ask. Copies in our private backups are replaced as backups rotate, within 14 days.
Leaving or deleting. Use the Leave the waitlist form to ask us to take you off the list or to delete your signup entirely. We act on requests by hand, so a request does not change anything until an administrator has dealt with it. If you leave without deleting, we keep a record that you left so that we respect that choice.
In your browser. While you browse in one tab, the campaign labels from the link you arrived by and the last article you read are kept in that tab’s session storage, and are sent only as part of a waitlist signup. They disappear when you close the tab.
Editors
Signing in to the studio requires an email address and a password. Passwords are stored as Argon2 hashes and never in plain text. A session cookie identifies you while signed in and expires after eight hours. Revision history records which account saved each version.
Preferences kept in your browser
The colour theme, the hide-images setting on the journal and your cookie preferences are stored in your browser’s local storage. They never leave your device.
Sharing
We do not sell or rent personal information. We disclose it only if required by law or to protect the security of the Services.
Your rights
You can ask what information we hold about you, ask for it to be corrected or deleted, and object to its use. For the waitlist, use the Leave the waitlist form. Other contact details are on the About page.
Changes
We will update this page when our practices change and record the date at the top.