Privacy

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

Last updated 3 September 2026

Aste is a running coach. To build a training plan and change it as your training goes, it holds 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 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. Contact for any privacy question or request: support@asteperformance.com.

What Aste collects

Your account

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 and 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.

Alongside that: your first name, your time zone, and the settings you pick in the app.

Your body and your training profile

Aste asks for the things a coach needs before it can write a plan. These 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.
• Your injury status, meaning whether you are running clear, running with a niggle, or coming back from an injury.
• 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.

Injury status, sex, age, body fat and resting heart rate are health data.

Your plan and how it changes

The plan itself, week by week and session by session, with target paces, heart-rate ranges and strength sets. Aste also keeps a record of every adjustment made to your plan: what set it off, what the plan looked like before and after, and its own running estimate of your fitness.

Your runs, including where you ran

For every run you record or import: 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 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: 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.

If you correct an estimate by typing or by speaking, that correction is sent to Anthropic word for word so the estimate can be redone. Speaking is covered under Apple below.

What the coach writes about you

When the coach writes something about your training, a copy of that text is kept, 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. 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.

Technical records

Running the service produces technical records. Sign-in attempts are rate-limited by IP address, so your IP address is processed when you sign in, and the sign-in service keeps its own audit records of account events. Aste's hosting provider also produces server logs in the course of running the platform. 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.

On your phone

Some things are 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.
• 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. Deleting the app removes it.
• 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.

Who else processes your data

Four companies are involved, and no others.

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.

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.

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, which meal of the day it is, and any correction you typed or dictated.

For coaching text: 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 prescribed 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.

What never goes to it

• Your name and your email address.
• Your date of birth, your sex, your height and your weight.
• Your injury status.
• Your GPS routes.
• Your heart-rate traces.
• Your account identifier. Anthropic receives nothing that points back at you.

Anthropic processes what it receives in order to produce the text or the estimate, then deletes it within 30 days. It does not use it to train models.

Where your data lives

Your database records, your account and your meal thumbnails 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, meal corrections and the coaching facts listed above. Nothing else leaves the EU by that route. Signing in with Apple or Google, and speech recognition, run on those companies' own infrastructure.

How long it is kept

Your data is kept until you delete your account. Nothing expires on a schedule, and there is no automatic clear-out of old runs, routes, meals or coaching records. If you want something gone before then, delete the item in the app where the app lets you, or delete your account.

The technical records are the exception. Sign-in audit entries and server logs are held by the sign-in service and the hosting provider on their own retention schedules, which Aste does not set, and deleting your account does not remove them.

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, given when you enter it or connect Apple Health. Health data carries its own consent requirement on top of the ordinary one: Article 9(2)(a).
• Security and keeping the service running covers the technical records above, on the basis of legitimate interests, Article 6(1)(f).

You can withdraw consent at any time. Turn off Apple Health in the iOS Health app to stop that flow, stop recording runs, or delete your account to withdraw it completely. Withdrawing does not undo processing that already happened.

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, email support@asteperformance.com. Requests are answered within 30 days.

Getting a copy of your data

Ask by email and a copy of your data is sent to you within 30 days. 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 including your injury status, in the app. You can edit or delete any run or meal you logged. 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.

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 affects your data, you will be told, as the GDPR requires.

Children

Aste is not built for children and is not intended for anyone under 16.

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.

Contact

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