Terms of Service English / 日本語 Get the App
PRIVACY POLICY

Privacy Policy

Last updated: October 17, 2026 (English edition; corresponds to the Japanese edition last updated October 6, 2026) · Esquisse Works (“we” or “us”) sets out this Privacy Policy regarding the handling of users’ personal information in Cave Note, a wine journaling app (the “App”).
Label photos are sent to AI
To read the wine’s details, label photos are sent to an external AI service (Google).
Location data is stripped on your device
Information contained in the photo itself, such as the shooting date and time and the shooting location (GPS), is removed on your device before the photo is sent. However, for records with “Save location” turned on, the coordinates read from the photo are saved separately as numbers. This setting is on by default, and you can switch it for each record or for all records at once in Settings.
No sharing, no ads
What you record is never made visible to other users. We serve no advertising and do not track you across other companies’ services.

1Information We Collect

The App collects the following information.

Account informationEmail address, and the identifier and display name provided by the authentication provider (Google, Apple)
Label photosImages of wine labels taken with the camera, or images selected from your photo library
Recorded dataWhat you record yourself: producer, wine name, vintage, region, grape varieties, type, importer, rating, price, place of purchase, date drunk, tasting notes, and so on
Location informationFor records with “Save location” turned on, the coordinates (latitude and longitude) indicating where the record was made. If you photographed the label in the App, this is the position measured at the time of shooting; if you chose a photo from your photo library, it is the shooting location originally recorded in that photo. For details, see “4. Location Information for Where You Drank”
Scan historyThe date, time and result of each analysis, the identifier of the AI model used, the confidence for each field read, the processing time, and the number of scans this month
Monthly recapIf you turn on the monthly recap, the title and text generated from that month’s records, and the identifier of the single most memorable wine of that month
Purchase historyThe status of purchases, renewals and cancellations of products purchased in the App (the type of product, the purchase date, the end date of the period, and the purchase identifier issued by the store). Credit card numbers and other payment information are handled by the App Store and Google Play, and we do not receive them
UsageEvents for screens viewed and major actions (creating, updating and deleting records; starting a scan and its result). A pseudonymized user ID is used to identify users; names and email addresses are not sent. For details, see “8. Usage Measurement and Error Reporting”
Error informationWhen the app crashes or encounters an error: the content and location of the error, the OS and app versions, and the device model. For details, see “8. Usage Measurement and Error Reporting”
Notification tokenFor a device on which you have turned on push notifications, the identifier the OS issues so that notifications can be delivered to that device (an FCM registration token), together with the OS type, the app version and the OS version. The content of label photos, Recorded Data and tasting notes is not used to deliver notifications. For details, see “About push notifications” below
InquiriesThe type you select, the message text and the reply email address you submit through in-app contact (Settings → Contact us). The app version and OS type are sent along with it for investigation. If you send an inquiry with the reply address left blank, we do not store a reply address and do not send a reply
Access logs, etc.Information recorded automatically in providing the service, such as IP address and the OS and app versions

The App may ask for permission to use your device’s location. There are two purposes, both related to “where you drank.” One is the location information in the table above, that is, keeping with a record the place where the label was photographed. The other is showing your current location on the map; this is only drawn on screen and is neither stored nor sent, so it is not included in the table above. We ask only for location access while you are using the App. For details, see “4. Location Information for Where You Drank.” The App does not access your contacts, calendar or the like. Access to the camera and the photo library is used only to photograph and select labels.

About push notifications. The App may send push notifications. They are off by default. Only when you turn them on in Settings do we ask for the OS’s notification permission and store the notification token in the table above on our servers. A token points to your device as a destination; we do not use it to serve advertising or to track you across other companies’ apps or websites. We send only announcements from the App and important notices, and a notification carries only a title, a body and a type indicating which screen to open. If you turn notifications off in Settings, or turn off the App’s notifications in your device settings, that device is excluded from sending. The same applies if you delete the App.

2How We Use Information

—Providing the App’s service and realizing its features (reading labels; saving, searching and tallying records)
—Storing Recorded Data and restoring it, including when you change devices
—Recording where you drank and looking back on the map (only for records with “Save location” turned on)
—Showing your current location on the map and the approximate distance to a recorded place
—Generating the text of the monthly recap (only for users who turn it on)
—Improving reading accuracy and response time, and investigating problems
—Counting the images analyzed by label recognition and managing the free usage allowance
—Identity verification and preventing unauthorized use
—Delivering push notifications of announcements and important notices (only to devices with notifications turned on)
—Responding to user support requests

3Label Photos and AI Analysis

Reading labels, the App’s central feature, is performed using an external AI service. Label photos that you photograph or select are handled as follows.

(a)Preprocessing on your device. Before sending, the photo is reduced in size and rebuilt as a JPEG on your device. As a result, the metadata contained in the original image (Exif), such as shooting date and time, shooting location (GPS) and device information, is not carried over. By the time a photo reaches our servers, it does not contain this information.
(b)Sending to Google. To read the text on the label and organize it into fields such as producer, wine name and vintage, the photo is sent to the Gemini API of Google LLC. For labels whose wine cannot be identified by reading the text alone (for example, labels with only a stylized title or a picture), we cross-reference information on the web, also through the Gemini API. In the course of this cross-referencing, words and phrases describing the label’s features may be used in searches.
(c)Not used for training. This transmission is made through an API that we have contracted for business use. The photos and reading results we send are not used by the provider to train generative AI models.
(d)Storage of the photos themselves. After analysis, the photo is kept in Supabase storage as the image attached to your record, with access controls so that only your own account can view it. Other users and third parties cannot view it.

Please refrain from sending photos in which anything other than a label appears (such as people or documents that could identify an individual). Only labels are meant to be read, and we do not intentionally analyze any other subject.

About the monthly recap. Only if you turn it on in Settings, in order to create a short text (a title and body) from the previous month’s records, the content of that month’s records is sent to the Gemini API of Google LLC. Until you turn it on, and after you turn it off, this transmission is not made. What is sent is the brand, producer, region, grape varieties, type, vintage, rating, date drunk, taste tags and tasting notes, plus a price band (a category such as “under ¥2,000,” not the specific amount). We do not send photos, location information (coordinates, or the text of the place of purchase or where you drank), record identifiers, email addresses, or any other information that identifies the user. As with label photo analysis, this transmission is made through an API that we have contracted for business use, and the content sent is not used by the provider to train generative AI models. The generated text is stored on our servers together with your records, and is erased along with them when you delete your account. Even if you turn the recap off, text that has already been generated remains.

4Location Information for Where You Drank

The App lets you keep a record together with “where you drank” and look back on it on a map. The location information handled here is of two kinds with different natures. One is the “where you drank” coordinates saved with a record ((a) to (d)). The other is the device’s current location, used only to show your position on the map and not stored ((e)). Communication for the map itself is described in (f).

(a)There are two sources. When you photograph a label in the App, the device’s location is measured at the moment of shooting, and that single point is treated as “where you drank.” When you choose a photo from your photo library, the shooting location originally recorded in that photo (Exif) is read on your device. The record screen shows the source: “From where you shot it” for the former and “From photo location” for the latter. We ask for permission to use location for this measurement the first time you press the shutter while “Save location” (see (c) below) is still on. We do not ask merely because you opened the scan screen. If you do not grant permission to use location, or if a photo has no shooting location, no coordinates are obtained (the record itself can still be created as before).
(b)Only two numbers are saved. The latitude and longitude that are read are stored in an area separate from the record itself, with access controls so that only your own account can view them. We never put the coordinates back into the photos sent to our servers (as described in “3. Label Photos and AI Analysis,” Exif is removed before sending). We do not round or blur the coordinates. However, if you have turned on the setting that also saves photos taken in the App to your device’s camera roll, the photos that remain on the device carry the shooting location, just as with an ordinary camera app (only when “Save location” in Settings is on). Those photos stay on your device and are not sent to us.
(c)The default is “save.” “Save location” on the record screen is on by default, and the coordinates are saved when you create a record from a photo that has a shooting location. If you do not want to keep them, turn this switch off for each record, or change the default itself to “don’t save” in Settings. For records you have already saved, you can also remove the coordinates by turning the switch off on the edit screen and saving.
(d)There is no outlet. We do not provide the coordinates to third parties and do not use them for advertising. They are not included in CSV exports or in usage measurement (“8. Usage Measurement and Error Reporting”). They are never made visible to other users.
(e)Showing your current location (not stored). The map can show a mark for where you are now. For this display, the App may ask for permission to use your device’s location. We ask for this purpose only when you press the current-location button on the map. We never ask when the App launches (for the permission to keep where a label was photographed with a record, see (a); the location permission is shared, so answering it once applies to both purposes). The current location that is read is used only to draw the mark on the map and to show the approximate distance to a recorded place, and is neither stored nor sent. It does not reach our servers, and is not included in CSV exports or usage measurement. When you leave the map screen, it does not remain on your device either. If you do not grant permission, you can still use the map and your records as before. You can revoke permission at any time in your device settings. We ask only for location access while you are using the App, and we do not collect location in the background.
(f)About displaying the map. When the map is displayed, map images (tiles) corresponding to the visible area are fetched from OpenFreeMap. This communication carries the approximate visible area and your IP address, but does not transmit the content of your records or the coordinates themselves. In addition, when a place is shown as an address, the coordinates are passed to the address lookup function built into the OS (provided by Apple on iOS and by Google on Android). This conversion is performed by your device’s OS and does not go through our servers.

If you keep recording wines you drink at home, your home’s location can be inferred from the saved coordinates. If you want to avoid this, change the default to “don’t save” in Settings as described above.

5Disclosure to Third Parties

We do not provide users’ personal information to third parties except in the following cases.

—Where the user has consented
—Where disclosure is required by law
—Where it is provided to a contractor necessary for providing the service (the service providers in the next section)

We will not make what you record visible to other users, nor provide it to third parties for advertising.

6Service Providers We Use

The App uses the following external services, and the information obtained is processed and stored on these contractors’ servers (which may be located outside Japan). Please also review each service’s privacy policy.

SupabaseDatabase, authentication and photo storage
supabase.com/privacy
GoogleReading wine details from label photos and identifying the wine (Gemini API), usage measurement (Firebase Analytics), delivery of push notifications (Firebase Cloud Messaging), and authentication with a Google account
policies.google.com/privacy
AppleAuthentication with an Apple account, and delivery of push notifications to iOS devices (Apple Push Notification service)
apple.com/legal/privacy
RevenueCatConfirming and managing the status of products purchased in the App (RevenueCat, Inc.). Only a pseudonymized user ID and purchase information are sent; Recorded Data, label photos and email addresses are not
revenuecat.com/privacy
SentryRecording and investigating crashes and errors in the App (Functional Software, Inc.)
sentry.io/privacy
OpenFreeMapDelivery of map images (tiles). The content of your records and the coordinates themselves are not sent
openfreemap.org

On our website (including this page), we use Google Analytics to understand how the site is accessed. Google Analytics collects anonymous traffic data using cookies and similar technologies. For details, please see How Google uses information from sites or apps that use its services.

7Data Storage and Retention

User data is stored on Supabase’s cloud servers. We take appropriate security measures to protect the data, but we do not guarantee the complete security of transmission over the Internet.

Recorded Data and photos are kept until the user deletes them. A record deleted in the App is kept in the Trash for 30 days, after which it is automatically erased, photos included. Data that you do not restore from the Trash cannot be recovered. If you delete your account, all records, photos and scan history are erased.

8Usage Measurement and Error Reporting

To improve quality, the App sends information on how its features are used to Firebase Analytics. What is sent is a pseudonymized user ID, the screens viewed, and events for actions such as creating, updating and deleting records and starting a scan and whether it succeeded. We never send your name, email address, label photos or the content of what you record.

When the App crashes or encounters an error, we send the details to Sentry in order to investigate the cause. What is sent is the content and location of the error, the OS and app versions, and the device model. We never send your name, email address, IP address, label photos or the content of what you record. This transmission is made only in versions distributed through the stores.

We do not use this information for advertising purposes, and we do not track users across other companies’ apps or websites (tracking). At present, the App has no setting that stops only these transmissions individually. If you wish to stop them, please delete the App from your device.

9Your Rights

View and correctYou can check and edit what you have recorded in the App at any time. If an AI reading result is wrong, you can also correct it from the record screen
Take your data with youYou can export your Recorded Data in CSV format from Settings
DeleteYou can delete individual records in the App. You can delete the account itself from Settings, and all records, photos and scan history are erased. Deleted data cannot be restored. For the procedure if you have already deleted the App and for the scope of data erased, see Delete Your Account
ContactFor questions about how your data is handled, please contact us at the address below

10Use by Minors

The App is intended for keeping records about alcoholic beverages and is not intended for use by anyone under 20. We do not intentionally collect personal information from children under 13.

11Changes to This Policy

We may change this Policy as needed. If there is a significant change in how information is handled, such as the addition of a recipient of photos, we will notify you in the App or on this website.

12Contact

For questions about this Policy, please contact:

Esquisse Works
Email: [email protected]

This is an English translation of the Privacy Policy originally written in Japanese. If there is any discrepancy between the Japanese version and the English version, the Japanese version shall prevail.