← Brew

Privacy

Scope and controller

This notice describes Brew. Other dryyyve apps have their own privacy pages. Last updated: 18 September 2026.

Charles Walczynski
Breidenbacherstraße 25
55116 Mainz, Germany
Email: brew@dryyyve.com

Hosting and requests

This website is hosted by ALL-INKL.COM – Neue Medien Münnich, Hauptstraße 68, 02742 Friedersdorf, Germany. Delivering the site involves processing your IP address, request time, requested URL and technical browser/request information. A data processing agreement is in place with the hosting provider. In this hosting account, website access logs and access statistics are disabled. Technical request data still have to be processed to deliver the site and maintain its security (Article 6(1)(f) GDPR). This setting does not rule out separate operational or security processing by the hosting provider.

Email contact

Email sent to brew@dryyyve.com is handled through Google Workspace, provided by Google Cloud EMEA Limited, 70 Sir John Rogerson’s Quay, Dublin 2, Ireland. Google processes the message and contact details to deliver and secure email. A Google Cloud Data Processing Addendum is in place. Processing outside the EU may occur with safeguards under applicable adequacy decisions or Standard Contractual Clauses. During the transition, ALL-INKL.COM may also process necessary outbound email delivery data. See Google’s contracting entity information and the Google Cloud Data Processing Addendum.

Data used by this app

Brew stores recipes, coffee entries, statistics, preferences, supplies and dose settings under aeropress-data, and an active timer under aeropress-active-timer-v1. Sharing a recipe creates a link or QR code locally. Information you deliberately share is visible to its recipients.

Browser storage and your choices

Game and preference data described above stay in this browser and are not uploaded to a dryyyve account. Persistent browser storage remains until you reset it, clear the site's browser data or the browser removes it. Temporary sessionStorage ends with the browsing session. You can remove site data in your browser settings; this also removes saved progress. HTTP and HTTPS, different devices and different subdomains have separate storage.

Storage supporting the function you request is used for that function; the applicable exception for strictly necessary device storage is Section 25(2) TDDDG. Where stored information is personal data, processing to provide the requested function is based on Article 6(1)(b) GDPR; optional appearance preferences support convenient operation under Article 6(1)(f). No browser analytics or advertising storage is used. Passive server-side daily counters are described below.

Offline use

A service worker stores this app's files in browser Cache Storage so the app and its legal pages can work offline after installation. Files are refreshed with application updates. Clear this site's data in browser settings to remove the offline copy. Cached notices show the date of the version stored on your device.

External resources and links

Fonts, scripts, icons and game resources are served from this website. No analytics, advertising or external font/CDN requests are initiated by this version. Following an external link or using your device's sharing service opens a service with its own privacy policy.

Contact and your rights

If you email me, I process your contact details and message to respond (Article 6(1)(f) GDPR, or Article 6(1)(b) for a contractual request). Messages are retained for the correspondence and any applicable legal retention obligations. Depending on the processing, you may request access, correction, erasure, restriction or portability, and object to processing based on legitimate interests. Contact the email above. You can also complain to the data protection authority of Rhineland-Palatinate or another competent authority.

Passive daily counters

This app counts daily responses to necessary server GET requests, including bots, reloads and cache fetches. Daily totals are kept for 90 days; older rows are removed on the next counter request. It stores no IP addresses, user agents, referrers, campaign data, user IDs or content, and offline use is not counted. The processing supports product operation under Article 6(1)(f) GDPR. Private copies are created when the authorised dashboard is read. After a successful daily copy, copies older than seven days are removed. Without further requests or if copying fails, stored totals or existing copies can remain longer. There is no additional browser tracking or consent prompt.