Contents
Information we receiveLocal storage and backupPhotos and the timerPurchasesGoogle Play Billing diagnosticsFiles you exportRetention and deletionExternal pages and supportUpdates and contactAndroid · Updated 3 October 2026
StackWorks explains how information is handled in the Android app Brew Lab.
Information we receive
The app has no account registration or ads. We do not use our own analytics or tracking service, or send the contents of your records to our servers. Google Play Billing sends technical diagnostic information to Google as described below.
Local storage and backup
The app handles bean names, roasters, origins, roast dates, stock and photos; brew dates, coffee and water amounts, temperature, grind, taste, ratings and notes; custom recipes and settings in its on-device storage. It does not sync records to our servers or the cloud. Android automatic backup is disabled in the app configuration.
Photos and the timer
When you attach a bean photo, Android’s photo picker lets you select the photo. The app copies only that selection into private storage; it does not read your whole photo library.
A brewing timer started by you uses an ongoing notification to show time, steps and pour cues. You can pause, finish or cancel it from the app. We do not use server push notifications. Optional spoken guidance uses the Android text-to-speech engine configured on your device; the engine provider’s policies apply to its handling of information.
Purchases
Plus purchases and entitlement checks use Google Play Billing. The app communicates with Google Play about the Plus product, purchase status and purchase identifiers (purchase tokens). This information is used to process purchases and confirm or restore paid features. It is not sent to our servers or used for our own ads or behavioral analytics. We do not receive your payment-card information. Google Play’s terms govern payment and purchase information. Purchases from the iOS app do not transfer to this Android app.
Google Play Billing diagnostics
The Google Play Billing library sends technical diagnostic logs to Google, including API usage, success or failure, and billing-service connection results. Google uses this information to improve billing operation and performance and support errors. Logs may be sent during library initialization or billing-service connections and checks even if you do not make a purchase. There is no separate in-app switch to disable this SDK logging. The app does not pass the contents of bean or brew records, photos or notes into these diagnostic logs.
Diagnostic metadata includes the app package and version, the billing-library and Android version information, and a random session identifier generated when the SDK initializes a billing client. This identifies the billing-client session; it is not the device’s Android ID or advertising ID.
Google’s applicable policies govern its handling of information. About Billing library diagnostic logging
Files you export
When you choose to export or share, the file is passed to your selected destination or recipient. That service’s rules apply at the destination.
CSV and JSON backups are not password-encrypted. Photos are not included in JSON backups. They may contain your notes, so choose the destination and recipient carefully. JSON backups use this Android app’s format; they are not imports of the iOS app’s CSV files.
Retention and deletion
Records are kept on the device until you delete them. The app’s deletion tools remove bean or brew records. To remove all stored app data, including copied photos, clear its storage in Android settings or uninstall it. Deleted records cannot be recovered without a backup you keep.
Manually exported files and copies at a sharing destination are not removed by deleting app data or uninstalling. Delete unneeded files at those locations too. Google Play manages purchase information; deleting app records does not change your purchase or refund status.
External pages and support
External links, including support and official information, open in a browser and are governed by the destination’s privacy policy. Information you choose to include in a support email is used to answer your inquiry. Do not send unnecessary personal information or backup passwords.
Updates and contact
Changes to this policy will be published here.
StackWorks
contact@stack-works.dev