This Privacy Policy explains what information Fysiqal collects, how we use it, and who we share it with. It's written to describe what the product actually does, not generic boilerplate — if a section below doesn't match what you see in the app, tell us at support@fysiqal.com.
1. Information you provide
- Account info: name and email, used for sign-in and communication, plus the date you confirmed you're 16 or older when you created the account. Passwords are handled by our authentication provider (Supabase Auth) — we never see or store your password in plain text.
- Training profile: your primary goal, training days per week, session duration, equipment access, experience level, and (optional) age, weight, height, sex, and activity level — used to generate your program and nutrition targets. Sex and activity level are optional specifically because they're only used to sharpen calorie/macro estimates (Mifflin-St-Jeor); Fysiqal works without them.
- Injury restrictions: anything you note is used to steer program generation away from contraindicated movements. This is self-reported information, not a medical record, and is treated as sensitive — it's never shared with anyone besides a coach you've actively subscribed to.
- Workout logs: exercises, sets, reps, weight, and RPE you log, plus recovery check-ins (sleep, soreness, energy).
- Progress photos: if you choose to upload them, they're stored in a private Supabase Storage bucket, readable only by your account, and only ever served back to you via short-lived signed URLs — there is no public URL for any progress photo, ever.
- Form Studio video: for a private check, still frames are taken from your video in your browser and sent to our AI provider for analysis; the video stays on your device and only the feedback is saved to your account. When you send a clip to a coach, the clip is uploaded to private storage so that coach can review it. It stays until you delete it (a deleted review can be restored for 7 days, then it's erased), and an upload that never reached a coach or got a read is removed after 30 days.
- Meal photos: similarly processed by our AI vision provider to recognize food items and estimate portions; the photo itself isn't stored — only the nutrition log entry you confirm.
- Payment information: handled entirely by Stripe. Fysiqal never receives or stores your full card number — only a Stripe customer/subscription reference.
- Coach messages: if you subscribe to a coach, messages between you are stored so both sides can see the conversation history; they're visible only to the two of you.
2. Information we collect automatically
Like any website, our hosting keeps request logs (IP address, the page or API address requested, browser type and time) to run and secure the service. If error monitoring is turned on, an error report carries the technical details of what broke — the page, the browser and device type, and the error itself — not your training data.
We measure page speed ourselves: a sample of visits sends the page path (with any ids removed), which speed measure it is (such as Largest Contentful Paint), its value and whether the device is a phone, tablet or desktop. These measurements carry no account, name or email.
If Fysiqal has a Google Analytics 4 property configured (it may not, depending on the deployment), we collect standard, aggregated site-usage analytics — pages visited and button clicks on our public marketing pages — to understand what's working. This is never tied to your training data, and is disabled entirely (no script loads at all) if no GA4 property is configured.
In the Shop we also keep our own anonymous interaction counts — for example that a search returned no results (as a length range, never the words you typed), that the size guide was opened, or which checkout step was reached — so we can fix what gets in the way. These records carry no account, session, IP address or free text, only whether the shopper was signed in. If your browser sends Global Privacy Control, none are recorded. Separately, an order notes whether a Shop story, activity or guide page was visited earlier in the same browser tab, so we can tell whether those pages help.
3. How we use your information
- To generate and adapt your training program, nutrition targets, and recovery guidance.
- To power AI Coach (including program generation), Form Studio, and meal-photo recognition via our AI provider.
- To connect you with a coach you've chosen, and give that coach visibility into your real training history once you've subscribed to them (not before).
- To process payments and manage your subscription.
- To respond to support requests and, if you've opted in, send product updates.
We do not sell your personal or health data to third parties, ever.
4. Who we share information with
Fysiqal runs on a small number of service providers. Each one gets only what its job needs:
- Supabase — database, sign-in and file storage. Your account, training data and uploaded files live here, protected by row-level security that scopes each table to the people allowed to see it. Supabase also sends account emails, such as confirming your address and resetting your password.
- Google Cloud (Firebase App Hosting) — runs the Fysiqal website and app servers. Every request passes through it, so it handles the data in those requests and keeps the request logs described in section 2.
- Google (Gemini API) — our AI provider, the model behind AI Coach. It receives what an AI feature needs to answer: the training details and questions you send AI Coach (including program generation and Ask), Form Studio frames, meal photos, voice notes you ask us to transcribe, and notes a coach turns into a draft.
- Stripe — processes payments, subscriptions and coach payouts. It receives your payment details directly, plus your email and what you're buying. Stripe's own privacy policy covers the payment data it holds.
- Printful — makes and ships Shop orders. For each order it receives the name and shipping address you enter at checkout and the items ordered.
- Resend — delivers the emails we send ourselves: order updates, coaching updates and reminders, notifications you've turned on and guides you request. It receives your email address and the content of each email.
- Food databases (Open Food Facts, and FatSecret or Nutritionix where enabled) — when our own food catalog can't find a match, the words you searched (or a barcode) are sent from our servers to look it up. They don't receive your account, email or IP address.
- Push services (Google, Apple, Mozilla) — if you turn on notifications, your browser's push service delivers them. Messages are encrypted for your device; the service sees only that a notification was sent.
- Sentry (only when error monitoring is turned on) — receives the error reports described in section 2.
- Google Analytics (only if configured) — aggregated public-site usage, never your training data.
- OpenStreetMap — route maps on cardio sessions load their map tiles from OpenStreetMap, so it sees your IP address and the map area shown.
- Services you connect — if you connect Oura, WHOOP or Google Health, we receive the readings you authorize (such as sleep, heart-rate variability, resting heart rate and activity); a coach who connects Google Calendar shares only busy times, never event details. You can disconnect any of them in Settings.
- Your coach — only if you've subscribed to them, and only the training data you share for coaching (sessions, programs, check-ins), never your payment details.
We don't share your data with advertisers or data brokers.
5. Data retention and deletion
We keep your data while your account is active, so your program and progress history stay intact. Settings → Trust & Privacy has "Download my data" (a JSON file covering every table that holds your data) and "Request account deletion". A deletion request starts a 14-day grace period that you can cancel from the same page. After it ends, a daily job cancels any subscriptions you pay for, removes your Form Studio media and permanently deletes your account and the data linked to it.
Your posts, comments and reactions in Community are deleted with your account. If other people replied to one of your comments, their replies stay and your comment shows as "Deleted", with no name and no text. Messages you sent in a conversation that belongs to someone else, such as a care-team thread, stay in that conversation shown as from a "Deleted account".
A few records outlast the account. Shop orders are kept, no longer linked to you, for tax and accounting. We keep a short record that the deletion happened (your email and the dates). Stripe keeps its own payment records under its privacy policy. Email support@fysiqal.com for an export, a deletion or any question about what a specific export contains.
6. Security
Data is encrypted in transit (HTTPS) and at rest (Supabase's infrastructure defaults). Every database table has row-level security enabled — most scope access to your own account; a few (like coach and product reviews, or your public Community activity if you've opted into it) are visible by design, the same way they'd be visible in the app itself. Uploaded files (progress photos) live in a private storage bucket with no public path — access is only ever granted via short-lived signed URLs generated for you, the owner.
7. Children's privacy
Fysiqal is not directed at, and we don't knowingly collect data from, anyone under 16.
8. Changes to this policy
We'll update the effective date above whenever this policy changes, and we'll aim to describe real product behavior at the time — not a generic template.
9. Contact
Questions, data-export requests, or deletion requests: support@fysiqal.com.