Imaginelle Labs ("we", "us", "our") operates the Sayvour mobile application ("App"). This Privacy Policy explains what information we collect, how we use it, and your choices regarding your data.

We believe in transparency and minimal data collection. Sayvour is designed to keep your food diary on your device. We do not require user accounts, and we do not sell your data to third parties.

1. Information We Collect

1.1 Data Stored Locally on Your Device

The following data is stored only on your device and is never stored on our servers:

  • Food diary entries: Meal names, descriptions, portion estimates, nutrition information, and timestamps for entries you log
  • Nutrition data: Calorie and macronutrient estimates computed from your logged meals
  • App settings: Your preferences such as daily nutrition goals, units, and notification times, and the profile data needed to calculate your calorie requirements, such as your age, sex, height, weight and activity level

This data remains on your device. It is not stored on our servers, and we cannot access it.

1.2 Data Processed When You Log a Meal

When you log a meal, the description you give is sent anonymously to our AI processing service, run on our servers, to work out what you ate and estimate its nutrition. Depending on how you log, that is:

  • Voice: Your audio recording is sent for transcription. It is processed in real-time and not stored after processing.
  • Meal description text: The transcribed or typed text of your meal is sent to an LLM (large language model) service to infer meal content and nutritional information. This text is not stored after the response is returned.
  • Photos: A photo of your plate or of a nutrition label, if you choose to take one, is sent for the same purpose. The photo is processed in real-time and not stored after the response is returned.
  • Saved foods: To match a meal against foods you have saved in the App, the names of those saved foods may be sent alongside the description. They are not stored after the response is returned.

1.3 Google Drive Backup (Optional but Highly Recommended)

If you choose to back up your food diary to Google Drive:

  • Google account: You will need to sign in with your Google account. We do not create or store a separate user account.
  • Backup data: Your food diary database is uploaded to your personal Google Drive and remains there until you delete it. We do not maintain copies on our servers.
  • We use a limited Google Drive scope that restricts our access to only files created by Sayvour. We cannot read other files in your Drive.

This feature is optional but highly recommended. The App functions fully without it. However, because your food diary is never stored on our servers, we cannot restore it if it is lost, for example if your phone is lost or reset, or the App is uninstalled. A Google Drive backup is the only way to recover it.

1.4 In-App Purchases

If the App offers paid features, purchase transaction data is processed by Apple or Google and their payment processing partners to verify and manage your purchase status. We do not directly handle or store payment information. Subscription status is managed for us by RevenueCat, which receives purchase information from Apple or Google and assigns your installation an anonymous identifier. That identifier is a random string; it is not your name, email address, or device serial number.

1.5 Usage Record on Our Servers

To enforce fair-usage limits and to understand how the App is used, our servers keep a usage record linked to the anonymous identifier described in 1.4:

  • The anonymous identifier itself
  • Your plan and its history, the store it was bought from, and your billing dates
  • How many meals you log and labels you scan, and by which method (voice, typing or photo)
  • When you use the App: the days you log, and your first and most recent log
  • Which features you use, your progress through setup, and streak milestones
  • The date of your last backup, any answer you give to our one-question survey, and your App version and platform

This record contains no information about what you ate, and no profile or progress details, such as your weight log or calorie intake trends. Meal descriptions, photos, nutrition results, your profile, your weight log and your calorie trends are never stored on our servers. We also keep daily totals of logs across all users with no identifier attached, which we use to understand how the App is used.

Our servers also see your IP address when the App connects and use it briefly to limit request rates. We do not store it.

1.6 Data We Do NOT Collect

  • We do not collect your name, email address, or phone number
  • We do not track your location
  • We do not use analytics or advertising tracking SDKs
  • We do not collect device identifiers for advertising purposes
  • We do not read your contacts, photos, or other personal files
  • We do not store your voice recordings, photos, meal descriptions or food diary data on our servers
  • The App is not directed at anyone under 18, and we do not knowingly collect data from anyone under 18

2. How We Use Your Information

We use the limited data we process to:

  • Provide meal logging: Converting your spoken, typed or photographed meal into a food diary entry with estimated nutrition information
  • Enable cloud backup: Saving and restoring your food diary to your personal Google Drive (only when you initiate it)
  • Manage purchases: Verifying your purchase status for any paid features
  • Apply plan allowances: Counting your meal logs and label scans against your plan's allowance, using the usage record described in 1.5
  • Prevent abuse: Rate-limiting processing requests to maintain service quality
  • Understand usage: Looking at usage totals to see how the App is used and to plan its capacity

3. Third-Party Services

The App uses the following third-party services, each governed by their own privacy policies:

  • AI processing providers — Transcribe your voice input and infer meal content and nutritional information from text and photos. Audio, text and photos are processed in real-time and not retained.
  • Cloudflare — Runs our servers and stores the usage record described in 1.5. Cloudflare's privacy policy
  • RevenueCat — Manages subscription status and provides the anonymous subscription identifier described in 1.4. RevenueCat's privacy policy
  • Google — Google Drive and Google Sign-In for optional backup and restore. Google's privacy policy
  • Apple / Google — Process in-app purchase transactions where applicable. Subject to their respective privacy policies.

4. Permissions

The App requests the following device permissions:

  • Internet: Required. Every meal log, label scan, purchase check and backup goes through our servers. Without internet access you can view your diary but cannot log.
  • Microphone: Required for voice logging. Audio is only captured when you tap the record button; the App does not record in the background. Without it you can still log by typing or by photo.
  • Camera: Required for photo logging and nutrition label scanning. A photo is taken only when you choose to take one. Without it you can still log by voice or by typing.
  • Notifications: Optional. Used for meal reminders and progress notifications at times you choose. You can disable them in your device settings at any time.

5. Data Storage and Security

  • Local storage: Your food diary is stored in a local database on your device, protected by your device's built-in security (screen lock, device encryption).
  • Data in transit: All network communication uses HTTPS encryption.
  • Voice data: Audio sent for processing is transmitted over HTTPS and is not stored after the response is returned.
  • Google Drive backups: Protected by your Google account security. We use a limited Drive scope that restricts access to only files created by Sayvour.

6. Data Retention

  • Local data: Retained on your device until you delete it within the App or uninstall the App.
  • Voice recordings: Not retained. Processed in real-time and immediately discarded.
  • Google Drive backups: Retained in your Google Drive until you delete them. We do not maintain copies.
  • Purchase records: Managed by Apple and Google per their retention policies.
  • Usage record (1.5): Kept for as long as the App is offered, so that your allowance is enforced and your usage history is available if you return. While you have an active subscription, the record is needed to provide the service and cannot be deleted. Once your subscription has ended, or if you never subscribed, it is deleted on request (see Section 7).

7. Your Rights and Choices

You have full control over your data:

  • Access: All your food diary data is visible within the App at all times.
  • Delete: You can delete individual entries, or all data, at any time within the App. Uninstalling the App removes all locally stored data. Deleting data within the App or uninstalling it does not remove the usage record on our servers described in 1.5.
  • Usage record: Once your subscription has ended, or if you never subscribed, you may request deletion of the usage record held on our servers by writing to the address in Section 10. We will respond with the information required to identify the record, and will confirm to you once it has been deleted. While a subscription is active, the record is required to administer your allowance and cannot be deleted.
  • Permissions: You can revoke any permission at any time through your device settings.
  • Backup control: You choose whether to enable Google Drive backup. You can delete backups from your Google Drive at any time and revoke the App's access via your Google account settings.
  • Notifications: You can disable notifications at any time through your device settings or within the App.

8. International Data Transfers

When you log a meal, your audio, text or photo may be processed on servers located in the United States. The usage record described in 1.5 is stored on Cloudflare's infrastructure, and subscription status is managed by RevenueCat, both of which may process data in the United States. By using the App, you consent to these transfers for the purposes described in this policy. Meal data is not stored after processing.

9. Changes to This Policy

We may update this Privacy Policy from time to time. The current version is always the one published on this page, and the "Last updated" date at the top shows when it last changed. We do not send individual notices of changes, so we encourage you to review this page periodically.

10. Contact Us

If you have questions or concerns about this Privacy Policy or your data, please contact us at:
support@imaginelle.ai