Who else sees your data

Seven companies receive data from Aste today. This is all of them, and what each one gets.

Last updated 4 October 2026

Each entry is a company that receives something today. If that changes, this page is updated. What Aste itself collects and keeps is set out in the privacy policy.

Behind the seven. Each of them runs on infrastructure it rents in turn. Supabase's Irish region is Amazon Web Services in Dublin, and PostHog's German one is Amazon Web Services in Frankfurt; Brevo runs on OVH in France and Google Cloud in Belgium; Anthropic, Apple, Google and Sentry run their services on their own and rented data centres. None of those hosts receives anything from Aste directly, and each is bound to the company above it by that company's own processing agreement.

Supabase

Supabase runs the database, the sign-in system, the file storage and the server functions behind Aste.

It receives everything the app stores. Your email address and name. Your training plan and the settings it was built from, including height, weight, sex and age. Every run you record, with its GPS route and heart rate trace. Your body measurements. Your meals, their calorie and nutrient numbers, and their photo thumbnails. The coach's writing about your training, including the internal records of it you cannot see in the app.

This is held in the European Union, in Ireland. Supabase stores it and serves it back to the app, and does not use it for anything else. Running the service also produces ordinary operational records, such as sign-in attempts and server logs, and rolling backups of the database that age out within seven days. The privacy policy covers those.

Anthropic

Anthropic provides the language model behind two features. The two send different things, so they are set out separately.

Meal photos

When you photograph a meal, the photo is reduced on your phone to 1280 pixels on its longest edge. That reduced copy is what is sent to Anthropic, together with which meal of the day it is.

If you then tell Aste what the estimate missed, your words are sent word for word, together with the estimate as it stands on your screen and which meal of the day it is. The photo is not sent a second time.

Nothing else goes with it. Not your user id, not your name or email, not your body details, not your plan, not your runs. The full-size photo never leaves your phone and Aste does not store it. What Aste keeps is a small thumbnail, so the meal has a picture in the app.

What is in the frame is up to you. A photo with a face, a screen or a document in it carries that too, and Aste does not check for it before sending. Keep the shot to the plate.

What the coach writes

When the model writes something the coach says to you, it is given counts and labels rather than your records. For example, how many runs you have missed, that the sessions in question were tempo sessions, which week of the plan you are in, how far the session is, how many of the planned runs in the last seven days you completed, and whether each of protein, carbs and fat came in under or over target. It is also given the name you gave your race, if you typed one.

It is not given your name, your email, your date of birth, your sex, your height, your weight, your GPS route, your heart rate trace or your account identifier. None of those are part of what the coach's writing is built from.

What Anthropic does with it

Anthropic processes what it receives in order to produce the text, then deletes it within 30 days. Under its commercial terms it does not use it to train its models. Anthropic's API is not pinned to a region, so this content may be processed outside the European Union; the transfer is covered by Anthropic's data processing agreement, which includes the European Commission's standard contractual clauses.

Apple

Four things go to Apple, and they are unrelated to each other.

Sign in with Apple

If you sign in with Apple, Apple confirms who you are and returns an identifier to Aste. On the first sign-in it also returns your name and an email address. That address may be a Hide My Email relay, in which case Aste never has your real one.

Speech recognition

If you dictate a correction to a meal estimate instead of typing it, your phone transcribes what you said, and the audio may be sent to Apple to do that. The transcribed text then goes to Anthropic with the estimate as it stands, the same as a typed correction. The photo is not sent again.

Maps

Your route is drawn on an Apple map while you run and on the run afterwards. Drawing a map means asking Apple for the map of that area, so Apple sees which part of the world is being looked at. Your recorded route is not sent to Apple, and the map is drawn on your phone.

Notifications

If you allow notifications, Apple's push service delivers them to your phone. Apple receives your phone's notification address and the notification, which is a fixed line and a reference number the app uses to open the right message. It carries no health data and nothing the coach wrote.

For all four, Apple decides for itself what it does with what it receives, under its own privacy policy. Aste does not set Apple's rules and cannot delete what Apple holds.

Google

Google is a way to sign in and nothing more. If you choose it, Google confirms who you are and returns your name and email address to Aste.

There is no Google software in the app. Google receives no health data, no meals, no runs and no training data. Like Apple, Google handles its own sign-in service under its own privacy policy.

PostHog

PostHog counts how the app is used, so it is possible to see where people get stuck. It also receives recordings of the app's screens, described under Recordings of the screens in the privacy policy. They are pictures of the app as you use it. Before they leave your phone, these are covered: your name and email, your password and sign-in codes, your body measurements, your heart rate, your routes, your meal photos, and the notes you write on a workout. What the coach writes to you shows, including a note after a run that mentions your heart rate. Some screens are never recorded: a run in progress, the meal camera, the screens where you agree to the use of your health data, and the setup screens for Apple Health and your body details.

It receives an account number and a record of things you did: that you finished a step of the setup, that you committed a plan, that a workout was logged, that a meal was logged. Alongside those it holds a few labels about the account — how you signed in, whether the account is free or paying, whether a plan is active, the race distance, the plan length, the experience level, whether Apple Health is connected, the region your phone is set to, and the app version, device model and iOS version.

It receives no body measurement and no heart-rate reading as a record. Not your name, not your email, not your date of birth or age, not your height, weight or sex. Not your meal photos, not your meal descriptions, not your heart rate, not your GPS route. None of these is sent as a record. In the screen recordings each one is covered, with two exceptions: what your meals are called and made of shows, and so does a heart-rate figure the coach mentions after a run. If the app refuses an account for being under 18, that it was refused is recorded, without the year.

In those records, your answers in the setup appear as the choice you made, a range or a count, never as a body figure: a weekly distance band, how many runs a week, a recent race time rounded to five minutes. For your height, weight, sex and birth year it is told where the value came from — Apple Health, an earlier plan, or you — and whether you gave a sex at all, and not the value.

A run reaches PostHog as a rounded distance, its duration and its moving time. It is also told the kind of session, whether it was indoors, whether it matched the plan and how you rated it; whether it was recorded on the phone, on the watch or imported; and whether it has a route and heart-rate readings. The route and the readings themselves are never sent.

A meal reaches it as which meal of the day it was, the date, whether it was logged by photo or by hand, how many items it had, and whether it has a photo.

Each of those carries the identifier of the record, which means nothing outside Aste's own database.

Once a day it is also sent a snapshot of each account: whether a plan is active, the race distance, which week of the plan it is, how many days it is since you signed up, and whether you logged fewer meals in your second week than in your first. The first time you log meals on three days in your first week, that is recorded too, with the number of days.

It also receives no location and no IP address. The project is set to discard the IP address at the door, and every event additionally carries a flag that switches off PostHog's own country lookup, so neither the address nor anything derived from it is stored. When you delete your account, Aste asks PostHog to delete what it holds about you; if that request fails, the records stay until PostHog's own schedule removes them. That schedule is set by the plan Aste is on — one year today for usage records, and 30 days for screen recordings.

This is held in the European Union, in Germany. PostHog processes it under its data processing agreement and does not use it for anything else.

Sentry

Sentry records crashes and errors, so a fault can be found and fixed rather than guessed at.

It receives an account number, the crash or error itself, the app version and build, and the device model and iOS version. Error messages are stripped of anything that looks like an email address, a token or a file path before they are sent, and the trail of steps attached to an error is reduced to the address of the request without its query.

It receives no health data, no meals, no runs and no training data, and it is not told your IP address.

This is held in the European Union, in Germany, and cannot be moved once an organisation is created there. Errors are held for the length of Sentry's plan and then removed.

Brevo

Brevo sends the emails the app sends you. Today those are the messages that carry a code: when you sign up with an email address, when you reset your password, and when you change your email, which sends a code to both the old address and the new one.

It receives your email address and the message itself. It is not given your name or anything you have recorded in the app. If you sign in with Apple or Google and the app never emails you, Brevo receives nothing about you.

This is held in the European Union, in France and Belgium. Brevo keeps a record of each message it sent on its own schedule, which Aste does not set. Deleting your account does not remove it.

What is not here

• No advertising network. Aste carries no advertising and does not sell your data.
• No advertising or marketing analytics. PostHog and Sentry count how the app is used, record its screens with the details listed in the privacy policy covered, and record its crashes, and nothing else. Neither is a tracker, and neither is given your name or your email — only the account number your records already hang on.
• No third-party trackers. The app's privacy manifests declare no tracking and no tracking domains.
• No food or nutrition database. Every calorie and every gram of protein, carbs and fat in the app comes from the estimate made from your photo or from what you typed yourself.
• No payment processor. Nothing is charged yet. When subscriptions start, Apple takes the payment and Aste receives only whether you are subscribed, never a card number; this page will say so when it applies.
• Apple Health data is never used for advertising and is never sold.

This website

These pages are static and carry no scripts, no cookies and no analytics. They are served by Cloudflare, which sees the ordinary request records any web host sees, including your IP address, and keeps them on its own schedule, which Aste does not set and cannot read. Nothing you do on this site reaches your Aste account, and Aste does not know you visited.

One page is not static: a plan card shared as a link, at an address of the form asteperformance.com/p/…. It is built when it is opened, from the card's image and two lines of text the runner published from the app, and it carries no scripts, no cookies and no analytics either. Cloudflare serves it and sees the same request records; nobody at Aste sees who opened it. The privacy policy says what the card carries and how the runner removes it.

Mail you send to the support address passes through Cloudflare on its way to the inbox where it is read.

Questions

Write to support@asteperformance.com and ask. The privacy policy covers what is collected, how long it is kept, and how to delete it.