Privacy Policy
Version 1.0 · Last updated 2026-09-06
Impatient Coffee handles your data responsibly and hereby informs you about the processing of your personal data for which we are the controller according to the provisions of the EU GDPR.
The controller is Florian Demmer, in Portugal; the imprint has the details.
Questions about any of this go to [email protected], which is the address to write to about your data and the rights set out in section 3.
Below you can find the most important information on our typical processing of your data. The term "data" refers to personal data within the meaning of the GDPR only.
Contents
- 1. Website Visitors and App Users
- 2. Contact and Support Requests
- 3. Your Rights and Further Information
- 4. Information for Non-EU and US Residents
1. Website Visitors and App Users
1.1 Server Log Data
Delivering a page means two providers see the request for it. Both process the ordinary server log data (IP address, user agent, requested address, timestamp) for as long as it takes to serve the site and keep it standing, on the basis of Art. 6 (1)(f) GDPR.
| Service | What it does | Where |
|---|---|---|
| DigitalOcean | Runs the server the site is served from | Frankfurt (FRA-1), EU |
| Cloudflare | DNS, TLS, and protection against abuse | Its own network, at the point nearest you |
1.2 Technically Required Cookies
Below you find a list of technically necessary cookies. None of them follow you anywhere, and there is nothing here to consent to or switch off.
1.2.1 Session Cookies
We use a session cookie to keep a user-specific setting for the duration of your visit: the language you are reading in, where that differs from the one your browser asks for.
The data is automatically transmitted by the browser of the user. The cookie is deleted at the end of the session.
1.2.2 Security Cookies
We use IT security cookies on our website to protect the site and its visitors
against IT security attacks and malicious bot usage. These include Cloudflare's
__cf_bm and cf_clearance cookies.
The data is automatically transmitted by the browser of the user. Both expire after 30 minutes by default.
1.3 App Data
| Where | Name | What is in it |
|---|---|---|
| Local storage | theme | Whether you chose light or dark |
| Indexed database | impatient.db | Everything below, as a small SQLite database |
The database holds your settings, your saved favorites, your brew log (each brew with its recipe, timings, and whatever rating, tasting notes and measurements you added to it) and the dial-in you last used for each recipe, so a recipe opens where you left it.
It also holds one identifier: a random string this device generated the first time the app ran, which every row is stamped with so that a future account could claim them. It is not derived from anything about you, is not sent anywhere, and identifies nothing outside this browser.
Clearing this site's data in your browser settings deletes all of it at once, and for good; there is nothing kept elsewhere to restore it from.
1.4 Analytics
Visits are counted with Plausible Analytics, which is built to measure a site without identifying the people using it. It stores nothing on your device and reads nothing from it, and it does not follow you to other sites.
What it records is the page address and where you arrived from. Your browser, operating system and kind of device are read from your user agent, and your approximate location (country, region and city) from your IP address. Those two are also what a daily changing hash is worked out from, so that a returning visit can be counted as the same one. Neither is stored, and the salt behind that hash is replaced every 24 hours, after which the day's visits cannot be tied to anything.
What remains after that is counts: how many visits a page had, from which country, on which browser, on which day. Those are not personal data. For completeness: they are kept for three years, which is the retention our Plausible plan carries, and deleted once they are older than that.
The addresses recorded are pages, not what you looked at: the identifiers this app puts in a link (which saved favorite a recipe was opened from, which brew in your log is on screen) are removed before anything is sent.
The counting requests go to this site's own domain and are passed on from there, so no separate analytics host is contacted by your browser.
1.5 Content from third parties
1.5.1 YouTube Embedding (Privacy Enhanced Mode)
Some recipes link a video, embedded from YouTube's privacy-enhanced host
youtube-nocookie.com. It sits inside the recipe's "About the Recipe" panel,
which is closed until you open it, and loads only once it comes into view; a
recipe you read without opening that panel does not reach Google at all. When it
does load, Google receives your IP address, your browser, and the page you are
on. Google states that in this mode nothing is written to your device for
advertising or tracking unless you play the video.
The collection and processing that follows is Google Ireland Limited's, Google Building Gordon House, 4 Barrow St, Dublin, D04 E5W5, Ireland. Google Ireland Limited uses Google LLC in the USA (1600 Amphitheatre Parkway, Mountain View, CA 94043, USA) as its service provider.
Impatient Coffee has no influence on the data processing of Google. For information about the processing of personal data by Google, please refer to the Google Privacy Policy.
2. Contact and Support Requests
Writing to us is your choice; nothing on this site asks for it. If you do, we receive your email address, your message, and whatever else you put in it, attachments included.
That is used to answer you and for nothing else: no mailing list, no analytics, nothing passed on. The basis is Art. 6 (1)(f) GDPR, our interest in replying to somebody who wrote to us.
A message is kept while the matter is open and for as long afterwards as we may need to look back at what was said, then deleted.
Mail to any address at this domain is routed by Cloudflare, which already fronts this domain, and comes to rest in a mailbox on Google Workspace, run by Google Ireland Limited. Both handle these messages for us under their own data processing terms, and Google may process them in the United States; that transfer rests on the EU-US Data Privacy Framework and the standard contractual clauses those terms include.
3. Your Rights and Further Information
Nothing about you is decided by a machine here, put simply: no profiling, and no automated decision that carries legal weight or anything close to it.
Beyond that, the GDPR gives you the following rights. To make use of any of them, write to [email protected].
- Ask, whenever you like, what personal data of yours we are processing.
- Have it corrected where it is wrong, or completed where it is half the story.
- Have it deleted, unless the law obliges us to keep it a while longer.
- Have us hold it without using it, where the conditions for that are met.
- Object to processing done for profiling or direct marketing.
- Object because of something particular to your situation, where we are processing on a balance of interests. That is Art. 6 (1)(f), which covers most of what this page describes.
- Take the data you gave us elsewhere, where the processing rests on your consent or on a contract, and as long as doing so treads on nobody else's rights.
- Withdraw your consent, where we rely on it, from that point forward. What was done beforehand stays done.
- Complain to a data protection supervisory authority, any time you think the law has not been kept.
4. Information for Non-EU and US Residents
This page is written to the GDPR, because that is the law we fall under. If you are reading it from outside the EU or the EEA, your own country's privacy law may apply on top of it. If that asks for something this page does not cover, we will tell you separately if required.