Magnesia
Information

Privacy Policy

1. Scope

This Policy explains how Magnesia processes data when you use the App or submit a website waitlist request.

Lucía is responsible for decisions about user accounts, health features, optional AI, support and technical diagnostics. Mariano decides the purposes and data sent for PostHog product analytics and is responsible for that processing.

2. Data stored on your device

Your profile, wellness answers, medication information, health-condition inputs, supplements, supplementation plan, reminders and tracking records are stored locally on your device. Using online features can send relevant information off your device, as described below. Local storage can also be affected by your operating system and device backups.

3. Data processed by Magnesia servers

We process account and infrastructure data needed to operate the service: email or authentication identifiers, device identifiers, language/subscription metadata, access limits, rate-limit counters, public configuration, support communications, and technical logs.

When you submit your email through the website waitlist form, we use it to contact you about availability and invitations. The request is sent through Zoho Mail to our contact mailbox; it does not create an app account or grant beta access. Cloudflare hosts the form and Turnstile checks technical connection data to prevent automated submissions. You can ask us to remove your waitlist request at [email protected].

4. AI features and OpenAI

AI features require a separate permission for remote processing; accepting legal documents does not grant it. You can decline or withdraw this permission in Settings → AI processing permission. Without it, new AI requests are blocked. Manual plan editing, reminders and intake tracking remain available subject to your account’s access. Withdrawal stops new requests; it cannot recall information already transmitted and does not delete your account or local data.

When you use AI plan generation or Ask AI, the information needed for the request passes through Magnesia servers to OpenAI. This can include profile answers, medication and health information, current plan details and your messages. The response also passes through online services before reaching your device. AI requests therefore involve remote processing, even when your profile and plan are stored locally. Provider retention and security processing are separate from storage on your device.

5. Usage and technical data

Magnesia processes account and request metadata, token usage, model name, estimated cost and success/error status to operate, secure and debug the service. AI request logs are designed to exclude prompts, responses, medication, health conditions, supplements and plan content. Account and infrastructure records are separate from the telemetry described below.

When enabled, Sentry receives predefined technical error and operation categories, severity, approximate time, a random per-event identifier and technical platform, environment, version, build and app-update data. These reports exclude names, emails, account identifiers, health data, medication, messages, free text and unfiltered error details. Session recordings and screenshots are not enabled for this monitoring.

When usage analytics is enabled, Magnesia automatically records usage actions (navigation and use of features), their times and durations, sessions and version data to understand journeys and improve the app. These data are sent to PostHog with a random identifier for each account on this installation; guest activity stays separate. We do not send names, emails, account identifiers or health, conversation or support content, or enable session recordings or screenshots. Linked actions may reveal health-related behavior; these data are not anonymous.

Pending events may be sent for seven days. Received events are kept for usage analysis and applicable rights handling, without an automatic deletion deadline. To request access, objection or deletion, email [email protected], including if you use the app as a guest. Locating records may require information from your installation, where the association with your account is stored. Erasing local data does not erase PostHog records.

The direct connections to Sentry and PostHog can expose the source IP address and connection metadata to the provider, even when the report or event does not include an account identifier. We do not describe the entire flow as anonymous or confined to your device.

6. How we use data

  • Provide authentication, subscription access, rate limits, and configuration.
  • Generate AI responses when you request AI features.
  • Send support communications when you contact us.
  • Improve quality, security, reliability, and performance.
  • Comply with legal obligations.

7. How we share data

  • Supabase for authentication, infrastructure data, configuration, technical logs and the servers that process AI requests.
  • RevenueCat and app-store providers for subscription management.
  • OpenAI for AI responses when you use AI features.
  • Sentry for the restricted technical error monitoring described in section 5, where enabled; not for your health profile or AI questions.
  • PostHog for the allowlisted product-usage and reliability events described in section 5, where enabled. Mariano determines the purposes and data categories of this analytics processing.
  • Brevo for authentication emails and controlled support categories and technical fields sent from the app, and Zoho for the contact and support mailboxes. Direct emails are processed by the mail providers involved.
  • Authorities when required by law.
  • We do not sell your personal data.

The in-app support form does not allow free-form text. Direct emails include what you send and the account or technical information needed to respond. Do not send health information, medication lists, supplement plans, passwords or sign-in codes. See Contact and support.

8. International transfers

Service providers may process data outside Argentina or the country where you live. The location and handling of data depend on the service involved. Contact [email protected] with questions about a particular service or transfer.

Sentry technical reports and PostHog product-analytics events, where enabled, are sent directly from your device to their United States services. The connection can expose your source IP address to each provider. Accepting legal documents does not, by itself, expressly authorize these transfers. AI processing permission covers AI features, not Sentry monitoring or PostHog analytics.

9. Retention

Local data and device backups are managed on your device and through your operating-system or backup provider. Signing out is not a complete data-erasure procedure. Account records, support messages, subscription records and technical logs are handled separately by Magnesia and the relevant service providers.

For a request about retention or deletion, contact [email protected]. We will explain the scope of the request, any records that must be retained and any actions needed with a provider. See Delete account and data for the distinction between local data, account data and subscriptions.

10. Your rights

Depending on your jurisdiction, you may request access, correction, update, portability, restriction, objection or deletion of your personal data. Write to [email protected]. We may need to verify that the account is yours before acting on a request. Do not include health information in the request.

When signed in, you can request deletion of your online account from Menu → Delete account. This sends a request to our team; it does not immediately delete your account or local data. We will confirm when processing is complete. If you cannot access the app, or want to exercise another right, write to [email protected].

11. Security

We apply reasonable technical and organizational measures, including encryption in transit, access controls, and logging. No system is 100% secure; we cannot guarantee absolute security.

12. AI and automated decisions

AI-generated outputs are informational and are not medical diagnosis, treatment, or medical advice. You can manually edit your plan and avoid AI features where available.

13. Crisis Handling Policy

Magnesia is not an emergency service and does not provide crisis counseling.

If you submit content that expresses intent of self-harm, suicide, violence toward others, or immediate danger, Magnesia may process the relevant input and related technical logs for safety operations, incident response, and legal compliance. In these cases, Magnesia will:

a) interrupt the normal Ask AI consultation flow,

b) show a crisis message with emergency resources,

c) not generate supplement plan changes based on that message.

Where required by law, we may share the minimum necessary data with service providers supporting safety operations and with competent authorities.

If you or someone else may be in immediate danger, contact local emergency services now.

Resources for Argentina: 911 for emergencies. National mental-health orientation and support: 0800-999-0091, available free of charge 24 hours a day. For immediate danger, call emergency services.

14. Minors

We do not intentionally collect data from minors. If you believe a minor used the App, contact us to delete the account.

15. Changes to this Policy

We may update this Policy. We will notify material changes via the App or email when applicable and may request renewed consent.

16. Contact

Magnesia is offered by Lucía Brumnich and Mariano Ramonda, acting personally from Argentina. Magnesia and Beleza Software are project names, not separate legal entities. Contact: [email protected]. Postal address: Quintana 3112, Santa Fe, Santa Fe, CP 3000, Argentina.