Privacy policy
Last updated 13 November 2026
Polaris (“we”) is a personal coaching service: a web console at projectpolaris.dev and an iPhone app. This page says what Polaris collects when you use them, where it is kept, and who else handles it. It describes how the service works today. Polaris is run by All Great Things Inc., a Texas corporation (allgreatthings.io), 2297 Prospect Drive, Frisco, TX 75036.
In short
- Polaris reads Apple Health on your iPhone. It never writes to Apple Health.
- Polaris never sells your data. Apple Health data is never used for advertising.
- Coach’s replies are written by OpenAI. Coach asks for your OK before it sends OpenAI anything, and you can withdraw it at any time.
- If you connect an Oura ring in the iPhone app, your Sleep page shows Oura’s data and Coach can read it through Oura’s own service. It is never used to train AI, and disconnecting deletes it at once.
- If an app you use, such as Zwift, writes your rides to Apple Health, Polaris reads them from Apple Health like any other workout.
- The keys that connect Polaris to your data stay on Polaris servers. Your iPhone holds only its own sign-in token, in the iOS Keychain.
- Crash reports from the iPhone app go to Polaris only. The app has no third-party crash or analytics tools.
- You can request a copy of your data by email (the link works for 7 days), or delete your account by typing DELETE.
What Polaris collects
- Your account
- Your email address and name from Google or Apple sign-in, or your email address and a password you choose. Passwords are stored only as a one-way hash. For the iPhone app, Polaris also stores your Apple or Google user ID and the email that sign-in service shares. Apple may share a private relay email address.
- A request for access
- If you ask for access to Polaris, on the welcome page or by emailing alpha@projectpolaris.dev: your name, email address and message, and, if you say, how you heard about Polaris and which description fits you best (a man over 40, a woman over 40 in perimenopause or menopause, or something else). The form also records that you agreed to this, which browser you used, and where your visit started: the first Polaris page you opened and when you opened it, the website that linked you there (its address only, not the page), and any campaign tags on that link. It also records your approximate location (country, region, city and a point accurate to about 11 km), which Cloudflare works out from your internet address; Polaris does not store the address itself. If you used a member’s personal link, Polaris records which member it was. That member is not told. For an email, Polaris keeps the sender’s name and address, the subject and the first part of the message, not attachments or the rest of the mail. Polaris also records what it decides, and a short recommendation from an AI assistant (see Who else handles it).
- Apple Health (iPhone app only)
- If you allow it, the app reads these from Apple Health: activity (steps, energy, exercise, stand and move time, distances, flights climbed, activity rings), workouts and running or cycling measurements, walking speed and steadiness, body measurements (weight, body fat, lean mass, BMI, height, waist), heart (heart rate, resting and walking heart rate, heart rate variability, heart rate recovery, VO2 max), breathing, blood oxygen, blood pressure, wrist temperature and breathing disturbances during sleep, sleep, mindful minutes, time in daylight, nutrition (energy, protein, carbohydrates, fat, fiber, sugar, water, alcoholic drinks), and your date of birth and sex. You choose which to allow, and Polaris reads only those. The app asks only to read. It does not ask to write to Apple Health. If an app you use, such as Zwift, writes your rides to Apple Health, Polaris reads them from Apple Health like any other workout. You can change or remove this access at any time in the iPhone’s Health settings.
- What you tell Coach
- Your messages, the photos of food you send, your answers to Coach’s questions, and the notes Coach keeps from your chats (facts and preferences). You can review or delete these notes on the web, in Settings.
- Your choice about Coach and OpenAI
- Whether you agreed to Coach sending your data to OpenAI, or withdrew, when, which version of the wording you saw, whether you did it in the iPhone app or on the web, and the email of the account you used.
- Your records
- Food, weigh-ins, tape measurements and their placement protocols, body assessments such as DEXA and skinfold tests, optional age/height/sex and activity inputs for estimates, pain check-ins, workouts, training plans, goals and targets. If you upload a body-assessment PDF or image, Polaris keeps the private original and an editable extraction draft. Analysis sends that file to OpenAI using your Coach AI consent; manual entry works without it. You review the extracted values before saving. Deleting a saved assessment also deletes its attached original. Unconfirmed drafts older than one day are removed when you next import a report. Coach records something only after you confirm it, and you can also log some of these yourself in the console. Web Body progress records, settings and report originals are included in your account data export and deletion.
- Oura (if you connect it)
- You connect an Oura ring from the iPhone app: you sign in to Oura and choose what to share. Polaris then reads, from your Oura account: sleep (scores, bed and wake times, sleep stages, heart rate, heart rate variability, breathing and body temperature), readiness and what went into it, activity (steps and calories), blood oxygen, workouts, stress and resilience, cardiovascular age, VO2 max, and your ring’s battery level. It reads the last 90 days when you connect, then checks for new data every 4 hours. Polaris keeps your Oura user ID and the keys Oura gives it, encrypted, and nothing else from your Oura profile.
- Your iPhone
- A device name, a token that identifies this iPhone to Polaris (stored only as a hash), the push-notification token Apple gives the app, when the app last connected and last synced, your notification choices and quiet hours, and crash and hang reports from Apple’s MetricKit with the app and iOS version. These reports describe app crashes and hangs, not health data.
- Problems you report
- When you use Report a problem, Polaris keeps what you write, the name of the screen you were on, the app version, your device model, your time zone and the time you sent it, the names of the last few pages you opened, and, only if you choose to include it in the iPhone app, a screenshot. Polaris uses these only to find and fix the problem: its staff read them, and the AI tools it uses to fix bugs may read your words and the screen details, never the screenshot. Screenshots are seen only by Polaris staff and are deleted 30 days after you send them. Your reports are deleted with your account.
- Using the website
- Polaris counts page views and a few button presses, each with the page path, a device class (phone, tablet or desktop) and a random session ID kept in your browser session. Your browser session also remembers the first page you opened and which website linked you there; this leaves your browser only if you send a request for access or tap Get the app on iPhone (see Tapping Get the app), or if that page was a member’s personal link (see Opening a member’s link). Signed-in visits are tied to your profile. Signed-out visits, including this page, are recorded as anonymous. Polaris records this itself. On polarishealth.ai, the public pages also load Google Tag Manager, which runs Google Analytics, and Microsoft Clarity. Google Analytics receives the page address, the site or ad that linked you there (including campaign tags in the link), which buttons you press, how far you scroll, which films you play, your browser and device type, and your approximate location from your IP address. Clarity records how the page is used (mouse movements, taps, scrolling and clicks) so Polaris can replay a visit and see where people get stuck; anything typed into a form is masked before it leaves your browser. Both set their own cookies. In the European Economic Area, the United Kingdom and Switzerland they wait for your yes; everywhere else they start on, and you can turn them off with Cookie settings at the foot of every public page. A browser that sends Global Privacy Control never gets ad cookies. None of these run on the signed-in console, on projectpolaris.dev or in the iPhone app, and Google signals and ad personalization are turned off.
- Opening a member’s link
- If the first Polaris page you open in a browser session is a member’s personal link, Polaris records that the link was opened, when, which member it belonged to, and your approximate location (country, region, city and a point accurate to about 11 km), which Cloudflare works out from your internet address. Polaris does not store the address itself or the code in the link, and records this once per browser session whether or not you ask to join. A random ID kept in your browser session lets a request for access you send, or a tap on Get the app, mark the record as requested. That member is not told.
- Tapping Get the app
- When you tap Get the app on iPhone, Polaris records the tap, then shows you the install steps. The record holds when you tapped, the page you tapped on, where your visit started (the first Polaris page you opened and when, the website that linked you there, its address only, and any campaign tags on that link), which member’s personal link you came through, if any, and your approximate location (country, region, city and a point accurate to about 11 km), which Cloudflare works out from your internet address. A random ID kept in your browser session counts two taps in one visit once. Polaris does not store your internet address, your browser, the code in a member’s link or anything that names you, and sends none of this to Apple. That member is not told.
- Joining the Android waitlist
- When you join the Android waitlist, Polaris keeps your email address, where on the site you joined and when, and nothing else: no name and no account. It sends you a short confirmation at once, then one email when Polaris is on Android, and uses the address for nothing else.
- Cookies
- A session cookie that keeps you signed in, and an invite cookie that lasts two hours while you accept an invitation. A cookie also remembers which profile an administrator is viewing. On the public pages, Google Analytics and Microsoft Clarity set their own cookies (see Using the website), and your browser remembers your cookie choice.
- Emails and notifications
- A record of the emails and push notifications Polaris sends you, so it does not send the same one twice and respects your notification choices. For each email, Resend tells Polaris whether it was delivered or bounced, and whether it was opened or a link in it was clicked (the link’s address, not what you did after). Polaris uses this to see which emails help, and keeps it as long as the record of the email.
How Polaris uses it
- To show you your data and to let Coach suggest training, food and recovery.
- To sync Apple Health, sign you in, and send the emails and notifications you receive.
- To decide on your request for access and reply to it. A person decides every request. An AI assistant reads new requests and suggests an answer, and cannot invite anyone or send email.
- To find and fix mistakes in Coach. Polaris runs an automated review of Coach conversations and its operators read conversations when they investigate a problem.
- To learn what members ask for. Each night an automated review notes what members ask Coach for, such as a device they’d like Polaris to read, and its operators can open the conversation behind a request to understand it.
- To keep the service running and secure, and to count which parts of it are used.
- To show your Oura data on your Sleep page, and to let Coach use it in your coaching, if you connect Oura. Coach reads Oura data only through Oura’s own service for AI apps (its MCP server), only to answer you, and never from Polaris’s stored copy.
- Polaris does not sell any of your data, and does not use Apple Health or Oura data for advertising.
- Polaris never uses your Oura data to train, test or improve AI models.
Where it is kept
Polaris keeps your data on servers it operates in the United States. Conversations, notes, photos, sign-in and device records, notification settings and data read from Oura are in Polaris’s database. Your health data and records are in your personal data store, which Polaris keeps separately for each member.
When the iPhone app syncs, it sends Apple Health data to Polaris. Polaris passes the daily summary, workouts and sleep to your personal data store, and keeps the rest of what you allowed (daily totals and individual readings) in its own database. Traffic to Polaris’s servers passes through Cloudflare.
Polaris makes an encrypted backup of its database every night and keeps it in Cloudflare R2. Daily backups are kept for 15 days and monthly backups for 400 days.
Who else handles it
Polaris uses these services to run. Each handles data under its own terms.
- OpenAI
- Coach’s replies are written by OpenAI language models. Before Coach answers you for the first time, it asks for your OK, and it does not run without it. To answer you, Polaris then sends OpenAI your messages to Coach and your recent conversation, food photos or body-assessment reports you attach, Apple Health summaries such as sleep, workouts, steps and weight, and the parts of your records Coach needs, such as food logs, goals and training plans. Each night, OpenAI models also read the day’s Coach conversations to keep the notes Coach keeps about you up to date, run an automated quality review of Coach conversations, and note what members ask Coach for. To prepare bug reports and test cases, OpenAI may also receive possible names with short passages from conversations or problem reports, before Polaris replaces those names. It also helps build test cases from conversations with names replaced. Polaris asks OpenAI not to store Coach’s responses for later retrieval. If you connect Oura, Coach may also send OpenAI the Oura data it reads through Oura’s own service to answer you. The help chat on the support page is written by OpenAI too: what you type there goes to OpenAI to answer you, and the chat is kept for 90 days. When you write to Polaris Support, OpenAI reads your message, with the account details our support team sees (never your Coach conversations or health numbers), to sort it and draft a reply that a person checks before anything is sent; for a member who hasn’t given Coach their OK, it doesn’t. How long OpenAI keeps what it receives, and what it may use it for, is set by OpenAI’s API terms.
- Oura
- If you connect your ring, Oura sends Polaris the data you chose to share, under Oura’s own terms and privacy policy. Polaris sends Oura only its requests for your data, and a request to revoke Polaris’s access when you disconnect.
- Resend
- Sends Polaris’s emails, including the replies to the access-request form on the welcome page. It receives the email address and what the email says, and reports back whether each email was delivered, opened or clicked.
- Apple
- Sign in with Apple in the iPhone app, and the Apple Push Notification service, which receives the app’s push token and the text of each notification.
- Sign in with Google on the website and in the iPhone app, and Google Tag Manager and Google Analytics on the public web pages (see Using the website). Google’s sign-in service handles your Google account details and can also handle device information, approximate location and information about how you use sign-in. On Google’s own sign-in pages, you may be asked for a phone number for account security. Google Analytics is separate from the iPhone sign-in service. Polaris does not send either of these services Apple Health records or Coach conversations.
- Microsoft Clarity
- Records how the public web pages are used (see Using the website), with form entries masked. It is not used on the signed-in console or in the iPhone app.
- Google Cloud
- Hosts Polaris’s servers, its database and the keys it uses to reach other services, in the United States (Iowa, region us-central1), and keeps the database’s backups. Your data, including health data and Coach conversations, is stored there. Google Cloud handles it only to run these services for Polaris, under Google Cloud’s data processing terms.
- Cloudflare
- Carries traffic to Polaris’s servers and stores the encrypted nightly backups. It also receives email sent to alpha@projectpolaris.dev and passes the sender, subject and text to Polaris.
- Cursor
- An AI assistant that runs in Cursor reads new requests for access, including the name, email address and message, and suggests whether to invite the person. It can only read and recommend: it cannot invite anyone or send email, and a person decides every request. Cursor’s Privacy Mode is on, so under Cursor’s terms the requests are not used to train AI models.
- TypeSafe
- A decision-support service. Polaris may send it coded training information, such as a readiness band, the day’s session type and your goal, without your name, your messages or your profile ID. It may also send short summaries of Coach quality problems found in conversations.
- Anthropic (Claude Code)
- Runs the automated coding agent Polaris uses to investigate bugs and propose fixes. It can receive a problem summary, short excerpts of a Coach conversation, the words and screen details from Report a problem, technical error details and logs from an earlier fix attempt. Polaris replaces names where its preparation checks find them; health details and other personal information can remain. A report’s optional screenshot is never sent to this agent.
- Grokbot reviewers (currently shut down)
- The Grokbot reviewers and tester bots used by Polaris’s operators are currently shut down. Polaris still has tools that can export original Coach messages and the inputs and results of Coach’s tools to a connected reviewer. Those contents can include health data and other personal information; account codes do not anonymize them. The tester tools can also send messages to Coach and return its replies and tool details to the connected reviewer.
- GitHub and Slack
- Polaris’s operators track Coach quality problems in private GitHub issues and Slack alerts. A problem report can include a short excerpt of a conversation. Test cases built from real conversations have names replaced first; health details and other personal information can remain.
Polaris may also disclose information when the law requires it.
Who at Polaris can see it
Polaris’s operators use an administrator console that shows members’ conversations, records, usage and technical logs. It is limited to administrator accounts. They use it to support you, fix problems and improve Coach. Members see only their own profile.
Your choices
- Get a copy. In the iPhone app, open Settings, then Your data, then Request a copy. Polaris emails a download link to your sign-in address. The link works for 7 days. The copy does not include food photo images or the records of other people opening your personal link, and it holds only the most recent records from your personal data store.
- Delete your account.In the iPhone app, open Settings, then Delete account, and type DELETE to confirm. This cannot be undone. Polaris erases your Coach conversations and notes, your sign-in, push settings, crash reports, the Apple Health data in its own database, any data read from Oura, any activities previously read from Intervals.icu, the records of people opening your personal link and your original request for access from its own database at once, and asks Oura to revoke Polaris’s access. Your confirmed logs (food, weigh-ins, pain, workouts) and the health data Polaris copied from Apple Health are held on the Polaris data server and are erased within 7 days. Apple Health on your iPhone is not touched. Polaris also asks Apple to disconnect Sign in with Apple. If that cannot be done, the email confirming your deletion tells you how to remove Polaris yourself in your iPhone’s Settings. If the app says it cannot delete your account, or you use Polaris only on the web, email us and we will delete it.
- Cookies on the public pages. Cookie settings at the foot of every public page turns Google Analytics and Microsoft Clarity cookies on or off.
- Withdraw a request for access. Reply to the email Polaris sent you, or email us, and we will delete it.
- Backups and service providers. Copies in Polaris’s encrypted backups are removed when those backups expire (see Where it is kept). Copies held by the services listed above follow their own policies.
- Coach and OpenAI. Coach asks for your OK before it sends your data to OpenAI. You can withdraw it at any time: in the iPhone app, open More, then Privacy; on the web, open Settings. Coach then stops until you agree again, and the rest of Polaris, including Apple Health sync, keeps working. Withdrawing does not recall what was already sent.
- Apple Health. You can stop Polaris reading Apple Health at any time in the iPhone’s Health settings.
- Oura. To stop Polaris reading Oura, disconnect it in Settings, under Data sources, on the web or in the iPhone app. Polaris asks Oura to revoke its access and deletes everything it read from Oura at once. If Polaris cannot reach Oura, it tells you, and you can also remove Polaris in the Oura app. The Show Oura switch only hides Oura from your dashboard; Polaris keeps reading it until you disconnect.
- Notifications. In the iPhone app you can turn each kind of notification off and set quiet hours.
- Sign out. Signing out of the iPhone app revokes that iPhone’s token at once.
How long Polaris keeps it
- Your conversations, notes, logs and synced health data are kept until you delete your account. After that, Polaris’s database is cleared at once and the data server within 7 days.
- Data read from Oura is kept while Oura is connected, and deleted at once when you disconnect it or delete your account. Copies in Polaris’s encrypted backups are removed when those backups expire.
- If you previously connected Intervals.icu, Polaris deletes the activities it read from it at once on request or when you delete your account, and copies in Polaris’s encrypted backups are removed when those backups expire.
- Crash and hang reports from the iPhone app are deleted after 90 days.
- A record that a member’s link was opened is deleted a year after it was opened, or sooner if that member deletes their account.
- A record of a tap on Get the app is deleted a year after the tap, or sooner if the member whose link you came through deletes their account.
- An email address on the Android waitlist is kept only to tell you when Polaris is on Android, and deleted after that email, or sooner if you ask.
- A request for access that does not become an account is deleted 90 days after Polaris declines it. If you are on the waitlist, it is deleted a year after the decision or your last message, whichever is later. If no one has decided, it is deleted a year after your last message, and an invite you never used, a year after it was sent. If you become a member, it stays with your account and is erased when you delete the account.
- A code that connects your iPhone expires after 10 minutes.
- A data-copy link works for 7 days.
- Backups are kept for 15 days (daily) or 400 days (monthly).
How it is protected
- The keys that connect Polaris to your personal data store and your health sync stay on Polaris servers, and are never sent to your iPhone or browser.
- Passwords are stored only as a one-way hash. iPhone tokens and connect codes are stored only as hashes.
- Polaris checks your access on every request, and a person who is not signed in, or has no access, sees no member data.
- The keys Oura gives Polaris are encrypted and never leave Polaris servers.
- Backups are encrypted before they leave the server.
- If a security breach affects your data, Polaris will tell you as the law requires.
Age
Polaris is for people aged 18 and over. It is not meant for children, and Polaris does not knowingly collect data from anyone under 18. If you believe someone under 18 is using Polaris, email us and we will delete their account.
Changes and contact
When this page changes, the date at the top changes with it. Questions about privacy or your data, or a request to see, copy or delete it: jason@allgreatthings.io, or by post to All Great Things Inc., 2297 Prospect Drive, Frisco, TX 75036.