Levvi

Privacy policy

Last updated: September 25, 2026

Your privacy matters to us. This policy explains what information Levvi handles, why it is used, when it may leave your device, which providers are involved, and how to request access or deletion.

Available features vary by platform and app version. The handling described below depends on the features you choose to use.

1. About Levvi

Levvi is a personal organization app for tasks, routines, self-care, menstrual cycle, fertility, pregnancy, and wellbeing.

Levvi follows a local-first approach: the main record can stay on your device when a feature allows it. Optional features such as account login, purchases, backup or export, product diagnostics, address search, and remote notifications use the network as described in this policy.

2. Information stored on your device

Depending on what you choose to create or enable, Levvi may store the following locally:

  • tasks, routines, notes, and a place label or coordinates that you choose for a task;
  • medications, reminders, doses, and water intake;
  • menstrual cycle, fertility, pregnancy, mood, energy, and wellbeing records;
  • health readings: on Android, when you authorize Health Connect; on iPhone and iPad, when you authorize Apple Health; and summaries or other values derived from them;
  • pets, family members, and images you choose to add;
  • preferences, settings, notification configuration, and other app state;
  • account session information needed to keep you signed in on the device.

These categories are not collected for everyone. They depend on what you enter, import, authorize, or enable. Local storage does not mean that every optional feature is offline; the network flows are listed in section 4.

3. Health information

With your explicit system permission, Levvi can read selected health information. On Android, those readings can come from Health Connect. On iPhone and iPad, they come from Apple Health. The available types depend on the permissions you grant.

Health readings are used in the app for organization, visualizations, and wellbeing insights. Levvi does not provide a medical diagnosis or replace professional care.

Levvi product telemetry is not a backup path for your health records. The current event filter removes events whose labels identify health, cycle, fertility, pregnancy, trying to conceive, partner mode, or energy check-in. A backup or export is different: if you choose it, it can include local health settings, summaries, fertility or pregnancy data, and other values derived from your records.

4. When information leaves your device

Some network flows run as part of app operation; others occur when the related feature is used or enabled:

  • Account and sign-in: Apple Sign in or Google Sign-In sends authentication information to Levvi’s API. Levvi stores the account email, name when available, sign-in provider, and internal account identifiers needed to authenticate you and manage the account.
  • Backup and export: a manual export or cloud backup can contain tasks, medication records, cycle, fertility or pregnancy data, health settings and summaries, preferences, pets, family members, and optional images. A file may be shared through the destination you choose in the system share sheet, including iCloud if you choose it. Optional cloud backup can use Levvi’s API or Google Drive depending on the platform and feature. Levvi does not automatically upload health information to iCloud. On iOS, Levvi excludes local Documents, Preferences, and Application Support data from iCloud device backup; use manual export if you want to transfer those records to another device. The Levvi server keeps one account-linked backup and replaces it when a newer backup is uploaded.
  • Purchases and subscriptions: RevenueCat receives the app user identifier and, after account login, the email or display name that Levvi sends to it. It processes product, purchase, and entitlement status so Levvi can provide the plan you selected. Apple or Google processes the store transaction under its own terms.
  • Product analytics and diagnostics: if you opt in from Me in the app, Levvi sends batches containing an app-generated device identifier, an available device or hardware identifier, platform, app version, timestamps, and product or diagnostic events such as screens, features, subscription actions, and errors. When you are signed in, the server can associate the device with your account. You can withdraw this optional consent in Me. The event filter described in section 3 is label based and is not a substitute for the data minimization described here.
  • Address autocomplete: when you type an address in the task location search, the text you submit is sent to the Nominatim service operated for OpenStreetMap to return suggestions, together with language and regional search parameters. The selected label and coordinates can be saved with the local task and can be included in a backup or export.
  • Remote notifications: when you grant notification permission and sign in, Firebase Cloud Messaging issues a device token. Levvi sends that token and the platform to its API, links it to your account, and uses Firebase to deliver remote notifications. Local reminders scheduled on the device do not require this remote registration.

5. Why we use this information

We use information to provide the features you request, authenticate your account, restore and manage purchases, perform a requested backup or export, deliver remote notifications, protect the service, troubleshoot failures, and understand aggregated product usage.

Levvi does not sell personal or health information. The current product is not configured to use the content of health or cycle records for behavioral advertising.

6. Providers and sharing

The app sends information needed for the selected feature to the providers below. Each provider handles its own service data under its applicable terms and privacy policy:

  • Apple and Google: sign-in, app store purchases, and the health platform selected on the device;
  • RevenueCat: subscription catalog, purchase status, entitlements, and the identifiers needed to associate a purchase with the Levvi account;
  • Firebase Cloud Messaging: remote notification delivery and device token handling;
  • Nominatim and OpenStreetMap: address search suggestions based on the text you submit;
  • Google Drive: optional cloud backup on supported platforms. Google Drive or iCloud may also receive a manually exported file if you choose them in the system share sheet;
  • Levvi’s API and database infrastructure: account data, server backups, device registrations, and product or diagnostic events described above.

A file you export or share can be copied by the destination service or recipient. Check the destination before sending sensitive information.

7. Permissions

Levvi may request the following permissions when a feature needs them:

  • access to the device health app;
  • notifications;
  • camera or photo library access when you choose an image;
  • file access for importing or exporting a backup.

You can revoke system permissions in your device settings. Revoking permission stops the related access; it does not automatically erase data that you already saved, exported, or shared.

8. Security

We use access controls, authenticated service calls, and HTTPS connections for the network features described here. Local data is also subject to the security of your device and operating system.

No storage or transmission method removes every risk. Protect your device, account, exported files, and cloud storage account, especially when a backup contains health or other sensitive information.

9. Retention and deletion

Retention depends on where the information is stored and which feature you use. We do not promise one universal retention period for every category.

  • Local records remain on the device until you edit or delete them, clear the app data, or uninstall the app. A file you export or share remains wherever you saved or sent it until you or that destination deletes it.
  • Account data, the account-linked server backup, device and push registrations, and product or diagnostic records are kept while needed to operate and support the account. The server backup is replaced by a newer upload and is deleted with a successful Levvi account deletion. Withdrawing analytics consent stops future collection and clears pending events on the device; existing server records can be removed through account deletion or a data request.
  • You can start account deletion in Levvi under Me, Profile, and Delete account. A successful deletion removes the Levvi account and its linked server data, device records, push registrations, analytics events and sessions, and trial data; Levvi also requests deletion of the linked RevenueCat customer. Apple sign-in may require reauthentication. Store subscriptions must be canceled separately through Apple or Google.
  • Copies held by Apple, Google, RevenueCat, Firebase, Nominatim/OpenStreetMap, Google Drive, iCloud, or a file recipient follow those providers’ policies and may require a separate request or deletion action. We may retain information when required by law or needed to resolve security, fraud, disputes, or other legal obligations.

10. Your rights

Under applicable law, including the LGPD where it applies, you may request access, correction, portability, information about processing and sharing, deletion, or revocation of permissions and consent. Some requests may be limited by a legal obligation or by data held by an independent provider.

For account deletion, use the in-app flow or see the account deletion page. For other requests, contact us and describe the request without sending health records or documents in the first message. We may need to verify your identity before responding.

11. Changes to this policy

We may update this policy when the app, its providers, or applicable law changes. The date at the top shows when this version was last updated.

12. Contact

Questions about this policy or a data request can be sent to: suporte@devlopes.io