Privacy policy

Effective 30 October 2026

Compass is an alarm clock app made by Alanview ("we", "us"). When your alarm goes off, an AI voice calls you, checks you're awake and tells you about your day. This policy explains what Compass collects, where it goes, and how to delete it. Questions go to admin@alanview.com.

1. What our servers keep

Your account. When you sign in, we store your email address and a user ID. If you sign in with Google, we also store your name, your Google account ID and the link to your profile picture, which Google shares with us when you sign in. This is kept in our database, hosted by Neon in the United States, until you delete your account.

Sign-in codes. If you sign in by email, we send a 6-digit code through our email provider, Resend. We store only a scrambled (hashed) copy of the code and delete it within 15 minutes. To stop abuse, we count sign-in requests, code tries and new accounts per email address and per IP address. Those counts expire within a day.

Usage limits. We count the wake-up calls each account starts per day, and how many calls start in total, so costs stay under control. The counts are stored by user ID with Upstash and expire after two days. Each account also has a number of live call minutes a month, so we add up how long its calls last. For that, our server keeps the ElevenLabs ID of each call it starts for you until the call is over and counted (at most eight days), and each month's total of seconds for about two months after. It reads only each call's length from ElevenLabs, not what was said.

Your Google Calendar connection. To stop one account using another's calendar connection, our server keeps a scrambled (hashed) copy of your calendar connection's token together with your user ID. It can't be turned back into the token. It expires after 400 days without use.

Server logs. Our server runs on Vercel in the United States. It logs requests, including IP addresses and the user ID of signed-in requests, to keep the service running and look into problems. Vercel keeps these logs for a limited time.

We don't store your calendar events, goals, alarm schedule, or recordings of your voice on our servers.

2. Google Calendar

Connecting Google Calendar is optional. If you connect it, you choose one Google account, then pick which of its calendars Compass reads, and can give each a nickname.

What Compass reads. Compass asks Google for read-only access to:

• the list of your calendars (names and colors), so you can choose which ones Compass uses, and
• the events on the calendars you chose. From each event Compass uses the title, start and end time, location, the names of the people invited, and the notes. Before the notes are stored or used, Compass removes links, email addresses, phone numbers and long numbers such as meeting PINs.

Compass never creates, changes or deletes anything in your Google Calendar.

How it works. When you connect, Google sends our server a one-time code. Our server exchanges it with Google for a token and passes the token to your phone, which keeps it in Android's encrypted secure storage. When the token needs refreshing, your phone asks our server to get a fresh one from Google, because that step needs a secret only our server holds. Our server passes tokens along without saving or logging them, apart from the scrambled copy described in section 1.

Your phone then fetches your events directly from Google and stores today's and tomorrow's on your phone. Our server doesn't store your events. The only parts that pass through it are the short sentence your alarm says about an event and the morning briefing recorded in your voice (section 3).

How Compass uses your calendar. Only to tell you about your day: to show today's events in the app, to have your alarm mention them while it rings, and to have the voice read them to you and answer your questions about them during your wake-up call.

Who else receives it. During your wake-up call, today's events from the calendars you chose, as described above, are sent to ElevenLabs, our voice provider, with the other details in section 3, so the voice can talk about your day. Before your alarm, a short sentence about each of up to three of the day's events, and the morning briefing with the day's events, are also sent to ElevenLabs to be recorded in your voice (section 3). That's the only place your calendar data goes. It's never sent to Google's Gemini service.

What we never do with Google data. We don't sell it, use it for advertising, use it to decide credit-worthiness or for lending, give it to data brokers, or use it to create, train or improve AI or machine learning models. People at Alanview don't read it, except when you ask us to, for example to help with a problem you report, when it's needed to look into a bug or abuse, or when the law requires it.

Disconnecting. In Compass, go to Settings, then Google Calendar, then Disconnect. This deletes the token, the stored events and the morning briefing recorded from them (section 3) from your phone and asks Google to revoke Compass's access. Signing out does the same. You can also remove Compass's access at any time at myaccount.google.com/permissions.

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

3. Your wake-up call and ElevenLabs

Compass's voice is provided by ElevenLabs. When a call starts, your phone sends ElevenLabs:

• the name you gave Compass,
• the date and your local time,
• the weather for your area,
• today's events from the calendars you chose, with their nicknames,
• your goals and the briefing style and length you chose,

and, while the call is running, the sound from your microphone. ElevenLabs uses these to run the conversation, including a language model that writes the voice's replies. ElevenLabs doesn't keep recordings of the call's audio. It keeps a written transcript of each call for 30 days, then deletes it. After each call, ElevenLabs' language model also reads the transcript and makes a short summary, a note of the call's mood, and a few automatic checks: whether the voice did its job (for example, whether it ended the call after saying goodbye), whether you said you were up and how long that took, how many nudges it took, how the call ended, whether you asked about something else, and whether you named a focus for today (only yes or no, never what it was). These are kept with the transcript and deleted with it after 30 days. We look at them in aggregate, across many calls, to improve the voice. ElevenLabs' own privacy policy is at elevenlabs.io/privacy-policy.

Your alarm's spoken goals. So the alarm can talk to you about your goals even with no connection, Compass writes and records what it says ahead of time, when you add or change a goal, change your name or pick another voice. Your phone sends your goals' titles, the name you gave Compass and the voice's style to our server. Our server asks Google's Gemini model to write a short sentence for each goal, then has ElevenLabs speak each sentence in your voice. The sentences and audio are kept on your phone. Our server doesn't keep them. Google receives only the goal titles, your name and the style, never your email address or account. We use Google's free Gemini service, under which Google may use what it receives to improve its products and AI models, and people at Google may review it; see Google's Gemini API terms. If you'd rather this didn't happen, leave goals out of Compass or keep their titles general.

Your alarm's spoken events. If you connected Google Calendar and left "Calendar in briefing" on, your alarm also mentions the day's events while it rings, for example "You have Team standup at 10 AM. Time to get ready for it." Your phone writes these sentences itself, from each event's title and start time, for up to three events on the day of your next alarm. It records them ahead of time, like the goals: your phone sends each sentence through our server to ElevenLabs, which speaks it in your voice. Our server doesn't keep the sentence or the audio, and ElevenLabs may keep them in our account's speech history under its own privacy policy. The audio is kept on your phone and deleted once the alarm no longer says it, or when you disconnect Google Calendar. Event details are never sent to Gemini.

Your morning briefing. If your wake-up call can't go live (you're offline, it can't connect, or there are no live minutes left), Compass still reads you the morning briefing after you say you're up. So it can be in your voice, Compass records it ahead of time, within a day of your next alarm. Your phone writes the briefing itself from what it already has: the name you gave Compass, the date, the saved forecast for your area, the events on that day from the calendars you chose (each one's time, title, calendar nickname and location; event notes and invited people aren't in it), your goals and, if you chose the long briefing, their descriptions. Your phone sends the briefing's sentences through our server to ElevenLabs, which speaks them in your voice. Our server doesn't keep the sentences or the audio, and ElevenLabs may keep them in our account's speech history under its own privacy policy. The audio and its words are kept on your phone, only for the next alarm: each new briefing replaces the last one. Disconnecting Google Calendar deletes it from your phone at once, and the next one Compass makes leaves your events out. Signing out, signing out everywhere and deleting your account delete it from your phone. The briefing is never sent to Gemini.

Apart from those checks in aggregate, we look at call transcripts only to look into a specific bug or abuse, or when you ask us to.

4. What stays on your phone

Compass stores these only on your phone: your settings, alarm schedule, goals, briefing preferences, your calendar choices and nicknames, today's and tomorrow's calendar events, and what your alarm says recorded in your voice (section 3). Signing out, or signing out everywhere, deletes the recordings from your phone.

Location and weather. If you allow it, Compass reads your approximate location, rounded to about a kilometre, and sends it to our server, which gets your forecast from MET Norway, the Norwegian weather service. MET Norway sees our server, not you. Our server keeps each forecast for up to three hours under the rounded location, so people nearby share it, and doesn't store it with your account. Our host's request logs may hold the rounded location for a few days. Your phone's built-in geocoder, which on most Android phones is provided by Google, turns your location into a city name. You can type a city instead. Our server looks it up in its own list of towns, and the name goes nowhere else.

Backups. Android may back up Compass's on-phone database (your settings, alarms, goals, calendar choices and saved events) to your own Google account through Android's backup feature, depending on your phone's settings. That backup is between your phone and Google. We can't see it. Your sign-in and your calendar connection's token aren't backed up.

Microphone. Compass uses the microphone only during a wake-up call, or when you try a call while setting up the app.

5. Who we share data with

We use these providers to run Compass. Each gets only what it needs:

• Vercel (hosting our server) and Neon (our user database), in the United States, and Upstash (usage counts and sign-in codes)
• Resend (sending sign-in emails): your email address and the code
• Google (sign-in and Calendar)
• ElevenLabs (the voice call, the alarm's spoken goals and events, and the morning briefing recorded in your voice): the details in section 3
• Google (Gemini): your goals' titles, your name and the voice's style, to write what your alarm says (section 3)
• MET Norway (weather): your approximate location, sent by our server, without anything that identifies you

We don't sell personal information or share it for advertising. We may disclose information if the law requires it, or as part of a merger or sale of our business, in which case we'll ask for your permission before your Google data is transferred.

6. Security

All traffic between the app, our server and our providers is encrypted with HTTPS. Your sign-in and your Google Calendar token are kept in Android's encrypted secure storage on your phone.

7. Deleting your data

• Your account: in Compass, go to Settings, then Delete account. This deletes your account on our server straight away and everything Compass keeps on your phone. Without the app, email admin@alanview.com from the address you sign in with and we'll delete it within 30 days. See Delete your account.
• Calendar: Settings, then Google Calendar, then Disconnect, or remove Compass at myaccount.google.com/permissions.
• Everything on your phone: uninstall Compass, or clear its storage in Android's app settings.

8. Children

Compass isn't for children under 13, and we don't knowingly collect data from them. If you think a child has signed up, email us and we'll delete the account.

9. Changes

If we change this policy, we'll update the date at the top. If we change how we use your Google data, we'll tell you in the app and ask for your consent before the change applies to you.

10. Contact

Alanview, admin@alanview.com