Compass
Privacy policy
Last updated October 18, 2026
Compass is Mick Olinik's own system of record for his work: his to-dos, meetings, projects, calendars and notebooks. It is not a public service and there are no open sign-ups: the only people who use it are Mick and the people he invites. Compass holds itself to GDPR principles as of October 17, 2026, plus the stricter US rules: the bar it measures itself against, not a claim that any one law applies. Questions, and every request below, go to mick@rockstarcoding.com.
If you were in a meeting with someone who uses Compass
- Compass may hold the notes or the transcript of that meeting, and the names of the people in it, because the person who uses it keeps a record of their own work.
- The text may be read by an AI model (Anthropic) to name, file or summarise the meeting for that person's own review. No decision about you is made by the model, and no AI provider trains on it.
- A game tape describes what people said, committed to and did; it never infers anyone's emotions, health, stress or trustworthiness.
- Speakers in a transcript are labels, like Speaker 1. Compass never builds a voiceprint of anyone.
- Nothing about you is sold, rented or used for advertising.
- You can ask for a copy of what Compass holds about you, for a correction, or for your name to be removed, by writing to mick@rockstarcoding.com.
- A handwritten page is treated like paper: a request about one is answered by deleting the page.
If Mick invited you to use Compass
- What you add is seen by others only through sharing: an area shared with them, a notebook shared with them by name, or your whole space if you let someone see it.
- The text of a to-do you add may be read by Anthropic's model to suggest a project and a size. Meeting notes you bring in from your own Notion may be named, filed or summarised by it, and the game tapes you make are written by it.
- A recording you upload is transcribed by Deepgram or OpenAI.
- Compass keeps a record of every change: what changed, who made it and when. You can read the history of everything you can see in Activity.
- If someone you share your whole space with opens it, you see one line saying so in your Activity.
Who handles data for Compass
- Supabase: the database and sign-in.Sees everything Compass stores, kept in the United States (us-east-1). Compass uses it to store and serve data and asks it for nothing else. Terms not yet checked.
- Cloudflare: hosting, the background jobs, and file storage (recordings, handwriting tiles).Sees every request to Compass, and the files it keeps. Compass uses it to run and store, and asks it for nothing else. Terms not yet checked.
- Anthropic: the AI model that names and files meetings, writes their summaries and game tapes, suggests a project and a size for a new to-do, and splits a dictated paragraph into to-dos when asked.Sees the text of those meetings, summaries and to-dos; never calendar data and never audio. Compass calls it through its paid API, whose terms exclude training on what is sent. Terms not yet checked.
- OpenAI: transcribing a recording, when its key is set.Sees the audio of a recording someone uploads. Compass calls its paid transcription API, which does not train on what is sent unless a customer opts in; Compass never opts in. Terms not yet checked.
- Deepgram: transcribing a recording, when its key is set.Sees the audio of a recording someone uploads. Every request Compass makes opts out of Deepgram's Model Improvement Program. Terms not yet checked.
- Google: the calendars a person connects, and the typefaces on game tape pages.Sees calendar events (read, and the events Compass itself writes); for typefaces, the reader's address and browser. Compass never sends calendar data to an AI model, and follows Google's API Services User Data Policy. Terms not yet checked.
- Resend: email: sign-in links, invitations and booking confirmations.Sees the address and the message. Compass uses it to deliver mail and asks it for nothing else. Terms not yet checked.
- Notion: a source, not a processor: Compass reads a person's meeting notes from their own Notion, read-only.Sees nothing new: Compass never writes to Notion. Not applicable. Terms not yet checked.
How long things are kept
This schedule is decided and being put in place; until it runs, Compass deletes nothing on its own, and anything can be removed on request.
- Meetings, game tapes, projects and to-dos: kept until their owner deletes them.
- Calendar event attendees and descriptions: two years after the event.
- Booking names, email addresses and answers: one year after the booked time.
- Raw transcription responses: 30 days.
- The reasoning behind a filing suggestion: 90 days.
- Records of background runs: 90 days.
- The before and after values in the change history: three years; the line that a change happened stays.
What Compass asks Google for
- Read access to the calendars of the Google account you connect (
calendar.readonly). - Permission to create, change and remove events (
calendar.events). Compass uses it only on events Compass itself wrote; it never edits or deletes an event a person made. - Your email address (
openid,email), so Compass knows which Google account is connected.
What Compass does with it
- Shows your events together in one week view inside Compass, and links each event to the meeting notes it belongs to.
- Works out your free and busy times for your own booking pages and availability links.
- Writes events into your own connected calendars: Busy holds, copies of events at the level of detail you choose, bookings people make with you, and outside-working-hours blocks.
- Shows other people only what you choose to share in Settings. Booking pages and availability links show nothing else.
Where it is kept
- Events Compass reads are stored in its database (Supabase, United States, us-east-1), readable only by the account that connected them and the people that account shares them with.
- Google access and refresh tokens are encrypted at rest with AES-256-GCM. The key is held only on the server, never in the browser.
What Compass never does
- Sell, rent or share Google user data with anyone.
- Use it for advertising.
- Send Google calendar data to an AI model, or use it to train one.
Compass's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Your control
- Remove a calendar in Compass (Settings, Calendars, Remove): its stored events are deleted, and so are the stored tokens once no other calendar from that Google account remains.
- Revoke Compass's access at any time at myaccount.google.com/permissions.
- Ask for a copy of your data, a correction, or for everything to be deleted, by writing to mick@rockstarcoding.com.
Changes
Any change to this policy is made on this page, with the date above.