This policy explains what personal data we collect when you use SACORO, what we use it for, who else is involved, how long we keep it, and the rights you have. It describes what the product actually does. Where something is switched off, it says so rather than describing it as if it were running.
Who is responsible for your data
SACORO is operated by Velvet Viking Ltd (company number 17404255, registered in England and Wales, registered office 7 Myrtle Drive, Halifax, HX2 8HQ). For data protection purposes we are the data controller for the personal data described here.
To exercise any of the rights below, or to ask a question about your data, contact support@velvetviking.co.uk.
What we collect
Account data: your email address and the authentication records needed to sign you in. You sign in with a link we email you, so there is no password. If you sign in with Apple or Google, we receive your name and email address from them.
What drives your running, only if you tell us: the motivations you choose, such as a personal best or your health and wellbeing. See "The AI coach" below.
Programme data: the answers you give when you set up a training block — your goal distance and date, your current weekly volume, the days you can run, your benchmark performance and your goal times — and the plan SACORO builds from them.
Completed sessions: for each session you log, the distance, the pace, your heart rate where it is recorded or imported, your rating of perceived effort, how the session felt, any splits you enter, and any notes you write.
Daily check-in, where you record it: how you are feeling that day, how your legs feel, and how you slept. You can use SACORO without providing this.
Injury, pain and illness information where you supply it, through the check-in or in a session note. It is stored with the day it relates to and used to decide what to recommend next, including recommending that you do not run.
Coaching output: what SACORO produces about your training — execution reviews, athlete-state and readiness assessments, proposed plan changes, whether you accepted or declined them, and, where you use the AI coach, its written analysis of a run or a week. This accumulates into a longitudinal record of your training, which is what lets coaching decisions take your history into account.
Coach Memory, only if you turn it on: short one-line notes of what you asked the AI coach and the choices you made, such as turning down an extra run, so the AI coach can pick up where you left off. See "The AI coach" below.
Subscription data: which plan you are on, your billing period, whether you are in a trial and when it ends, and the status of your payments. We do not receive or store your full card number, expiry or security code.
Support correspondence: what you write to us and what we reply.
Operational and security information: records needed to keep the service running and to detect and prevent abuse, such as authentication events and error diagnostics. This includes the date and time your account last received access, recorded no more than once an hour. It tells us an account is in use; it is not a behavioural analytics stream, and we deliberately do not build one. Our diagnostic logs are written so as not to contain email addresses, tokens, secrets, signatures or full provider error payloads.
We do not use analytics, advertising or tracking technology, and we do not collect advertising identifiers.
Information that can indicate something about your health
Some of what SACORO holds is ordinary training information — distance, pace, the days you can run. Some of it is not so easily categorised. Heart rate, how you slept, how your legs feel, an entry saying you are unwell or in pain, and the readiness assessments built from them can all say something about your physical condition.
We do not treat everything as health data, because that would be inaccurate, and we do not pretend none of it is, because that would be worse. Where you tell SACORO you are injured, in pain or ill, that is information about your health, and you are choosing to give it to us so the product can respond to it.
You are never required to provide it. The check-in is optional, notes are optional, and SACORO works without them, with less to go on.
The lawful basis for running SACORO is our contract with you — Article 6(1)(b) of the UK GDPR. That covers your account, your subscription and the ordinary training processing that produces your plan. Providing the service has never rested on your consent, and it does not now.
The health-indicating information above needs something more, because special-category data does. For that, and only that, we rely on your explicit consent under Article 9(2)(a). The two sit together: the contract is why we can run the service, and your explicit consent is why we can use heart rate, sleep, readiness answers, how a session felt, and what your notes say about pain, illness or how you slept.
We ask for that consent separately, and it looks like what it is. It is a single opt-in that starts unticked, on the same panel as the heart-rate fields it governs, recorded against the version identifier health_data_consent_v1. Consent is never inferred from something else you did: not from accepting these terms, not from creating an account, not from paying, not from entering a heart rate, and not from reaching the end of setup. Leaving it unticked is recorded as a decision not to consent, which is why we do not keep asking.
Declining costs you the readings, not the product. SACORO still builds and adapts your plan, still scores your sessions, and still tells you what to do next. The controls that collect the covered information are simply not shown, with one line saying why. A session scored without heart rate gets exactly the score an athlete who never owned a chest strap would get; a missing reading is never read as poor readiness.
You can withdraw at any time from Settings, using the same switch in both directions. From that moment we stop collecting the covered information and stop using it: typed, imported and device-supplied heart rate are refused, and your stored heart-rate profile values are cleared. Where a connected service such as Strava sends us an activity, the covered fields are removed before the activity is written down, so without valid consent they are never stored rather than stored and ignored.
What withdrawal does not do is erase your past. Covered information you logged while consent was in place is retained and becomes inert: it is excluded from every coaching decision, target and longitudinal reading for as long as consent is absent, and it is not processed at all rather than kept under some other justification. We say this plainly because the opposite claim is the tempting one — withdrawal is not a purge, and we are not going to describe it as one. Erasure is a separate right, it is handled separately, and you can ask us for it.
Your consent record is kept as its own append-only history — each decision, its version and when it was made, and no later edit to what an earlier decision said. If the purpose ever materially changes, the version changes with it and every consent to the old version stops counting until you are asked again. The record holds nothing about your body, so it survives an erasure of the health information itself: it is the evidence that what we already did was lawful when we did it.
Distance, pace, time, splits, completion, rating of perceived effort, benchmarks, race results, pace zones and your own note text are ordinary training data and are not inside this boundary. They are processed for every athlete under the contract, consented or not, and withdrawing consent leaves them untouched.
None of this information is sent to monday.com or to Stripe, none of it is used for advertising, and none of it feeds a secondary analytics warehouse.
What we use it for
To build and adjust your training plan, and to produce the coaching output that is the substance of the product.
To decide what to recommend next, including holding you back or telling you not to run when what you have recorded says you should not.
To keep your plan and history available across your devices, and to restore it when you sign in again.
To take payment, manage your subscription and trial, and keep the financial records we are required to keep.
To operate the service — signing you in, keeping it secure and available, and diagnosing faults.
To answer your support requests.
That is the complete list. We do not profile you for advertising, and we do not measure your behaviour in the product for marketing purposes.
What we will not do with it
We do not sell your personal data, and we do not share it with third parties for their own marketing.
We do not use your individual training data to train or fine-tune machine learning models offered to anyone else, and we do not make it available to third parties for that purpose.
Who else is involved
We use a small number of service providers, each acting on our instructions under contract, and each with access only to what it needs.
Hosting and database: our managed database is provided by Supabase and hosted in the European Union. Vercel hosts the website, the application and the server functions that talk to the database.
Authentication and database: Supabase provides our authentication and our managed database. Signing in uses a link we email you rather than a password, so no password for SACORO exists to be stored or stolen. Sending that link necessarily processes your email address, and the sign-in email is currently delivered through our authentication provider's own sending infrastructure.
Payments: card payments for web subscriptions are handled by Stripe as our payment processor. Your card details go to Stripe and not to us. We receive the state of your subscription and its payments — whether you are in a trial, when it ends, whether a payment succeeded — and never your full card number, expiry or security code.
Internal operations: we use monday.com as an operational mirror for commercial and lifecycle tasks. It receives operational state only, against a pseudonymous reference rather than your account identifier. It does not receive your training sessions, heart rate, pace, perceived effort, readiness or athlete-state information, your notes, your training history, any other coaching evidence about you, or your payment-provider customer identifier. It is not a source of truth about what you are entitled to.
The AI coach: when you use the AI coach, Anthropic processes what we send it as our data processor, under contract and for no other purpose than answering. See "The AI coach" below for exactly what that is and is not.
We do not otherwise disclose your data, except where we are legally required to.
Connected services, when you choose to use them
SACORO supports optional connections to services you already use. Every one of them is off until you connect it, requires your authorisation through the other service, and can be disconnected at any time from your account settings.
Strava. If you choose to connect it, we ask Strava only for permission to read your activities. We do not ask for permission to write anything back to Strava, and we do not ask for your Strava profile. The access credentials for the connection are held server-side in storage that is closed to direct access, and the activities we receive become part of your training record.
Disconnecting is immediate and complete: we delete the stored credentials, delete the Strava activities we had staged, and tell Strava to revoke our access. If Strava stops accepting our credentials, we clear the connection rather than leave it looking connected when it is not.
Strava is a separate company with its own privacy policy and terms, and it does not endorse SACORO.
Devices and watches, including Garmin. Garmin is not currently available. No Garmin connection exists, no Garmin data is received and none is sent. The groundwork is in place on our side, but until it is switched on there is nothing to describe. If that changes we will update this policy before any data flows, and connecting will remain your choice.
If a connection is not enabled for your account, no data passes to or from it.
The AI coach
SACORO's AI coach uses Anthropic's API to explain and discuss coaching decisions that SACORO's own deterministic engine has already made. It does not decide anything itself: it cannot prescribe a session, compute a pace, or write anything into your plan.
To write an analysis of a run or a week, the AI coach is given your logged figures for that run or week — distance, pace, time and effort — and SACORO's own conclusions about them. Your heart rate is included only where you have given the health-data consent described above; without it, heart rate is withheld from the AI coach exactly as it is withheld from every other coaching decision. Free-text notes you write yourself are never sent, and no information that originated from a connected service such as Strava is ever sent, even where that service is connected. The analysis the AI coach writes is saved with your plan, the same as any other coaching output.
If you ask the AI coach a question directly, what you type is sent to Anthropic as well, together with the same kind of training information, so it can answer you. The same rules apply to that exchange: heart rate only with consent, no free-text notes, and nothing originating from a connected service.
Anthropic processes this information under contract with us, to provide the response and for no other purpose. It is not used to train or fine-tune models offered to anyone else.
Coach Memory is off until you turn it on in Settings. With it on, SACORO keeps short one-line notes in your account: what you asked the AI coach, and choices such as turning down an extra run. The most recent few are given to the AI coach as background with each question. Nothing from a connected service such as Strava is ever kept, and pain, illness and other health details are kept only where you have given the health-data consent described above. You can read or clear the notes in Settings at any time.
If you tell us what motivates your running (for example a personal best, or your health and wellbeing), we keep your choices with your training plan and include them in the context our AI coaching provider receives, so your coach can encourage you in the right way. They never change your training plan, and you can change or clear them at any time in Settings.
Where your data is stored, and transfers
Your account and training data are stored in a managed database hosted in the European Union.
Some of our providers are established outside the UK or operate support functions elsewhere. Where personal data is transferred outside the UK, we rely on the safeguards UK data protection law requires, such as adequacy regulations or standard contractual clauses with the additional protections that go with them.
The SACORO application also keeps a copy of your current plan and recent activity on your own device so it works offline. That copy is under your control and is removed when you uninstall the app or clear its data.
How long we keep it
While your account is open we keep your training history, so it stays available to you and so coaching decisions can take it into account. We do not delete it routinely — losing your history would make the product worse for you.
Coach Memory notes are kept until you clear them in Settings or delete your account, and only the most recent 100 are ever kept.
If you delete your account, we delete your account and the training data associated with it from our live systems. Copies can persist briefly in routine encrypted backups before those rotate out.
Records of payments we have taken are not deleted with your account, because we are required to keep financial and tax records. When your account is deleted, those billing records are separated from it: the account and subscription identifiers are cleared from them, leaving a de-identified financial record. That record holds no email address, no name, no postal address, no card details, no IP address and no payment-provider payload. It exists for accounting, tax, fraud prevention and legal obligations, and it cannot be used to reconstruct your training.
If you would rather we deleted your account for you, email support@velvetviking.co.uk.
Cookies and storage on your device
The marketing website sets no cookies and stores nothing on your device. The application stores what it needs to keep you signed in and to work offline. Our Cookie Policy sets out the full inventory.
Your rights
Under UK data protection law you have the right to access a copy of your data, to have inaccurate data corrected, to have your data erased, to obtain it in a portable form, and to object to or restrict certain processing. Where we rely on your consent for anything, you can withdraw it at any time, and withdrawing it does not affect what was done before.
You can delete your account from within the product at any time. For anything else, contact us and we will respond within the period the law requires.
If you are unhappy with how we have handled your data, please tell us first so we can put it right. You also have the right to complain to the Information Commissioner's Office at ico.org.uk.
Changes to this policy
If we make a material change to how we handle your data, we will tell you before it takes effect. The date at the top of this page shows when it was last updated.