Privacy policy
This policy covers the Brew with Tom Android app and this website. The journal is stored locally and Google Play handles purchases. In builds 9 and later, Sentry diagnostics are off by default and require separate, voluntary consent in Settings.
Data controller and contact
Bartosz Kamiński, sole trader trading as Bartosz Kamiński (portfolio: bk.dev.mobile). NIP: 1181466003. Correspondence and complaints: ul. Miodowa 11, 05-870 Bieniewice, Poland. Email: support@outlinego.com. Please include “Brew with Tom” in your subject.
Your journal and local settings
Recipes, ingredients, batch records, gravity and temperature readings, process events, tasting notes, reminders and settings are stored in the app’s local SQLite database or private device storage. No Brew with Tom account or developer-operated journal-sync service is provided. We do not receive your journal merely because you use the app. Your free-plan usage and verified Plus entitlement are stored locally too.
Android system backup or device transfer may process app data according to your device, Google account and backup settings; the current Android configuration allows platform backup. This is separate from our own app, which does not operate a cloud backup service.
The versions of the terms, safety notice and provided privacy policy, acceptance time and language, and a separate diagnostics choice are stored locally. On installed Android builds these records are outside the journal and system-backup directories. Journal exports exclude them. Reinstallation or restoration on another device requires a new choice; an update to the same installation preserves the record. A change to the required document version prompts for acceptance again.
Backup files and reminders
You can export a journal backup to a location you select through Android and restore a compatible file. Backup files can contain your recipes, batch names, notes, readings and reminders. They are not encrypted by the app. Choose a trusted destination, restrict access and manage exported copies yourself. A cloud-drive app or recipient you choose applies its own privacy rules. Restoring a backup replaces the journal currently on that device; it does not restore a Google Play purchase.
Local notifications use the reminder title and batch details, which can include notes. They may appear on your lock screen according to your Android settings. Android notification permission is requested for reminders; reminders are rescheduled after restart. Turn notifications off or adjust lock-screen visibility in Android settings. File selection uses Android document interfaces. Some older Android builds declare legacy file-storage permissions for compatibility.
Google Play purchases
Google Play processes payments under its privacy policy and purchase terms. The app receives product information, purchase status, a purchase token, receipt and signature-verification information to verify and acknowledge Plus and restore it. A verified receipt and signature are stored in the app’s private preferences to recognise entitlement after restart and offline. The app refreshes purchases through Google Play, including when returning to the foreground. We do not operate a separate receipt-verification server or receive your payment-card details through the app. Google controls retention of its transaction records.
Error reports and diagnostic logs
In builds 9 and later, the Sentry SDK is not initialised before explicit consent has been saved. Use Settings → Documents and diagnostics to opt in voluntarily or turn reporting off at any time. Declining does not limit Start or Plus. Accepting the terms is a separate choice and does not enable reporting. Consent covers future filtered JavaScript error reports, selected technical logs and recent screen names, not your brewing journal.
Filtered JavaScript reports contain an error category and fixed technical description, code locations, event identifier and time, release/build, environment, operation category and recent screen names without navigation parameters. Original JavaScript error messages, arbitrary app state, request data, journal content and user objects are removed by the app’s JavaScript filter. Selected logs contain fixed technical messages and operation names; ordinary console output is not collected as app logs.
Native Android crash reporting is disabled in builds 9 and later. We do not use the native transport or its disk queue. Withdrawing consent blocks new sends, aborts active requests and invalidates the previous in-memory queue even after opting in again. It does not delete information already received by Sentry. Offline reports are not replayed after a process restart. Earlier test build 8 initialised Sentry automatically and included native crashes; that previous configuration is described in archived version 2026-11-09.1.
Default personal-information collection is disabled. Sentry still receives connection information, including an IP address, when the device connects. The app uses an EU ingestion endpoint in Germany. EU ingestion does not imply that every part of Sentry’s service, support, account metadata or subprocessors is confined to the EU. Applicable processing terms and transfer safeguards are described in Sentry’s privacy information and Data Processing Addendum. Replay, screenshots, view-hierarchy attachments, performance profiling and advertising analytics are not enabled by this integration.
Withdraw consent using the Settings switch without restarting the app. Withdrawal does not affect the lawfulness of earlier processing. If saving the choice fails, reporting stops immediately in the current process, and the app asks you to retry saving before closing. You can contact the publisher to request deletion of previously sent reports.
This website and support email
This static site is hosted with Google Firebase Hosting. Google processes connection information such as IP address and request metadata to deliver and secure it. See Firebase privacy information. The website does not add analytics, advertising scripts, embedded social-media players, third-party fonts, account registration or application cookies. The demonstration video is served from this site and starts only when you choose to play it.
If you email us, we process your email address, message and any attachments to answer questions, handle complaints or protect legal rights. Send only what is needed. Do not send an entire journal, sensitive information or payment credentials unless specifically necessary for the issue.
Purposes, legal bases and recipients
Where the GDPR applies, voluntary diagnostics in builds 9 and later rely on consent (Article 6(1)(a)). Providing purchased features and handling related requests rely on contract performance; required records and consumer matters rely on legal obligations; website security, responding to enquiries and protecting legal claims rely on legitimate interests. Those interests are providing a secure website and supporting users. You may object to processing based on legitimate interests. This policy and acceptance of the terms do not substitute for diagnostics consent.
Recipients include Google for hosting and Play services, Sentry and its authorised service providers for diagnostics, email-service providers for correspondence, and authorities or professional advisers when legally required or needed to handle claims. We do not sell journal data or use it for targeted advertising. Providers may process information internationally under their applicable agreements and safeguards, including standard contractual clauses where relevant. Contact us for details of safeguards applicable to your request.
Retention and deletion
Local data remains until you remove it or clear the app’s data. Deleting a recipe can archive it so an existing batch retains its recipe history; deleting batches does not reset the Start creation counter. To remove all private app data, use Android Settings → Apps → Brew with Tom → Storage → Clear data, or uninstall the app. Clearing cache alone does not erase the journal. Android backup copies and exported files are managed separately at their destinations. Make a backup first if you want to keep your journal.
Diagnostic events and logs are retained subject to the retention limits of the Sentry plan and the time reasonably needed to investigate and fix problems, then deleted or allowed to expire. Provider backups follow their own deletion cycles. Support correspondence is kept for the time needed to resolve the enquiry and comply with applicable record-keeping or legal-claim periods, then deleted. Firebase and Google control their own connection and purchase-record retention under their policies.
Contact us to request deletion of diagnostic or support data. There is no Brew with Tom account to delete, and we cannot remotely erase a journal stored only on your device. Because reports do not contain an app-account identity, we may need proportionate information such as an event reference, app version and approximate incident time to locate a report; avoid supplying more personal information than necessary.
Your rights
Where applicable, you may request access, rectification, erasure, restriction, portability, or object to processing based on legitimate interests. You may complain to a supervisory authority, including the President of the Polish Personal Data Protection Office (UODO) or your local authority. Rights are subject to their legal conditions; we may need to verify a request proportionately. We do not use these data for automated decisions producing legal or similarly significant effects. The app is intended for adults of legal drinking age, not children.
Changes to this policy
This version describes the current integration, including automatic diagnostics. Material changes will be dated and communicated where required. A new privacy-policy version does not replace a consent request where consent is required.