🍷 Privacy Policy

Cavea app · Last updated: June 2026

  In short:
  Cavea does not collect, sell, or share any personal data.
  Your wine cellar data is stored on your device or in your own Google Drive or Dropbox
  space when you enable synchronisation.
  The developer has no access to this data.

1. Who are we?

Cavea is a personal wine cellar management app developed by Alain Benard.

The app is available on Android, Windows, and Linux.

Source code available on GitHub.

2. Data processed by the app

Cavea has no centralised server and does not collect user data. The app contains no advertising system, no behavioural analytics tool, and no marketing tracking mechanism.

The data processed by the app is exclusively what is required for managing your wine cellar:

Bottles and references.
Appellations.
Vintages.
Storage locations.
Purchase dates.
Tasting notes and ratings.

This information is stored in a SQLite database named cave.db.

App preferences (file paths, sync settings, user options) are stored locally on the device.

3. Local mode

Cavea can operate entirely in local mode.

In this mode, all data remains stored solely on the user's device and never leaves it.

No connection to Google Drive, Dropbox, or any remote server is required.

4. Google Drive (optional)

If the user enables shared storage mode, Cavea can access their Google Drive account via the official Google API to store and synchronise wine cellar data across multiple devices belonging to the same user.

4.1 Google data accessed

As part of this feature, Cavea accesses only the following data:

The Google account selected by the user during authorisation (email address, used solely to identify the authentication session).
The Cavea folder created or used by the app in Google Drive.
Files created and managed by the app in that folder (cave.db and technical lock files).

Cavea does not access any other files or folders in the user's Google Drive.

4.2 How Google data is used

Data accessed via Google Drive is used exclusively to:

Store the SQLite database containing wine cellar data.
Synchronise data across multiple devices belonging to the same user.
Create and manage technical lock files required for concurrent access consistency.
Ensure data integrity during synchronisation operations.

This data is never used for any other purpose.

4.3 Storage and sharing

Data remains stored exclusively in the user's own Google Drive space.

No data is transmitted, sold, rented, analysed, or shared with the developer or with any third party.

The developer has no technical access to files stored in the Cavea folder of the user's Google Drive account.

4.4 Google permissions

Cavea uses the Google Drive drive.file scope. This permission limits access to files created or managed by the app and does not grant access to the rest of the user's Google Drive content.

The user can revoke this permission at any time from their Google account security settings (myaccount.google.com/permissions).

5. Dropbox (optional)

Cavea can also use Dropbox as a shared storage space, as an alternative to Google Drive.

5.1 Dropbox data accessed

When Dropbox synchronisation is enabled, Cavea accesses only:

The Cavea folder created in the user's Dropbox space.
Files created and managed by the app in that folder (cave.db and technical lock files).

Cavea does not access any other files or folders in the user's Dropbox account.

5.2 How Dropbox data is used

Data is used exclusively for:

Storing the SQLite database containing wine cellar data.
Synchronising data across multiple devices belonging to the same user.
Managing lock files.

This data is never transmitted, sold, analysed, or shared with the developer or with any third party.

6. Data sharing

Cavea does not sell, rent, share, or transmit any user data to third parties.

No data is used for advertising, marketing, analytics, or profiling purposes.

The developer has technically no access to wine cellar data stored locally or in the user's cloud spaces.

7. Security

Data is stored in a standard SQLite file.

Data protection depends primarily on the security mechanisms implemented on the device or cloud account used by the user (PIN, system encryption, Google or Dropbox authentication, etc.).

Authentication tokens required to access cloud services are stored locally using the secure mechanisms provided by the operating system (Keychain on Android, Credential Store on Windows, libsecret on Linux).

8. Google API compliance

Cavea's use of data obtained from Google APIs is strictly limited to providing the features described in this privacy policy, in compliance with the Google API Services User Data Policy, including the Limited Use Requirements.

In particular, data obtained via Google APIs is never used for:

Advertising or marketing.
User profiling.
Training artificial intelligence or machine learning models.
Sale or transfer to third parties.
Any purpose unrelated to wine cellar data synchronisation.

9. Your rights

All data remains under the exclusive control of the user.

You can at any time:

Delete locally stored data.
Disable cloud synchronisation from the app's Settings.
Revoke Google Drive access at myaccount.google.com/permissions.
Revoke Dropbox access from your Dropbox account security settings.
Delete files stored in your cloud spaces.

10. Contact

For any questions regarding this privacy policy:

GitHub Issues

11. Changes

This policy may be updated with new versions of the app.

The date at the top of this page indicates the version currently in effect.