Privacy notice

The data controller is Jānis Višķers, self-employed running coach, Malduguņu iela 12, Mārupe, Mārupes novads, LV-2167, Latvia, e-mail jvmilesavers@gmail.com. This notice covers the Mile Savers training plan app. The shop at milesavers.lv has its own privacy policy.

• Your name and e-mail as entered by your coach in the invitation, and your Mile Savers shop account identifier.
• Your programme and its end date, if your coach entered them.
• The training plan written by your coach.
• Your completion marks: kilometres, minutes, a 1 to 5 rating of how the session felt, the reason for a skipped session and a note to your coach.
• Comments written by you and your coach.
• Your goal, races (name, date, distance, surface, priority, target and achieved time) and records entered by you or your coach.
• Your availability for training, if you enter it.
• Your coach's notes about your training – in the app only your coach sees them.
• Technical records: sign-in time, session, language and notification settings, and which version of the terms you accepted and when.

Health data (heart rate, wellness, heart rate thresholds) is processed only if you connect a watch and give your separate consent – see section 8. Please do not write diagnoses or other sensitive information in comments.

We need the data to provide the service you ordered: an individual training plan with coach support (performance of a contract). Technical records are kept for the security of the app (legitimate interest). We do not use your data for marketing and we do not sell it. From your watch data the app automatically evaluates your training load, fitness and thresholds (see section 8) – in legal terms this is profiling. Threshold automation may raise your threshold by itself, and your coach or you can undo it. We make no automated decision with legal or similarly significant effects.

Your coach sees your data. The technical maintainer of the app, Pauls Rubenis, accesses it only when needed to fix a fault. To check that the app's calculations are correct, he looks only at summaries – for example the average difference between our calculation and the watch account's – never at one athlete's activities. Other athletes never see your data. If you connect Google Calendar, the plan text also goes to your Google account – see section 9.

The application server (Render) and the database (Neon) are located in Frankfurt, Germany. Both are services of US companies with data processing agreements in force. Sign-in uses your Shopify customer account, the same one you use in the shop; the app never sees or stores a password. On a second device (a phone, for example) you can also sign in with a one-time code shown by the app on a device where you are already signed in: it is valid for 10 minutes and once, and we store only its hash, not the code itself.

We keep your data while you have an account. If you ask us to delete your account, we delete the account, plan, completion marks and comments within one month; database backups may retain them for up to 7 more days.

The app uses only strictly necessary cookies: for your signed-in session and for the sign-in step itself. There are no analytics or advertising cookies.

You can connect your Intervals.icu account so that workouts from your watch appear next to the plan. This happens only with your separate consent at the moment you connect; before that we process no such data. We then process: your activities with all fields Intervals.icu keeps for them (date, sport, name and description, distance, duration, pace, heart rate, cadence, elevation, calories, training load, laps, weather, your perceived exertion and feel, gear, tags, weight and resting heart rate on the day, device name, and the full per-second recording your watch made – heart rate, power, cadence, speed, altitude, temperature, respiration, running and pedalling metrics; from this recording we compute and store your best 1, 5, 10, 21 and 42 km times, which become the records on your profile, and the time in each of your heart rate, pace and power zones (by the zones in force on the day of the activity) shown on Progress, and from Intervals.icu we take your best times over those distances across the whole history stored there, including before you connected, with the activity number, date and type – these too become the records on your profile); laps from the original watch file, which we read in memory and do not store; the route of the activity for the map – only if you tick it separately (section 8a); wellness data that your watch sends to Intervals.icu or that you enter there yourself (sleep, HRV, resting heart rate, weight, SpO2, respiration, steps, VO2max, fitness and fatigue, subjective ratings, and other entries of yours such as blood pressure, nutrition or menstrual cycle phase); your training zones and thresholds, and sex, date of birth, height and weight from your profile. Wellness data is optional: untick "Wellness Data" on the Intervals.icu consent screen.

Thresholds for each sport – threshold pace for running, FTP (threshold power) for cycling, and threshold and maximum heart rate for both – that your coach or you enter in the app are stored with their source, date and history; we calculate your training zones from them (your coach or you can adjust them), and we also write the thresholds to your Intervals.icu sport settings so that your watch shows pace ranges; we do not change your heart rate zone boundaries there. We also determine thresholds automatically from your races and training (heart rate thresholds from your heart rate recording): for every change or suggestion we store an explanation and the evidence (which race or session and how), and your coach or you can change or undo it; values entered by your coach are never changed automatically. We accept and estimate heart rate thresholds and heart rate zones only with this same consent. If you untick "Update" next to "Settings" on the Intervals.icu consent screen, we write nothing to your settings.

From your watch recording (pace, heart rate or power) and the thresholds in force on the day of the activity we calculate the load of each activity ourselves, and from it your fitness, fatigue and form. The heart rate load formula uses the sex from your Intervals.icu profile. From the plan your coach publishes we calculate the planned load and estimate your form for the coming days; you and your coach see these numbers. From your running recordings we find your best 2–20-minute efforts, which may lead to a threshold pace suggestion for your coach. To check that these calculations are correct, we compare them with Intervals.icu's calculations and look at the comparison only as summaries. We also store the Intervals.icu account settings that determine its calculations: load method order, heart rate load type, gradient adjustment and form display.

We write the plan your coach publishes for the next 7 days to your Intervals.icu calendar so that the workouts reach your watch; you can turn this off on the Connections page.

This is health data, so the legal basis is your explicit consent (GDPR Article 9(2)(a)). There are three purposes: so that your coach can compare what you did with the plan and see your load; to check that the app's calculations are correct (summaries only); and so that in future an automated tool may help the coach draft the plan – the coach always approves the plan. Before such a tool is enabled we will tell you, add the recipient to this notice, and you will be able to opt out. Today your coach sees this data; the maintainer sees only summaries for checking calculations and what is needed to fix a fault. You can withdraw consent at any time on the Connections page by disconnecting the account: we stop receiving data immediately and you can delete everything already received there. Deleting your account deletes this data completely.

We store the route of an activity only if you tick the map separately on the consent page; everything else works the same without it. The route contains no point closer than 400 m to the start or finish of the activity – even where the route passes there midway – so it does not reveal where you live or work. The map is shown only to you and your coach. Your browser loads the map background from OpenStreetMap Foundation servers (tile.openstreetmap.org): they see your device's IP address and the area you view, but not your training data or who you are. You can switch the map off at any time on the Connections page – we then delete all routes; disconnecting the watch always deletes them.

If you wish, you can connect your Google account so that the published plan appears in your Google Calendar. The app then creates a separate calendar named "Mile Savers – Treniņi" in your account and writes into it only the coach's plan text and the target breakdown for the next 120 days, one all-day event per day. The app requests and receives access only to this one calendar that it created itself (Google scope "calendar.app.created"); it cannot see or change your other calendars or events. Each event also carries a link to your day view in the app (it opens only with your account) and an internal marker by which the app recognises its own events; your name, e-mail or account identifier never go to Google. We receive and store nothing about you from Google except the access tokens, the identifier of our calendar and the identifiers of the events written into it; tokens are stored encrypted. Watch and wellness data never go to the calendar.

The legal basis is your own request to enable this feature (GDPR Article 6(1)(b)). The recipient in this case is Google Ireland Limited, which processes your calendar under its own terms and privacy policy; the plan text in your calendar is as visible as any other event of yours. You can disconnect at any time on the Connections page: we revoke access on Google's side and delete the tokens on ours; you can keep the calendar as history or have it deleted. When you delete your account we revoke access in the same way, but the calendar with the plan already written into it stays in your Google account – you delete it yourself.

Mile Savers' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: only to run this feature, never for advertising or to train AI models, and no human reads it except for security or bug investigation with your consent.

You have the right to access your data, correct it, delete it, restrict its processing, receive it in a portable form and object to processing. Write to the e-mail above and we will reply within one month. If you believe your data has been handled incorrectly, you can lodge a complaint with the Data State Inspectorate of Latvia (Elijas iela 17, Rīga, LV-1050, dvi.gov.lv).