Fawna

Privacy Policy

Last updated: 22 October 2026

Fawna is a nutrition companion that adapts to your life stage. We built it to be private by default: your day-to-day nutrition, cycle, and health data live on your device, and we collect as little as possible. This policy covers both the Fawna app and this website (fawna.app).

The website (fawna.app)

  • Waitlist — if you join our early-access list, we store the email address you give us so we can send you one note when Fawna launches. You can unsubscribe or ask us to delete it at any time.
  • The quiz — your quiz answers stay in your browser to show your result. We don’t send your health answers to a server; only your email is saved if you choose to join the list.
  • Hosting — our hosting and security providers process requests to deliver and protect this website, including technical request information.

Data that stays on your device (the app)

  • Food logs, hydration, measurements, symptoms, life-stage setup and daily goals are stored on your device. Health integrations require your device permission. Online target and coaching requests can send selected life-stage inputs and nutrition totals to our backend to calculate guidance.
  • Signing in does not sync these device records between devices. They remain on the device after sign-out. Saved recipes, meals, shopping lists, plans and custom foods use account-backed storage when you save them online.

Data we process (the app)

  • Account information — the native app requires sign-in. We process an account identifier and the information supplied by your selected sign-in method to secure your account.
  • Product analytics — limited usage events and an account or device identifier to understand what to improve. Product analytics are not used for advertising.
  • Diagnostics — crash and performance data to fix bugs.
  • Purchases — purchase status and account identifiers through Apple or Google Play and RevenueCat. We do not receive your card details.

Service providers

We use a small set of trusted processors, each only for its stated purpose:

  • Supabase — account, authentication, and backend storage.
  • Resend — delivery of account-confirmation and password-reset emails.
  • Cloudflare — website hosting, security and forwarding support email to our Google-hosted support inbox. Support requests include the information you choose to send; avoid sending unnecessary health details.
  • PostHog — product analytics.
  • Sentry — crash and performance diagnostics when enabled; it is not configured in the current store candidate.
  • RevenueCat, Apple & Google Play — purchase management.
  • Apple & Google — sign-in and speech recognition. Voice logging may use a speech provider when on-device recognition is unavailable.
  • USDA FoodData Central and Open Food Facts — food database lookups using search terms and product barcodes.

Food data credits

Food reference data includes USDA FoodData Central, made available under CC0 1.0, and information from Open Food Facts, which is made available under the Open Database License. Open Food Facts product data retains that license. These credits do not make your private account records or food logs public.

How we use data

To provide and personalize the app, keep it reliable and secure, manage subscriptions, and improve the product. We do not sell your data, and we do not use it for third-party advertising.

Your choices & rights

  • Delete your account and data at any time from within the app (Profile → Delete account).
  • Use Profile → Privacy & data to export or delete device records. Account deletion and device-record deletion are separate actions.
  • Revoke Apple Health / Health Connect access anytime in your device settings.
  • Depending on your region (e.g. EEA/UK under GDPR, California under CCPA), you may have rights to access, correct, or delete your data — contact us and we’ll help.

Data retention

We keep account and waitlist data while it’s needed. When you delete your account (or ask us to remove your waitlist email), account removal is processed by our backend. Device records must be deleted separately on each device. Provider retention and backup schedules also apply; contact us for access or deletion requests.

Children

Fawna is not directed to children under 13, and we do not knowingly collect their data.

Changes

We’ll update this page if our practices change, and revise the date above.

Contact

Questions or requests: support@fawna.app.

Get early access →