GoalBlocks

Privacy Policy

Effective October 11, 2026 · Applies to the GoalBlocks app for iPhone and Apple Watch

The short version

We use your training, nutrition and health data to coach you. We never sell it, never share it with advertisers or data brokers, and there are no ads in GoalBlocks.
AI features run only after you say yes. Our AI partners, OpenAI and Google, see only what is needed to answer you, never your name, email or account, and they do not train their models on it.
Your run routes stay on your device. To show the weather on a past run, we send only an approximate area, rounded to about a kilometre.
Our analytics tool never receives your Health readings, and you can switch it off in Settings.
You can export your data, or delete your account and everything in it, from inside the app.

Who we are

Module Creative LLC ("we", "us") builds GoalBlocks, a training and nutrition coaching app. This policy explains what data GoalBlocks handles, why, and the choices you have. If anything here is unclear, write to us at hello@goalblocks.app.

What we collect

Account

You sign in with Apple, with Google, or with an email address and password. We receive your email address and, if you share them, your name and profile picture. With Sign in with Apple you can hide your real email; the private relay address works fully with GoalBlocks. If you sign up with email and password, the password is handled by our sign-in provider (Supabase) and stored only as a secure hash; we never see or store the password itself. A profile photo you pick inside the app stays on your device.

Your profile and answers

During setup and in the app you tell us about yourself: your name, date of birth, sex, height and weight, your training experience, goals, race, schedule, gym and equipment, and any injuries, limitations or trouble spots you mention.

Health and fitness data

With your permission, GoalBlocks reads from Apple Health: workouts and workout routes, running distance, steps, active and resting energy, heart rate, resting heart rate, heart rate variability, VO2 max, respiratory rate, blood oxygen, body and wrist temperature, sleep, body weight and body composition, nutrition, and your date of birth and biological sex. It writes back the runs and strength sessions you complete and the meals you log, so your history stays consistent across apps. You choose each of these in the Health app.

Inside the app you also create training data directly: goals, training plans, completed sessions, strength sets and weights, bodyweight test results, body weight entries, readiness check-ins, and how a session felt.

Location

During outdoor runs, with your permission, GoalBlocks uses your location to record route, pace, distance and elevation. Route coordinates are processed on your device and saved to Apple Health on your device. They are never uploaded to our servers. Only summary numbers such as distance, duration, pace and elevation gain sync to your account.

The weather card on the home screen uses your location to fetch a forecast from Apple Weather. To show the weather on a past run, the app sends Open-Meteo, a weather service, an approximate area (rounded to about a kilometre) and the date, with nothing that identifies you.

Meal photos and food logging

When you photograph a meal or a nutrition label, the photo is sent to our servers and to our AI partners to estimate its nutrition. A small preview image is kept so your meal log has a thumbnail, and it is deleted from our servers automatically after 30 days. The estimate itself (calories, protein and so on) stays in your log. When you type a meal instead, the text is sent to our AI partners to estimate it.

Food searches go through our servers to FatSecret, our food database, and ingredient lookups to the USDA FoodData Central database. Barcode scans are looked up in Open Food Facts directly from your device, using only the barcode. None of these receive your identity.

Coach

Your conversations with the coach are stored with your account so they survive reinstalls. So the coach remembers you, it also keeps short notes from your conversations (for example an injury, a preference or a goal you mentioned) and a log of your last 28 days of training and meals. Check-ins you schedule with the coach are written on our servers at the time you chose.

To answer some questions, the coach can search the web through our AI partner. When a reply cites a website, the app loads that site's small icon from DuckDuckGo, which receives only the site's name.

If you speak to the coach, your voice is turned into text by Apple's speech recognition, on your device whenever your iPhone supports it. We do not keep the audio.

Feedback and support

When you write to us from the app (help and support, feedback, or sending us a coach conversation), we store your message, the email you want us to reply to, a short line about your app version and device, a one-way hash of your network address to limit spam, and, if you chose to send one, the conversation. Screenshots you attach travel to our inbox by email and are not stored on our servers. These messages reach us through Resend, our email delivery service.

Usage analytics

We use PostHog to understand how GoalBlocks is used: which screens you visit, which features you use, and product events such as finishing setup, starting and finishing a session and how long it took, logging a meal and how, applying a plan change, the coach's daily call (for example keep the plan or ease off), and purchases and which plan. These events are linked to a random account identifier, not to your name or email.

Analytics never include your Health readings. Heart rate, heart rate variability, sleep, body weight and composition, readiness scores, meal contents, photos, what you write to the coach, and locations are never sent to PostHog. You can turn analytics off in Settings, and the app works the same without it.

Device and notifications

If you enable notifications, we store a push token and an app-specific device identifier so a notification reaches the right device, a log of what we sent you, and your notification preferences. We do not collect advertising identifiers or device fingerprints, and we do not track you across other companies' apps or websites.

Purchases and promo codes

Subscriptions are processed entirely by Apple. We never see your card number or billing details; we receive only your subscription status so the app knows what you have access to. A promo code you enter is checked on our servers and is not linked to anything else about you.

What we do with it

Everything above serves the same purpose: building your plan, adapting it to how you are actually recovering and progressing, and coaching you. Specifically, we use your data to:

Generate and adapt your training plans across your goals
Compute readiness, recovery and progress from your workouts, sleep and heart data
Estimate nutrition from photos, labels, descriptions and food searches
Answer your questions and suggest plan changes through the coach
Send the notifications and check-ins you have chosen
Keep your data in sync across your iPhone and Apple Watch
Answer you when you write to us

We also improve GoalBlocks itself. To understand which programs work and to tune how plans adapt, we analyze de-identified, aggregated training data: how far athletes get in a program, how many sessions they complete, how long sessions take, and how plans hold up over the weeks. These numbers are no longer connected to your name, email or account. Improvement work never uses your photos or what you write to the coach, and we never re-identify this data. You can opt out in Settings, and the app works the same without it.

We do not use your data for advertising or marketing. We do not sell it or rent it. We do not share it with data brokers. We never use Apple Health data for anything other than the features described here, and we never disclose it to third parties for advertising, marketing or data mining. GoalBlocks does not store Health data in iCloud.

AI features

You choose

The coach, meal photo and label analysis, typed meal estimates, and the AI-written wording of some check-ins and notifications use AI models run by our partners. None of them run until you allow it, the first time you open the coach or scan a meal. You can change your answer at any time in Settings, under Privacy. While it is off, those features stay off and notifications use plain written text.

What is sent, and to whom

Coach replies: your message, the recent conversation, and a summary of your training context (goals, plan, recent sessions, readiness, sleep and heart trends, meals, and injuries or limitations you told the coach) go to OpenAI, and to Google for some requests.
Meal photos and labels: go to Google, with OpenAI as a backup.
Typed meals: go to Google.
Check-ins and notification wording: short training summaries go to OpenAI.

What is never sent

We never send your name, email address or account identifier to our AI partners. What you type or photograph is sent as you give it, so leave out anything you would rather not share.

How our partners handle it

We use OpenAI and Google through their business APIs. They process what we send to return a result to GoalBlocks. OpenAI states that it does not use data sent through its API to train its models and keeps it for up to 30 days to monitor for abuse. Google processes it under its paid Gemini API terms, under which it does not use your data to improve its products and keeps it only for a limited time to detect abuse.

The coach is a training tool, not a medical professional. Its suggestions are not medical advice. Talk to a doctor before acting on anything that concerns your health.

Who processes your data

We run GoalBlocks on a small set of service providers, each doing one job:

Provider	What it does	What it handles
Supabase	Hosts our database, sign-in and file storage	Your account and all synced app data, in the United States (AWS us-east-1)
OpenAI	Coach replies, web search for the coach, check-in and notification wording, meal photo backup	What the AI features section describes, never your name, email or account
Google	Meal photo, label and typed meal analysis, some coach replies; optional sign-in	What the AI features section describes; your Google account email if you sign in with Google
FatSecret	Food nutrition database	Food search text and selected foods, without your identity
USDA FoodData Central	Ingredient nutrition data	Ingredient names, without your identity
Open Food Facts	Barcode lookups	The barcode, from your device
Open-Meteo	Weather on past runs	An approximate area (about a kilometre) and a date
PostHog	Usage analytics	Screens, features and product events, linked to a random account identifier; never Health readings
Resend	Delivers support messages to our inbox	Your message, reply email and any screenshots you attach
DuckDuckGo	Icons for websites the coach cites	The cited site's name
Apple	Sign in with Apple, subscriptions, push notifications, Apple Health, Apple Weather, speech recognition	Per Apple's own privacy policy

These providers act on our instructions and may not use your data for their own purposes. We share data beyond this list only if the law requires it, to protect the rights and safety of our users, or in a business transfer such as a merger, in which case this policy continues to apply to your data.

How long we keep it

Your account, profile and training data: for as long as your account exists.
Meal photo previews: deleted from our servers automatically after 30 days.
Coach conversations: until you delete them or your account.
Coach notes: until they are removed or you delete your account. The training and meal log keeps only the last 28 days.
Records of AI use (which feature, when, and how much was processed, never the content): 400 days, or until you delete your account.
Usage analytics: deleted from PostHog when you delete your account.
Support messages: kept while we help you. Copies that reached our email inbox are deleted when you ask.

Deleting your account removes your account and its data from our servers right away, including photos. It is not a soft delete, and your data takes no further part in improvement work. If you signed in with Apple, we also ask Apple to revoke GoalBlocks' access to your Apple ID.

Your controls and rights

Delete your account from Settings in the app. This permanently removes your account and its data from our servers.
Export your data from Settings in the app, as a file you can keep.
AI features can be turned off in Settings, under Privacy.
Apple Health access can be granted, narrowed or revoked at any time in the Health app on your iPhone.
Location, camera, microphone and photo access are controlled in iOS Settings and can be revoked at any time.
Notifications can be tuned or turned off in the app and in iOS Settings.
Usage analytics and product improvement can each be turned off in Settings in the app.
Coach conversations can be deleted one at a time or all at once, in the app.

Depending on where you live, you may also have legal rights to access, correct, export or delete your personal data, to restrict or object to processing, and to complain to a data protection authority. You can exercise any of these with the in-app controls or by emailing hello@goalblocks.app. We respond within the timelines the law requires, and we do not discriminate against you for exercising your rights.

Security

Data moves between your device and our servers over encrypted connections (TLS). On our servers, your data is isolated per account: our database enforces row-level rules so one account can never read another's data, and meal photos live under access rules scoped to your account. Access to production systems is limited to what operating the service requires.

Children

GoalBlocks is not directed at children under 13, and we do not knowingly collect data from them. If you believe a child has created an account, contact us and we will delete it.

International transfers

Our servers are hosted in the United States (AWS us-east-1, Northern Virginia), and our AI partners may process data in the United States. If you use GoalBlocks from elsewhere, your data is transferred there and protected as this policy describes. Where the law requires specific safeguards for transfers, such as standard contractual clauses, we rely on those with our providers.

Changes to this policy

If we change this policy in a way that matters, we will tell you in the app before the change takes effect. The date at the top always reflects the current version.