CookSync - Privacy Policy
CookSync is designed as an offline-first Android application. Data created in the app remains on the user's device and is not sent to servers operated by Nuvement.
1. How CookSync works
CookSync coordinates the preparation of multiple dishes through local scheduling, cooking sessions, countdowns and Android notifications. The current version does not require an account and does not use a Nuvement backend or Nuvement cloud services for the app to operate.
2. Data stored on the device
Information entered or generated by the user, such as dishes, preparation steps, meals, kitchen configuration, schedules, sessions and history, is stored locally in the app's private storage, primarily in a SQLite database.
This data may include information freely chosen by the user in names and descriptions. Nuvement does not receive this content and cannot access it remotely.
When the user chooses to create a manual backup, selected data is written to a JSON file in a location chosen by the user.
3. Collection, transmission and sharing
CookSync does not use user accounts, analytics, advertising, profiling or Nuvement cloud services. The app does not transmit user-created content or usage data to Nuvement or third parties.
The app uses third-party software components for local technical functions such as database storage, notifications, timezone handling and app version information. CookSync does not use these components to send user data to analytics or advertising services.
If a user chooses to save or share a manual backup through Android, this is a user-initiated action. The selected storage provider or receiving app may process the file under its own privacy policy. CookSync does not automatically send backup data to Nuvement or third parties.
4. Notifications and Android permissions
CookSync may use local notifications and exact alarms to provide cooking reminders. It may also use Android system events, such as device restart, to restore scheduled notifications. These functions operate locally on the device. Notification permissions are optional and denying them does not prevent Cooking Mode from working.
5. Backup and device-to-device transfer
CookSync does not use automatic cloud backup or automatic device-to-device transfer. The Android configuration explicitly excludes application databases, preferences and files from the backup and transfer features managed by the operating system.
Users may voluntarily create a local JSON backup from the app and save it in a location they choose or share it through an Android app. A backup contains dishes and preparation steps, saved meals and kitchen configuration. It does not contain cooking sessions, countdowns, notifications, history, history retention settings or planning times.
Backup files are not encrypted. Anyone who receives a file can read its contents. A user may manually import a backup into CookSync; this replaces the local dishes, saved meals and kitchen configuration. Import is not available while a cooking session is active.
CookSync does not automatically transfer data to another device. Any transfer using a backup file is a manual action chosen by the user.
6. Retention and deletion of local data
Local data remains on the device until the user deletes it through available app features, clears the app's data in Android settings, or uninstalls CookSync. Because Nuvement does not hold a remote copy of local data, Nuvement cannot recover or delete it remotely.
A manual backup remains in the location selected by the user until the user deletes it or that storage provider removes it. Nuvement cannot access or delete backup files.
7. Email communications
If a user voluntarily contacts Nuvement by email, Nuvement receives the information included in the message and uses it only to handle and respond to the communication. This information is not collected by CookSync.
This processing is based on Nuvement's legitimate interest in handling the communication. Correspondence is kept only as long as reasonably necessary, or longer where required by law. The email provider may process data under its own privacy policy.
8. Rights and control over data
For data stored exclusively on the device, control remains with the user through CookSync and Android features. Nuvement cannot access this data remotely.
For personal data provided directly to Nuvement, users may exercise their applicable data protection rights by contacting Nuvement using the address provided in this policy. Users also have the right to lodge a complaint with the competent supervisory authority.
9. External services and platforms
Distribution and installation of the app may involve Google Play and Android services on the device. These services are provided by third parties and operate under their own policies and terms. This policy describes the behavior of CookSync and services directly operated by Nuvement.
10. Changes to this policy
This policy may be updated when the app's features, data practices or applicable requirements change. The published version will always show the date of the latest update.
11. Controller and contact
CookSync is published under the Nuvement brand. The contact person and controller for any processing described in this policy is Antonio Cirillo, Italy.
For privacy-related requests: nuvement.apps@gmail.com.