privacy policy

Who's responsible for your data

Both amb.training and amb.coaching are operated from Switzerland by house of amb . gasser (sole proprietorship, Via Ronchetto 16, 6821 Rovio, Switzerland), who acts as the data controller for either. See our impressum for the full legal notice. We built amb for athletes everywhere, so we hold this policy to the Swiss Federal Act on Data Protection (FADP) and, for anyone in the EU/EEA, the GDPR. In practice, the same protections either way. Questions about this policy, or requests about your own data, go to hello@trainwithamb.com.

What we collect

Account data: your name and email address, from Google or Apple Sign-In. we never see or store your Google/Apple password.

Training data: your workouts (duration, distance, heart rate, power, pace, cadence, speed, route/elevation, calories) and the training sessions and plans you create or apply. On the app, this comes from Apple Health with your explicit permission; on the web, from any indoor sessions you record here. By default we store a summary of each workout: its sport, start, duration and distance and its average values (average heart rate and power), so the workout shows up across your devices and for a coach you linked, plus the training sessions and plans themselves. The detailed heart-rate, power, pace and GPS data behind a workout stays in Apple Health unless you switch on amb insights, see below.

amb insights: detailed workout data (optional, off by default): this is about the detailed data of your workouts. If you switch it on under Data & privacy in the iOS app, amb analyzes that detail and stores a copy of it on our servers (every heart rate, pace and power sample and the route, for up to two years back), so it also shows on your other devices and a coach you linked can see it. If it is off, only the average values above reach amb, and only those can be shown. Switching it off deletes the copy of the details; the average values stay. There are no switches on the web, you decide in the iOS app.

Advanced insights (amb pro): with amb insights on, amb uses the detail of your workouts (heart rate, kilometre splits, power) to work out the numbers of each workout (time in each zone, best efforts, how much pace or power you get per heartbeat, how much your heart rate drifted), to check your thresholds against your workouts, and to prepare the insights before and after your sessions. Since October 9, 2026 our servers do this calculation from the copy of your workouts stored with amb insights, so your iPhone, iPad, amb.training and your coach all see the same values. The results are stored with your account: the numbers of each workout, the insights for your sessions, a suggested threshold, and your fitness, fatigue and load per day (the last 180 days). They exist only while amb insights is on; switching it off deletes them. Also stored: what you answer under a finished session (how hard it felt on a scale of 1 to 10, the reason you pick when it went differently than planned, such as "Heavy legs" or "Time", the reason for a long pause, and up to three words of your own if you pick "Other"). They exist only while amb insights is on, like the results above; your coach sees them only if you share the details of your workouts. A suggested threshold is never applied on its own; you choose to use it or keep yours. You can switch Advanced insights off under amb insights and keep only the detailed data; that deletes the results on the device, and we record your choice like any consent. Whether Advanced insights and "Load past workouts" (per connected platform) are on is stored with your account, so your choice holds on all your devices.

Your feedback on hints: if you tap thumbs up or down on a hint (such as an insight before a session), or use or keep a suggested threshold, we store that answer with your account, together with which kind of hint it was (sport, how much history it was based on, the suggested and current value). We use it only to find out which hints help and to improve them. Nobody follows up on it.

Workouts from a device platform (Suunto, COROS, Wahoo, Hammerhead): if you connect one of them, we receive a summary of each finished workout: moving and total time, distance, average and normalized power, heart rate, cadence, ascent and calories (from COROS: time, distance, average heart rate and calories; the amb app on your iPhone reads them from COROS, where you connected it). We store the summary so the workout shows up in amb on all your devices. The detailed second-by-second data stays with the platform and is loaded and kept only while amb insights is on. You can delete any workout in the app, and disconnecting a platform deletes all the workouts that came from it. We also keep the access token that lets amb send the sessions you choose to your account there, until you disconnect. With "Load past workouts" on (the default, under Connected apps), amb also loads the summaries of your workouts of the last 2 years from that account, once, in the background; nothing older. Switch it off, before or after connecting, and only new workouts reach amb.

Connections you approve: when you connect an AI assistant by signing in, our authentication provider keeps the approval until you disconnect it.

Notifications: if you allow push notifications, we store a device token so we can send them through Apple's push service.

Consent records: each time you give, decline or withdraw a consent, we record what it was, when, and the exact wording you saw. We keep this to be able to show that consent was given, for as long as your account exists. They are deleted together with the account.

Device pairing (Trainer tab): if you connect a heart rate monitor or smart trainer via Bluetooth, that connection and its live data stay on your device for the session. only the resulting workout summary (not a raw data stream) is saved to your account.

Profile settings: your thresholds, training zones, and goals, as you enter them. Also your birthday, and your resting and maximum heart rate, as you enter them or as Apple Health provides them with your permission. These are optional. Your resting and maximum heart rate are used to calculate your heart-rate zones. Your birthday is used for age-based estimates, such as a maximum heart rate you have not entered yourself, and a coach you link can see it. Leave out what you do not want to share; amb works without it, with less precise zones.

Check-ins and questionnaire answers: if you have a coach, the answers you give in the coach questionnaire (the days you cannot train, preferred times, equipment, areas of pain or injury to avoid loading, your sport background, goals and wishes, and free text about them) and your weekly check-in (how the week felt). Some of this tells something about your health. We use it only to show it to the coach you linked to, and to plan with you.

Sign-in and security records: when you sign in, we keep the time, the kind of device (browser or app) and the IP address of each session, and our infrastructure keeps server logs of requests, which our database provider keeps for about one day. We use them to keep accounts secure and to spot misuse. The sign-in record lasts as long as the session. Only an administrator at amb can see these records.

Why we process it, and on what basis

• Contract. Running your account and showing you your own training data is necessary to provide the service you've signed up for.
• Consent. Your workout and heart-rate data, and everything else that tells something about your health or body: your resting heart rate, areas of pain or injury, how a week felt, and your questionnaire answers. This is "special category" health data under GDPR (and sensitive personal data under the Swiss FADP), so we only process it because you've explicitly chosen to connect Apple Health or a device, which includes the average values of a workout. The detailed data needs your separate yes (amb insights), never by default. You can withdraw that consent at any time (in Apple Health's own permissions, by disconnecting a device, or by switching amb insights off in the iOS app).
• Consent, for analytics. Google Analytics runs only if you switch it on in the cookie choice, and you can switch it off at any time. See "Cookies and local storage".
• Consent, for e-mails. If you are a coach and switch on e-mails about new messages. This is optional, off until you switch it on and confirm it, and you can withdraw it at any time. See "E-mail about new messages".
• Legitimate interest. Keeping the service secure and working as intended, including the sign-in and security records above, to protect accounts and the data in them from misuse, and improving amb's hints and the workout description from your feedback and the kept descriptions described below. You can object to this, see "Your rights".
• No advertising use. We never use your health data, or any other data, for advertising or marketing, and we never sell it or pass it to data brokers.

No automated decisions

amb does not make decisions about you by software alone that have legal or similarly significant effects. Numbers such as your training load, and any plan or suggestion, are for you, or your coach, to read, accept or change.

Who else sees it

We use a small number of processors to run amb. we don't sell or rent your data to anyone:

• Supabase (database and sign-in). stores your account and training data, and verifies you're signed in. The data is held in the EU (Ireland). Privacy policy.
• Lovable (website hosting). hosts this website, including its aggregate visit statistics and standard server logs. Privacy policy.
• Google Ireland Limited and Google LLC (Google Analytics), only if you switch analytics on in the cookie choice. receive your page views and your IP address, see "Cookies and local storage". Google privacy policy.
• Cloudflare (security and delivery). sits in front of the website to protect it from abuse and sets a short-lived bot-protection cookie. Privacy policy.
• IONOS SE (e-mail), only if you are a coach and switch on e-mails about new messages. sends the confirmation e-mail and these e-mails from our mailbox, so it handles your e-mail address and the text of those e-mails. It is a German provider. See "E-mail about new messages".
• Apple Push Notification service, only if you allow push notifications. receives your device token and the text of the notification so it can be delivered. Apple privacy policy.
• Google and Apple. only if you sign in with them, to verify your identity. Google privacy policy, Apple privacy policy.
• Stripe and its company Link, LLC (the seller), if you are a coach and subscribe to amb.coaching. See "Payments" below. Privacy policy.
• Apple, if you buy an amb pro subscription in the iOS app, and for Apple Health if you connect it. See "Payments" below. Apple privacy policy.
• Device and training platforms you connect, such as Hammerhead, COROS, Suunto and Wahoo. Only if you connect them; each has its own privacy policy, which applies to what it holds. We keep the connection token so we can send a workout you chose to your device. Their own privacy policies apply to what they hold.
• AKI.IO GmbH (Berlin, Germany), only when you use "Describe your workout" in the workout editor (amb pro) and the description goes to our server, or when you tap "Tell me more" under an insight, or when amb writes the short text of an insight for you (see "Insight texts"). For "Describe your workout" it receives the text you type there and the steps of the workout you are editing; for "Tell me more" the figures shown on that insight, your next goals, your last two weeks in numbers and the rest of the week's plan (see "Tell me more"); for the short text of an insight the facts listed under "Insight texts". Nothing else. It runs the AI model on servers in the EU (its only subcontractor, AIME GmbH, Berlin, provides the GPU servers) and, by contract, neither logs nor stores the text or the answer. See "Building a workout from a description". Privacy policy.
• The AI assistant you connect, such as Claude, ChatGPT or Gemini, and the AI assistant a coach connects. See the two AI sections below. These providers are chosen by you or your coach, not by us.
• A coach or athlete you connect with. only if you actively link, and only what your consent settings allow. See "Connecting a coach" below — this is the one case where another person, not a processor working for us, sees your data.

Our database and sign-in service run in the EU (Ireland). Switzerland and the EU recognize each other's data protection standards as adequate. Some providers named above, such as Stripe, Apple, Google, Lovable, Cloudflare and Supabase as companies, are providers that may handle data outside the EU and Switzerland, including in the United States. Where that happens, the data goes to the United States, and we rely on the safeguards the law provides: the standard contractual clauses recognised in the EU and Switzerland, or, for a provider certified under it, the Swiss-US and EU-US Data Privacy Framework. The AI assistants you or your coach connect are chosen by you, not by us.

Connecting a coach

amb.coaching lets an athlete link their account to a coach, or a coach receive links from athletes, entirely by choice. Linking shares data between two accounts that would otherwise never see each other's information:

• As an athlete, linking to a coach with their code is one decision, and you confirm it in a pop-up before anything is shared. It lets your coach see your planned sessions, goals, which sessions you completed with their average values (duration, distance, average heart rate and power), whether you have amb pro, and your full profile, including thresholds, heart rate zones and birthday. The detail of your workouts (heart rate, pace and power over time, and splits) your coach sees only while amb insights is on. It also lets your coach add, move and change your planned sessions, including a plan you applied yourself. Only sessions you have actually done are shared, never anything upcoming from your own side. A coach never sees your login details, other accounts, or anything you haven't shared this way, and can only change sessions that aren't completed yet, never mark one done on your behalf. Earlier links follow the same rule: what your coach sees of the detail depends on that one switch.
• A coach using an AI assistant is a separate yes. See "Your coach and AI" below. Linking a coach never switches it on.
• As a coach, turning coaching on for your account generates a personal code and makes your name visible to any athlete who links to you with it. You only see athletes who've actively linked to you, never anyone else's.
• Messages. anything sent through the in-app chat between a coach and their linked athlete is visible to both of you, stored the same way as your other account data, and removed if either of you deletes it. A reaction you put on a message (thumbs up, thumbs down, important or question) is stored with that message and is visible to both of you. If either account is deleted, the coaching link and all its messages are deleted for both of you.
• Who is responsible for what. amb is responsible for the platform and for sharing your data with your coach as you chose. Once your coach has received your data, your coach is responsible for it under their own agreement with you, which is made outside amb, and under the law that applies to them. amb does not provide or check that agreement.
• Ending it. either side can end the link at any time. The other side's access stops immediately; sessions already planned stay in the athlete's calendar, since removing them would be its own kind of data loss. After a link ends, the coach must delete or anonymize the athlete's data they hold, unless the law requires them to keep it.
• Legal basis. the same as above — consent for the link itself and for what you choose to share, contract for running the coaching features you've both opted into.

E-mail about new messages

Coaches only, and only if you ask for it. In your profile on amb.coaching you can choose to get an e-mail when an athlete's message to you has stayed unread for a few minutes. It is off until you switch it on. We send at most one e-mail per chat and hour.

What is in it. The athlete's first name, how many messages are waiting, and a link to the chat. Never the text of a message. There is no advertising and no newsletter, and nothing in these e-mails tracks whether you open them or what you click: the logo is a fixed image from our own site, and the links are plain links.

Double opt-in. When you tick the box we send you one e-mail to confirm. You only get the other e-mails after you click the button in it. We then store when you confirmed and for which e-mail address, as proof of your consent. If you change the address you sign in with, you confirm again. The confirmation link works for 7 days. If you do not click it, nothing is sent and nothing more is stored than the request.

Basis and withdrawal. Your consent (Art. 6(1)(a) GDPR, and the equivalent under the Swiss FADP). You can withdraw it at any time, by unticking the box in your profile or with the link at the bottom of every e-mail. The e-mails stop at once, and the stored confirmation is deleted.

Who sends it. The e-mails go out from our mailbox at IONOS SE, a German provider, which handles your e-mail address and the text of the e-mail. To avoid repeats we also remember when we last e-mailed you about each chat.

Tell me more

With Advanced insights on (amb pro), the card under a finished session has a part called "Tell me more". You rate how hard the session felt (1 to 10) and, when it went shorter or longer than planned or had a long pause, you pick the reason. You can add up to three words of your own. As soon as every question that was asked is answered, our server asks an AI model to write a longer explanation of the session, a few sentences. Nothing is sent before you have answered.

• What is sent: what the card shows: the session's name, sport and planned duration, the verdict (for example "As planned"), the recorded duration, average heart rate, average power and distance, the comparison with your similar sessions and the insight's text. What you answered: your rating, the reason, the reason for a long pause and your words. To put it in context also your next goals (name, days to go, sport, distance, target time), your last two weeks in numbers (training load per week, fitness, fatigue and form today and 14 days ago, number of workouts and hours) and what is planned for the rest of the week (each day's session name, sport, length and main set). The day of the session and today's date go along, so the text names the right day. Not your name, e-mail, account id, other profile details, single workouts or anything else in your account.
• Who processes it: AKI.IO GmbH in Berlin, Germany, as our processor, with an open AI model on servers in the EU, on the same terms as for "Describe your workout": by contract it neither logs nor stores the figures or the answer, processes nothing outside the EU and does not use them to train AI models.
• What we keep: your answers with your account (see above). The longer text stays on your phone. That a request was made, when and how many tokens it used, for 90 days, to limit use and see the cost. Not the figures and not the answer.
• Never for Strava: a workout that comes from Strava gets no questions and nothing is sent.
• Legal basis: providing the feature you asked for (contract), with your consent to amb insights for the data it uses.

Insight texts

With Advanced insights on (amb pro or the free trial) and amb insights on, amb writes the short text of an insight for you: before a planned session (written shortly before it, with a "Why" that explains how the session helps), after a session, and for your week. Rules in amb decide what the text says and count every number; an AI model then words it so that it reads naturally and does not repeat itself. This happens in the background on our server, without you tapping anything. The text is a recommendation or an observation, never a decision. If the AI's wording does not pass our checks (for example a number is lost or invented), the written phrase from the amb library is shown instead.

• What is sent: the library phrase with its numbers, the sport, the name of the session, planned and actual minutes and its main set, how many sessions of your week are planned and done, your goal (name, time to go, target pace), your form, fitness and fatigue, your last seven days against your usual week, the other sessions of the same day and of the week, similar earlier sessions with the effort you gave them and the text you read, the day of the session and today's date, your usual hours per week and usual session length per sport, the number of weeks in a row you completed your plan, and the insight texts you were shown over the last weeks (so the wording varies). Not your name, e-mail, account id, other profile details, single workouts or the recordings.
• Never for Strava: a workout that comes from Strava is not analysed and nothing from it is sent. If a second source has the same workout (for example COROS or Apple Health), that copy is used.
• Who processes it: AKI.IO GmbH in Berlin, Germany, as our processor, with an open AI model on servers in the EU, on the same terms as for "Tell me more": by contract it neither logs nor stores the facts or the text, processes nothing outside the EU and does not use them to train AI models.
• What we keep: the insight text with your account, as long as amb insights is on (switching it off deletes it), and that a request was made, when and how many tokens it used, for 90 days, to limit use and see the cost.
• You decide: switch Advanced insights off under amb insights and no text is written. The thumbs under an insight only tell us whether it helped; they do not change what you are shown. You can fold the insight cards up; that choice is stored with your profile so it holds on all your devices.
• Legal basis: providing the feature you switched on (contract), on the data you allowed with amb insights (consent).

Building a workout from a description

With amb pro, the workout editor in the iOS app, on amb.training and on amb.coaching has a field "Describe your workout". You describe a session in your own words, and amb turns it into the steps of a workout, which you see first and only then add.

In the iOS app, amb first tries to build it on your iPhone or iPad (its own reading of the text, then Apple Intelligence on the device, where available). Then nothing leaves your device. Only if that doesn't work, or you ask for another try, does the text go to our server and the processor below. On the web it always goes to the server.

• What is sent: the text you type into that field, the steps of the workout you are editing (lengths, targets, sports) and its name and sport. Not your name, e-mail, account id, profile, completed workouts or anything else in your account.
• Who processes it: AKI.IO GmbH in Berlin, Germany, as our processor, with an open AI model running on servers in the EU. The request goes from our server; the AI never reaches your account. By contract (data processing agreement), AKI.IO neither logs nor stores the text or the answer, and processes nothing outside the EU; it does not use them to train AI models.
• What we keep: to limit use and see the cost we record that a request was made, when and how many tokens it used, for 90 days. When a description reaches the server because the device's own answer didn't fit, or because you asked for another try, we also keep the text, the steps your device built and the steps returned from the server, with your account, for 180 days, to see where the reading on the device goes wrong and improve it. Otherwise we keep nothing of the text or the answer.
• Please don't type personal or health details into the field; a workout description doesn't need them.
• If you don't use the field, nothing is sent. The editor works fully without it.
• Legal basis: providing the feature you asked for (contract). Keeping the text and both answers for 180 days to improve the feature is our legitimate interest; you can object to it at any time (see "Your rights"), and we then delete what we kept of yours.

Connecting your own AI assistant

amb doesn't build its own AI chatbot. Instead, if you choose to, you can connect an AI assistant you already use (like Claude, ChatGPT or Gemini) to amb, so you can ask it about your own training and have it help plan. This works differently from how most apps handle AI:

• You connect it by signing in. In your AI assistant's settings you add amb as a connector, sign in with your own amb account and approve on amb's own page. We don't send your data anywhere on our own initiative. Personal access tokens created earlier keep working until you revoke them.
• You confirm first, twice. In the amb app a notice lists what the assistant can access and asks you to confirm before the steps appear. On the sign-in page you confirm again for that specific assistant, that you own the account and are connecting your own AI account. If you press Cancel, nothing is connected. We record every decision.
• What it can read: your completed workouts with their detail (heart rate, pace, power, distance, duration), your planned workouts and calendar, your zones and thresholds, and your goals. Nothing else in your account.
• What it can change: it can create, edit and delete planned workouts in your calendar. It cannot change completed workouts or your account.
• Your AI provider is your own relationship. We don't pick, pay for, or operate the AI you connect, and the data it asks for is released by amb to the assistant you authorised; what its provider does with it afterwards, including any transfer to the United States, is not under amb's control. Your consent covers that release. Depending on your subscription and settings, that provider may use your conversations and data to train its models. That is outside amb's control and responsibility, so check the privacy settings of your AI account.
• You can disconnect an assistant at any time under AI assistants in amb, or revoke a token there. Once you do, that AI can no longer access anything.
• If you never connect one, none of this applies to you. amb works fully without it.
• Legal basis: your consent, which you can withdraw by disconnecting the assistant.

Your coach and AI

A coach can connect their own AI assistant to amb.coaching to plan training faster. Because that touches athlete data, it has its own rules, and your coach cannot use it for you unless you say yes:

• Your separate consent. Under Data & privacy, "Let your coach use an AI assistant" is off by default and has its own Confirm pop-up. Until you switch it on, your coach's AI assistant does not see you at all. You can switch it off at any time and it stops right away. A yes you gave for one coach does not carry over to another coach.
• Pseudonymized, not anonymous. Your name is replaced by a code such as "Athlete 0247" before anything reaches the assistant, and your free-text notes, goal names and contact details are not shared. Because your coach can still map the code back to you, this is pseudonymized data, which remains personal data under the law.
• What the assistant sees about you: your training overview, recent sessions and training load, the days you cannot train, and your preferences and limits you gave your coach. If you share detailed data with your coach, it also sees your current thresholds and zones.
• What it can do: help your coach draft, schedule and adjust your planned sessions. Your coach stays responsible for what ends up in your calendar.
• The coach confirms too. Before creating a connection, the coach confirms that they own their account, are connecting their own AI account, and are allowed to use an AI assistant for the athletes they coach.
• Their AI provider is their own relationship. Depending on the coach's subscription and settings, that provider may use data to train its models. That is outside amb's control and responsibility.
• Legal basis: your consent, recorded when you give it and when you withdraw it.

Payments

Coaches. If you subscribe to amb.coaching, Stripe handles the payment, and the seller is Link, LLC, a Stripe company in the United States. Stripe and Link, LLC collect and store your name, billing address, tax details and payment details, under Stripe's own privacy policy. We never see or store your card number. We send Stripe your email address and an internal account id, so the subscription can be tied to your account. We keep your Stripe customer id, your plan, its status and its renewal or end date, so we know whether your access is active.

Athletes. If you buy an amb pro subscription in the iOS app, Apple handles the payment under its own terms. We receive from Apple a signed record of the purchase (the product, its status and its dates). It is tied to your account with your account id, not with your name or email. We keep the product, status and dates so the app and the web know whether amb pro is active.

We process this because we need it to provide the plan you bought. Invoices and payment records are kept as long as tax and accounting law requires (10 years in Switzerland), even if you delete your account.

An administrator at amb can give free access to an account, and this is recorded with a reason. Nothing about your training data is part of that.

Cookies and local storage

We don't run any advertising trackers. The website is hosted on Lovable, and its own visitor statistics are switched off. The only optional technology is Google Analytics, which stays off until you switch it on in the cookie choice (on your first visit, and any time later with the round cookie button at the bottom left of every page).

We use your browser's local storage to keep you signed in, to remember a handful of your own preferences (like your last selected time range) and to remember your cookie choice. The hosting platform sets these cookies, which the site needs to work:

• __cf_bm (Cloudflare): bot protection, 30 minutes.
• __dpl (Lovable): routes your visit to the current version of the website, 7 days.

Google Analytics (only with your yes). If you switch analytics on, your browser loads Google's analytics code and Google sets two cookies, _ga and _ga_<container id> (both up to 2 years), which recognise your browser between visits. Google receives the pages you open (never the numbers in the address that identify your account or a workout, and never what you type), your browser and device type, and your IP address, which it uses to work out roughly where you are and which it says it does not store in Google Analytics. We use it to see which pages are used and how, nothing else. Advertising features, Google signals and personalised ads are switched off, and we keep the data for the shortest period Google offers (2 months). Google may process the data in the United States, on the basis of the EU-US and Swiss-US Data Privacy Framework and the standard contractual clauses.

amb.coaching has its own cookie choice and its own Google Analytics property. The choice is kept separately in your browser for each of the two websites, so switching analytics on at one does not switch it on at the other.

Your choice. The legal basis is your consent. It is off until you switch it on, declining costs you nothing, and you can change your mind at any time with the cookie button. When you switch it off, we stop sending and delete the Google cookies in your browser. Data already sent stays with Google until it expires after the retention period above. We store your choice only in your browser.

If the cookies or analytics change, we update this page, and we will add a choice before introducing any other technology that needs your consent.

How long we keep it

For as long as your account exists, unless you delete a workout, disconnect a device (which deletes the workouts that came from it) or switch amb insights off (which deletes the copy of the details). Delete your account. from Profile in the app, or your account settings on the web, no email needed. and your training data and profile are erased immediately, other than what we're legally required to retain.

Deletion happens in our live system at once. At the moment our database provider does not make automatic backups on our plan. Should that change, any backup is overwritten within 30 days, and if we ever restore one, we delete again every account that was deleted since. The provider's request logs are kept for about one day.

If something goes wrong

If a security incident affects your personal data, we'll act at once. Where Swiss law requires it, we tell Switzerland's FDPIC as soon as possible. Where the GDPR requires it, we tell the competent EU/EEA data protection authority within 72 hours of becoming aware of it. If the incident is likely to put you at high risk, we also tell you without undue delay.

How we protect your data

• Connections to amb are encrypted (HTTPS).
• Access rules in the database itself mean an account can read only its own rows and what has been shared with it, for example by linking a coach.
• We never see or store your Google or Apple password.
• Access to administration is limited to one administrator account.
• Connections to devices and AI assistants use tokens that you can revoke at any time.

No system is perfectly secure, which is why the incident section above exists.

Your rights

Wherever you are, you can ask us to:

• show you what we hold about you (access),
• correct it (rectification),
• delete it (erasure). or do this yourself directly, see above,
• give you a copy in a portable format (portability),
• stop a particular processing activity (objection),
• pause processing without deleting anything (restriction),
• withdraw a consent at any time. This does not affect what was done before you withdrew it, and
• tell you where the data we hold about you came from, if it did not come from you.

Email hello@trainwithamb.com for any of these. We answer within 30 days, and usually much sooner. You can also complain to Switzerland's Federal Data Protection and Information Commissioner (FDPIC), or, if you're in the EU/EEA, your own local data protection authority, at any time.

Age requirements

amb isn't directed at children, and we don't knowingly collect data from anyone under 16. You confirm that you are at least 16 when you sign in, and the iOS app asks about your age when you start. If you believe a child's data reached us without appropriate consent, email hello@trainwithamb.com and we'll delete it.

Changes to this policy

If this changes in any meaningful way, we'll update the date at the top of this page and tell you in the app or by email. If a change needs your consent again, we ask before it applies. The date also shows which version you are reading.