Privacy Policy

Bymax Bio is maintained by Bymax One LTDA, a company registered in Brazil. We act as the controller of the personal data processed by the app.

To reach our privacy team, write to support@bymax.one.

Data you enter directly: weight, body measurements, medications, doses, symptoms, nutrition logs (hydration, calories, protein), daily wellbeing, configured reminders, notes and app preferences.

Technical data collected automatically: a pseudonymous local identifier, device model, operating system, language and crash diagnostics. The identifier is generated on your own device and is never linked to your name or email. For usage data and crash reports, we send only a one-way hash of this identifier. Subscription management (RevenueCat) receives the identifier in its original form, along with technical and purchase data, and the update check sends technical data to Expo. The full list of what each provider receives is under Sharing with third parties.

We do not require you to register a name, email, phone, government ID or address to use the app.

To provide and operate the app, personalize your experience, calculate charts and indicators and meet legal obligations.

While usage data is on — and it starts on, except in the regions listed under Legal basis — we process pseudonymous events to understand which features are used and improve the product. Pseudonymous is not anonymous: the identifier is stable per installation, so the events form a continuous series tied to your device.

We do not use your health data for advertising, nor do we sell it to third parties.

We process your personal data on the basis of our legitimate interest in operating and improving the product (Art. 7, IX of the LGPD; Art. 6(1)(f) of the GDPR), our legal obligations and, where applicable, your consent.

Outside the European Union, Norway, Iceland, Liechtenstein and the United Kingdom, usage data and crash reports rest on our legitimate interest in keeping the app working and improving it (Art. 7, IX of the LGPD; Art. 6(1)(f) of the GDPR), not on your consent: both services start the first time you open the app, before you are asked. Turning either one off, on the screen that asks or in Settings › Privacy, is your objection to that processing, and sending stops immediately.

In the European Union, Norway, Iceland, Liechtenstein and the United Kingdom — as set by your device's region or time zone — usage data and crash reports start off and are sent only if you turn them on. There the basis is your consent (Art. 6(1)(a) of the GDPR), which you can withdraw at any time in Settings › Privacy, and sending stops immediately.

Sensitive health data (including menstrual cycle records) is stored on your device, and you can erase it at any time. It is not part of usage events, and it leaves the device only if you export it yourself and share the file. Crash reports go through a filter meant to strip health information before they are sent, but that filter has not yet been verified against real production traffic (see Telemetry and crash reports).

Providers acting on our behalf under contractual agreements. As with any network connection, each of them also sees your device's IP address.

• Usage data (PostHog) — pseudonymous app-usage events, tied to the hash of the local identifier, with no health values. Stops receiving anything as soon as you turn that option off;
• Crash reports (Sentry) — technical diagnostics about the failure, tied to the same hash. Pseudonymous, not anonymous. They are meant to carry no health data, dose, medication name or note: a keyword filter strips those fields and fragments before sending, but it has not yet been verified against real production traffic. Stops receiving anything as soon as you turn that option off;
• Subscription management (RevenueCat) — receives the local identifier in its original form, not the hash the other services get, and, through its own SDK, your device type, operating system and when you last used the app. After a purchase or a restore it also receives the Apple App Store receipt or Google Play purchase token, and builds your purchase and subscription history from it. It starts every time the app opens, whenever the installed build has a purchases key configured, and the usage-data and crash-report switches do not turn it off;
• Update check (Expo, expo.dev) — when the app opens, and when you tap Check for updates in Settings › About, the app contacts Expo's update server and sends technical data about the device and the installed version (platform, runtime version and current update). No health data goes with it, and the privacy switches do not turn it off either.

Subscription payments, when applicable, are processed directly by the Apple App Store or Google Play; we do not collect or store card data.

We do not sell your personal data.

Scope: these integrations (PostHog, Sentry, RevenueCat and Expo) apply only to the Bymax Bio mobile app. This marketing site does not run product analytics — at most, aggregated traffic metrics from the hosting provider (Cloudflare).

Usage data and crash reports are two separate options, and both start on: the services start the first time you open the app, before the question. On a new install that question shows both on and lets you turn either off; if you had already turned one off, it appears off and can be turned back on there. In the regions listed under Legal basis, both start off instead: nothing is sent until you turn one on, and the question shows both off. You can turn each on or off at any time in Settings › Privacy; turning one off stops it there and then, and anything still pending is discarded rather than sent.

Usage events follow a predefined list and carry no health values: no dose, medication name, note, weight or measurement value, symptom severity, injection site or menstrual cycle data. They record how features are used — for example, that a weight or an application was logged, without the value, or that the Cycle tab was opened in Metrics.

Crash reports describe the failure and the device it happened on. Before sending, a keyword filter strips fields and fragments related to health, along with email addresses and identifiers. That filter has not yet been verified against real production traffic, so keeping health information out of these reports is the goal, not a guarantee.

Menstrual cycle tracking records (period dates, symptoms, predicted phase) are sensitive personal data under Article 11 of the LGPD and special-category data under Article 9 of the GDPR.

This data is stored on your device and is not part of usage events. It leaves the device only if you tick the cycle section in an export yourself and share the file it creates; that section starts unticked. The caveat about the crash-report filter, described above, applies here too.

The feature is opt-in, requires explicit acceptance of its disclaimer and can be deleted in Settings › Female health › Clear cycle data.

Our service providers may process data in countries outside Brazil and outside your own country.

We adopt appropriate safeguards, such as standard contractual clauses, to ensure a level of protection compatible with the LGPD and the GDPR.

Access, correction, deletion, anonymization, portability, objection to processing based on legitimate interest and withdrawal of consent regarding your personal data.

To exercise these rights, write to support@bymax.one.

You can also erase your records from the device in Settings › Delete all data; what that action keeps is described under Data retention.

If you believe your request was not handled properly, you can lodge a complaint with Brazil's National Data Protection Authority (ANPD) or with the data-protection authority where you live — in the European Union, your country's supervisory authority.

We retain your data for as long as needed to provide the service and meet legal obligations. Purchase records are kept for the applicable tax and contractual periods.

Deleting all data in Settings removes your health records from the device but keeps the local identifier and the first-install date, so your purchases can be restored. Both privacy options return to their initial state, as on a new install — on, or off in the regions listed under Legal basis — even if you had changed one, and the app asks the question again; you can change them there or in Settings › Privacy.

Uninstalling the app removes everything held on the device, the identifier included. Neither action removes anything already sent to a provider while an option was on — that takes a deletion request: tap Support in Settings › About, and the email already carries your code for privacy requests, which does not identify you by name. Make the request before uninstalling: only uninstalling erases the identifier that lets us locate those records, and it exists only on your device.

We adopt reasonable technical and organizational measures: encryption in transit, access controls and periodic review.

No system is completely secure; in the event of a relevant incident, we will notify you, Brazil's data protection authority (ANPD) and any other authority the law requires, such as an EU supervisory authority.

The app is intended for users aged 18 and older. We do not knowingly collect data from minors under 18.

If you are a legal guardian and identify improper collection, contact us so we can remove it.

We may update this policy to reflect changes in the product, the law or security practices.

Material changes will be communicated within the app before they take effect.

Questions, rights requests or any privacy matter: support@bymax.one.