What's new on 9 November 2026. If you log water, we now keep the time of each glass as well as the count, for 28 days. Your monthly running summaries, including figures from Apple Health, can now be kept for up to 24 months. Our analytics can now count more about how the app is used, including your plan and paywall use, a rough age range and sex if you gave them, and a few labels about your goal and running. We also keep a small record, with no name, of which offers we showed, so that deleting and re-creating an account does not reset the limits on offers. We now say that short notes about your use of the app, including your country and any city of more than 100,000 people, go to our private team channel in Slack, under a short code. Because these changes affect how we use your data, the app asks you to agree again.
What's new on 7 November 2026. If you run outdoors, the app now keeps your routes on your phone, so it can recognise when you repeat one and draw it for you. You can also let the app learn where your runs usually start, so Dayla can time your run to finish at your door. Your home stays on your phone and is never sent to our server. When the route feature is switched on, our server keeps a short summary of each route you run, never the route itself. The routes we keep, and anything we upload to Strava for you, now leave out the first and last few hundred metres of each run. The new section "Routes and home" has the details.
What's new on 2 November 2026. If you scan a meal, a food label, or your fridge or cupboard, the photo is sent to our AI provider, Anthropic, only to recognise the food. We never store your food photos. You can also turn on fueling memory and do a sweat check, both optional and for adults only. To tell you about places near your run, we send your rough start location, accurate to about 1 km, to Wikipedia and OpenStreetMap once per run. We never send them your route or who you are. You can turn local notes off in Settings.
What's new on 29 October 2026. You can now give Dayla your height and weight, or let her read your weight from Apple Health, for fueling, run energy and your weight trend. We use your weight to size fueling suggestions (grams of carbohydrate per kilo), to estimate the energy your runs use, and to show you how it changes alongside your running. Never for weight-loss advice. Height and weight from Apple Health: Only if you allow access. Your height, and your weight readings from the last 16 weeks, refreshed once a day while Apple Health is connected. Disconnecting Apple Health removes them. If you switch on "Help improve Dayla's coaching", PostHog also receives your training level band (1 to 5) and its rough range, which Dayla works out from your runs. Never the readings behind it. Because these changes affect how we use your data, the app asks you to agree again.
What's new on 15 October 2026. Dayla can now suggest the best time for today's run. To do this she can use your usual wake and bed times, worked out on your iPhone from the sleep you share from Apple Health; a rough location, for the weather where you are; and, only if you connect it, your calendar. Your iPhone sorts each calendar event into a type, such as work, travel or social. Only the start time, end time and type leave your iPhone. Event names, people, places and notes never do. The suggested time can show on your lock screen and widget. You choose whether to turn these on; nothing changes until you do.
What's new on 14 October 2026. If you allow it, Dayla also reads a short summary of each workout from the last 16 weeks that is not a run, such as cycling, swimming, strength training or yoga: the type of workout, the day, the time of day, how long it lasted, your average and highest heart rate and the energy it used. We never read where you went. While Apple Health is connected, Dayla refreshes these summaries once a day when you open the app, and the new summary replaces the old one. Your weekly sleep averages from Apple Health, the average time you slept per night for each of the last 13 weeks, are kept together with your weekly resting heart rate averages, for as long as Apple Health stays connected. Because these changes affect how we use your data, the app asks you to agree again.
Dayla is a running coach app made by Dolomitica Ltd, a company registered in England and Wales (number 11844886), registered office Flat 93 Biddulph Mansions, London W9 1HU, United Kingdom.
Dolomitica Ltd decides how your data is used, which makes us the "controller" under data protection law. For any question or request about your data, write to hello@dolomitica.co.uk. We reply within one month.
Heart rate, sleep (including the wake and bed times we work out from it), resting heart rate, your past runs from Apple Health, your physiology, your height and body weight, and health details you tell Dayla, such as a niggle or that you are getting back from an illness, are health data. We process them only with your explicit consent, given on the "Before we start" screen.
| What | Examples | Where it comes from |
|---|---|---|
| Account | Your Apple sign-in identifier, an encrypted sign-in token, and the email Apple shares, which can be a private relay address. We don't send email to it. Before you sign in: a temporary account tied to a random ID made by the app, of which we store only a one-way code, with when it was created and last used. | Sign in with Apple; the app |
| Profile | The name you tell Dayla, your goal and the race behind it (its name, date and target time, if you give them), weekly running, the days you can run, the notes you give Dayla (which can mention a niggle), units, your time zone, your coaching preferences, a pause in your plan and its reason if you give one, and the plan changes you agree to in chat. If you choose to give them, your year of birth and your sex: we use them to estimate your heart-rate zones until your runs teach us your own, and the year of birth to check you are 16 or over. If you choose to give them, your height and body weight, and, if you allow it, your weight readings from Apple Health over time. We use your weight to size fueling suggestions (grams of carbohydrate per kilo), to estimate the energy your runs use, and to show you how it changes alongside your running. Never for weight-loss advice. | You, in setup, chat and Profile & settings; your time zone from your phone |
| Your numbers | Max heart rate, resting heart rate, best 5K and 10K, training zones and threshold, each marked as stated by you, measured or learned, with their history; how much your heart rate drifted on each run; Dayla's daily insights from your runs; and, if you bring in your past runs from Apple Health, the weekly averages of your resting heart rate over the 13 weeks before | You, your runs, and Apple Health |
| Height and weight from Apple Health | Only if you allow access. Your height, and your weight readings from the last 16 weeks, refreshed once a day while Apple Health is connected. Disconnecting Apple Health removes them. | Apple Health, through the app on your phone |
| Runs | Heart rate (including from an Apple Watch, through Apple Health), pace, cadence, distance, duration, elevation, your GPS route (without the first and last few hundred metres of each run, once it is stored on our server) and the weather when you ran | Your phone during the run; the weather service |
| Past runs from Apple Health | Only if you connect Apple Health and bring in your past runs. A summary of each run your watch or apps saved to Apple Health in the last 16 weeks: the date, the time of day (morning, midday or evening), duration, distance, average and highest heart rate, climb, indoors or outdoors, whether it came from an Apple Watch or another app, and a one-way code so the same run isn't counted twice. Also your fastest run near 5K, 10K, half-marathon and marathon distance in the last 12 months (at most 4), the highest heart rate a workout recorded in that time, and weekly averages of your resting heart rate and sleep over about the last 90 days. Never your routes, splits or second-by-second data, and never the names of the apps that saved them. Your phone works out these summaries and sends them only after you sign in. If you allow it, Dayla also reads a short summary of each workout from the last 16 weeks that is not a run, such as cycling, swimming, strength training or yoga: the type of workout, the day, the time of day, how long it lasted, your average and highest heart rate and the energy it used. We never read where you went. We keep these summaries for as long as Apple Health stays connected, and disconnecting deletes them. While Apple Health is connected, Dayla refreshes these summaries once a day when you open the app, and the new summary replaces the old one. You do not have to do anything, and disconnecting Apple Health stops it and deletes what was kept. | Apple Health, through the app on your phone |
| Workouts saved to Apple Health | If you run with the Dayla app on your Apple Watch, it saves the run to Apple Health as a running workout (type, heart rate, distance and energy). This stays on your devices in Apple Health; we don't receive it from there. | The Dayla app on your Apple Watch |
| Recovery and feel | Sleep and resting heart rate, if you allow access, and how you say you feel today, whether you tap it or tell Dayla in chat. They are sent with each daily card; we keep only your 7 most recent days of these daily readings (the weekly averages above are kept separately). Weekly averages from your past runs are covered in the row above. | Apple Health; you |
| Usual wake and bed times | Only if you turn on better timing for the best time to run. For today and tomorrow, worked out on your iPhone from your Apple Health sleep. They are health data. They are sent with the app's requests to work out your suggested run time. We keep them in our server's memory for today and tomorrow only, never in a database or logs. | Apple Health, through your iPhone |
| Rough location | Only if you turn on better timing for the best time to run. Accurate to about 11 km. It is sent with the app's requests so Dayla can get your local weather and tell when you are away from your usual running area, where your usual times may not fit. To tell, she compares it with where your recent runs started. We keep it in our server's memory for today and tomorrow only, never in a database or logs. | Your phone |
| Calendar busy times | Only if you connect your calendar. The start and end of your events today and tomorrow, each with a type your iPhone gives it: work, travel, social, workout, appointment, race or other. All-day events are sent only if they are travel or a race. Your iPhone only lets an app read your whole calendar or none of it, so Dayla reads it on your phone and sends only the times and the type. Event names, people, places and notes never leave your iPhone. | Your iPhone's calendar, sorted on your iPhone |
| Your run time | The time you pick for today or tomorrow, if you pick one, and the times you tell Dayla you can't run, such as before work only. Whether you turned on better timing, and whether your calendar is connected. | You |
| Getting back from illness | Only if you tell Dayla in chat that you are getting back from an illness and say yes to her offer to keep your plan easy: when you said yes, how many days you were ill and whether you mentioned a fever, as you told her, and when and why the easy period ended | You, in chat |
| Conversations | What Dayla says to you during runs, and the speech audio made from it, including greetings with your name; the summary Dayla writes after a run. From chat, Dayla keeps only what changes your coaching: plan changes and other things you agree to, how you say you feel today, and numbers you state, such as your max heart rate. Each chat thread stays on your phone. Your messages, and a one-line note of what you agreed in your other chats that day, pass through our server to the AI without being stored. | You and Dayla |
| Coaching memory | The day Dayla last checked in with you or asked how you feel; which seasonal runs she offered and your answer; the body-scan runs she offered, and whether you took them or said no; whether you want walk breaks in your easy runs | Your use of the app |
| Food and fueling | Only if you use them. The foods you save from a food photo (names, estimated amounts and the time); your fueling memory, if you turn it on; your sweat check results, if you do one; what you pick to eat today and what you carry on a run; the glasses of water you log and when. Never the photo itself. The "Food, fueling and places" section says more. | You; the photo you scan |
| Local notes | Which places you have heard about, as scrambled codes with no name, position or time, and the kinds of your last six notes. A note Dayla speaks is in your run's transcript like her other lines. | Your runs; our server |
| Route summaries | Only when the route feature is on. For each route you run: its length, its shape, its total climb, the rough position of its hills (to 100 metres), and the name you give it. Never the route itself, and never any coordinates. | Your phone |
| Feedback | How a run felt, and your answers to the optional questions after a run, including anything you write, linked to that run | You |
| Consent | When you agreed, which you can only do after confirming you are 16 or older; to which version of this policy; that the app showed you the usage-signals notice; your "Usage signals" and "Help improve Dayla's coaching" choices; and the history of those choices | You |
| Usage | Unless you switch usage signals off: which screens and features you use, whether they worked, and a few settings, tied to your random account ID. Never your messages, health readings, pace or location. The "Services" section lists exactly what. | The app and our server |
| Technical logs | Errors and server events. They include a random account ID so we can trace a fault, and can include a short one-way code made from your IP address so we can block abuse, but never names, emails or towns. | Our server |
Some comparisons, such as your usual heart-rate drift or how your heart rate at an easy pace compares with your earlier runs, are worked out from your stored runs when they are needed and are not stored themselves.
We keep a monthly summary of your running, including figures worked out from Apple Health, for up to 24 months, so Dayla can show how you change over time. The summaries are mostly totals and averages, such as your runs, minutes, distance and resting heart rate; for up to 14 easy runs a month we also keep the day, pace and average heart rate of each run. Never your route or second-by-second readings. Disconnecting Apple Health removes the Apple Health part, and deleting your account removes all of it.
We don't collect payment details: the beta is free.
Food photos (optional, adults only). If you scan a meal, a food label, or your fridge or cupboard, the photo is sent to our AI provider, Anthropic, only to recognise the food. We never store your food photos. Anthropic deletes them automatically within 30 days, or longer only if flagged for misuse or required by law, and does not use them to train AI models. If you choose to save a result, we keep the list of foods, their estimated amounts and the time, and you can change or delete it at any time. We use it only to tailor your fueling suggestions, never for weight-loss advice, and it is never used for analytics or advertising.
When you correct a food Dayla got wrong, we keep the two food names, with nothing that links them to you, so we can improve food recognition for everyone. Your photos are never used for this.
Fueling memory (optional, adults only). If you turn it on, we keep the foods you pick and save, when you had them, what you carried on a run, and your answers about your stomach and the last part of a run. We use them only to tailor your fueling suggestions, never for weight-loss advice, analytics or advertising. Turning it off deletes them.
If you tell Dayla about foods you avoid, including allergies or intolerances, we keep that list to shape your meal ideas and share it with our AI provider only to write them. It is never used for anything else, you can change or delete it at any time, and it is deleted with your account.
If you allow body data, your meal ideas also use your age band, sex and weight band, shared with our AI provider only to write them, and never shown back to you.
Sweat check (optional, adults only). If you do one, we use your weight before and after a run to work out how much you sweat, and keep only that result, the temperature and the length of the run. We don't keep the two weights.
Water (optional). If you log water, we keep how many glasses you had each day and the time you logged each one, for 28 days. We use them to show your day and to time the water nudges Dayla shows you. They are never used for analytics or advertising, and the AI that writes Dayla's coaching never receives your counts.
Unless fueling memory is on, what you pick to eat today, and what you carry on a run, is deleted at the end of that day.
Local notes. To tell you about places near your run, we send your rough start location, accurate to about 1 km, to Wikipedia and OpenStreetMap once per run. We never send them your route or who you are. A note Dayla speaks is kept in your run's transcript like her other lines. Which places you've already heard about is stored only in a scrambled form, so she doesn't repeat herself. The kinds of your last six notes (such as history or fun) are kept next to that list, so she can vary them. You can turn local notes off in Settings.
Routes kept on your phone. If you run outdoors, the app keeps your routes on your phone, so it can recognise when you repeat one and draw it for you. The start and the finish are trimmed off before a route is saved. Routes you haven't run for 12 months are deleted. In Settings you can forget one route, or all of them.
Route summaries on our server (only when the feature is on). Our server keeps a short summary of each route: its length, its shape, its total climb, the rough position of its hills (to 100 metres), and the name you give the route. It never receives the route itself, or any coordinates. A summary is deleted when you forget the route, after 12 months unused, or with your account.
Home (only if you allow it). The app can learn where your runs usually start, so that Dayla can time your run to finish at your door. That place stays on your phone and is never sent to our server. Near home, and near where each run starts, your position isn't sent at all. During a run, our server receives a rough distance to home, or to where you started. It uses that distance only for that run and never stores it. You can forget home in Settings.
Stored routes and Strava. The routes we keep, and anything we upload to Strava for you, leave out the first and last few hundred metres of each run. The amount we trim varies, so the start can't be worked back to.
We use your data to coach you, keep Dayla working, and improve it.
| Purpose | Data used | Legal basis |
|---|---|---|
| Set you up before you sign in | Account (the temporary account), what you write in setup | Providing the service you asked for, plus your explicit consent for health data |
| Coach you: today's session, coaching during runs, answers in chat | Profile, your numbers, runs, past runs from Apple Health, recovery and feel, getting back from illness, conversations, coaching memory | Providing the service you asked for, plus your explicit consent for health data |
| Suggest the best time for today's run | Your usual wake and bed times, your rough location, your calendar's busy times (if you connect it), the run times you pick and the times you say you can't run, your past runs | Providing the service you asked for, plus your explicit consent for health data (the wake and bed times come from your sleep), given when you turn on better timing. For your calendar: your consent, given when you connect it. |
| Start your plan from the running you already do, count your past runs toward your plan, and show you what Dayla learnt from them | Past runs from Apple Health, profile | Providing the service you asked for, plus your explicit consent for health data |
| Learn your zones and fitness over time | Runs, your numbers | Same as above |
| Tailor your fueling suggestions from food photos, saved foods, fueling memory and the sweat check | Food and fueling | Your consent, given when you turn each one on |
| Recognise routes you repeat, draw them, and time your run to finish at your door | Route summaries, and on your phone only: your routes and your home | Providing the service you asked for. For home: your consent, given when you allow it. |
| Tell you about places near your run (local notes) | Local notes, your rough start location | Our legitimate interest in telling you about where you run. You can object at any time by switching local notes off in Settings; it stops from that moment. |
| Keep Dayla safe and working: fix errors, prevent abuse, limit costs | Technical logs, account | Our legitimate interest in a reliable, secure service |
| Read the answers you choose to send after a run | Feedback | Your consent, given by sending them; every question is optional |
| Improve Dayla: usage signals | Usage, your plan and paywall use, your profile labels, age range and sex, and short notes to our team channel in Slack | Our legitimate interest in understanding how Dayla is used, so we can fix what doesn't work and make it better. You can object at any time by switching "Usage signals" off in Settings; collection stops from that moment. |
| Improve Dayla's coaching: samples of your conversations with Dayla | Conversations | Your explicit consent through "Help improve Dayla's coaching", which you can withdraw any time |
| Prove you consented | Consent record | Legal obligation |
| Stop offer limits being reset by deleting an account | Offer limit record | Our legitimate interest in applying our offer limits fairly. You can object by writing to hello@dolomitica.co.uk. |
The Dayla app contains no third-party code: it talks only to our own server, Apple, dayla.co and the weather service. These services handle data only to provide their part of Dayla, under our instructions. Some are in the United States; those transfers rely on safeguards such as the EU's Standard Contractual Clauses.
| Service | What it does | What it receives | Where |
|---|---|---|---|
| Railway | Hosts our server and database | Everything listed above | Amsterdam, Netherlands (EU) |
| Anthropic | The AI that writes Dayla's coaching and chat replies; also used in our engineering tools when we diagnose problems | Your first name, what you write in setup and chat (including your notes), your run data, numbers and recovery readings, the summaries of your past runs from Apple Health if you bring them in, your height and body weight, and how your weight has changed, if you give them or allow Apple Health, health details you share, such as being ill, and the summaries from Apple Health listed above (your past runs, your other workouts, your weekly resting heart rate and sleep averages), and the time Dayla suggests for your run; public text about places near your run, for local notes, with nothing that identifies you; the photo of a meal, a food label, or your fridge or cupboard, if you scan one, only to recognise the food; never your routes; never your email or location | United States |
| OpenAI | Turns Dayla's words into her voice | The words Dayla speaks, which can include your first name and your town | United States |
| Open-Meteo | Local weather for your card, your check-in and your runs | Your location rounded to about 1 km (or about 11 km when it is your phone's rough location for the best time to run), so it can return local weather. Our server and the app on your phone both ask; the app's requests also carry your phone's IP address. Open-Meteo keeps request logs for 90 days. | Switzerland |
| Wikipedia | Tells you about places near your run (local notes), through the Wikipedia API (wikipedia.org) | Your rough start location, accurate to about 1 km, once per run. Never your route or who you are. | Various |
| OpenStreetMap | Tells you about places near your run (local notes), through the public Overpass API (overpass-api.de) | Your rough start location, accurate to about 1 km, once per run. Never your route or who you are. | Various |
| Apple | Sign in with Apple; TestFlight for the beta; notifications you ask for | What Apple's own policies describe. When you delete your account, we ask Apple to revoke Dayla's sign-in. | Apple |
| PostHog | Usage analytics, unless you switch usage signals off | Usage events tied to your random account ID: which screens and features you use; whether things worked, and how quickly, in ranges (such as under 2 seconds); whether you typed or spoke a chat message; how long a run was in ranges (such as 15 to 30 minutes), and the type of session; that you paused or resumed your plan and roughly for how long, never why; which check-in questions you answered and whether you tapped or typed, never your answer; and your 1 to 5 feedback scores; whether you turned on better timing or connected your calendar; whether you picked a run time for today or tomorrow (never which time) and whether it matched Dayla's suggestion; whether a run started inside the suggested time; and what Dayla's suggestion was mainly based on (the weather, your usual time, daylight, your calendar or your own pick) and how sure she was, never the times or the reason itself. When paid plans arrive, PostHog also receives how you use the paywall and offers: whether you saw or tapped the paywall, upgrade prompts and locked items, which plan you looked at (monthly, quarterly or annual), how long you looked (in ranges), which price test group you are in (a letter, never the price), whether a purchase started, finished, was cancelled or failed and why, whether it was a test or live purchase and through which store, whether an introductory or other offer was involved, whether you restored purchases, and whether you are on a trial, a paid plan or the free version. It also receives renewals, cancellations, expiry, refunds, billing retries and plan changes, as events with the plan and rough ranges, and when we showed you an offer or you used one and what prompted it. Never the price you paid, the amount, the currency, your payment details or exact dates. After a run, PostHog also receives how many moments Dayla found as a rough count (none, one, two or three, four or more), how many she was sure about (none, one, two or more), and which moment you tapped. Never what the moments were. Also a few settings: voice style, units, app version, sign-up week, and yes or no for notifications, Apple Health and a heart-rate strap; whether you finished setup, and which version of setup and of this policy you saw. Also a few facts from your profile, as plain labels: the kind of goal you chose, the race distance, whether you set a race date and roughly how far away it is (for example about 6 weeks, or no date), whether you set a target time or just want to finish, how often you run now, and how many days you can run. Never your race name, date or target time. If you gave them in your profile and you are an adult, your age range (such as 35 to 44, never your year of birth) and your sex. If you switch on "Help improve Dayla's coaching", PostHog also receives your training level band (1 to 5) and its rough range, which Dayla works out from your runs. Never the readings behind it. Never your messages, heart rate or other health readings, pace, location, names, or race names, dates or target times. | EU |
| Slack | Our private team channel, for internal notifications about how the app is used, unless you switch usage signals off | A short note about your use of the app: that you finished a run, its type, how long and how far it was, which number run it is, whether you came back after a break or ran on race day, which country you are in, and the city if it has more than 100,000 people, which plan you are on, and that you connected Strava. It carries a short code that stays the same for you instead of your name or email. Never your name, email, exact location, heart rate or route. | United States |
| Cloudflare | Hosts the dayla.co website | Standard website request data such as your IP address and browser | Global network |
Strava (only if you connect it). When you connect Strava, each run you finish is sent to your Strava account: its route (with the first and last few hundred metres removed, by an amount that varies), time, distance, heart rate and splits, plus a line saying Dayla coached it. From then on, Strava's own privacy policy applies to that copy. Dayla never reads your Strava data. You can disconnect in Settings at any time; runs already on Strava stay there.
Internal run reports are made only for our own test accounts, never for yours.
We keep your data while your account is open, so Dayla can coach you and learn your patterns.
Most of these you can do yourself in the app, at any time.
The app records simple usage signals — for example which screens you open, which features you use, and whether they worked — so we can improve Dayla. These signals are tied to a random ID, never include your messages, health readings, pace or location, your year of birth or your race names, dates or target times, and are processed in the EU. You can switch them off at any time in Settings; that also stops the short notes to our team channel in Slack. Separately, and only if you turn it on, 'Help improve Dayla's coaching' shares samples of your conversations with Dayla so we can improve her coaching. It also lets our analytics receive your training level band (1 to 5) and its rough range.
The signals go through our own server to PostHog; the "Services" section lists exactly what they contain.
Unless you switch Usage signals off, a short internal note about your use of the app is sent to our private team channel in Slack: that you finished a run, its type, how long and how far it was, which number run it is, whether you came back after a break or ran on race day, which country you are in, and the city if it has more than 100,000 people, which plan you are on, and that you connected Strava. It carries a short code that stays the same for you instead of your name or email, and never your name, email, exact location, heart rate or route. These notes stay in our team channel after you delete your account or switch usage signals off, but nobody can link the code to you once your account is gone.
We have not started collecting conversation samples yet. Before we do, we will update this policy to say how they are chosen, who reviews them and how long we keep them.
We never record your screen and never use advertising identifiers. Switch either one off in Profile & settings and collection stops from that moment.
If you test Dayla through Apple's TestFlight, Apple shares with us the feedback, screenshots and crash reports you choose to send, with your device model and app version. Apple's own privacy policy covers TestFlight itself.
Feedback you send us directly as a tester, by message or in a call, is used only to improve Dayla.
Email: hello@dolomitica.co.uk
Company: Dolomitica Ltd, registered in England and Wales, number 11844886
Version 2026-11-09 · effective 9 November 2026