Privacy

What Aste records about you, where it goes, and how to get a copy of it or delete it.

Last updated 9 October 2026

Aste is a running coach. To build your training plan and adapt it as your training develops, it keeps a detailed record of your body, your runs and what you eat. Most of that is health data, which the GDPR calls special category data and protects more strictly than ordinary personal data.

This page describes the app as it works today. If something changes, this page changes with it.

Who is responsible

Aste is published by Alexhander Törnqvist, Kellgrensgatan 10, 112 51 Stockholm, Sweden, who is the data controller for everything described here. For any privacy question or request, contact support@asteperformance.com.

What Aste collects

Your account

Aste holds your email address, and a password if you signed up with one. If you signed in with Apple or Google instead, Aste receives an account identifier from them, together with the name and email address they pass on. Sign in with Apple can hide your real address behind a relay address, and it returns your name only the first time you authorise it.

Aste also holds your first name, your time zone, and the settings you pick in the app.

Aste records when your account was last used. The time is written when you sign in and when the app renews your sign-in, which it does while you use it online, and it is written at most once every 24 hours. The record exists so that an account nobody uses can be found later. Nothing acts on it, and there is still no inactivity rule.

Your body and your training profile

Aste asks for the information a coach needs before it can write a plan. These details are stored with your plan:

• Height and weight, and body-fat percentage if you provide it.
• Your biological sex and your age.
• Your resting heart rate.
• How active your days are outside running.
• Your running experience, a recent race result if you have one, how many days a week you run and which days, how far you run in a week, your longest recent run, and what strength equipment you have.
• Your race goal: the distance, the date, and the name you type for it.

Resting heart rate and body fat are health data. Age and sex are not, on their own, but Aste holds them alongside the rest and treats the whole profile the same way.

Your plan and how it changes

Aste keeps the plan itself, week by week and session by session, including target paces, heart-rate ranges and strength sets. It also keeps a record of every adjustment made to your plan: what triggered it, what the plan looked like before and after, and Aste's own running estimate of your fitness.

Every one of those adjustments is made by the calculation, not by a person. Nobody at Aste reads your plan or decides what goes in it. What the calculation decides changes your training targets and nothing else: it has no legal effect on you and no bearing on anything outside the app.

Sharing your plan

When you share your plan card as a link, Aste publishes the card at a public web address on asteperformance.com and keeps the image and the two lines the page prints under it: the race and the race day. The address is a long random code that cannot be guessed, and it is not your plan's identifier. Anyone who has it can open the page, and nothing on it names you: the card carries no name, no email address and no account identifier.

Nothing is published until you tap a share destination that carries a link: WhatsApp, Messenger or More. Sharing to a Story, or saving the card to your photos, publishes nothing. You can remove the link at any time from Plan settings, and the page disappears; deleting your account removes it too. The next share makes a new link.

The page is served by Cloudflare, which sees the ordinary request records any web host sees, including the IP address of whoever opens it. The image is stored by Supabase in the EU (Ireland). The page carries no scripts, no cookies and no analytics, so Aste does not know who opened it or how many times.

Your runs, including where you ran

For every run you record or import, Aste stores the date and time, distance, duration, average heart rate, cadence, elevation gain, calories, whether it was indoors, how hard it felt, any name or notes you type, and which app and which device recorded it.

For a run you record in Aste itself, it also stores:

• Your route as precise GPS. Latitude, longitude, elevation and a timestamp for each sample, kept until you delete the run or your account.
• Your heart rate through the run, sampled about once every five seconds. A one-hour run holds roughly 720 readings.
• Your kilometre splits, and your pauses.

A run imported from Apple Health arrives without a route and without pauses. Its splits and heart rate are worked out from what Apple Health holds.

Location is recorded only while a run is in progress. iOS shows its blue location indicator for the whole time. Aste does not record your location when you are not running.

Your meals, and your meal photos

For every meal you log, Aste stores the date, which meal of the day it was, whether you photographed it or typed it, its name, its calories, its protein, carbs and fat, and the individual foods identified in it.

Meal photos work like this:

• The full-resolution photo from your camera is never sent anywhere and never stored.
• A copy reduced to 1280 pixels on its longest edge is sent to Anthropic to produce the estimate. It is held in memory for that one request and is not stored.
• A separate, smaller copy at 320 pixels on its longest edge is stored so the meal has a thumbnail in the app. It sits in a private storage area that only your account can read.

A photo can contain more than the meal. Keep faces, screens, documents and medication labels out of the frame. Aste needs to see the plate and nothing else.

If you tell Aste what an estimate missed, by typing or speaking, your words are sent to Anthropic 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. Speaking is covered under Apple below.

What the coach writes about you

When the coach writes something about your training, Aste keeps a copy of that text, together with the facts it was written from and a note of whether the text was used or thrown away. It is kept so the coach's writing can be checked and improved.

These records are kept for 30 days. A job runs once a day and deletes every record older than that. The one exception is a record being used to look into a fault in the coach's writing: it is kept until that is closed, and then the same 30 days apply to it.

You cannot see these records in the app. They are personal data about you, so they are covered by a request for a copy of your data, and they are deleted with your account.

Notifications

If you allow notifications, your phone gives Aste an address that Apple's push service uses to reach it. Aste stores that address against your account, with which of Apple's two delivery services it belongs to and whether "Plan changes" and "Weekly recap" are switched on for that phone. For each notification it sends, Aste keeps a record of which message it was about, which phone it went to, and what Apple answered.

The address is removed when you sign out on that phone (if the phone is offline at that moment, the next time Aste is opened on it with a connection), the next time you open Aste after turning its notifications off in iOS Settings, when Apple reports that it no longer works, and when you delete your account. Withdrawing your consent to health data does not remove it, because it is not health data and your account stays. The record of what was sent is removed with the message it was about.

Technical records

Running the service creates two kinds of technical record. Sign-in attempts are also rate-limited by IP address, so your IP address is processed when you sign in.

Sign-in audit entries. The sign-in service writes an entry for each account event, such as a sign-up, a sign-in or a deletion. These entries are kept in Aste's database. An entry can carry the account's email address and its identifier, and that includes the entry written when an account is deleted. A job runs once a day and deletes every entry older than 90 days, so an entry can be kept for up to 91 days.

Server logs. Supabase, Aste's hosting provider, produces server logs while running the platform. It keeps them for 1 day on the plan Aste uses today, and for 7 days on the plan Aste moves to at public launch. Aste does not set that period.

These records exist to keep accounts secure and the service working. They are not used to profile you and they are not combined with your training data.

How the app is used

Aste records what you do in the app, so it is possible to see where people get stuck and what is worth fixing. This goes to PostHog, hosted in the EU.

The usage records are what you did and a few facts about it, never the record itself. That you finished a step of the setup, and which step. That you committed a plan. That a workout was logged, and whether it was a run or a strength session. That a meal was logged.

In the usage 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 it 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.

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 your app version, device model and iOS version. Each one is attached to your account identifier — the same opaque number the rest of your records use — and not to your name or your email.

The usage records carry no body measurement and no reading. Not your height, weight, sex, date of birth or age. Not your daily activity level. Not your meal photos, your meal descriptions or anything else you typed. Not your heart rate. Not your GPS route or any coordinate. Those stay in Aste's own database. If the app refuses an account for being under 18, that it was refused is recorded, without the year.

No location and no IP address either. The project is set to discard your IP address at the door, and every record additionally carries a flag that switches off PostHog's own country lookup, so neither the address nor anything worked out from it is stored.

Recordings of the screens. While you use the app, it also records what its screens look like, as a series of pictures — about one a second — with where you tapped. That shows where people get stuck in a way the records above cannot. The recordings go to PostHog too, hosted in the EU.

Before a picture leaves your phone, a black box is drawn over your name and email, your password and your sign-in codes; your height, weight, sex, birth year and age, and how active you are day to day; your heart rate and heart-rate zones; your routes and maps; your meal photos; and the notes you write on a workout.

Everything else on the screen shows as you see it. That includes your plan, the distance, pace and time of your runs and how they felt, the weights and reps you logged, the name you gave your race or a workout, what your meals are called and made of and their calories and nutrients, and what the coach writes to you. When the coach's note after a run mentions your heart rate, its average or its highest, that shows too. It is the one place a heart-rate figure appears in a recording.

Some screens are never recorded at all: a run while it is happening, on your phone or from your watch; taking a photo of a meal, until the photo has been read; the screens where you agree to the use of your health data; and, during setup, the screens where you connect Apple Health or give your height, weight, sex and birth year.

Recordings are kept for 30 days and then deleted. When you delete your account, Aste asks PostHog to delete them along with your usage records.

Crashes and errors

When the app crashes or hits an error, a report goes to Sentry, hosted in the EU. It carries the fault itself, your account identifier, 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 a report is reduced to the address of the request without its query. Sentry is not told your IP address, and it receives no health data, no meals, no runs and no training data.

On your phone

Some information is held on your phone and your watch rather than on the server.

• Your settings: notifications, haptics, recording preferences, whether Apple Health is connected, and a marker of how far the Apple Health import has read. These are never uploaded, with one exception: the "Plan changes" switch is also stored on the server, against that phone's notification address, so that Aste knows whether to send to it. It is described under Notifications above.
• Your account identifier, so a run recorded while you were signed in reaches your account and not somebody else's.
• Runs that have not reached the server yet. If you record a run with no signal, it waits on the phone until it can be sent, with its full GPS route and heart rate. A three-hour run is about 2 MB, and it is protected by the phone's own encryption. It is removed once it is sent. If the server refuses it for good, or if you sign out before it goes, it stays on the phone rather than being thrown away, so it can be counted and looked at instead of disappearing without telling you. Deleting your account does not reach it, because it never left the phone. Withdrawing consent on that phone removes it, and so does deleting the app.
• On the watch: finished runs waiting for the phone to collect them, and a copy of the plan week the watch is showing you. Both sit in the watch's own storage under the watch's encryption.
• Meal thumbnails you have already seen may be held in your phone's ordinary web cache, the way any image in any app is.

What Aste does not do

Apple Health

If you connect Apple Health, Aste reads the following. iOS asks you about each of these and you can refuse or withdraw any of them in the Health app.

Aste writes three things back to Apple Health, and only for runs you record in Aste itself:

• The workout.
• Its route.
• Its walking and running distance.

Active energy is deliberately not written back. Your watch or phone has already counted those calories, and writing them again would double-count your day.

On the watch, the permission sheet asks to save heart rate, distance and active energy as well. watchOS requires that permission before an app can run a workout session and read live values from it. The Aste watch app uses it to read, and saves nothing itself.

Turning off Apple Health stops new data arriving. It does not remove what Aste already holds; for that, delete the item or delete your account.

Who else processes your data

Seven companies receive data from the app today, and no others.

Each of the seven 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 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.

This website, including the page behind a plan card you have shared as a link, is served by Cloudflare, which sees a visit but never your account; Who else sees your data covers it.

Product analytics

PostHog receives the usage records and the recordings of the screens described under How the app is used. They come from three places — the app itself, Aste's own server functions, and the database when a row is written — and all three send the same account identifier, so they describe one person rather than three.

PostHog holds it in the European Union, in Germany, under its data processing agreement. It is not used for advertising, it is not combined with anything from outside Aste, and it is not sold.

Crash reporting

Sentry receives the crash and error reports described above, from the app and from Aste's server functions. Its organisation is created in the European Union, in Germany, and that cannot be changed afterwards. It runs under Sentry's data processing agreement.

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.

There is one exception. When you open Share on a run, Aste asks Apple for the name of the place the run started, so the share card can print it, for example "Kungsholmen, Stockholm, Sweden". That sends Apple the first point of the route and nothing else. The name stays on your phone until the app is closed, and it is not stored with the run.

Speech

You can correct a meal estimate by speaking instead of typing. Aste uses Apple's speech recognition for that, and it is not restricted to on-device transcription, so your recorded speech may be sent to Apple's servers to be turned into text.

Apple handles that audio under its own privacy policy. Typing the correction instead avoids this.

Push notifications

When the coach has a change to your plan for you to review, or a note about your eating, Aste asks Apple's push service to put a notification on your phone. Apple receives your phone's notification address and the notification itself. The notification is a fixed line, the same for everyone: "Plan update — You've got a change to your plan. Tap to review the change." or "Nutrition update — You've got a note about your eating. Tap to review your targets." With it goes a reference number the app uses to open the right message when you tap it.

On Sunday evening, when your weekly recap is written, Aste sends one more: "Weekly recap — Your week is in. Tap to read it." It carries the same fixed line for everyone and the recap's reference number, nothing about your week. "Weekly recap" in App Settings turns it off on that phone.

It carries no health data, no numbers and nothing the coach wrote. What the coach wrote stays in the app. No notification is sent between 21:00 and 08:00 in the time zone your phone last reported to Aste (or UTC, if it never has); one that falls in that window waits until 08:00.

What goes to the AI model

Aste writes its coaching text with a model run by Anthropic, and estimates meals from photos the same way. What crosses is deliberately narrow.

For a meal estimate: the reduced photo and which meal of the day it is. For something the estimate missed: what you typed or dictated, the estimate as it stands, and which meal of the day it is.

For coaching text: figures worked out from your records, never the records themselves. 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 many days it is to your race, how far and how fast a session is meant to be, how many of the planned runs in the last seven days you completed, and what the plan has you eat that day. After a run: your average pace, your fastest and slowest kilometre, how the first third of the run compared with the last, the pace of each rep, and your average and highest heart rate for that run. After a meal: what it contained, whether you logged it in the morning, afternoon or evening (never the time itself), what you have eaten that day so far against the day's targets, and how many days in a row you have been inside your calorie target. For the weekly recap: the week's totals (distance, time and climb), how many of the planned sessions you did, each run's distance, pace and average heart rate, which sessions were missed by their day of the week (never their date), how many meals you logged against the week's targets, the totals of the four weeks before, and any record the week set. It is also given the name you gave your race, if you typed one.

What never goes to it

• Your name and your email address.
• Your date of birth, your sex, your height and your weight.
• Your GPS routes.
• Your heart-rate traces. Two numbers per run cross, its average and its highest, and nothing else of your heart rate.
• Your account identifier. Aste attaches nothing that points back at you.

What you put into a photo or a correction is another matter. A photo with a face in it, or the name of a race only a few people ran, can identify you on its own. Aste does not read what you send to check for that, so the list above says what Aste attaches. It is not a promise that every request is anonymous.

Anthropic processes what it receives in order to produce the text or the estimate, then deletes it within 30 days. Under its commercial terms it does not use it to train its models. Both are Anthropic's commitments to Aste, and if either changes, this page changes.

Where your data lives

Your database records, your account, your meal thumbnails and the image behind a plan card you have shared as a link are hosted in the EU (Ireland).

Anthropic's API is not pinned to a region, so the content sent to the model may be processed outside the EU. That transfer is covered by Anthropic's data processing agreement, which includes the European Commission's standard contractual clauses — the approved mechanism for sending personal data outside the EU.

That applies to meal photos, what you add to an estimate, and the coaching facts listed above. Nothing else leaves the EU by that route.

Emails the app sends are sent by Brevo from the EU (France and Belgium).

Your usage records and the recordings of the screens are hosted in the EU (Germany), and so are your crash and error reports.

Signing in with Apple or Google, speech recognition, and delivering notifications run on those companies' own infrastructure.

If you want a copy of the contractual safeguards for a particular transfer, ask at the address below.

How long it is kept

Your data is kept until you delete it, or until you delete your account. There is no automatic clear-out of old runs, routes, meals or the coaching messages you can read in the app, and there is no inactivity rule: an account that has not been opened for a year keeps everything.

Two things in Aste's database have a fixed period. The record kept of what the coach wrote is deleted after 30 days. That is described under "What the coach writes about you" above. Sign-in audit entries are deleted after 90 days. That is described under "Technical records" above.

If you want something gone before then, delete the item in the app where the app lets you, or delete your account.

Deleting a run removes everything recorded with it: the route, the heart-rate readings, the splits and the pauses. Deleting a meal removes it, its photo and the coach's note about it. If the same photo belongs to another meal, because you logged that meal again from your previous meals, the photo stays until that meal is deleted too.

Backups. Supabase keeps backup copies of the database on a rolling schedule, and a deleted record can sit in those copies for up to seven days before it ages out. Backups exist to recover the whole service after a failure. Aste never uses one to bring a deleted account or a deleted item back.

Usage records and crash reports. When you delete your account, Aste asks PostHog to delete your usage records and the person they hang on. That request is made once, during the deletion, and your account is deleted whether or not it succeeds; if PostHog cannot be reached at that moment, the records are not deleted then, and stay until the retention period below ends. Each service removes what it holds on its own schedule, set by the plan Aste is on, which Aste cannot shorten. On the plan Aste uses today that is one year for usage records, 30 days for recordings of the screens, and the length of Sentry's plan for crash reports. Sentry keeps no per-person store, so there is nothing there to delete with an account.

The technical records are the other exception. Deleting your account does not remove them. Sign-in audit entries are deleted once they are older than 90 days, by a job that runs once a day, so an entry can be kept for up to 91 days. That includes the entry written when you delete your account, which carries your email address and your account identifier. For up to 91 days after you delete your account, your email address remains in that entry. Server logs are kept by the hosting provider for 1 day on the plan Aste uses today, and for 7 days on the plan Aste moves to at public launch. Aste does not set that period.

Brevo keeps a record of each email it sent, on its own schedule, which Aste does not set. Deleting your account does not remove it.

Why Aste is allowed to hold this

• Your account and the app itself run on the contract between you and Aste. In the GDPR's terms, Article 6(1)(b).
• Health data is held on your explicit consent: Article 9(2)(a). The sign-up screen has a box you tick before an account is created. It reads "I accept the Terms, Privacy Policy and consent to the use of my health data to build and adapt my training plan", and the words "health data" open a list of what that covers. One box covers the terms and the consent together. An account created before the box existed is asked for consent the first time it opens a version of the app that has it, and cannot be used until it answers. Aste records what you consented to, which version of the text you were shown, and when. What health data Aste holds is what you enter and, if you connect it, what it reads from Apple Health.
• Security and keeping the service running covers the technical records above, and the record of when your account was last used, on the basis of legitimate interests, Article 6(1)(f).
• Knowing how the app is used, and fixing it when it breaks covers the usage records, the recordings of the screens and the crash reports, on the basis of legitimate interests, Article 6(1)(f). There is no advertising and no profiling for advertising. The usage records and the crash reports carry no health data. The recordings of the screens show your plan, your runs and your meals as they appear in the app; your name and email, body measurements, heart rate (other than where the coach's note mentions it), routes, meal photos and workout notes are covered. You can object to it at the address below.

You can withdraw consent at any time, in the app under Security & privacy. Withdrawing removes your health data and keeps your account. Your plan and what you told Aste to build it, your runs and their routes, your heart-rate traces and zones, your meals and their photos, your body measurements, your coaching history and the coach records you cannot see are all deleted after you sign in again to confirm it is you. Meal photos are removed from storage first, and the rest goes in one step. Runs waiting to be sent are removed from the phone you withdraw on and from your watch, and from any other phone the next time the app is opened on it. Your account, your name and your sign-in stay, and so do your phone's notification address and the record of the consent you gave and withdrew. No notification is sent to an account that has withdrawn.

Because every part of Aste runs on health data, an account without consent can do nothing in the app except consent again, sign out, or delete the account. If you consent again you start from nothing: what was removed is not brought back.

Short of withdrawing, you can turn off Apple Health in the iOS Health app to stop that flow, or stop recording runs. Withdrawing does not undo processing that already happened, and a copy of what was removed can survive in a database backup for up to seven days, as described under “How long it is kept” above. The usage records described under “How the app is used” are not removed by withdrawing. They hold no health value, and they go when the account is deleted. The recordings of the screens are not removed by withdrawing either; they are deleted after 30 days, or with the account.

Your rights

You have the right to get a copy of your data, to have it corrected, to have it erased, to receive it in a portable form, to restrict how it is used, and to object to processing based on legitimate interests.

You can also complain to a data protection authority, and you do not have to raise it with Aste first. Aste is established in Sweden, so the Swedish authority is Integritetsskyddsmyndigheten (IMY), and you can complain to them or to the authority in the country where you live.

To exercise any of these rights, email support@asteperformance.com.

Requests are answered within a month. If a request is complex, the GDPR allows up to two more months, and you will be told within the first month if that is needed. There is no charge.

Because a copy of your data includes your routes and your health record, you may be asked to prove the account is yours before anything is sent.

Getting a copy of your data

Ask by email and a copy of your data is sent to you within a month. That includes the coach records you cannot see in the app.

There is no export button in the app. The request is handled by hand. If that changes, this page will say so.

Correcting things

You can change your first name, your height and weight, and your plan inputs, in the app. You can delete any run or strength session you logged. On a run you can change its name, your note and how you rated it; its distance, time and route cannot be changed in the app. A logged strength session cannot be edited in the app yet. You can delete any meal you logged. A meal can be changed until you confirm it, and after that it cannot be edited in the app yet. For any of those, email the address above and it is corrected or removed by hand.

For anything the app does not let you edit, email the address above.

Deleting your account

Deleting is built into the app, under Security & privacy. Aste shows you how many workouts, meals and photos you are about to lose, and the plan you are training on, then asks you to sign in again before it deletes anything.

Deleting your account does not cancel an App Store subscription. Once subscriptions exist, cancel with Apple separately.

Security

Everything travels over HTTPS.

Every table in the database has row-level security switched on, so a signed-in account reaches only its own rows, and the database enforces that rather than the app.

Meal thumbnails sit in a private area keyed to your account. The plan and coaching records are written only by the server. You can read them, and the only thing you can change is marking a coach message as read, which cannot be undone.

No system is secure against everything.

If a breach reaches your data, you will be told. The GDPR requires that only when the risk to you is high; Aste tells you regardless, and reports the breach to IMY where the law requires it.

Children

Aste is not built for children and is not for anyone under 18.

The app asks for the year you were born, not the date, so it cannot tell 17 from 18 within one year. It refuses anyone it cannot be sure is 18, which includes people who turn 18 later in the same year, and it says which January they can start. An account that is refused can be deleted there and then.

The app does not delete such an account by itself. If Aste learns that an account belongs to someone under 18, it is deleted by hand, with its data.

Changes to this page

When what Aste does with your data changes, this page is updated and the date at the top changes.

If a change is significant, you will be told by email rather than left to notice it here.

If Aste ever wants to use your health data for something new, a change to this page is not consent. You will be asked, separately, before it starts.

Contact

Any question about this page, or any request under it: support@asteperformance.com.