This Privacy Policy explains how Nascimento e Memolo Desenvolvimento de Programas de Computador Ltda (“ENDIA”, “we”, “us”) collects, uses, stores, shares, and deletes information when you use the ENDIA FLOW mobile application (the “App”) and the website endiaflow.com (the “Site”).
This English version applies to users in the United States, Australia, New Zealand, India, Singapore, and Hong Kong. It should be read with the Terms of Use and the Account Deletion page. Where it applies, the Consumer Health Data Privacy Policy adds detail for U.S. consumer-health laws.
1. Who we are
Data controller: Nascimento e Memolo Desenvolvimento de Programas de Computador Ltda, CNPJ 68.454.409/0001-11, Alameda Professor Lucas Nogueira Garcez, 865, Sala 01, Vila Thais, Atibaia – SP, 12942-020, Brazil.
Privacy: privacy@endiaflow.com. Support: support@endiaflow.com. Phone: +55 11 97380-1961.
2. Who can use ENDIA
ENDIA FLOW is for people aged 18 or older. We do not knowingly collect personal information from anyone under 18. If you believe a child has provided information, contact privacy@endiaflow.com and we will take reasonable steps to delete it.
3. Information from the App
3.1 Account. Name and email from the sign-in method you use, such as email and a flow pass, Google Sign-In, or Sign in with Apple when available. We also keep a Firebase user ID and the App user ID used with RevenueCat for subscriptions.
3.2 Check-in. If you enter a Body/Mind check-in, that report stays on your device. We treat it as information about how you say you feel. It is not uploaded as a health record.
3.3 Optional rhythm. If you choose a camera reading, frames are processed briefly in memory on your device to calculate a numerical pulse rate, then overwritten. We do not create, store, or transmit photos, videos, biometric templates, faceprints, or facial geometry.
If you authorize a wearable, the App may read heart rate and, when available, heart rate variability from Health Connect or HealthKit / Apple Health, in read-only mode. The App does not write to those platforms. Information read from those platforms is used only to inform the session and to maintain the summarized reference. It is not used for advertising, sold, used to build marketing profiles, or shared with data brokers. Our use of Health Connect information follows the Health Connect Permissions policy, including its Limited Use requirements.
The only rhythm information that may leave the device is a summarized reference linked to your account: median heart rate when real readings exist, median HRV when a real wearable reading exists, sample counts, and an HRV-metric identifier such as RMSSD or SDNN. Raw readings and session history stay on the device.
3.4 Subscription and technical. Subscription status from the app store and RevenueCat. Technical data needed to run the App, such as device type, operating system, app version, and country or region where a provider supplies it. We also keep separate records of camera and wearable consent, including the disclosure version accepted and the time of acceptance. These records are part of the App account data hosted in Google Firebase / Firestore.
3.5 We do not collect photos, videos, audio recordings, GPS or precise location, contacts, messages, or advertising identifiers from the App. We do not use App rhythm data for advertising.
4. Information from the Site
4.1 Early Access and similar signups. If you submit the form, we collect name, email, and the time of signup, stored with our provider Supabase. We use this to send launch and availability messages when you have agreed. You can unsubscribe from those emails or ask us to delete the signup at privacy@endiaflow.com. Deleting an App account does not automatically remove a separate website signup.
4.2 Site measurement and advertising technologies. The Site may load Google Tag Manager, a Meta Pixel, and Tinybird through a first-party site-performance script commonly called Flock.js for page traffic and performance. When campaigns are on, tags managed in Google Tag Manager may send page views, lead events, call-to-action clicks, and Google Ads conversion measurement, including a conversion linker. When a lead event is sent, the email from the form may be sent in hashed form to Meta for advanced matching. These events are sent from the browser and may include IP address, user agent, and cookie or similar identifiers used by those tools.
We do not send heart rate, HRV, check-in, or other App health data to Meta, Google Ads, Tinybird (including through the Flock.js script), or Supabase.
Where required, we ask for consent before non-essential cookies or similar technologies, and you can withdraw that consent.
We do not sell App health or check-in information, and we do not share that information for advertising or targeted advertising. We do not sell personal information for money. Certain Site advertising disclosures described in this section may be considered “sharing” or “targeted advertising” under some U.S. state laws. Where those laws apply, we provide the rights and choices they require.
5. Why we use information
We use App information to create and secure your account, run the optional rhythm-informed session, keep the summarized reference, restore it after reinstall, manage subscriptions, provide support, and handle deletion or privacy requests.
The App may automatically use your Body/Mind check-in and, when authorized, optional rhythm signals to inform the state or session experience shown to you. This processing is for wellness personalization and does not make decisions that produce legal or similarly significant effects.
Heart rate, HRV, and check-in information may be considered sensitive or health-related information under applicable law. Where consent is the basis, we ask for it separately from account creation, before the system permission, for the purpose of informing the session. You can refuse the camera and the wearable and use the manual check-in only.
Camera and wearable permissions can be withdrawn through the App where available or through your device or health-platform settings. Where consent is the legal basis for processing, you may also withdraw that consent by disabling the relevant feature or by contacting privacy@endiaflow.com.
We do not use this information for diagnosis or treatment, credit, insurance, employment, or housing decisions.
6. Who receives information
App account and the summarized rhythm reference: Google Firebase / Firestore, as our processor.
Subscription status and App user ID, not heart rate, HRV, or check-in: RevenueCat.
Purchases: Apple App Store or Google Play, under their rules.
Website signups: Supabase.
Website measurement and advertising: Meta, Google through Tag Manager and Google Ads, and Tinybird through the Flock.js script, as described above. They do not receive App health data.
We do not share consumer health data with affiliates. We would ask for separate consent before sharing App health data with anyone other than a processor needed to host the summarized reference.
7. Retention and deletion
Account data and the summarized reference are kept while the account is active. When deletion completes, we delete the Firebase Authentication account and the Firestore document, and we request deletion of the linked RevenueCat customer profile where technically applicable.
We do not keep scheduled backups. Deletion from active systems may not immediately remove limited residual copies or technical logs maintained temporarily by service providers for security, integrity, legal, or similar purposes. Any such retention is limited to what is necessary under the provider’s applicable processes or legal obligations.
The website deletion page cannot erase data that exists only on your device. In-App deletion removes local rhythm-reference data and local session history on that device. You can also uninstall the App or clear app data. Deleting your account does not delete information stored in Apple Health, Health Connect, or your wearable’s own app.
Deleting the account does not cancel an app-store subscription and does not remove a separate website signup. A later sign-in creates a new ENDIA account. Restore Purchases may attach an existing store entitlement to that new account. It does not revive the deleted account or reset a trial the store treats as used.
Billing, tax, fraud-prevention, app-store, or other purchase records may remain with Apple, Google, RevenueCat, or other providers where required by law, app-store rules, or record-keeping. We may also keep limited information where reasonably necessary for security, fraud prevention, tax, accounting, disputes, or similar legal duties. That retention is limited to what is necessary. This is the same rule stated on the Account Deletion page.
8. International processing
We are in Brazil. Providers such as Google, Apple, RevenueCat, Meta, and Supabase may process information in the United States and other countries. Where the law requires safeguards for an international transfer, we use contractual or equivalent measures available from those providers.
9. Your rights
Depending on where you live, you may ask to access, correct, or delete personal information, withdraw consent, or object to or restrict certain processing. Contact privacy@endiaflow.com. We may verify the request. We respond within the time the applicable law requires.
You may also make a privacy complaint to us at privacy@endiaflow.com. We will review the complaint and respond within the period required by applicable law. That address is our privacy and data-protection contact.
Australia: if you are not satisfied with our response, you can contact the Office of the Australian Information Commissioner at oaic.gov.au.
India: privacy@endiaflow.com is our grievance contact.
Singapore: privacy@endiaflow.com is the public contact for our Data Protection Officer and data-protection matters.
United States consumer health data: see the Consumer Health Data Privacy Policy, including how to appeal and how to contact a state attorney general where that policy applies.
10. Security
We use access controls and encryption in transit for account data sent to our providers, and encryption at rest provided by those hosting providers. No method of storage or transmission is completely secure.
11. Changes
We may update this Policy. The Site and App will show the effective date. If a change requires new consent, we will ask for it.
12. Contact
Nascimento e Memolo Desenvolvimento de Programas de Computador Ltda
CNPJ 68.454.409/0001-11
Alameda Professor Lucas Nogueira Garcez, 865, Sala 01, Vila Thais, Atibaia – SP, 12942-020, Brazil
privacy@endiaflow.com · support@endiaflow.com · +55 11 97380-1961