Privacy policy for this website
Last updated: 1 November 2026
1. In brief
This website introduces the Grumbly app and runs a waitlist for the app’s launch. It sets no cookies (with one exception for protection against attacks, section 6) and loads nothing from third-party servers. Personal data is only processed when you visit the website (section 3), join the waitlist (section 4) or send an email (section 5).
The app itself has its own privacy policy.
2. Controller
Luca-Georg Wallenfels
Togostraße 5
13351 Berlin
Germany
Email: support@getgrumbly.app
3. Visiting the website
Whenever a page is requested, the hosting provider processes technically necessary data: IP address, time, requested page, amount of data transferred and details about browser and operating system. This is needed to deliver the pages and to protect operation against misuse and attacks.
- Legal basis: Art. 6(1)(f) GDPR (legitimate interest in a working and protected website).
- Hosting provider: Cloudflare Pages by Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA, as a processor under Art. 28 GDPR (Cloudflare’s Data Processing Addendum, part of its terms). For part of the data, Cloudflare is a controller itself, for example for security and statistical data derived from it, such as threat scores for IP addresses, and may also use it to operate and improve its services.
- Transfer to the USA: Cloudflare delivers the pages through its global network, so a request may also be handled by servers outside the EU, in particular in the USA. Cloudflare is certified under the EU-U.S. Data Privacy Framework; the transfer is based on the EU Commission’s adequacy decision for it (Art. 45 GDPR). For transfers without an adequacy decision, for example if the certification lapses, the standard contractual clauses in the contract with Cloudflare apply (Art. 46(2)(c) GDPR).
- Retention of server logs: The logs of requests that Cloudflare keeps as a processor are stored for at least 31 days. Cloudflare doesn’t state a fixed maximum. Under the contract with Cloudflare, they are kept only as long as they are needed to perform it, at most until it ends. For data where Cloudflare is a controller itself, its privacy policy only gives criteria for how long it is kept, not a fixed period.
4. Waitlist
On the home page you can join the waitlist with your email address. You can sign up from the age of 16.
What data: The waitlist database holds
- your email address,
- the language of the page you signed up on (German or English),
- the times you signed up, the last confirmation email was sent and you confirmed, and until when the confirmation link is valid,
- how many confirmation emails went to your address (limited, so nobody can flood someone else’s address with emails),
- which version of the consent text was shown next to the form,
- for the links to confirm and to unsubscribe, only a hash of the random codes, not the codes themselves, including the unsubscribe link in the launch email,
- after you confirm, the personal discount code assigned to you (a one-time code from Apple) with its expiry date, plus the time it was assigned and the time the launch email with the code was sent.
The email service Resend also keeps copies of the emails sent: with your address, the links to confirm and to unsubscribe including the codes in them and, in the launch email, your discount code.
A hidden field in the form keeps out automated sign-ups. Whatever is entered there is not stored.
Preventing misuse: The server function counts how often sign-ups come from the same IP address within an hour, for IPv6 from the same network range (/64), because a connection usually gets a whole range like that. If there are too many, it turns down further sign-ups. For this it doesn’t store the IP address or the network range, only a hash of it made with a secret key, together with the hour and the number of sign-ups. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in keeping the waitlist free of automated mass sign-ups and email misuse). A daily job in the database deletes all counters older than one day, so they exist for at most two days. In its own logs, the function records neither email addresses nor IP addresses. Supabase’s technical logs of every call to the function, however, contain the IP address and the requested URL. The codes to confirm and to unsubscribe are not part of that URL, because the website’s pages send them by POST. The exception is one-click unsubscribing from your email app: the address for it, which the email carries for your email app, contains the code to unsubscribe. Supabase keeps these logs for 1 day for this project.
What for: Your address is only used to send you the confirmation email and a few emails about the app’s launch, for example when Grumbly appears on the App Store. It isn’t used for anything else, isn’t sold and isn’t passed on to advertising or analytics services. Whether you open an email or click a link in it is not tracked.
Personal discount code: As a thank-you for signing up, you get 20% off the first year of the yearly plan, and the terms are on the page “Waitlist discount terms”. Apple creates the code without any link to you; it is only assigned to you in the waitlist database. Apple receives neither your address nor the assignment from the waitlist. If you redeem the code, Apple processes the purchase under its own terms and privacy notices; there is no matching of which entry redeemed its code. The launch email with the code goes to your waitlist address.
Legal basis: your consent, Art. 6(1)(a) GDPR, including for assigning the code and the launch email with the code. The times you signed up and confirmed and the version of the consent text also serve as proof of consent (Art. 7(1) GDPR). The times the code was assigned and sent make sure each entry gets exactly one code and no launch email goes out twice, and they help with questions about the code; the legal basis for this is Art. 6(1)(f) GDPR (legitimate interest in reliable sending).
Confirmation by email (double opt-in): After signing up, you get an email with a link to confirm. Only once you confirm are you on the waitlist. This way, nobody can sign up someone else’s address. The confirmation link is valid for 7 days from the most recent confirmation email; links from earlier emails stay valid until then. If you don’t confirm, the entry is deleted once the link has expired: by the daily job in the database at most one day later, so at most 8 days after the most recent confirmation email.
Where the data is kept:
- Supabase (database and server function of the waitlist): Supabase Pte. Ltd., 65 Chulia Street #38-02/03, OCBC Centre, Singapore 049513, as a processor under Art. 28 GDPR. The database is located in Frankfurt am Main, Germany (AWS region eu-central-1), and the server function is explicitly run there too: the website’s forms and the address for one-click unsubscribing set the region. For operation and support, Supabase and its subprocessors may access it from third countries, in particular Singapore and the USA. Basis: standard contractual clauses of the EU Commission (Art. 46(2)(c) GDPR).
- Resend (sending the emails, including the launch email with the code): Plus Five Five, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA, as a processor under Art. 28 GDPR. The emails are sent from Ireland (region eu-west-1), but emails, logs and metadata are stored in the USA. Resend is certified under the EU-U.S. Data Privacy Framework; the transfer is based on the EU Commission’s adequacy decision for it (Art. 45 GDPR). For transfers without an adequacy decision, for example if the certification lapses, the contract with Resend contains standard contractual clauses (Art. 46(2)(c) GDPR). For usage data such as sender, recipient and logs, Resend is a controller itself and may also use it to operate its service, prevent abuse and improve its service.
In third countries such as Singapore or the USA, there is no level of data protection that the EU Commission has generally recognised as adequate (for the USA only for certified companies). Authorities there may be able to access data without you having the same legal remedies as in the EU.
How long: until the app launches and then until 30 days after your launch email was sent, which is when your code’s redemption period ends. The daily job in the database then deletes your entry together with the code, at most one day later. Entries that didn’t get a launch email are deleted once 30 days have passed since sending began, also at most one day later. Codes not assigned to any entry contain no information about you; they are deleted when they expire, at the latest 31 days after sending began.
If you unsubscribe or withdraw your consent before then, your entry is deleted right away, together with any code already assigned to it. Supabase keeps no daily backups for this project.
Deleting the entry in the database doesn’t reach the copies at the email service: Resend keeps sent emails and logs for 30 days, and in backups for up to 7 more days. Addresses where an email permanently couldn’t be delivered or was reported as spam are on a suppression list at Resend until they are removed from it. For usage data where Resend is a controller itself, its privacy policy only gives general criteria for how long it is kept, not a fixed period.
Unsubscribing and withdrawal: Every email contains a link to unsubscribe. It opens a page on this website where you delete your entry with a button; the link in any of the emails works. If your email app offers to unsubscribe you itself (one-click unsubscribe), that deletes your entry too. You can also withdraw your consent informally by emailing support@getgrumbly.app. Withdrawal doesn’t affect the lawfulness of processing before it.
5. Contact by email
If you email support@getgrumbly.app, for example with a question, to unsubscribe or to exercise your rights, your email address, your name if you give it, the content of your message and the time are processed to answer your request.
- Legal basis: Art. 6(1)(f) GDPR (legitimate interest in answering requests); where it concerns a contract or steps before one, Art. 6(1)(b) GDPR; where it concerns your rights under the GDPR, Art. 6(1)(c) GDPR.
- Receiving emails: Cloudflare (Email Routing; provider, role and transfer to the USA as in section 3) receives incoming emails and forwards them to the mailbox, according to Cloudflare without storing their content. The sender, recipient and subject of each email remain in Cloudflare’s logs for 31 days.
- Mailbox provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. There is no data processing agreement under Art. 28 GDPR with this provider. It is not bound as a processor and handles incoming messages under its own terms of use. Processing may also take place on servers outside the EU, and the transfer to the USA relies on the adequacy decision for the EU-US Data Privacy Framework.
- Retention: The message is deleted once your request has been dealt with, unless statutory retention obligations require it to be kept longer.
Please don’t send health data by email, so no entries, symptoms or screenshots of them.
6. Cookies
This website sets no cookies, stores nothing on your device and loads no fonts, images or scripts from third-party servers. The only exception is a check page from Cloudflare (section 3): only if Cloudflare classifies a request as a possible attack, which can also happen by mistake, can it appear instead of the requested page. If you pass the check, you get a technically necessary cookie (cf_clearance), so that the check doesn’t appear again right away. The check page may also set cookies that Cloudflare uses to identify technical problems (cf_chl_rc_i, cf_chl_rc_ni, cf_chl_rc_m). Only the waitlist forms send data to the server function at Supabase: the sign-up form and the buttons on the pages to confirm and to unsubscribe. These two pages contain a small script of their own. It only reads the code from the link, stores nothing and only sends something once you click the button. The code sits in the link after the # sign; the browser doesn’t send that part to the website’s server, so it isn’t in its logs either.
7. No automated decisions
There is no automated decision-making, including profiling, within the meaning of Art. 22 GDPR.
8. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and withdrawal of your consent (Art. 7(3)). To exercise them, email support@getgrumbly.app.
Right to object (Art. 21 GDPR): Where data is processed on the basis of legitimate interests (section 3, preventing misuse and the times the code was assigned and sent in section 4, and section 5), you can object at any time on grounds relating to your particular situation.
9. Right to lodge a complaint
You can lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the member state where you live. The competent authority is the Berlin Commissioner for Data Protection and Freedom of Information (Berliner Beauftragte für Datenschutz und Informationsfreiheit), Alt-Moabit 59-61, 10555 Berlin, Germany, datenschutz-berlin.de.
10. Obligation to provide data
You don’t have to provide any data. Without an email address, however, you can’t join the waitlist.