Privacy policy
As of 7 October 2026.
1. Who is responsible
Controller under the GDPR (DSGVO) ("Verantwortlicher"): see the Impressum for name and postal address. Contact for all privacy questions: hello@stackrig.dev. We have not appointed a data protection officer; we are not required to (§ 38 BDSG).
2. Visiting this website
The website is delivered by Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA, as our processor. To deliver the pages and protect them against attacks, Cloudflare processes technical data of every request: IP address, date and time, requested address, referrer, browser and operating system. Legal basis: our legitimate interest in a secure and working website (Art. 6 (1) (f) GDPR). Cloudflare is certified under the EU-U.S. Data Privacy Framework; we have concluded a data processing agreement with Cloudflare. We do not keep these request logs ourselves. Cloudflare shows us aggregate traffic figures made from these requests (for example the number of requests per day and per country); in its dashboard we can also see single requests with their address where Cloudflare's protection blocked or challenged them.
Beyond that we use no analytics service of another company, no cookies for counting and nothing that identifies you. We count ourselves how the site and the playground are used, to improve Stackrig. What we count is listed in the next paragraph; we count nothing else. The public pages set no cookies. If you sign in to a Stackrig account (section 5), your browser keeps the sign-in (a session token) in its local storage; this is strictly necessary to provide the account you asked for (§ 25 (2) no. 2 TDDDG).
What we count: for each day we keep plain totals, never a record per visit: how often each public page was opened and whether the device was a phone or another device; how often the button or link in a guide's "Try it in Stackrig" box was followed, and whether it leads to the playground or to the waitlist; and in the playground how often a template was opened (and which), Play was pressed, a node was added (and of which kind), a share link was made, a design was exported, the upgrade dialog was opened (and for which reason), and an error occurred (and of which kind, never its message). In the playground each number counts roughly the minutes in which this was done, not the clicks: an open page sends an event at most once a minute per name and detail. A total holds a day, a name from these lists and a number. It holds no identifier, no cookie, no time of day, none of your designs, and not your IP address, which is used for one minute by the rate limiter that protects the counters. We cannot tell who did something, nor whether two counts come from the same person. The counting runs at Cloudflare, which handles these requests like every other request to this website (see above), and the totals are stored at Supabase (section 4), where a technical log can show that something was counted and when, but not by whom. Legal basis: our legitimate interest in improving Stackrig (Art. 6 (1) (f) GDPR). If your browser sends the signal "Global Privacy Control" or "Do Not Track", we count nothing for you.
Partner links: links in a block marked "Advertising" lead to partners who pay us a commission if you become their customer. The link carries our partner number, so the partner learns that you came from stackrig.dev. DigitalOcean's link runs through the affiliate network Awin (AWIN AG, Berlin, Germany): Awin receives the click before it passes you on, records it and may set a cookie of its own, so that the commission can be credited to us. We receive totals of sign-ups and commissions, no data about you. We load nothing from partners on our pages and set no cookie; after the click the partner's own privacy policy applies, and Awin's for a link that runs through it.
3. The playground (the Stackrig app)
The simulation runs entirely in your browser. Designs you create are stored only in your browser's local storage (IndexedDB) on your device; we do not receive them. When you create a share link, the design is encoded in the part of the link after "#", which browsers do not send to any server; whoever you give the link to can read the design. Exported files stay on your device. This stays true as long as you do not use an account. With an account, only the designs for which you turn on "Save to cloud" are sent to us (section 5).
The app also keeps a few notes of its own in your browser's local storage: which hints you closed,
whether the welcome line was shown, and the date of your first visit, by which it decides when to
show a hint about accounts. When you ask for a sign-in mail, it also notes the email address you
asked it for, for one hour, to tell you if a sign-in link opens a different account, and a mark
that this question is still open until you answer it. When you switch the language, it notes your
choice (German or English, key stackrig.lang) so the next page opens in it. These notes
stay on your device and are not sent to us.
The blog's search also runs in your browser: the index it searches is loaded as a whole, like any other file of the site, and what you type is not sent to us and not stored.
4. The waitlist
What we store:
- your email address,
- your optional answers: what describes you best, and whether and how much you would pay,
- the version of the consent text you agreed to, the time of sign-up and of confirmation, and the times and number of emails we sent you (to limit resending),
- cryptographic fingerprints (hashes) of the confirmation and deletion links we sent you – not the links themselves.
We do not store your IP address with your entry. To protect the form against abuse, the number of requests per IP address is counted for one minute by Cloudflare's rate limiter and then discarded.
Purpose: to tell you when Stackrig Pro is ready and about important changes, and to ask you for feedback on the product (for example, whether you would like to talk to us). We evaluate the optional answers only as totals (how many people chose which answer) to decide on the product and its prices. No newsletter, no advertising, no passing on to third parties for their own purposes.
Legal basis: your consent (Art. 6 (1) (a) GDPR). You can withdraw it at any time with effect for the future: with the link in every email we send, or on the waitlist page, or by email to hello@stackrig.dev. Withdrawing deletes your entry immediately.
Double opt-in: after you sign up, we send you an email with a confirmation link. Only confirmed addresses are on the waitlist. If you do not confirm within 48 hours, the link expires and your entry is deleted automatically within the following day. We keep the time of sign-up and of confirmation as proof of your consent for as long as the entry exists.
How long: until you withdraw your consent, and at the latest until 12 months after the public launch of Stackrig on 30 September 2026, whichever comes first. Then all waitlist entries are deleted automatically. A deleted entry is gone from our nightly backup copies at the latest 7 days later (section 5, "Backups").
Service providers (processors) for the waitlist and the counting:
- Cloudflare, Inc. (USA) runs the waitlist and counting interface (Cloudflare Workers) and the rate limiter; see section 2 for the transfer basis.
- Supabase, Inc., 970 Toa Payoh North #07-04, Singapore 318992, stores the waitlist and the daily totals in a database in Frankfurt am Main, Germany (Amazon Web Services, region eu-central-1). Access from outside the EU by the provider cannot be excluded; it is covered by the EU standard contractual clauses in Supabase's data processing agreement (Art. 46 (2) (c) GDPR).
- Brevo (Sendinblue SAS), 106 boulevard Haussmann, 75008 Paris, France, sends the emails. Data is processed on servers in the EU. Open and click tracking are switched off.
5. Accounts and cloud save
An account is optional. You need one to save designs to the cloud and to use them on several devices. The terms of use apply to it.
What we store: your email address; the way you sign in (a link sent by email, or GitHub); if you sign in with GitHub, the data GitHub sends us with your approval: your GitHub user id, user name, name, the address of your avatar, your email address and GitHub's mark that it is verified; an optional display name you enter; the version of the terms you accepted and when; the designs you save to the cloud, their names and up to ten earlier versions of each; the times of creation and change. For security, the sign-in service records the time, the IP address and the browser type of a sign-in and keeps them with the session.
Purpose and legal basis: to provide the account and the cloud save you asked for (Art. 6 (1) (b) GDPR), and to protect the service against abuse (Art. 6 (1) (f) GDPR).
Sign-in mails contain a link and a code and are sent by Brevo (section 4). To send one, we store your address, the code and the link's token until the mail is sent or given up, at most 15 minutes, and then delete them. A hash of your address stays for 24 hours, only so that no more than 3 sign-in mails an hour and 10 a day can be sent to one address; such a hash is still personal data. Protection against automated sign-ups: the form that asks for your email address uses Cloudflare Turnstile (Cloudflare, section 2), which checks technical properties of your browser to tell a person from a program.
GitHub sign-in: if you choose it, you are sent to GitHub, Inc., 88 Colin P. Kelly Jr. St, San Francisco, CA 94107, USA, which processes your sign-in under its own privacy statement as an independent controller. We receive only the data listed above.
Where: accounts and designs are stored by Supabase in Frankfurt am Main, Germany (section 4).
How long: until you delete the design or the account. A deleted design stays in the trash for 30 days, where you can delete it at once; then it is erased. The trash holds up to 3 designs: deleting a fourth erases the oldest one in it at once. Deleting your account erases your profile, your designs and your sign-in data immediately. An account that has not been used for 24 months is deleted 30 days after a notice by email.
Backups: we make an encrypted copy of the database every night and delete each copy after 7 days. The copy is made on a machine that GitHub, Inc. (88 Colin P. Kelly Jr. St, San Francisco, CA 94107, USA, a Microsoft company) provides as our processor only for that run of a few minutes, outside the EU: there the database is read and encrypted, and only the encrypted copy leaves the machine. GitHub is certified under the EU-U.S. Data Privacy Framework. A deleted design or account, and everything stored with it, is therefore gone from all copies at the latest 7 days after the deletion. The copies are stored with Cloudflare (section 2), in the EU, encrypted with a key that only we hold.
Export and deletion: in the app under Account you can download all your data as a file and delete your account yourself.
6. Your rights
You have the right to access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21). You can withdraw consent at any time (Art. 7 (3)). Write to hello@stackrig.dev. You also have the right to lodge a complaint with a supervisory authority (Art. 77), in particular in the EU member state of your habitual residence, your place of work or the place of the alleged infringement. For the data of an account you can also use the export and the deletion in the app.
7. Is providing data required?
No. Joining the waitlist is voluntary. Without an email address we cannot tell you about the launch. The two questions are optional. An account is voluntary too: the playground works without one. Without an email address or a GitHub sign-in we cannot create an account.
8. Changes
We update this policy when our services change (for example when accounts or paid plans are introduced). The date at the top shows the current version.