Skip to content
Menu ▾

Privacy policy

Last updated: 2026-11-09

Draft for the TestFlight preview. This policy will be reviewed by a lawyer before the public launch.

VVake (also called VVake Fit) is a fitness coaching app for iPhone and Apple Watch, with this website, vvake.com. This policy explains in plain words what we collect, why, who else sees it, how long we keep it and what you can do about it. It covers the apps (TestFlight previews included), the VVake API they talk to, the desk companion for Mac, the VVake plugin for Claude Code and this website, including vvake.com/rewards.

VVake is a training and wellness app. It is not a medical device and does not diagnose, treat or monitor any health condition.

Plans, coach replies and health data in VVake are suggestions, not medical advice. Read Health & safety and your responsibility

The short version

  • No ads, no sale of your data, no tracking across apps or websites.
  • We count which features are used (never what you do in them), on our own servers, to improve VVake. You can turn it off any time.
  • Health data is used only to coach you. It is never sold, never used for advertising and never shown to other people.
  • Your GPS route stays on your iPhone or Apple Watch and in Apple Health. Our servers never receive your location in a form we can read: your routes are backed up to your account end-to-end encrypted, with a key held only on your devices, so VVake can't read them. The only readable route we ever receive is one you choose to share for one challenge: trimmed at both ends, kept only while that challenge lasts, then deleted. When you look for places to train nearby, we receive a point rounded to about 1 km, which we don't keep.
  • You can use VVake without signing in, and you can delete your account and everything with it.
  • Our database and stored files are kept in the European Union.
  • $VVAKE prizes are optional. If you link a wallet, its address and weekly prize amounts become public on a blockchain, which can't be erased.

Who we are

VVake is run by the VVake team, which is responsible for the personal information described here.

Person in charge of the protection of personal information (Québec Law 25): the founder of VVake. You can reach them at privacy@vvake.com.

What we collect, and why

We collect as little as we can. Here is all of it, grouped by what it is for.

  • Your account. A random account ID, created the first time you open the app (a guest account, with no name or e-mail). If you sign in: your Apple or Google account identifier, your e-mail address (Sign in with Apple lets you hide it behind an Apple relay address) and your name if you give it. Also your display name, your VVaker (avatar) choice, the home city you pick, your time zone, your language, your theme (light or dark) and your coach settings. Why: to keep your training across devices and show your name to the people you challenge.
  • Your devices. For each iPhone or Apple Watch you use: a device ID made by the app, whether it is a phone or a watch, its model and when it was last seen; sign-in tokens (we keep only a hash of them); and a push notification token if you allow notifications. If you sign in on vvake.com/rewards, that browser is added as a device named "Web (vvake.com)"; each computer you link to Claude Code is added with its name (see Desk companion and Claude Code). Why: to keep you signed in, let you sign a device out and send the alerts you asked for (challenges, crew quests, My Pulse). To check that sessions come from the genuine app, we keep an App Attest key identifier and Apple's attestation receipt for each app install; they identify the install, not you.
  • Your sessions. For each workout: the sport, start and end time, active time, distance, average and maximum heart rate, time in each heart-rate zone, steps, cadence, calories, effort score, points and streak, and a sample every 10 seconds of distance, heart rate and steps. For a camera workout, the counts of the session (moves, sets, reps, the load you typed; see Camera workouts), never an image. Never GPS coordinates we can read (your route backup is end-to-end encrypted, see Location; a route race adds only when you started and finished the route and the metres covered on it). Why: your journal, stats, streak, plan, races against your own past sessions, challenges and City Clash.
  • Live coach workouts (VVake Coach Plus). While a live conversation with the coach is possible during a workout, the app tells our API that the workout is running: the sport, when it started, its clock, whether it is indoors, its running totals (distance, steps, seconds of wrist movement or pedalling) and your heart-rate samples since the last update. Each message is signed by the device with Apple's App Attest (iPhone, Apple Watch) or checked with Google Play Integrity (Android, Wear OS), which tells us it comes from the genuine VVake app. Why: the live coach works only during a real workout (your plan's minutes a week and any minute packs, 5 per workout), and these checks stop scripts and copied requests from using it. We keep each workout's record 4 days, the minutes you used each week about 2 weeks, a salted hash of the device (never its ID) 60 days, and a trust score with any warning flags (flags 60 days; the score with your account). Your IP address is used only salted-hashed, for rate limits. Never used for ads or prizes.
  • What the coach remembers, and settings it changes. Short lines the coach keeps to coach you, by kind: how you like to be coached, likes and dislikes, facts about you (like "works night shifts"), how your body feels (like "left knee sore since Tuesday", never a diagnosis or the name of a health condition), life events and goals with their date, wins, and what worked or didn't. They come from what you tell the coach, from proposals you approve, from a short review the coach makes after a conversation (by our AI provider, Anthropic, see AI features) and from milestones in the app. You see, correct, add and delete them in You › What your coach remembers (in the apps, vvake.com/app and vvake.com/account); a line you edit is never overwritten. If you tell the coach a number from Apple Health or Health Connect is wrong (like "I slept 8 hours, not 6"), we store your correction next to that value, never over it, with the day and the value it replaced: the coach and your readiness use your number, Apple Health and Health Connect are never changed, you can undo it, and corrections are kept 60 days. When the coach proposes a settings change (heart zones, resting or maximum heart rate, reminders, focus lock, goals, how chatty it is), we keep the proposal and your answer, and for each change applied a record of the values before and after, which device or voice approved it and when, so you can undo it for 30 days. We also keep how your last 10 sessions felt (your one-tap feedback). Kept with your account and deleted with it; Fresh start clears the memory, feelings and proposals.
  • About you: what the coach learns to know you better. Along the way, the coach may remember personal details you share, like your hobbies, the foods you love, how you relax or that you enjoy a good meal out now and then, so it can talk with you like someone who knows you. They are listed under About you in What your coach remembers: you see, edit and delete them one by one, or all at once, any time. They are used only by your coach inside VVake: never for ads, never shared, never sold. Sensitive topics (a health condition, religion, politics, sexuality and the like) are kept only when you clearly ask the coach to remember them. The VVake team's dashboard sees only how many people have such notes, never what they say. Kept with your account and deleted with it; Fresh start clears them.
  • Get to know me: the coach's questions about you. Your coach may ask you one short question now and then (at most one a day, or up to 5 when you tap Get to know me), from a fixed list: what got you moving, your routine, what you do for fun, the food you love, how you relax, anything it should be careful with. It never asks about your weight, your body, health conditions, mental health, pregnancy, money or religion. We keep which questions were asked and whether you answered, so it doesn't ask twice; Forget the questions clears that list. Your answers are kept only as About you lines in your coach memory, which you edit or delete like any other; the VVake team's dashboard sees only how many questions are asked and answered, never the answers.
  • How you talk with the coach: patience and Hold to talk. We keep your Patience setting (Quick, Normal or Relaxed), whether Hold to talk is on, and a single number your device learns from your pauses (how long you usually pause before going on, in milliseconds), so every device waits the same way for you. No recording and no words are kept for this. When you say "later", the coach keeps one short note of the topic ("Pick up: …") in your coach memory, which you can delete. We count how long calls stay on hold and how often the coach checked in, as totals for the team, never the content.
  • Coach calls and your coach voice (VVake Coach Plus or Premium). If you turn coach calls on, the app sends us a short summary so your next call is about you: this week's plan against what you did (sessions planned and done, and up to 3 you missed) and, only when you share them from Apple Health or Health Connect, your recent sleep, resting heart rate and heart-rate variability (HRV), with how they compare to your usual. Only what your phone really has; nothing is guessed. We keep this summary at most 2 days and use it only to write your next coach call (see AI features). We also keep the coach voice you chose, a woman's or a man's: the coach speaks to you in that voice in workouts, calls and replies, on all your devices.
  • Your account page on vvake.com. Once you sign in on vvake.com/account, the page shows and changes the same settings the apps keep, through our API; it collects nothing new. Your 7-day agenda there is worked out each time you open it, from your plan, your approved coach changes and your usual times, and is not stored.
  • Move Quests and Crew Quests. Move Quests are short motion challenges (10 to 60 seconds: hands up, jumps, freeze) on your Apple Watch. The watch's motion sensor is read on the watch only; we receive just the result: the kind of quest, when it started, how long it lasted, the reps, whether it succeeded, the time of each rep, the longest hold, the peak acceleration, and whether the watch was on your wrist (yes, no or unknown, worked out on the watch from how recent your latest Apple Health heart-rate reading is). Never the raw motion stream. Why: to check the quest was real, give VV points and a little streak help, and count your movement for the Claude Code unlock. A Crew Quest is the same quest at the same time with your crew, the people you have faced in an accepted challenge: when you start one, your crew gets a push notification with your display name and the quest, and everyone who joins sees each other's display name, VVaker and result (success, reps, time, points and rank).
  • $VVAKE prizes (optional). If you link a wallet on vvake.com/rewards: its public address, when you linked it, that you confirmed being 18 or older, and the one-time message you sign to prove it is yours (kept 10 minutes). If you take the free entry: when you entered or withdrew. Your answers to the weekly skill question: when you answered and how many tries. Each week: whether the week counts for prizes (an entry, account and wallet from before the week, enough heart-rate effort, the skill question), the VV points of your counted sessions (capped per day), the VVAKE amount they give, its proof, and whether it has been claimed (read from the blockchain). See $VVAKE prizes and your wallet.
  • Your athlete profile. Your answers to the first-run survey (your sports and experience, sessions per week, usual length, a recent best, how hard it feels, your aim and any event, the days and minutes you have, and whether you have pain or an injury), plus the health fields you choose to share (see Health data). From these we compute your assessment: level, heart-rate zones, pace and cadence targets, weekly targets and coach notes. Why: to size your plan safely.
  • Your coach. What you say or type to the coach, its replies, the plan changes it proposes and whether you approved them, and the one-tap "how did it feel" after a session with any short note you add. Your conversation itself is not stored on our servers: only the last few turns are sent with each question so the coach can follow. We keep the text of spoken coach lines to produce and cache the coach's voice, and the summary of each proposed plan change.
  • Challenges and City Clash. The challenges you send or accept (what is measured, how long, status and result), the stickers you react with, the people you block, the clashes your city is in and whether you said "I'm in", and a "moving now" signal sent once when a session starts and once when it ends during a live clash. Your friends are only people you have already faced in an accepted challenge: we never upload your contacts. For a 24-hour challenge ("beat my mark") we also keep the mark (a distance and time, a distance or minutes, or the session it comes from), when the link was sent and until when it can be accepted, whether it is open to everyone, and for each person who accepts: when, their 24-hour deadline, the device that accepted (one acceptance per device), whether they chose to show their name on the board, the session that counted and its result, why a session did not count, and the VV points won. When you challenge a contact by text message, you pick the person in the iPhone's own contact picker and send the message yourself from the Messages app: VVake sees only that one person, never your address book, and uploads nothing about them; the app keeps their first name and how you sent it (text, link or X) on your phone only, so you can challenge them again. When you share a link through another app (WhatsApp, Telegram, Messenger, X…), you choose who gets it in that app: VVake never gets your friends or followers.
  • Training meetups. You can invite people you have already faced (friends, crew, challenge rivals) to train together. A meetup is visible only to the people invited. We keep its sport, time, duration, meeting point, the pace line you typed, how many people may come, who was invited, each answer, when someone tapped "I'm here" and which reminders were sent. The meeting point is a public place (a car park, trailhead, park, track…) picked on the map, for which we store only its OpenStreetMap id, or a custom meeting point the host drops on the map (see below). "I'm here" sends no location. Reports about a meetup are read by our moderators. Meetups are deleted 90 days after they end, and when the host deletes their account; your answers go with your account. "Add to calendar" makes a file on your device with the meetup's time, place and pace line only. If you connected Google Calendar, the meetups you are going to go to your VVake calendar there instead (see Calendar), unless you turn that off.
  • Custom meeting points. The host of a meetup can long-press the map to drop their own meeting point, with a name (up to 40 characters), an optional note (up to 200) and an optional photo. We keep its exact coordinates because you need them to meet, and only the people invited to that meetup can see the point, its note and its photo: it never appears on public maps, Spots, place notes or any list. When the point is not at a public place, the app suggests moving it to the nearest one. The photo is resized on your device and its location and camera data (EXIF) are removed before and after upload. The point, its note and its photo are deleted 7 days after the meetup ends (and with the meetup or the host's account). "Add to calendar" puts only the point's name in the file, never its coordinates.
  • Train together over a call. A meetup can be a call instead of a place: everyone trains where they are and sees a shared board. Each app sends its own numbers every 10 seconds while the board is open (elapsed time, distance or reps, heart-rate zone, and whether it is running, paused or done), never a position. Only the people in that meetup see the board and the cheers sent there; leaving the board tells nobody. Board numbers and cheers are deleted within two days after the meetup. The optional group audio goes through our hosting provider's real-time service (Cloudflare) between the people in the call: it is never recorded or stored, by us or by them. To keep the service affordable we count the minutes each account spends in the audio each day (a number, not the audio). The optional coach on the call only says a few prewritten lines on each phone.
  • Calls in an app you already use. The host of a call meetup can choose to talk over an app people already use (WhatsApp, Messenger, Telegram, FaceTime, Google Meet, Discord, Snapchat or another) instead of VVake's audio. The host makes the call there and pastes its link in VVake. We keep the link and which app it belongs to, and show it only to the host and the people who said they're in: never in notifications, public lists, Spots or maps. The link is deleted when the meetup's board is cleared, within two days after the meetup ends. The call itself happens in that app, under its own privacy policy: VVake doesn't see, hear or record it, and starts no VVake audio for it. The board, countdown and cheers stay in VVake. A link opens only when you tap it, and a link from an app VVake doesn't recognise asks you first. The coach's live talk stays in VVake.
  • My Pulse (optional). The stock symbols you choose to follow (up to 8), your alert thresholds, your Brand Team, quiet hours and how many alerts a day you want. My Pulse shows facts only, for fun; it is not investment advice.
  • Your VVaker image (optional). If you render a custom VVaker: the trait code you designed and the images it produced.
  • Your VVaker as your picture. Wherever other athletes see you in VVake (a meetup, a train-together board, a league, a challenge, a creator page), your VVaker is your round picture: a small head-and-shoulders crop of your current VVaker that your phone makes once (256 × 256 pixels, never a photo of you), or the picture of your cast VVaker. Only people who already see your name there see it. Where your name is hidden (“a mover”, a private profile, someone you blocked), people see initials on a coloured circle instead, never a picture. The picture's address is a random id with no name in it. When you change your VVaker, the new picture replaces the old one. Fresh start keeps it, like your VVaker; deleting your account deletes it.
  • Run moments (optional, kept on your phone). After a session you can add a photo or a 6-second video to it. It stays on your iPhone, linked to that session, and is never uploaded to VVake's servers. When you share it, the picture or clip goes through your iPhone's share sheet to the app you choose. Location data (EXIF and GPS) is removed from the shared picture, and the shared card never shows a map or where you were: if you turn on the route shape, its first and last 300 m are hidden. Delete the moment or the session and it's gone from your phone.
  • Setting up with your coach (optional): by voice or typed. When you set VVake up, or later from Tailor my app, you can talk or type with your coach instead of tapping the cards (the first meetup by voice is free, about 3 minutes, once per account and device; later voice catch-ups from Tailor my app use your live coach minutes, a few a day at most; typed a few times a day, free). The microphone is on only during a voice conversation and only after you tap to start it; you can mute it, end it or switch to the cards at any time; typing never uses the microphone. What you say or type is turned into the same answers the cards hold (goals, sports, where you train, an event, coaching style, voice, habits, music, notifications) plus a few things the cards never asked (why you started, which days and how long, the time of day, your equipment, which devices you have, what you want help with). The coach then proposes a setup (your screens, plan, reminders, habits, food if you want it, a crew, a first thing to try) and nothing is saved or changed until you confirm it; you can undo it all within 30 days. After you confirm, the coach keeps up to four short notes in its memory (why you started, your event and its date, how you like to be coached, a check-in after your first week), never a health condition; you see, edit and delete them in Coach memory. We keep the conversation's record (when, how long, typed or by voice, how many changes you applied, what it cost us) and the answers you save, never the audio and no text of the conversation.
  • Security and abuse prevention. Counters that limit how often something can be done, keyed by a salted hash of your IP address or by your account ID, and short-lived single-use codes (sign-in codes, watch link codes) stored only as hashes. Our server logs record errors, never health data or what you said to the coach.

Health data

VVake reads Apple Health (HealthKit) only with your permission, type by type, in the iOS permission sheet. You can change your choices at any time in the Health app or in Settings > Privacy & Security > Health.

  • During a session. Heart rate, steps and cadence, to score your effort for your heart (not speed), coach you live and record the session.
  • Only if you allow it. Age, sex, resting heart rate, heart-rate variability, VO2 max, height, weight and sleep, so your zones and targets fit you.
  • What reaches our servers. The session data listed above, and the health fields you tick to size your plan: age, sex, weight, height, resting and maximum heart rate, average sleep, and two choices you make yourself (low-impact only; easy effort only, for example during pregnancy or on a professional's advice). When you share Health with VVake (build 62), also one set of numbers a day: resting heart rate, heart-rate variability, VO2 max, hours of sleep and a maximum heart rate Health measured. Numbers only, never a condition.
  • Start workouts for me. If you choose Ask me or Start automatically (in the app's settings or on vvake.com/account), the app notices when you start walking or running and asks before recording it (Ask me) or records it for you (Start automatically). To do this it reads, on the device only, the motion chip's guess of what you are doing (walking, running, in a vehicle or still) on your phone and your watch (Motion & Fitness on iPhone and Apple Watch; Google Play services Activity Recognition on Android and Wear OS), and your recent steps history, so the workout starts from when you really set off. None of this leaves your device: a workout you keep is uploaded like any other, with a mark that it was started for you. Each device asks for the permission only when you pick one of these options; Off turns it off.
  • Vehicle check. During a walk, run or hike, the app checks on the device itself whether you seem to be in a car, bus or train (moving faster than on foot with no steps, steps longer than a body allows, or the motion chip saying vehicle). That stretch is paused and left out of the workout. Nothing new leaves your device: the session only carries a mark that a vehicle was detected and how many seconds were left out, so a session that was mostly a ride shows in your journal as not counted.
  • Fair points (anti-fraud checks). To keep points, leagues and challenges fair, each workout recorded with the phone alone is checked when it reaches us. Your phone adds a few facts about its own sensors: how many GPS fixes it got and how many were precise, whether the phone's system marked some locations as simulated (a mock-location app), how much the reported accuracy and altitude varied, how many seconds the motion chip said walking, running, still or vehicle, whether the phone looks like an emulator or is rooted or jailbroken, and whether the route is a point-for-point copy of one of your earlier routes (compared on your phone only). These are counts and yes/no answers, never a position. Our server compares them with the session's distance and steps it already receives. To spot one person recording the same walk on several accounts, it also compares, minute by minute, the distance and steps of sessions that started within a few minutes of each other, and keeps a salted hash of the network a session was sent from for 30 days. A session that can't be verified earns fewer points or none for now; it always stays in your journal and your streak, and a person reviews it. Nothing here leads to an automatic ban. Legal basis: our legitimate interest in preventing fraud. Matches are kept 30 days, reviews until they are decided; all of it is deleted with your account.
  • Adaptive coaching (build 62). From your sessions and these daily numbers, VVake works out how fit and how rested you are, the paces and heart rates that suit you and how you are progressing toward your goals, and keeps a history of what it learned and why. It also keeps your answers to its occasional questions ("How hard was that walk?", "Was that really your max heart rate?") with the session they are about, and for a planned session, its segments and targets and what was adjusted during it (a rest made longer, a rep shortened). This is used only to tailor your training, on the apps and on vvake.com: nothing changes without your tap, every change can be undone for 30 days, and you can keep every session on Fixed timing. Never for advertising, never sold, never shown to other people. The daily numbers are kept 400 days; Fresh start deletes them with what VVake learned (your sessions and their effort answers stay); deleting your account deletes everything.
  • What we write to Apple Health. Your Apple Watch saves your sessions as workouts in Apple Health, with the route for outdoor sessions. If you allow it, the outdoor sessions you record with your iPhone are saved there too, with their route.
  • Health in live calls and the first call. If you choose to, the coach can look at a short summary of the Health data you share during a live coach call or the optional first call (on that first call, the coach asks for access to Apple Health or Health Connect, and the system's own screen opens only when you tap). The app reads your data on your device and sends only a rough summary as ranges: about how many steps a day, your resting heart rate, how much you sleep and how many workouts a week (for example 7,000 to 8,000 steps a day, resting heart rate around 55 to 60, about 7 hours of sleep). Our server widens these ranges again before the coach sees them. The coach uses them to set or adjust your level, zones and week, never to make a diagnosis. No individual measurements leave your phone. The coach says nothing about your health aloud unless you are using headphones and have not asked it to stay quiet; otherwise it only shows it on your screen. This is not medical advice.

Your health profile is used only to plan your training and brief your coach. It is never sold, never used for advertising or marketing, never shown to other users and never a condition for taking part in anything. Competitions use one number: the effort score of the sessions you choose to count. Other people may see a challenge result or your city's total, never your heart rate, zones or any health value.

Health data you share is sent to our AI coach provider so the coach can answer you (see AI features). It is not shared with anyone else, except our hosting provider, which stores it for us.

Location

  • During outdoor sessions. VVake uses your location while you use the app during an outdoor session, to draw your route and measure distance. When you ask to race your best, it also checks the position your device last recorded, on the device itself, to suggest a route that starts near you. The live map keeps only your last position, on your phone itself and never uploaded, so the next map opens on you right away. The route stays on your iPhone or Apple Watch and in Apple Health; your Apple Watch also passes the routes it records, and during a workout where you are (so your iPhone's map can mirror it), straight to your own iPhone, never through our servers. It is never sent to our servers in a form we can read (unless you share a route for a challenge, below): we receive only totals such as distance and pace, and the end-to-end encrypted backup described next. Maps are drawn by Apple Maps.
  • Route backup (end-to-end encrypted). So your routes aren't lost when you change phones, the app backs each outdoor workout's route (recorded on your iPhone or your Apple Watch) up to your VVake account, end-to-end encrypted. Your iPhone encrypts it (AES-256-GCM) with a key that exists only on your devices, synced between them by iCloud Keychain; that key is never sent to us. We store only the encrypted bytes and a little metadata (which workout it belongs to, its size, when it was saved, and a fingerprint that tells your devices which key opens it). VVake cannot read your routes, and nobody else can download them: there are no public links. A route's backup is deleted when you delete that session, and all of them when you delete your account. If you lose every device and your iCloud Keychain, the backups can't be opened by anyone, including us.
  • Start workouts for me, in the background (iPhone). With Ask me or Start automatically, and only if you allow location in the background, iOS may wake the app now and then when you have moved some distance. The app uses that wake-up only to read the motion chip and discards the position at once: no location history is kept outside a workout, nothing of it is sent to our servers, and there is no continuous GPS while it waits. Without that permission, it works only while the app is open.
  • Your city. Your home city for City Clash is the city you type or pick, not your GPS position. You can change it once per season (28 days) or clear it at any time.
  • Route ghosts. Racing your own past route (a route ghost) uses the trace kept on your iPhone or Apple Watch (the watch passes its routes to your own iPhone directly); it is never sent to our servers in a form we can read. When you race, the app matches your position to the route on the device and uploads with the session only a summary: when you started and finished the route, the metres you covered on it and whether you finished. Never a position.
  • Sharing a route for a challenge (opt-in). Only if you choose it, for one challenge at a time, can you send a route to race. Before it leaves your device, the first and last 300 m are hidden (you can set 100 to 2,000 m; more on a loop, so the shared part never comes that close to where you started or finished) so the ends near your home don't show, and it is simplified to about 10 m. Only you and the people who accept that challenge can fetch it. We keep it only while the challenge lasts (at most 7 days to accept, plus 24 hours to race and 2 hours for late syncs) and delete it after, or as soon as the challenge is closed, declined or expires with nobody racing. It never appears on a public page: a challenge link shows only its length and climb.
  • Public totals only. City Clash and the live map show totals per city (shown only from 10 people moving, and rounded), never an individual's position, route or name.
  • Places to train near you, when you ask. When you look for places to practise a sport near you (on the phone, on the watch through the phone, or on vvake.com/app), your device reads your position once, while you use the app, and sends our servers only that position rounded to about 1 km (two decimals) and the sport. Our servers ask OpenStreetMap's Overpass service for that sport's places in whole map tiles of about 5 to 40 km around the rounded point, so neither we nor OpenStreetMap ever receive your exact position. We keep those map tiles (public map data) for up to 60 days, never your position, the search or who made it. Distances and directions are worked out on your device; the list sent to your watch stays on your devices. Places you save as favourites stay on your phone. Tapping Directions hands the place (not your position) to Apple Maps or Google Maps, under their own policy. Place data © OpenStreetMap contributors, under the Open Database License (ODbL).
  • Rating a spot and new spots. After a session you can rate the place in three taps: stars, whether you'd recommend it, a few tips from a list and, if you like, up to 80 characters of text. We keep your rating with your account and the place's identifier: an OpenStreetMap id, or for a spot OpenStreetMap doesn't know, a map square of about 150 m. Never your route, the session or the time of day. Other people only ever see totals, and only once a place has at least 3 ratings: the average, how many recommend it, how often each tip was given, and text tips after a moderator approved them. Never who wrote them. To tell you whether a spot is new, your phone (or vvake.com/app) sends once a point rounded to about 100 m and the sport; we use it for that answer and don't keep it. Ratings are deleted with your account.
  • Offline map areas (phone). If you save a map area for an outing without signal, the phone downloads that area's map tiles from OpenFreeMap (with the relief from the AWS Terrain Tiles open dataset) and keeps them on your device only. Like any map you view, those services see which map area is asked for, never your account; we are not told which areas you save. You see, refresh and delete saved areas in the app's map storage; deleting the app deletes them too. On the Apple Watch, the relief for a planned outing is copied from your iPhone to the watch, directly.

VVake on the web (vvake.com/app)

VVake also runs in your browser, for people who don't want to install the app. It uses the same account and the same servers as the app, and only what a browser allows:

  • Location, only during a workout or a places search. When you start an outdoor workout, your browser asks whether vvake.com may use your location. It is read only while that workout runs and the page is open on screen (a browser stops tracking when the phone locks or the page is hidden), to draw your route and measure distance, pace and climb. The route stays in your browser: we receive only the totals and a distance every 10 seconds, never a position. The map's tiles come from OpenFreeMap, which sees the map area your browser asks for, like any map site. Places near me reads your position once, when you tap Use my location, and sends only a point rounded to about 1 km (see Location).
  • A vehicle check, in your browser. During an outdoor walk, run or hike, the page checks your GPS speed (a browser has no step count) and pauses a stretch that looks like a car, bus or train. This runs in the page itself; we receive only the session's mark that a vehicle was detected and the seconds left out, never a position.
  • A planned session, adapted in your browser. When you start today's planned session (build 62), the page adapts it as you go, from your heart rate (with a strap) or your GPS pace: a rest ends when your heart has come down, a rep can stop early or get a little longer. It all runs in the page; with the workout we receive the session's segments and targets, what was adjusted, and your Easy / Moderate / Hard answers if the page asked, never a position. Choose Fixed timing in your settings to keep every part at its planned length (see Adaptive coaching under Health data).
  • Bluetooth heart rate, read in your browser. If you connect a heart-rate strap or arm band (Chrome or Edge, through Web Bluetooth), your browser reads the heart rate from it. We receive the heart rate every 10 seconds with the workout, its average, maximum and time in each zone, like a workout from the app; never the beat-to-beat intervals, the sensor's name or its Bluetooth address. Your browser remembers which sensor you picked, so the next workout can reconnect; forget it from the sensor screen or your browser's site settings.
  • Kept in your browser. The workout under way is saved in your browser (IndexedDB) every few seconds, so a reload or a closed tab can resume it; finished workouts wait there until they are uploaded, then they are deleted. Your goals, your Beat the clock attempts and personal bests (distance, target, plan, your time: at most 60), daily rhythm check-ins, voice settings and sign-in (for at most 24 hours) are kept in your browser's storage too; a Beat the clock session uploads only its goal and how it went (distance, target, plan, made, time), never a position. Signing out or clearing the site's data removes them. Your workout voice choice (voice on, essential only or off) and your heart-rate and speed zones per sport and the effort-by-feel switch (numbers only) are also kept with your account, so your other devices use the same.
  • Microphone and voice, only when you ask. Talking to the coach by voice (Talk to your coach, on every screen of vvake.com/app) only starts when you tap. With VVake Coach Plus or Premium it can be a live, hands-free conversation: your browser asks for the microphone, which stays on while the conversation is open and the page shows it; the page sends the sound only while it hears you speak (with the moment just before, so your first word isn't cut), through our server to our speech-to-text provider (ElevenLabs), as described under Microphone and speech, and nothing is recorded. The coach keeps listening while it talks, so you can talk over it; your browser's echo cancellation keeps the coach's own voice out of what is sent. Otherwise (tap to talk), your browser's speech recognition is used, which may send the sound to your browser's maker (for example Google for Chrome) to turn it into text; only the text reaches VVake. If the coach suggests places near you, your browser asks for your location first; it is used once for that search, rounded to about 1 km, and not kept. Workout cues play VVake's recorded coach voice: the same recordings for everyone, with no personal data, kept in your browser's Cache Storage so they play at once. Cues with your own numbers (pace, distance, time) and, with VVake Coach Plus, the coach's replies are spoken by the coach's voice (ElevenLabs) through our servers, as on the phone; your browser keeps that audio in memory only, never on disk. If the audio can't play, your browser's own voice reads the line, on your device.
  • The camera, only during a camera workout. When you open a camera workout, your browser asks whether vvake.com may use your camera (on a computer, its webcam). Your pose is found in the browser tab itself, by Google's MediaPipe Pose Landmarker served from vvake.com: each frame is analysed in memory and dropped. The video is never recorded, stored or sent, to us or anyone else, and nothing is saved to your files. Only the counts of the session are uploaded (moves, sets, reps, the load you typed, hold times, range-of-motion and tempo summaries, form cue ids and the results of the quick checks such as "raise your left arm now"), like a camera workout on the phone. The camera turns off when you leave the camera workout; you can block it at any time in your browser's site settings.
  • Any camera, including your iPhone on a Mac. You pick the camera from the ones your browser lists (a built-in webcam, a USB camera, or on a Mac your iPhone through Apple's Continuity Camera). Its name is shown to you and remembered in this browser only, to open the same camera next time; it is never sent to us. We only count that a camera other than the built-in one was used, as a total for the team.
  • The big screen (a screen link). When you show a camera workout on a big screen, we create a link that lives at most 2 hours and ends when you end it. Through our server (a Cloudflare Durable Object), the device that counts sends the screen what is on it: the move, reps, sets, timer, tips, the video and its time, and your heart rate only when you allow it. A screen that joins with the 6-digit code alone never sees your heart rate unless you turned that on; a screen signed in to your account joins without a code. No image or sound goes through the link. We keep only the last state while the link lives, and that a link was opened and a screen joined; everything is deleted when the link ends.
  • My videos and imported playlists. Every video you follow is kept in My videos on your account, so you can replay it: its link, title, creator and official thumbnail address, your move list as you edited it, your favourite star, how many times you did it, your best reps and when you last did it (at most 500 videos). If you import a YouTube playlist, it must be public or unlisted: our server reads its list of videos (up to 50 at a time) from YouTube's Data API, and we keep the playlist's id and title so you can re-sync it. Unless you link your YouTube account (see YouTube account), we never sign in to it, so we can't see private playlists or Liked videos; we never see your watch history. Delete any video, or all of them, any time; they are deleted with your account. The coach may suggest one of your favourites. The VVake team's dashboard sees only counts (how many replays, imports, favourites), never which videos.
  • Videos you follow (YouTube, Vimeo). When you paste a link, our server asks YouTube's or Vimeo's public page information (oEmbed: title, channel, thumbnail; for YouTube, when our YouTube Data API key is set up, the description, chapters and length) to propose the moves. When our rules can't read a list of moves from that text and your own words, the text (never the video) goes to our AI provider (Anthropic) to read the routine, like your own workouts (see AI features). We never download the video or its sound, and never read its captions. The routine is kept in your private routines library (and a shared cache of what a public video's page says, so the next person doesn't trigger another read); share it to the library only if you want, and the video's creator is credited. The video plays in the official YouTube player in its privacy-enhanced mode (youtube-nocookie.com) or Vimeo's player, inside the page: they load from YouTube or Vimeo, under their own terms and privacy policies, and may set cookies once you play. VVake still counts only your pose; the video's sound is never listened to.
  • Points, never prizes. A workout recorded in a browser is marked as a web workout: it counts for your journal, your streak and (with a heart-rate sensor, or the small capped points of a camera workout) your points, but never for prizes or City Clash scores, because a browser can't prove where the data comes from.

Microphone and speech

The microphone is used only while you speak to VVake: a voice command after you press the mic, or a question or conversation with the coach while it's open (one tap starts it; it stops listening when you say bye, tap End, pause or end the session, or your minutes run out).

On the phone, your speech is turned into text by the phone's own speech recognition (Apple's on iPhone, Google's on Android), on the device when it supports it (otherwise on Apple's or Google's servers, under their privacy policies). Only the text is sent to us, never the audio.

On the Apple Watch and Wear OS watches, which can't do that themselves, the recording of what you say to the coach is sent to our API and to ElevenLabs (speech-to-text) to be turned into text. We don't store the recording: only the text goes on to the coach.

Live conversations with your coach. During a live conversation (Talk to your coach, which VVake Coach Plus and Premium can open hands-free from any screen, a talk you start during a workout, a coach call you answer, or the optional first call when you set up VVake) the microphone stays on until the call ends, and the app shows it; it keeps listening while the coach talks, so you can talk over it, and the device's echo cancellation keeps the coach's own voice out. On phones that can, your words are recognised on your device and only the text is sent. On watches, on the web and on phones that can't, the sound goes through our server to our speech-to-text provider (ElevenLabs) as you speak, to turn it into text (on the web, only while the page hears your voice, not the silences in between); neither we nor the app keep any recording, and we ask the provider not to keep it either. The text of the conversation goes to our AI provider (Anthropic) to write the coach's answers, like coach chats, and to ElevenLabs to say them in the coach's voice. We keep the text of a live conversation with its call record for 90 days, then delete it; we never keep audio. The first call keeps no text: only the answers you confirm are saved, like the questions on screen. You can stop any call at any time, or answer on screen instead.

Coach replies are spoken with a synthetic voice made by ElevenLabs, in the coach voice you choose (a woman's or a man's), or by your device's own voice if you choose it. The coach is an AI, not a person, and not a doctor.

Camera workouts (phone)

On the iPhone and Android phone apps you can do a camera workout: you prop the phone 2 to 3 m away and VVake counts your reps and holds and gives form cues by voice.

  • The camera is used only while a camera workout is open. The app asks for camera permission the first time; the camera turns off when you leave the workout.
  • Your pose is computed on the phone. Apple Vision (iPhone) or Google's MediaPipe Pose Landmarker running inside the app (Android) finds the position of your joints, on the device. No image goes to us or to anyone else.
  • Video and images are never recorded, stored or sent. Nothing is saved to your photos or files, and no frame leaves the phone.
  • Only the counts are saved. With the session we keep the moves, sets and reps, the load you typed, hold times, range-of-motion and tempo summaries, the ids of the form cues you got and the results of the quick checks ("raise your left arm now") that show someone was really there. They are saved with the session and synced to your account like any session, and you can delete that session at any time.
  • You decide. You can turn camera permission off at any time in your phone's settings (iPhone: Settings > Privacy & Security > Camera; Android: Settings > Apps > VVake > Permissions); the rest of VVake keeps working.

Taught moves, custom trainings and coach profiles

You can teach VVake a move of your own, build trainings, share them, join other people's trainings and challenges, and, if you choose, show a public coach profile. This is what that involves.

  • A taught move is numbers only. When you teach a move, the template is built on your device from the joint positions the camera workout already reads: joint-angle curves, the timing of a rep, a tolerance and a few stick-figure keyframes (13 joints, no face) for its demo. Never a video or a picture, and a face can't be rebuilt from it. That template is what we store, and what a share link carries.
  • Trainings you share are visible to others. A training's name, description, level, tags, sets and the templates of the moves it uses are visible to the people you choose: everyone in Discover (public), only people with the link (link only, the default) or only you (private). Its page shows your name, and your handle if you have a public profile.
  • Coach profiles are opt-in. Off by default. If you switch it on, your name, handle, short bio, public trainings, followers and joins counts and coach score are public. Your city is shown only if you choose to show it.
  • Others see totals only. A training's page shows totals (how many people trained it, total reps, total heart points, the coach score), never who did what or anyone's heart data. On a challenge's leaderboard, only the members who chose to show their name appear by name.
  • What we keep. Your taught moves and trainings; the runs of a training (its score, how much of it was done, the time in the target zones and whether heart data was there, linked to the session); who joined or follows what; your reports and blocks; and creator points and shares for creators. Reports are read by our moderators.
  • Deleting. You can delete a taught move or a training at any time: it disappears everywhere it was shared. Copies already inside trainings that other people joined keep working for them, but are no longer shared. Deleting your account deletes all of it.

Nutrition (optional)

Nutrition is off unless you turn it on (Your VVake, or Settings › Nutrition). When it is off, nothing below happens: no meal logs, no meal ideas, no food talk from the coach. Calories and nutrients are estimates, not measurements, and nothing in Nutrition is medical or dietary advice: for a health condition, pregnancy or a difficult relationship with food, talk to a doctor or a registered dietitian.

  • Meal photos are analysed, then deleted. When you log a meal with a photo, your phone or browser first shrinks it (at most 1024 pixels, a few hundred kilobytes) and sends it to our API, which passes it to our AI provider, Anthropic, to recognise the foods and estimate portions. We do not store the photo on our servers, in our database, our file storage or our logs. Anthropic processes it as our service provider and, under its commercial terms, does not use it to train its models (see AI features). On vvake.com/app, photos are never kept anywhere. In the phone app, Keep photos (off by default) keeps a copy on your phone only, deleted with the meal or the app.
  • What we keep. Your meal log (time, meal, the foods with their grams and estimated energy, protein, carbohydrates and fat, how it was logged, an optional note), your nutrition profile (goal, diet style, allergies, intolerances, foods you dislike, cooking time, budget, meals a day, servings at home, the last number of servings and the last portion you chose, your Variety choice (Stable, Balanced or Adventurous), your price zone and cuisines, your weekly food budget and price corrections, the foods you already have, whether you are 18 or older, your Hide numbers and calm-mode choices), your meal plans and grocery lists, and a small portion-correction model: when you change a portion the AI guessed, we keep a correction factor per food family (pasta, rice, meat…) so the next guess fits you better. All of it stays with your account and is deleted with it. Fresh start keeps your meal log (like your Health data) and resets plans and ideas.
  • Your area, never your position. For seasonal produce and links to this week's grocery flyers, the app may use your country and region (like FR, or CA and QC). It is worked out on your device from a location you already allowed, then the coordinates are dropped: we only receive and keep the country and region code. You can clear it in Settings › Nutrition.
  • Allergies and intolerances. What you list is used only to keep those foods out of every idea, plan, grocery list and coach reply, and to show a calm note when a meal you log contains one. It is never shared, never used for ads and never shown to anyone else. Our checks are careful but can miss an ingredient: always read labels.
  • Calm mode and Hide numbers. Hide numbers shows how your day is going in words instead of calories, in one tap from every Nutrition screen. If you'd rather not focus on numbers, or if something you say suggests food is a hard topic, VVake keeps numbers hidden, never suggests eating less, and points to a professional once. We never suggest compensating food with exercise.
  • Apple Health and Health Connect (phone). Writing your meals' energy, nutrients and water to Apple Health or Health Connect is a separate switch, off by default.
  • Grocery slot in your calendar. On the web, Add to my calendar downloads an .ics file you open yourself; nothing is sent to a calendar service. If you connected Google Calendar, the trip goes instead to your VVake calendar there (see Calendar), only when you leave “In my Google Calendar” on. The time we propose is worked out from the times you chose before.
  • Cook with my stuff: fridge photos are analysed, then deleted. With VVake Coach Premium you can send up to 5 photos of your fridge, freezer or cupboards. Like meal photos, they are shrunk on your device, sent once to our AI provider to list the foods, and never stored on our servers, in our database, our file storage or our logs; on the web they are never kept anywhere. We keep only the list you confirm for that cooking session and count the use against your weekly allowance.
  • Meals and prep in your calendar. Off by default. On the phone, when you turn it on, VVake writes your planned meals and prep (titles like “VVake · Dinner”, the meal's name in the notes) to your device calendar and removes them with one tap; nothing goes to a calendar service through us. On the web, the calendar file is downloaded and opened by you. If you connected Google Calendar, we write them instead to your VVake calendar at Google, on every device (see Calendar), and the phone stops writing its own copies and removes the ones it wrote, so nothing is doubled. The usual meal times come from the times of meals you logged in the last 28 days, worked out for your account only.
  • A grocery list you share. Share a live list creates a link with a random code that we store only as a fingerprint (a hash). Anyone with the link sees the list's items, the planned shopping date and your first name, and can tick and add items, without an account. Nothing else from your account is shown: no meals, no targets, no allergies. The link stops working at the end you chose (14 days by default) or as soon as you tap Stop sharing; items added through it are kept on your list until you remove them. The page for the link is never indexed by search engines and keeps the code out of our website's logs.
  • Meal picks. When you pick a meal idea for a day, we keep that idea only (its name, ingredients, steps, minutes and allergens) and how many people it is for, until 14 days after that day. Deleting your account deletes them; Fresh start clears them with your meal plans.
  • Mark eaten. When you mark a planned or picked meal as eaten, the logged meal remembers which meal it came from, so Today ticks it and a second tap doesn't log it twice. The portion you choose (½, 1, 1½, 2 or another amount) scales the logged foods and is remembered for next time.
  • Meal ratings. When you rate a meal (Not for me, Fine or Loved it, optional chips like “Too long to prep” and a short note), we keep the meal's name, your rating, the chips, the note and the day. They are used only for your own suggestions: more of what you loved, quicker or cheaper meals if you asked, and never again a meal you said no to. The coach sees only a short list of the names of meals you liked or don't want. Ratings are never shared and never used for ads. You can delete a rating; Fresh start clears them with your meal plans, and deleting your account deletes them.
  • Shared week plans. Most week plans now start from VVake's own library of week plans, written once and shared by everyone. The library holds recipes only, never anyone's personal data. Your plan is then fitted to you on our server (allergies, diet, dislikes, ratings, portions, budget, Variety) without any AI call. Which library weeks and meals you had is read from your own saved plans, to keep the variety you chose; nobody else sees it.
  • Prices, your price zone and cuisines. Meal costs are estimates from a price table we write once from public average supermarket prices (no store tracking, no affiliate links), for a price zone: Canada, the US, France, Italy, Mexico or India (other places use the closest). The zone and the cuisines you pick stay coarse, a country-level choice, never a position. When you correct a price, the correction stays with your account and is used only for your own estimates: it is never shared with other people. Your weekly food budget, if you set one, is kept in your nutrition profile. All of it is deleted with your account.

Heart-rate strap (phone)

On the iPhone and Android phone apps you can pair a Bluetooth heart-rate strap or arm band (any sensor with the standard Heart Rate service), for phone workouts and camera workouts.

  • Bluetooth is used only to find and read your strap. The app asks for Bluetooth permission the first time you pair a sensor. It looks only for heart-rate sensors and never uses Bluetooth to work out where you are.
  • What the app reads. Your heart rate, the beat-to-beat intervals when the strap sends them, whether the strap touches your skin, and its battery level. The beat-to-beat intervals and the battery stay on the phone.
  • What we receive. The heart rate every 10 seconds with the workout, its average, maximum and time in each zone, like a workout from the watch. Never the sensor's Bluetooth address.
  • Remembered on the phone, forget it any time. The phone remembers the strap you paired (its id and name) so it reconnects at the next workout. Forget it in Settings > Heart-rate strap, or turn Bluetooth permission off in your phone's settings; the rest of VVake keeps working.

Phone and watch of different brands

To start, pause or end a watch workout from your phone when the two can't talk directly (an Android phone with an Apple Watch, an iPhone with a Wear OS watch), or when the direct link doesn't answer, your phone and watch pass the command through our server, signed in to the same VVake account. We keep each command at most 2 minutes (the workout's sport, indoor or outdoor, the plan's zone, and the device's answer), and the watch's live workout state (sport, start time, clock, heart rate, distance) at most 15 minutes, then delete them. Only your own devices can read them.

Meals on such a watch: it reads today's meals from our server and sends what you do there (Eaten, Undo, a meal you log by voice) straight to our server with its own sign-in, the same meal log your phone would have sent; nothing goes through the relay. Without a connection the watch keeps it and sends it later, once.

  • Nothing is kept for long. Commands go after 2 minutes, workout states after 15 minutes; your own devices only. There is no push: the watch checks only while VVake is open on it, or during a workout away from your phone.

Calendar

  • Your iPhone's calendar (optional). If you allow access, VVake reads only when you are busy (start and end times), never titles, places, notes or attendees, to find a free slot for your session. Those busy times are sent to our server to work out today's suggestion and are not stored. VVake writes sessions only to its own "VVake" calendar.
  • Google Calendar (optional). If you connect Google Calendar, we ask Google for your free/busy times, for permission to manage a calendar that VVake creates ("VVake"), and for permission to manage events on calendars you own, so your planned training can be blocked in your main calendar. We store your Google e-mail and the access tokens, encrypted. From your main calendar we read only when events start and end, whether they mark you busy and whether you declined them, never titles, places, notes or other people; beyond that we read only the events VVake created. What we write: in your main calendar, private busy events such as "VVake · Run 30 min" for your sessions in the coming week (others see only "busy"); in the VVake calendar, your planned meals, prep and batch cooking (when Meals or Prep is on in Nutrition), your grocery trip (when you put it in your calendar), the meetups and train-together calls you are going to (time, sport, pace line and the meeting point's name, never a custom pin's coordinates; a switch turns them off) and sessions you add yourself. Every event is private, with no reminders; meals, prep and the grocery trip never mark you busy, meetups do. We keep them up to date when your plans change (and once a day for the coming week of meals and month of meetups), and move or remove only the events VVake created. You can turn training blocks, meals, prep or meetups off in the app or on vvake.com; "Remove" in the nutrition calendar settings deletes every meal and prep event we wrote, past ones too. If you disconnect, we first remove VVake's coming events from Google (best effort), then revoke the access at Google and delete the tokens (Google gives VVake one permission, so a linked YouTube is unlinked too).

VVake's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

YouTube account (optional)

Linking your YouTube account is optional and off until you tap Link YouTube (in My videos or Settings › Connections). It is separate from Google Calendar: its own Google consent, its own stored access, unlinked on its own. Linking is turned on step by step (testers first).

  • What we ask Google for. Read-only access to your YouTube account (the youtube.readonly permission) and nothing else. VVake can't post, comment, like, subscribe, upload, change or delete anything on YouTube.
  • What we read. Your channel's name (to show which account is linked); the list of your playlists, private ones included, with their titles, privacy setting and number of videos; your Liked videos list, when YouTube makes it available; and, only for the lists you choose to import, each video's id, title, channel name and official thumbnail address (up to 10 lists and 200 videos per list at a time). We never read your watch history, subscriptions, comments, messages, or any video's picture or sound.
  • What we keep, and for how long. The access Google gives us (a refresh token), encrypted, kept apart from Google Calendar's; your lists' names and counts, cached for up to a day so the picker opens fast; and the videos you imported, in My videos, marked as coming from your YouTube, with the list they came from. Lists are read again when you tap Re-sync, and at most once a day when you open My videos (never in the background otherwise). A daily count of how many YouTube requests VVake made in total (no content) keeps us within YouTube's limits. Everything is deleted when you unlink or delete your account.
  • Never shared, never in the library. Your YouTube data is used only to show you your own lists and fill your own My videos. It is never sold, never used for advertising, never used to train AI models, never shown to other people and never put in the shared library. When you open one of these videos to follow it, its moves are read as for any video you follow (see Videos you follow, in VVake on the web). If you want to share a training made from one of them, VVake first checks that the video is public; a private video can't be shared. The VVake team's dashboard sees only counts (how many links, imports and unlinks), never which lists or videos.
  • Unlink any time. Unlink YouTube in My videos or Settings › Connections: we delete the stored token, the cached lists, the imported YouTube lists and their videos you never did, and Google revokes VVake's access right away. Google gives VVake one permission for both, so if Google Calendar is connected it is disconnected too: the app says so and you can reconnect Calendar right after. YouTube titles and channel names we haven't refreshed from YouTube for 30 days are deleted. Videos you already did stay in My videos with your move lists; delete them like any other. You can also remove VVake's access from your Google Account (link below); VVake then stops reading and asks you to link again.
  • Google's review. While Google reviews VVake's YouTube access, its consent page may show a warning that the app isn't verified yet. It is VVake asking for the read-only access described here, nothing more.

VVake uses YouTube API Services. By linking YouTube, you agree to be bound by the YouTube Terms of Service. Google's handling of your information is described in the Google Privacy Policy.

VVake's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Music

Apple Music and Spotify are controlled from your iPhone, and from your Apple Watch through your iPhone. VVake asks Apple Music (MusicKit) for permission to play your music and show what is playing. If you connect Spotify, sign-in happens on your iPhone, its tokens stay in your iPhone's Keychain, and your iPhone talks to Spotify directly: it reads what is playing, your Spotify devices, your playlists and Liked Songs, and sends play, pause, skip and volume commands and the search words you type or say on your watch. Unless you turn on Spotify on my watch (below), nothing about your music reaches our servers, and nothing about your workouts or health is sent to Apple Music or Spotify.

Spotify on your watch (optional, VVake Coach Plus). If you turn on "Spotify on my watch", your phone signs in to Spotify a second time for your watches and gives that sign-in to VVake. We keep the Spotify tokens encrypted and use them only to give your own signed-in watches a short-lived key, so they can control Spotify (play, pause, skip, volume, devices, your playlists, search) without your phone. We don't store what you listen to. Turn it off in Connections (or delete your account) and we delete the tokens. You can also turn it on from a watch (You › Spotify on this watch): we keep a pending request for 15 minutes and send your phones a notification to confirm; with no phone near, the watch shows an address and an 8-character code you can enter on any phone or computer to sign in to Spotify there (we keep only a hash of the code, and delete the request within about a week). You can also connect it from vvake.com/account: Spotify sends you back to our API with a single-use link valid 10 minutes, and the tokens are kept encrypted as above. The Spotify route you pick for your watches (Auto, Through my phone, Watch on its own) is kept with your account so your phone, your watches and vvake.com show the same; the newest choice wins. New Spotify sign-ins also allow reading your recently played songs, so when nothing plays your phone and watch show the last song (cover, title, artist) and can play it in one tap: they read it straight from Spotify, and it is not stored on our servers. "Check Spotify on this watch" sends us, only when you tap Send, technical results (device types, status codes, step timings, the route the request took, the audio output type such as speaker or headphones and its recent changes, the phone link state (reachable, seconds since last seen), network type, app and OS version), never names, songs or your account; we keep them 90 days.

Detailed music log (optional, off by default). If music doesn't play where you asked, you can turn on Detailed music log in the music settings of your phone or watch. While it is on, the app keeps in that device, at most the last 600 steps of what it does with Spotify: your taps on the music controls, the route it took (straight to Spotify or through your phone), each Spotify request with its status code and time, the watch-to-phone link state, device types in your Spotify list with their ids scrambled (a short code that can't be turned back into the id), whether something plays, the audio output type, the network type, and app and OS version. It never records your Spotify account, e-mail, sign-in tokens, device names, or any song, artist, album or playlist. Nothing leaves the device until you tap Send music log: then we receive that log, with a 6-character code shown on screen so we can find it, and no account id. If your phone and watch are connected, the other one sends its own log with the same code. We keep it 14 days. The switch turns itself off after 7 days, and the log stops when you turn it off.

AI features

  • The coach (Anthropic Claude). To write each reply we send Anthropic: your message and the last few turns (up to 6), the live numbers of your session (sport, time, heart rate and zone, distance, pace, cadence, gaps in a race or challenge, your city's clash score), today's plan and your session feedback, and a summary of your profile (display name, level, zones, targets and coach notes, your aim, the pain, low-impact and easy-only choices, streak, points and recent plan decisions). It also gets a short summary of your last 14 days (sessions per sport, minutes, time in zones, distance, average and maximum heart rate, how they felt), this week's planned and done sessions, last night's sleep and your resting-heart trend if you share them, your training settings (resting and maximum heart rate, zones, low impact, easy only, daily rhythm, daily move, focus lock), the settings changes you agreed to and what the coach remembers. Never the name of a health condition. We do not send your e-mail, account ID, location or contacts. Anthropic processes this as our service provider and, under its commercial terms, does not use it to train its models. Anthropic deletes it within 30 days, unless it must keep it longer to enforce its usage policy (up to 2 years for flagged content) or to comply with the law.
  • Meal photos and meal ideas (Anthropic Claude). Only if you turn Nutrition on. For a meal photo, Anthropic receives the shrunk photo, the meal (breakfast, lunch…), the hour and your language; for a meal you type or say, the text. For meal ideas and weekly plans, it receives your nutrition goal, diet style, allergies, intolerances and dislikes (to leave them out), cooking time, budget, the season and how hard your training days are. Never your name, e-mail, location or a health condition. Same terms as the coach: not used to train models; the photo is not stored by us.
  • Plan and settings changes. The coach can only propose a change to your plan or your settings. Nothing changes until you approve it, with a tap or a clear spoken yes, and a settings change can be undone for 30 days.
  • Speech-to-text on the watches (ElevenLabs). When you talk to the coach on an Apple Watch or a Wear OS watch, ElevenLabs receives the recording of what you said and returns the text. We don't keep the recording.
  • Live conversations (Anthropic, ElevenLabs). In a live conversation with the coach, Anthropic receives the text of each turn, like a coach chat, and ElevenLabs receives the sound of what you say when your device can't recognise it itself (watches, the web, some phones), then the text of the coach's answers to say them. We ask ElevenLabs not to keep the sound or the text. See Microphone and speech.
  • The coach's voice (ElevenLabs). ElevenLabs receives the text of the line to speak and returns the audio. We cache the audio in our storage; an identical line is shared between users.
  • Your VVaker image (xAI Grok Imagine). xAI receives a text description built from the VVaker traits you designed (style, colours, outfit). No name, photo or health data. The background is removed on your iPhone with Apple's Vision framework.

When an AI provider is not available, the coach falls back to scripted lines on our server.

Desk companion and Claude Code

The optional VVake desk companion counts continuous desk time from macOS's keyboard and mouse idle time, to remind you to move. It never reads keystrokes, code, screen contents or AI prompts. Today it keeps its state on your Mac and sends nothing to us.

The VVake plugin for Claude Code (optional, open source at github.com/4gjnbzb4zf-sudo/vvake-claude-plugin) holds new Claude prompts after a long stretch at the desk until you move. It measures desk time from the times of your prompts, on your computer.

  • Never sent. Your prompts, code, file names, file contents and transcripts. The prompt text is read only on your computer, to spot the plugin's commands and the "urgent:" prefix, and is not stored.
  • Sent to the VVake API. When you link it: your computer's name (shown on your phone so you can approve it) and a pairing code. Then, at most every 5 minutes and while a lock is on: your continuous desk minutes, when the lock started and from when to count your movement. Our server answers with your rule, your urgent / busy mode and the minutes you have moved since (from your sessions and Move Quests). We keep the computer's name, its last desk report and your rule.
  • On your computer. Its state, your rule and its access token stay in a folder in your home directory. On macOS, while a lock is on, it reads keyboard and mouse idle time (never keystrokes) to tell when you are away.
  • Unlink. Type /vvake:unlink, or unlink the computer in the app (You > Connections > Claude Code). The link page vvake.com/claude/<code> only shows the code and opens the app; it sends nothing to us.

$VVAKE prizes and your wallet

$VVAKE prizes are optional, and today they run on Robinhood Chain Testnet, where the tokens have no value. You never need a wallet to use VVake. In the apps you only see your points and read-only prize information; linking a wallet and claiming happen on vvake.com/rewards, from your own wallet. Prizes are for people 18 or older who entered with VVake Coach Plus or the free entry (same prize), linked a wallet before the week, moved enough with heart-rate data that week (at least 3 sessions of 10+ minutes or 90 active minutes, with movement) and answered the week's skill question; to check this we use your subscription status or free entry, when your account and wallet link were made, your counted sessions and active minutes, your skill answers, and the 18+ confirmation you give when linking. Legal basis: your consent, given by linking a wallet.

  • Signing in on vvake.com/rewards. With a code sent to the e-mail of your VVake account, or a link code shown in the app. This browser is then added to your devices as "Web (vvake.com)". The sign-in stays in that tab's session storage until you close the tab or sign out.
  • Linking a wallet. You connect a wallet you own in your browser and sign a free one-time message; we read the address from the signature. We never ask for, see or accept your recovery phrase or private keys, and we never hold your tokens or funds. One wallet per account. You can unlink it on vvake.com/rewards at any time: future weeks then stop counting.
  • Weekly lists. Every Monday we settle the past week: the VVAKE amount for each eligible account (VVake Coach Plus or free entry, linked wallet, enough effort recorded with the app on a real iPhone or Apple Watch, skill question, a seat in the pilot), checked by a person before anything is posted. The week's list (addresses and amounts, with their proofs) is published so anyone can check it, and its fingerprint (a Merkle root) is written to the blockchain. Names, e-mails and points are not in the list, but an amount says roughly how active that address was that week.
  • Claims. You claim by sending a transaction from your wallet. Like every blockchain transaction, it is public and permanent: the address, the amount and the time.
  • Your browser and the chain. The prize pool and contract figures on vvake.com/rewards are read by your browser directly from Robinhood Chain Testnet's public server (RPC), which sees your IP address like any server; explorer links open the public block explorer. Your wallet extension or app has its own privacy policy.

What can't be erased: nobody, us included, can edit a blockchain. Once a week's list is published and its root is on chain, or once you have claimed, your address and amounts stay public on the chain and in any copy someone made. If you delete your account or unlink your wallet, we delete the link between your account and the wallet and stop counting future weeks; our copy of past weekly lists keeps the address, points and amount without your account, so those weeks stay claimable by that address. If you don't want an address tied to your activity, don't link it.

Usage counts (Help improve VVake)

To learn which features help people and which nobody uses, the apps, the watches and the web app count how often each feature is opened and finished. This is our own counting, on our own servers: no analytics company, no advertising identifier, no tracking across apps or websites, nothing sold.

  • What is counted. For each day and feature: how many times it was opened and finished, and in which hours of your local day. Features come from a fixed list (for example “GPS workout”, “Log a meal”, “Coach chat”). Never what you do in them: no screen content, no messages, no places, no health values, no workout data.
  • Why. To decide what to improve, simplify or retire, and to see where new people get stuck while setting up.
  • How long. With your account for 120 days, then only daily totals per feature, with no account attached. Deleting your account deletes its counts at once.
  • Your choice. “Help improve VVake” is on by default and can be turned off in the phone apps' settings (Privacy) and in the web app (You › Privacy & account). Off stops the counting on every device linked to your account and deletes the counts we hold for your account at once.
  • Who sees it. Only the VVake team, on a private admin page that shows totals and hides any group of fewer than 5 people. Every look at that page is logged. No third party receives these counts.

Who else sees your data

We do not sell or rent personal information, we do not share it for advertising, and the apps contain no advertising, analytics or tracking SDKs. We share data only with service providers that process it on our behalf, and only what each one needs:

  • Cloudflare (United States; our data is stored in the EU). Hosts the VVake API, the database and file storage, the waitlist, the bot check on the website's signup form (Turnstile), and, only when it is switched on, the real-time audio of “train together over a call” (forwarded, never recorded).
  • Anthropic (United States). Writes the coach's replies and, if you use Nutrition, reads meal and fridge photos and writes meal ideas and recipes (see AI features).
  • ElevenLabs (Eleven Labs Inc., United States; data stored in the United States). Turns coach lines into speech, and what you say to the coach on a watch into text.
  • xAI (United States). Renders custom VVaker images from their traits.
  • Challenge links you share. A challenge link (vvake.com/c/…) shows anyone who has it the challenge itself: its title, sport, rules and end, your display name and VVaker for a friend challenge, the cities and scores for a city clash. You can stop a link from the app; it also ends with the challenge.
  • Share on Facebook. The button only opens Facebook's own share page with a vvake.com link. VVake uses no Facebook SDK, no pixel and no app id, and sends Facebook nothing; what you post is between you and Facebook (Meta Platforms, under its own privacy policy). The post's text is copied to your clipboard on your device so you can paste it.
  • Resend (United States). Sends sign-in codes and waitlist e-mails. It receives your e-mail address and the message.
  • Google (United States). If you sign in with Google, connect Google Calendar or link YouTube (read only). On Android and Wear OS, Google Play Integrity tells us that a session upload or a live coach workout comes from the genuine app.
  • Apple (United States). Sign in with Apple, push notifications (including crew quest invites), Apple Health, speech recognition, Apple Music, Maps, App Attest (which tells us a session upload or a live coach workout comes from the genuine app), TestFlight and the App Store, under Apple's own privacy policy.
  • Finnhub (United States). Market quotes for My Pulse. We send only the symbols that someone follows, never who follows them.
  • Spotify. From your iPhone if you connect it, and from our API and your watches if you turn on Spotify on my watch (see Music).
  • Robinhood Chain Testnet (public blockchain). Only if you link a wallet: the weekly roots and your claims are public to everyone (see $VVAKE prizes and your wallet).
  • Coinbase (United States). Our API reads the public ETH/USD price from Coinbase. No data about you is sent.
  • GitHub (United States). Hosts this website. Like any web host, it sees visitors' IP addresses.
  • OpenStreetMap's Overpass service (FOSSGIS e.V., Germany; when it is unavailable, OpenStreetMap France, France). Answers our servers' searches for places to train: it receives the map area and the kind of place asked for, never your position, your name or your IP address.

Other VVake users see only your display name and VVaker (on challenge and crew quest invites, on challenge links you send to anyone and in the lists of people you have faced), challenge results and your record against them, your crew quest results to the crew members who join, your city's totals, and, to the people you invite to a meetup, your display name and VVaker and who else is going. Never your health data, sessions or location, except a route you choose to share for a challenge, which only the people racing it can see (see Location).

We may disclose information if the law requires it, to protect someone's safety, or as part of a merger or acquisition, in which case this policy keeps applying to your data and we will tell you first.

Where your data is stored

Our database (Cloudflare D1) and file storage (Cloudflare R2: coach voice audio, VVaker images, your encrypted route backups and the photos of custom meeting points) are in Cloudflare's EU jurisdiction. Requests pass through Cloudflare's worldwide network, and several providers above are in the United States, so your data can be processed outside Québec, Canada and the EU. We rely on our providers' contractual safeguards: Cloudflare's, Anthropic's and ElevenLabs' data processing terms, which include the EU Standard Contractual Clauses, are part of their standard terms.

Security

Everything travels over HTTPS. Sign-in tokens are short-lived, rotate on every use and are stored only as hashes; Google tokens are encrypted; your tokens on the device sit in the iOS Keychain. Each request is checked and rate-limited, and our logs carry no health data. No system is perfect: if a breach puts you at risk of serious harm, we will tell you and the authorities as the law requires.

How long we keep it

  • Your account and everything in it: until you delete it. A session you discard is removed right away, with its encrypted route backup; we keep only its random ID, so a copy still waiting on your watch or another phone can't bring it back (deleted with your account).
  • Crew quests: a crew quest you started stays for the others who joined, without your name, after you delete your account.
  • Wallet link: until you unlink it or delete your account. The message you sign to link it: 10 minutes.
  • Weekly prize lists: public and permanent once published and on chain (see $VVAKE prizes and your wallet). Our copy keeps the address, points and amount, without your account once you delete it.
  • Coach calls (VVake Coach Plus, if you turn them on): each call's script, audio and status for 90 days, then deleted; with your account at once.
  • Usage counts: 120 days with your account, then daily totals per feature without any account; at once when you turn “Help improve VVake” off or delete your account.
  • Live conversations with the coach: the call record (when, how long, minutes used) and the text of what was said for 90 days, then deleted; never any audio; the first call keeps no text; with your account at once.
  • The summary for your next coach call (this week's plan and what you did, sleep, resting heart rate, HRV): at most 2 days, then deleted; replaced each time the app sends a new one.
  • Your coach voice (woman or man): with your account, until you change it or delete your account.
  • Live coach workouts: 4 days; the weekly minutes about 2 weeks; device hashes and warning flags 60 days; the trust score with your account.
  • What the coach remembers and its settings changes: with your account, until you delete a line, use Fresh start (memory, feelings and proposals) or delete your account (everything, including the before and after record). Your corrections of Health numbers: 60 days, or until you undo them, Fresh start or deleting your account.
  • Daily health numbers for adaptive coaching (resting heart rate, heart-rate variability, VO2 max, sleep hours, a measured max heart rate): 400 days, or until Fresh start or you delete your account. What VVake learned from them and its history: until Fresh start or you delete your account. Effort answers: with their session.
  • Spotify on my watch: the encrypted tokens and your route choice until you turn it off or delete your account; requests from a watch 15 minutes (deleted within about a week); Check Spotify reports 90 days, without your account.
  • Detailed music log: 14 days after you tap Send music log, without your account; on the device, the last 600 steps while the switch is on (it turns itself off after 7 days).
  • Claude Code pairing codes: 10 minutes.
  • Guest accounts: deleted automatically after 90 days without use.
  • A route shared for a challenge: only while that challenge lasts (at most 7 days + 24 hours + 2 hours), then deleted; at once when it is closed, declined or expires with nobody racing.
  • Sign-in and link codes: 10 minutes for e-mail codes, 2 minutes for watch link codes, 60 seconds for Google sign-in exchange codes.
  • Sign-in tokens: up to 60 days, or until you sign that device out.
  • Rate-limit counters: about 2 days.
  • Coach plan proposals: a proposal for today expires the next day; your decisions stay with your account.
  • Coach voice audio: a line only you had is deleted with your account; a word-for-word identical line other users also have stays for them.
  • Server logs: our servers don't keep request logs. If we turn them on to fix a problem, Cloudflare keeps them for 3 days, with no health data.
  • Backups: the database can be restored to a point in time for up to 7 days, after which deleted data is gone.
  • Website waitlist: until launch plus 12 months, or until you unsubscribe or ask us to delete it.

Your choices and rights

  • Delete everything. Delete your account in the app (You > Your account > Delete my account, guest accounts included) or by writing to privacy@vvake.com. This deletes your account, sessions, Move Quests, survey and health fields, devices, plan changes, challenges, crew quest memberships, My Pulse settings, VVaker images, your encrypted route backups, the coach audio only you had, your Claude Code links, your meal log, nutrition profile, meal plans and portion corrections, and your wallet link, and revokes Google access first. Data in Apple Health and on your devices stays under your control. Weekly prize lists already published and blockchain records can't be erased (see $VVAKE prizes and your wallet).
  • Sign out, discard a session. Sign out from the app at any time. To discard a past session: in You, long-press it in your journal or tap ⋯ and choose Discard this session, or tap Select to discard several. It is removed from your journal, streak, points and stats, on our servers and your phone. Unlink Claude Code in You > Connections; unlink your wallet or sign out on vvake.com/rewards. To sign out another phone, watch or browser, remove it in the app under You > Your account > Devices.
  • Access and portability. You see your sessions, profile, assessment and coach notes in the app. For a full copy in a machine-readable format (JSON), write to privacy@vvake.com. We answer within 30 days.
  • Correct. Edit your name, city, survey and health fields in the app, or write to us.
  • Withdraw consent. Turn off Health, location, microphone, calendar or notifications in iOS Settings; disconnect Google or Spotify; switch the coach voice off; unlink your wallet or Claude Code.
  • Complain. Write to us first, and you can also contact the Commission d'accès à l'information du Québec, the Office of the Privacy Commissioner of Canada, or the data protection authority where you live.

Québec and Canada (Law 25, PIPEDA): you can access and correct your information, withdraw consent, ask for it in a structured, commonly used technological format, and ask us to stop disseminating it where the law allows.

European Union and EEA: VVake is not offered there for now.

United Kingdom (UK GDPR): you have the rights of access, rectification, erasure, restriction, objection and portability. Our legal bases: performing our contract with you (running the app), your explicit consent for health data and optional features, and our legitimate interest in keeping the service secure.

California and other US states: we do not sell personal information or share it for cross-context behavioural advertising. You can ask to know, correct or delete your information, and we will not treat you differently for doing so.

Children

VVake is not for children under 13, and we do not knowingly collect their information. If you are under the age of digital consent where you live (14 in Québec), a parent or guardian must agree before you use VVake. Weight goals and meal reminders are for adults only. If you think a child has given us information, write to privacy@vvake.com and we will delete it.

Cookies and tracking

The apps do not use the advertising identifier and do not track you across other companies' apps or websites, so they never show the App Tracking Transparency prompt. They contain no third-party analytics or crash-reporting SDKs.

This website uses no tracking cookies and no third-party analytics. It remembers your language, theme and currency choice in your browser's local storage, which never leaves your browser. On vvake.com/rewards, your sign-in is kept in the tab's session storage until you close it. The signup form uses Cloudflare Turnstile to keep bots out.

The website and early-access waitlist

If you join the waitlist we keep your e-mail, your city (or the city you asked for), optionally your team and the wearable you use, your language, the referral code you used or received, and when you consented. We use them to run the city waitlist (counters, early tiers, referrals) and to send you the launch updates you agreed to. Legal basis: your consent. Every e-mail has a link to unsubscribe and delete your data. It is stored in Cloudflare's EU jurisdiction and the e-mails are sent by Resend.

When you open a challenge link without the app, the page asks the VVake API for the sender's display name and VVaker to show the invite. Challenge links show your display name and VVaker to whoever opens them, and an open challenge's board shows the display name, VVaker and result only of people who chose to appear on it (the others are counted, not named).

Subscriptions and TestFlight

VVake Coach Plus is not on sale yet: nothing is charged during the preview. When subscriptions open, Apple will handle payment and we will receive only the status of your subscription, never your payment details. In development builds only (not TestFlight or the App Store), VVake Coach Plus can be paid with testnet $VVAKE: we keep the invoice (the exact token amount and the reference price used) and, once paid, the public transaction found on chain; the receipt stays without your account after deletion so a payment can never be counted twice. VVake Coach Premium and live-coach minute packs are not on sale yet either. When they open, the App Store or Google Play handles payment; for a minute pack we keep the store's transaction id, which pack, when it was bought and when it expires (12 months), and a history of the minutes used, refunded or expired, with your account. If you delete your account the history goes; the transaction id stays without your account so the same purchase can never be counted twice.

During the beta, testers get VVake Coach Premium at no charge. We store the date your account first used a beta build (early tester) to show an "Early tester" badge and for a possible future thank-you; it is kept with your account and deleted with it.

If you test a preview through TestFlight, Apple shares with us the feedback, screenshots and crash reports you choose to send, with basic device information, under Apple's TestFlight terms.

Changes to this policy

We update this page when the apps change. Before any change that matters to you, such as a new kind of data or a new provider, we will tell you in the app. The date at the top shows the current version. This policy is available in English and French; both versions have the same value.

Contact

Questions or requests: privacy@vvake.com.