Request deletion of your Sprout account and cloud data
1. Who this policy covers
This policy describes how Sprout, the gratitude journal from Siam Soft Labs, handles information. The developer is Ruslan Grigorev, Kazakhstan. For privacy questions and requests, email siamsoftlabs@gmail.com.
Sprout lets you write gratitude notes, record how your day felt, grow a monthly plant, request AI reflections, and back up your journal after signing in with Google. This policy applies to those features, not to other Siam Soft Labs applications.
2. Your journal on your device
Your entries, moods, dates, monthly plants, saved reflections and preferences are stored on your device. Writing a journal entry does not by itself submit that entry for AI analysis. If you enable cloud backup, your journal can be uploaded as part of a backup, including automatically while that feature is enabled.
Local information remains until you remove it through the available app controls or clear the app's local data. Copies you export or share are separate files; removing the original entry does not remove those copies.
3. Google sign-in and cloud backup
If you sign in with Google, Sprout processes your Google account identifier, email address, email verification status and display name. These details connect your account to your backups and access rights. Sprout does not receive your Google password.
When you enable cloud backup, a snapshot is sent to our server. It can contain your journal entries and moods, dates and monthly cycles, plant data, saved reflections, preferences, and the information needed to restore your premium or sample state.
The active backup store keeps up to 30 most recent snapshots per account. Older snapshots are removed from that store when a new snapshot exceeds this limit. This is a count of copies, not a 30-day expiry. Disabling backup or uninstalling the app does not itself delete copies already on the server.
Backups travel over HTTPS. They are stored in a form the service can return to your authenticated account; they are not end-to-end encrypted. Access is restricted by account authentication.
4. AI reflections
When you request a weekly or monthly reflection, the relevant journal material is sent to our backend and then to OpenAI for processing. That material can include entries, moods, dates and context for the selected period. The app asks you to acknowledge this processing before requesting a reflection.
The generated reflection is returned to the app and can be saved locally and included in a cloud backup. The backend also caches generated results to handle repeated requests. These cached results are not automatically erased when a response is returned.
OpenAI applies its own API data controls and retention rules. See OpenAI's API data controls. Avoid submitting information about other people unless you have an appropriate basis to do so.
5. Purchases, service operation and support
- Purchases: Google Play handles Android payments. RevenueCat helps manage purchase status and entitlements and provides subscription analytics using an app user or installation identifier, purchase records and technical device information. Sprout does not receive your full payment card details.
- Service operation: our hosting and application systems process connection information, such as IP addresses, request times, routes, response status and technical error information, to operate the service and investigate failures or abuse.
- Support: when you email us, we receive your email address and the information you choose to include. Do not send passwords, sign-in tokens or payment card details.
6. Service providers and international processing
Data is handled by providers needed for the feature you use: Google for sign-in and Google Play purchases, OpenAI for AI reflections, RevenueCat for subscriptions, OVHcloud for our hosted backend and account backups, and Cloudflare R2 for encrypted disaster-recovery archives. Your data may be processed outside your country of residence.
Provider information is available in Google's Privacy Policy, OpenAI's Privacy Policy, RevenueCat's Privacy Policy, OVHcloud's data protection information and Cloudflare's Privacy Policy.
7. Account deletion and data retention
To request deletion of your Sprout account and associated cloud data, email siamsoftlabs@gmail.com with “Sprout data deletion” in the subject. Send the request from your linked Google email where possible. We may need to verify that the account is yours. You do not need to attach your journal.
We handle deletion requests manually. After verifying ownership, we remove the account and its associated data from our active systems, subject to any lawful retention requirements. We will tell you if additional information is needed, explain any data that must be retained, and confirm when the request has been completed. We process requests without undue delay and within any applicable legal deadlines.
Local journal data, server backups, account information, generated-result caches and service logs have different lifetimes. The 30-snapshot rule applies only to the active backup store. It does not set a time limit for account records, service logs, provider records or disaster-recovery backups.
The scheduled disaster-recovery system is configured to retain one encrypted archive for each of the seven most recent backup dates. Older archives in that rotation are removed when a new backup completes. This is not a promise of deletion after seven calendar days: if backups stop, the existing archives can remain longer.
Encrypted recovery archives can contain earlier copies until they are removed through this rotation. Service providers also apply their own retention requirements; where applicable, we request deletion of associated data they process on our behalf.
Signing out removes the saved sign-in on your device and disables cloud backup. It does not delete your account or cloud data. To request their deletion, use the email address above.
Removing the app, signing out, disabling backup and cancelling a subscription are separate actions. None automatically requests deletion of all server-side data. Purchase records held by Google Play or RevenueCat may need to be handled under their own policies and applicable record-keeping obligations.
8. Permissions and your choices
You can use the local journal without enabling cloud backup, decide whether to request an AI reflection, and manage available notification and photo-library permissions in your device settings. Saving or sharing a plant image happens when you choose that action. Any recipient or app you share it with handles its own copy.
Depending on applicable law, you may have rights to access, correct, delete or receive your information, or object to certain processing. Send requests to siamsoftlabs@gmail.com. You may also contact your local data protection authority.
9. Changes and contact
Changes to this policy will be published here with an updated date. Material changes to how a feature handles your data should be communicated before that changed processing begins.
Developer: Ruslan Grigorev / Siam Soft Labs, Kazakhstan.
Email: siamsoftlabs@gmail.com.