Privacy policy

Valeva is a coaching platform operated from Australia: a web dashboard for coaches and a mobile app for coaches and their clients, covering training, nutrition, check-ins, messaging and payments. Questions about this policy or your data: reach us via the support page.

Account and profile. Email address, name, and the optional profile you choose to add (photo, location, timezone; for coaches a bio, specialties and qualifications; for clients an optional goal weight).

Coaching data. The content that makes the product work: training programs and logged workouts, nutrition diary entries and meal plans, habits and habit logs, check-in forms and responses (including any photos or files you attach to an answer), messages between coach and client (text, photos, voice notes and video clips), a coach's private notes about their clients, body metrics, progress photos, and shared resources.

Payments. Payment is handled by Stripe through hosted checkout — card details never touch our servers. We store subscription status and what Stripe reports back to us (plan, amounts, billing state).

Technical. Device push-notification tokens (so messages and reminders can reach your phone) and the feedback you submit in-app. We do not collect advertising identifiers.

Some features handle health-adjacent information. We treat it as the most sensitive class of data in the product:

• Apple Health and Health Connect. With your explicit permission, the mobile app reads daily aggregates — steps, sleep duration, resting heart rate and weight — and stores them as entries in your metrics timeline. We only ever read; we never write to or change your health store, and you can revoke the permission at any time in your device settings.
• Connected wearable accounts (Fitbit, Garmin, Oura). If you connect one, we receive the same daily aggregates from the vendor's API. The access tokens are stored encrypted (AES-256-GCM) and are used only to fetch your readings. Disconnecting stops all syncing immediately; already-synced entries stay in your timeline until you delete them.
• Body-scan documents (DEXA and similar). A scan PDF you upload is processed to extract the printed values for your review and is then discarded — the document itself is never stored.
• How health data is used. Solely to show your readings to you and to the coach or coaches you are connected with. It is never used for advertising, never sold, and never shared beyond the processors listed below.

Some features send specific content to an AI provider, only when you use that feature:

• Meal photos, spoken or typed meal descriptions, and body-scan documents are sent to Anthropic to identify foods or extract printed values. The results are estimates you review and confirm — nothing is saved without your confirmation.
• Voice messages are transcribed by OpenAI (Whisper) so a caption can accompany the audio.
• A coach's program or meal-plan briefs are sent to Anthropic to draft a proposal the coach then reviews.
• This content is sent solely to deliver the feature. We do not permit these providers to use it to train their models.

Food barcode scans and food-name searches query Open Food Facts, a public food database, and FatSecret when a scanned barcode is not found in the first; the query is the barcode or search text itself. Food and nutrient data also comes from the USDA FoodData Central database.

If you choose to connect Google Calendar, Valeva requests read-only access to your calendar (calendar.readonly). The sync is one-way: we read the events in your primary calendar so they appear alongside your sessions in Valeva. We never create, change or delete anything in your Google Calendar.

• We request the minimum scope needed for that one job, and nothing else.
• A client's Google events are private to that client. A coach never sees them, and a coach's events are never shown to clients.
• We store the event details needed to show them (title, time, location, notes) and a reference to the original event. Access tokens are encrypted.
• Disconnecting Google Calendar in Valeva revokes our access and deletes the synced events from your Valeva calendar.

Limited Use. Valeva's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

Specifically: we do not send Google Calendar data to any AI or machine-learning provider, and we do not use it — raw, aggregated or derived — to develop, train or improve any generalised or foundational AI/ML model, our own or anyone else's. Google Calendar data is not used for advertising, and is never sold or transferred except as needed to run the feature you turned on, or where the law requires it.

We use a small set of infrastructure providers, each processing data only to run the service:

• Supabase — authentication and our database.
• Cloudflare R2 — file storage (photos, attachments, resources).
• Fly.io — application hosting, and the queue that delivers messages, notifications and reminders.
• Stripe — payments (hosted checkout; card data goes directly to Stripe).
• Resend — transactional email (invites, notifications you enable).
• Google Firebase Cloud Messaging — push notifications.
• Sentry — error reporting, as described under crash diagnostics.
• Anthropic / OpenAI / Open Food Facts / FatSecret — only as described under AI features and food search.

Your coach sees the coaching data the product is for: your training, nutrition, habits, check-ins, metrics and messages with them. Progress photos carry a per-photo visibility control — photos you mark private are never shown to your coach. In a coaching team, administrators can see coaching artifacts but never get automatic access to a client's food diary, photos or body metrics — that always requires a direct coach-client relationship. We never sell personal information to anyone.

Your coach can record injuries and physical limitations against your account — an area, which muscle groups it affects, whether to avoid, limit or watch it, and their own notes. They do this so the app can warn them when a programme they are writing would load something you are carrying.

This is health information, and it is your coach's own record: it is written and maintained by them, it is not shown to you in the app, and no other coach can read it. Ask your coach if you want to know what they have recorded, or want it changed. A Valeva support session can reach it, as described below.

It is deleted when either of you deletes your account. Valeva does not diagnose anything or decide what an injury means — the muscle groups a warning uses are the ones your coach chose.

If you ask us for help with something we cannot reproduce from a description, a Valeva administrator can open a read-only support session as your coach. During one they see what your coach sees, which includes the coaching data your coach already has access to — your training, nutrition, habits, check-ins, metrics, photos your coach can see, and your messages with them.

A support session cannot change anything: every attempt to write is refused by our API, not merely hidden. It lasts 15 minutes and then stops working on its own. Each one is recorded — who opened it, which coach's account, and every client whose data was opened — and those records are kept as an audit trail.

We do this to fix problems, never to browse. It is the only way Valeva staff see a client's coaching data, and clients are not notified of a session on their coach's account.

If your coach runs a community, what you post or comment there is visible to that community's other members and to your coach, along with your name and photo. Your membership of one is never shown to anyone outside it.

You can block another member. Blocking hides each of you from the other across every community you share, and the person you block is not told.

You can report a post or a comment. A report sends your coach the reported words, your reason and anything you add, and Valeva staff can see it too — so that we can act if a report is not dealt with. The person you reported is not told who reported them. A report keeps its own copy of what was reported, so it still records what you saw even if the content is later edited or deleted.

The coaching product — the dashboard and the mobile app — contains no third-party analytics, tracking or advertising SDKs. Your coaching data is never fed to an analytics platform. The one third-party SDK that does run in the product is an error reporter, and it is covered under crash diagnostics below.

Our public marketing website (valeva.com) uses Google Analytics to measure aggregate site visits — standard traffic measurement (pages viewed, rough region, how visitors found us). It runs only on the marketing pages, never inside the product, and is never linked to your account or coaching data.

When something in the product breaks, we need to know what broke. The dashboard and our servers send an error report to Sentry — a diagnostics service — containing the error, where in our own code it happened, and the page or request it happened on.

A report deliberately carries no coaching data. We switch off every category that would collect it, and strip what is left again before anything is sent: no request bodies, no database query text, no form contents, and none of the in-memory values our code was holding at the time. You are identified by your account id alone — never your name, email address or IP address — and we record no session replay, so your screen is never captured.

We also drop the query string from any address in a report, because that is where a search you typed would be. Reports are retained by Sentry for a limited period and used only to find and fix faults.

You can delete your account in-app (Settings → Delete account) or by emailing us. Deletion is a hard delete of your world — profile, logs, photos, files and connections. A few honest exceptions: messages you sent to other people remain in their conversations attributed to “Deleted user”, and product feedback you submitted is retained with your identity removed. Backups age out on a rolling basis.

Data is encrypted in transit; wearable tokens are encrypted at rest; file downloads run through signed, expiring, access-checked URLs; and coach-client access boundaries are enforced server-side on every request.

We handle personal information in accordance with the Australian Privacy Principles. You can access, correct or delete your data — most of it directly in the product, and anything else via the support page. If you're not satisfied with our response you can complain to the Office of the Australian Information Commissioner.

Valeva is not directed at children. You must be at least 18 to create an account.

If this policy changes materially we will update this page and the date above, and notify account holders where the change matters to them.