App Privacy Policy

Last updated 29 September 2026

This covers the Bright Miles phone and watch app. It explains what the app collects, why, who else sees it, and how to get all of it deleted. It is written to be read, not to be survived. The website and studio policy is separate.

⚠️ Not yet reviewed by a lawyer. Every statement here was checked against the code on 12 September 2026 and is accurate to the best of our knowledge, but it has not had a legal read.

Contents

The short version
Who we are
What the app collects
Health and fitness data
Miles, and what the AI sees
Your journal
Who else processes it
How long we keep it
Your rights, and how to use them
Children
Changes
Contact

1. The short version

No advertising, no ad network, no analytics SDK, no cross-site tracking. We have never sold personal data and we do not intend to start.

Your health data is never used for advertising, never sold, and never shared with anyone outside the people listed in section 7. Apple requires us to say that, and we would say it anyway.

What we hold is your account, the things you chose to log or post, and the conversations you had with Miles. Deleting your account deletes it, apart from the few things section 9 lists that the law makes us keep or that belong to someone else.

2. Who we are

Bright Miles is operated by Charles Hines of 3367 Moss Bridge Lane, Myrtle Beach, SC 29579. For anything in this policy, write to support@brightsidestreams.com. We are the data controller for the information described here.

3. What the app collects

Because you gave it to us

Account details — a username, an email address, and a password. Sign in with Apple or Google and we receive an identifier and the email you chose to share, with no password.
Profile — your display name, photo, birthday if you add one, your language, and your time zone. The time zone is how we know when it is 8am where you are.
What you post and send — stories, moments, photos and videos, comments, direct messages, group chats, and voice notes.
Contacts, as hashes only — if you ask us to find friends from your address book, your phone hashes the numbers before sending them. We compare hashes and never receive or store a phone number or a name from your contacts.
Support messages — what you send us, and our replies.
Flyers and saved QR codes — the flyers you make, and up to 5 QR codes you save (the link each one opens and the words under it).

Because the product produced it

Usage records — how many questions you asked Miles, how many spoken answers you used, your plan and subscription status. This is how the allowances work.
Technical logs — errors and diagnostic events, kept briefly so we can find and fix faults.
A push token, if you allow notifications, so the app can reach your phone.
QR code scans — we count how many times each of your saved codes is scanned. Just a number, never who scanned it or where they were. Daily counts are kept for 30 days. If a QR code you saved is reported and breaks our rules, we can turn it off, and keep a short note of why until you delete the code or your account.

What we deliberately do not collect

No advertising identifiers, no ad network, no analytics SDK, no cross-site tracking.
No card numbers. Subscriptions are billed by Apple or Google; we never see your card.
No contact names or numbers — only the hashes described above.
No continuous location. See section 4.

4. Health and fitness data

This is the most sensitive thing the app holds and it gets its own section.

What we read, only with your permission: workouts, steps, active energy, heart rate, resting heart rate, heart rate variability, sleep, and body weight — from Apple Health on iPhone or Health Connect on Android. You can refuse any of it, or withdraw it later in your phone's settings, and the app keeps working.
What the app records itself: runs, walks and rides you track (including the GPS route), strength sets, food you log, your weight, fasting windows, and step counts.
Location is used while you are tracking an activity, to draw your route and show local weather. It is collected during a workout, not continuously, and a route you post to a feed has both ends trimmed on your phone before it leaves — so a published run never starts at your front door.
Where it goes: it is saved to your own private account on our servers so it survives a new phone and so Miles can answer questions about your own training. Nobody else can read it. It is not a feed, it is not shared, and no part of it is used for advertising or sold. Apple's rules forbid that and so do we.

Food entries are stored as daily totals — calories and macros for a day — not as a list of everything you ate.

5. Miles, and what the AI sees

Your conversations are kept so the app can show you your own history and so Miles remembers the thread. You can clear a conversation, and deleting your account deletes all of them.
What he can look up: your own runs, lifts, food, weight, steps, fasting, sleep and heart data, your training plan, your journal if you have switched journal backup on, and anything you explicitly asked him to remember. He can only ever read your data. There is no tool that takes somebody else's name.
Where the thinking happens: your question, the recent conversation, and whatever he looked up are sent to an AI service provider, which writes the answer. The same goes for what you give Miles or the app to read or translate, like a message, a photo, a meal or a journal entry, and for the notes he writes you on his own, like your weekly letter. The provider that writes his answers does not train on them.
The notice. The app explains all of this in a notice called How Miles answers, which you can read again, or turn off, under Profile, Legal. The notes he writes on his own, like your weekly letter, only start once you have tapped Got it. Shows made in the studio, from the app or the website, are covered by the website and studio policy.
Pictures and scans. When you ask for a picture made from your photo, like a portrait, your look, or a story photo restyled, cut out or brought to life, the photo goes to an image service, and a picture you ask Miles to draw goes there as a description. A body scan sends the photo and the height, weight, age and sex you entered to a body-scan service.
Voice. Speaking to Miles on the phone is turned into text by your phone's own speech recognition, which Apple or Google provide, and it never reaches us as audio. On the watch, which has none of its own, the clip is sent to a speech-to-text service, turned into text, and not kept by us. The sound of a video you post goes to the same kind of service to write its captions, and so does what people say on a call while live captions are on; a caption in another language goes to the AI service provider to be translated. When Miles replies in his own voice rather than your phone's, the text of that answer goes to a voice service to be spoken, and so does the narration of a film of your run.
Your messages. When someone in a chat asks Miles, translates, asks for suggested replies or turns a voice note into text, the messages it needs go to an outside AI service to do it. The messaging rules you accept before your first message say the same.
Keeping the app safe. Photos and videos you post, and your profile photo, are checked automatically by an AI service for content that breaks the rules, so it can be kept off the app. This check runs on everything posted.
We do not read your conversations except where you report something to us, or where we are required to by law.

6. Your journal

Your journal is kept on your device. It is not uploaded or backed up unless you switch backup on, and we do not read it.

Some features send an entry to an AI service provider to answer it, and only when that feature is used: the reply under your latest entry on the Dreams and Moments pages, asking Miles about your journal (he can only read it with backup on), and making your year into a book, which asks you first. The provider writes the reply and does not train on it.

You can turn on journal backup if you want it to survive a lost phone. That is off unless you switch it on, and switching it on is the only way your journal is kept on our servers. If you do, it is stored privately against your account, nothing searches across it, and deleting your account deletes it.

7. Who else processes it

These are the only third parties that receive anything, and each receives only what its job needs:

An AI service provider — what you ask Miles or give him or the app to read or translate, with the context he looked up, to write his answers and the notes he sends you; the messages a chat feature needs; and the photos and videos posted to the app, to check them for content that breaks the rules. It does not train on them.
A voice service — the text of an answer, when you ask for it in his voice, the narration of a run film, and a story or bulletin you ask to hear read aloud.
A speech-to-text service — watch voice clips, the sound of videos you post, voice notes turned into text, and what is said on a call while live captions are on, for transcription only.
An image service — your photo, when you ask for a picture made from it, and the description of a picture you ask Miles to draw.
A body-scan service — the photo and the measurements you enter for a body scan.
Supabase — our database, where your account and everything above is stored.
Cloudflare — photos, videos and audio you upload, live video, and the nightly backups of our database, kept in private storage.
LiveKit — live audio and video for calls and rooms while they are happening.
Railway — the servers the app talks to.
Expo — delivery of push notifications.
Apple and Google — subscriptions, sign-in, and health data on your own device.
USDA FoodData Central — receives a food name to look up its nutrition. Nothing about you is sent.
Weather providers — receive an approximate location to return a forecast.
Amazon Web Services hosts the public terrain maps our server reads to correct the climb on a finished GPS activity. Each request names only a map square several kilometres across, never a point of your route, and never your account.
OpenTopoData receives the points of a finished route, with no name or account attached, only when those terrain maps cannot be read or the route covers too wide an area. It sends back the height of the ground at each point.
OpenStreetMap — when you ask for races near you, receives your approximate location, rounded to about a kilometre, to find your postcode. A city you type to search for races may go to it for the same reason.
RunSignup — receives that postcode, or the city you typed, to list the races near it. Neither service gets your name or account.

None of them is permitted to use your data for their own purposes, except OpenTopoData, OpenStreetMap and RunSignup: they are free public services we have no contract with, so we send them only what is described above, with no name or account.

Terrain data credits

The corrected climb is worked out from open terrain data, the Terrain Tiles dataset on the Registry of Open Data on AWS. Its sources ask to be credited, and we are glad to:

ArcticDEM terrain data DEM(s) were created from DigitalGlobe, Inc., imagery and funded under National Science Foundation awards 1043681, 1559691, and 1542736;
Canada terrain data contains information licensed under the Open Government Licence – Canada;
Europe terrain data produced using Copernicus data and information funded by the European Union - EU-DEM layers;
Global ETOPO1 terrain data U.S. National Oceanic and Atmospheric Administration;
Mexico terrain data source: INEGI, Continental relief, 2016;
United States 3DEP (formerly NED) and global GMTED2010 and SRTM terrain data courtesy of the U.S. Geological Survey.

8. How long we keep it

Your account and what you logged: until you delete it.
Conversations with Miles: until you clear them or delete your account.
Health, food, weight and training backups: the most recent picture, up to about six months of days.
Weekly report backups: your Sunday letters and the weekly reports frozen when each week ends, up to about a year of weeks, so a new phone gets them back. They are stored privately against your account, nothing searches across them, and only your own signed-in device can read them.
Technical logs: days, not months.
Backups of our database: one copy a night, in private storage, each rolling off within 30 days.

9. Your rights, and how to use them

You can ask for a copy of what we hold, correct it, delete it, or object to how it is used. Write to support@brightsidestreams.com and we will answer within 30 days.

When you delete your account, we delete it and what you put into it. That is your profile and login; your posts, moments, stories, comments and Anonymous Talk posts; your messages, and your membership of every group chat; your follows, friends and blocks; your runs and their routes, your strength log, and your food, weight, steps, fasting, sleep and heart data; your journal backup if you turned it on, and your weekly report backups; every conversation with Miles and everything he had remembered about you; your episodes, recordings, photos, videos and files; your games and scores, and your place in challenges and walks; your flyers and saved QR codes; the accounts you connected, such as YouTube, Twitch, Facebook or Instagram, and the access they gave us; and your push token, so the app stops contacting you. If any part of it fails, the app tells you rather than reporting success, and trying again finishes it.

What we keep, and why. A few things outlast an account, because the law requires them or because they belong to someone else:

Payment and tax records of what you paid us and anything we paid you, for as long as tax law requires.
Copies in our backups. Each night we keep a copy of our database, in private storage with no public address, so we can recover from a mistake or an outage. What you deleted stays in the copies made before you deleted it until they roll off, within 30 days.
A note that your username belonged to a deleted account, and which App Store or Google Play subscription was yours, so a subscription you have not cancelled can never pass to the next person who takes your username.
Your name in other people's things. Where your username is part of someone else's post or message, it stays part of it: a like, a view, a reaction, a poll vote, a mention in their story, a “seen” mark in a group chat.
What other people sent you. Photos, videos and files someone sent you in a chat belong to them, so they are not deleted with your account; the conversation itself is. Group chats carry on without you: your messages go, and everyone else’s stay.
A video of yours that someone else’s post or message still plays stays with it.
Recordings that are part of another member’s show, such as a take a teammate recorded in your studio, stay with that show.
A host’s record that you knew you were being recorded, if you were a guest on their show. It is their evidence about a recording that still exists, so it stays, marked as belonging to a deleted account, and it never applies to anyone who takes your username later.
Reports you made about another member stay, without your name, so they can still be acted on.
Your show’s web address stays reserved and empty, so nobody else can ever publish to the people who followed it.

You can also refuse or withdraw any individual permission — health, location, microphone, contacts, notifications — in your phone's settings, at any time, and the app keeps working without it.

10. Children

Bright Miles is not intended for children under 13, and we do not knowingly collect their data. If you believe a child has created an account, write to us and we will remove it.

11. Changes

If we change what we collect or who processes it, we will update this page and the date at the top. Material changes will be told to you in the app rather than left here to be discovered.

12. Contact

support@brightsidestreams.com — Charles Hines, 3367 Moss Bridge Lane, Myrtle Beach, SC 29579.