Cellar Book: Wine Inventory — Privacy Policy
Last updated: 2026-10-04
This privacy policy applies to the mobile app "Cellar Book: Wine Inventory" for Android:
- Google Play: package com.moon.winecellar, developer "janey-moon"
The app is developed and operated by Heekyung Moon (Google Play developer name: janey-moon).
Contact: ansgml2100@gmail.com
OVERVIEW
Cellar Book does not require an account. The app helps you keep an inventory of wine and other drinks, place bottles in racks or fridges you build, enter drinking windows, and record bottle openings. Your cellar record and label photos are kept in the app's storage on your device. The app also uses Google services for analytics, crash reporting, remote configuration, and advertising.
CAMERA, LABEL PHOTOS, AND NOTIFICATIONS
Camera: the app asks for camera access only when you tap "Take label photo" in the bottle editor, and then opens the system camera to take one picture. If you decline, you can still add bottles without a photo. Choose photo: the app opens the system photo picker, which needs no storage permission, and only the photo you pick is made available to the app. The app does not read, change, or delete other photos on your device.
A label photo you take or pick is saved as a JPEG in a "photos" folder in the app's storage, reduced so its longer edge is at most 1600 pixels (smaller photos are not enlarged), together with a small thumbnail for lists. The app deletes the intermediate resized copies it creates, but the camera or picker may leave a temporary copy of the original photo in the app's cache. Photos are not sent to the developer or to any analytics or advertising service.
Notifications: the app asks for notification permission only when you turn on "Monthly window reminder" in Settings. If allowed, it schedules local reminders on your device (on the 1st of each of the next 12 months, 10:00 local time) with a general message that opens the Drink window list; reminders do not contain bottle names or notes. If you decline, the setting stays off and the window list still works.
INFORMATION STORED ON YOUR DEVICE
The app keeps one cellar record containing: bottle lots (label name, drink kind and style, bottle size, vintage, producer, country, region, appellation, details, optional purchase cost and currency, optional drinking window, and a link to an optional label photo); each physical bottle and its rack position or "Unplaced"; racks and fridges (name, layers, positions, layout, zones and temperature notes); opening records (date, occasion, tasting note, optional score, and a copy of the lot name, kind, and size); records of bottles removed without drinking (bottle and lot IDs, the reason you chose — gift, broken, sold, or other — and the time of removal); a list of internal IDs of removed items so restores do not bring them back; and settings (home currency, manual exchange rates, and whether the monthly reminder is on). The default home currency is chosen from your device's region setting. Each new-lot or restock entry accepts 1–999 bottles; this entry limit does not cap the total inventory.
To protect against data loss, the cellar record is written to two alternating files, so the previous version stays in app storage until the next change is saved; if a file cannot be read, a copy of it is kept for safety. The app may also store basic operating information such as app-use count, whether the review prompt was shown, and cached advertising and More Apps configuration.
The app reads developer-controlled advertising settings and a More Apps list from Google Cloud Firestore and loads app icons from internet addresses in that list. It does not write to Firestore or send your cellar record or photos to the developer. Google services process technical data as described below.
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information, such as app launches, the launch screen view, a session count, review prompts and menu actions, the More Apps list being opened, launch ad displays, ad revenue events, app version, device type, and app-instance identifiers. Event parameters do not include bottle names, notes, prices, scores, or photos.
Google Firebase Crashlytics may process crash reports and related technical information needed to diagnose app problems.
The app shows ads through Google AdMob: an app-open ad (at launch and when you return to the app), an interstitial ad that may appear shortly after you save a bottle lot or record an opening, a banner ad, and a native ad in the close-app dialog. Google may process advertising identifiers and device, app, consent, network, and ad-performance information to provide and measure ads, and may use an IP address to estimate an approximate location even though the app has no location permission. Banner ads are shown only on the Bottles screen when no form or sheet is open. Apart from the app-open ad that can appear while the launch screen is showing, the app does not start a full-screen ad (app-open or interstitial) while a bottle, rack, or opening form, the menu, or the settings, record, or backup sheet is open, or while a photo, backup, share, or restore step is running.
PERMISSIONS AND ADVERTISING CHOICES
Feature permissions: camera (label photos) and notifications (monthly reminder). The app also declares the vibration permission, which Android grants without asking, for short haptic feedback when you tap main buttons and when a change or backup is saved. The app does not request location, microphone, contacts, or storage access.
At launch, Google's consent message (UMP) is shown first where required (for example in the EEA and UK). Ads are requested only after this step. Personalized ads are used only where consent is not required or your choice allows personalized advertising; otherwise ads are non-personalized. If the step completes and your choice does not allow ads to be requested, the app does not request ads. If the consent step fails (the consent information or message cannot be loaded, or your saved choice cannot be read), the app requests non-personalized ads only.
Where Google requires it, the app menu shows "Privacy choices", which reopens the consent message so you can change your choice; ads then follow the new choice. If that message cannot be opened, the app stops requesting new ads until it is next started. You can change camera and notification permissions in your device Settings at any time.
STORAGE AND YOUR CONTROL
Bottle detail: "Restock" adds unplaced bottles to the existing lot. "Remove without drinking" removes a bottle with a reason and does not create a tasting record. "Delete" removes the lot and its physical bottles; its opening records and remove-without-drinking records remain. Rack editor: "Remove rack" asks for confirmation and moves the rack's bottles to Unplaced. Settings: you can remove individual exchange rates and turn the reminder off, which cancels its scheduled notifications. The app has no in-app control to delete individual opening records or remove-without-drinking records.
Label photos: when the app starts and after each successfully saved change, the app deletes label photos and thumbnails in its "photos" folder that no current lot uses. A photo still used by another lot, a photo in an editor that is still open, and a photo from an import that is still in progress are kept. A newly taken or picked photo that you discard by closing the editor, replacing it, or removing it is deleted, or by a later cleanup if it cannot be deleted right away. This cleanup is skipped while a photo, backup, share, or restore step is running and is retried later; if the app cannot confirm that a change was saved, photo deletion waits until the cellar record is next read or saved successfully. Copies of photos inside backup or import sets are removed only when those sets are deleted.
Backups: "Create multipart backup" writes a new set of files to a "backups" folder in app storage. The set contains the full cellar record described above (including opening records, remove-without-drinking records, and settings) and the label photos linked to current lots. When the app starts and after each successfully saved change, unless a photo, backup, share, or restore step is running, the app keeps the three most recent backup sets and the three most recent import sets in app storage and deletes older ones, so a newly created set can make a fourth until that cleanup runs. Files shared or saved elsewhere are outside this cleanup. "Share backup files" passes each file to the system share sheet; the files are not encrypted, and the app or person you choose controls what they receive. When you import a backup, the selected files are copied into the app's cache, where the app does not delete them, and into an "imports" folder in app storage; the data is merged with your cellar, and the backup's settings replace your current settings.
To remove the app's local data, clear the app's storage in Android Settings or uninstall the app. Local data, including label photos and backup files in app storage, may be included in a Google or device backup depending on your backup settings (the Android app allows system backup). Uninstalling normally removes the active copy but may not remove an older backup, and files you shared or saved elsewhere are not affected.
For saved cellar records, use the app controls and your device's storage and backup settings; exported copies are managed wherever you kept them. For questions about data processed by Google, or to ask us for help with a privacy request, contact us at the address below.
We use these services under their applicable terms, and we ensure that third-party service providers with whom we share user data provide the same or equal protection of that data as stated in this policy. Data processed by Google is retained according to its service settings and policies:
- Google Privacy Policy: https://policies.google.com/privacy
- Firebase privacy information: https://firebase.google.com/support/privacy
- Google advertising technologies: https://policies.google.com/technologies/ads
SECURITY
Your cellar record, label photos, and backup files are kept in the app's private storage, which Android protects from other apps; they are not separately encrypted by the app, so protect your device with a screen lock. Backup files you share are readable by whoever receives them. Google services process analytics, crash, and advertising data; shared files and system backups are handled as described above. Communication between the app and Google services uses encrypted connections (HTTPS/TLS). No method of storage or transmission is completely secure, but we limit what the app handles to what is described in this policy.
IMPORTANT NOTICE
Cellar Book is an inventory and record-keeping tool. Drinking windows are years you enter; the optional style-table suggestion for some wines is a broad guide, not a prediction for a particular bottle. Purchase cost totals use only the amounts and exchange rates you enter and are not market values. The app does not judge the condition, safety, or authenticity of any bottle. Drink responsibly and follow the alcohol laws where you live.
CHILDREN
The app is intended for adults of legal drinking age and is not directed to children. We do not knowingly collect personal information from children.
CHANGES
We may update this policy if the app or its services change. The date above shows the latest revision.
CONTACT
Heekyung Moon (Google Play developer: janey-moon)
Email: ansgml2100@gmail.com