What Larkby knows about you.

Three things you type, two Larkby works out

You give a phone number, an email address, and the time you want to be woken. Larkby works out two more without asking for them. Your timezone is read from your browser, so the time you picked means the same thing wherever you are. Your country is taken from the number you typed rather than from the picker beside it — a +1 number with a Toronto area code is Canada even if the picker still says United States.

Four of those five are stored in Supabase. The phone number is not one of them: working out your country is the whole of what Larkby uses it for, and it is dropped as soon as that is done. There is no column for a phone number in any of Larkby’s tables, so there is nowhere for one to sit.

A message, and the voice that speaks it

None of this is required, and skipping it changes nothing about your wake-up call. You can write a short morning message — up to 200 characters — and choose the voice that speaks it. Both are stored against your account, and the words of the message are sent to xAI to be turned into speech. xAI is also the voice on the wake-up call itself, and what that means is set out below.

Larkby never asks you for anybody else’s details, and it keeps no phone number at all — not yours, and not anybody else’s.

A line for each call

Every wake-up call Larkby schedules gets a row of its own: the minute it is due, whether it is still waiting or finished, how many times it has been dialled, and the moment you spoke up to say you were awake. Larkby needs the count to know whether to ring again, and the confirmation to know the call did its job. Kept side by side over weeks, those rows are a record of which mornings you got up.

What was said on the call is not in them. The row holds the times and the outcome, and there is nowhere in it for anything else.

What a subscription records

Taking a paid subscription adds one more row: which plan, whether it is active, the amount charged, and the two identifiers Stripe uses to refer to you and to the subscription. Your card number is not among them — it is typed on Stripe’s own page and never reaches Larkby.

A password, or your Google account

Booking does not ask you for a password. The form wants a phone number, a wake time and an email, and nothing else. Afterwards you can set one, use your Google account, or neither — your booking stands either way. Once an account has a password, you are the one who chooses it, and there is still no column for a password in any of Larkby’s own tables: Supabase holds it, in the auth tables it manages, and checks it when you sign in.

Signing in with Google is the other way in. It happens on Google’s own page rather than on Larkby’s, so it is Google that checks who you are and your Google password never reaches Larkby. What comes back here is the email address on that account, which is what your mornings are stored against.

Three things there is nowhere to put

The company answerable for it

Larkby is made and run by Draft Labs Pte. Ltd. Everything above is that company’s to answer for: it decides what you are asked for and what that is used for, and it is who you are dealing with when you book a morning. Every other company named on this page is one your data passes through on its behalf, and the next section is the list of them.

Ask for a copy of what it holds, ask for it to be deleted, or ask a question about either, through the form at the foot of this page.

Everyone else it passes through

Supabase

The database, and the sign-in. Everything Larkby keeps is stored here; the session you hold once you are signed in is minted by Supabase, and your password sits in the auth tables it manages rather than in any table of Larkby’s own.

Twilio

The wake-up call, and the line it comes from. There is no phone number of yours to hand it: the one you type when you book decides your country and is then dropped, and Larkby has no column to keep it in. Larkby sends no text messages at all.

PostHog

Product analytics. On top of the events Larkby sends it, the library records clicks and the address of the page you are on, and it captures JavaScript errors.

xAI

The voice on the call. While a wake-up call is connected, everything said on it — your side and Larkby’s — is streamed live to xAI in both directions, because that is the only way anything can answer you. Your morning message goes the same way, on the call and again the moment you press play to hear it. Larkby passes that audio through and keeps none of it.

Railway

Hosting. Every request to Larkby passes through it.

Google

Sign-in, if you choose it over a password. It happens on Google’s own page rather than on Larkby’s, so Google is told which of its accounts is signing in here and your Google password never reaches Larkby. What comes back is the email address on that account, which is what your mornings are stored against.

Resend

Used only if you send the form below. It carries your address and your message to the operator.

Stripe

Only if a paid subscription is ever taken. It receives your email address.

What an ad link carries

Arriving from an advertisement means the link carries tags — gclid, and the utm_ set. Larkby reads them out of the address and hands them to PostHog, which attaches them to analytics events so it can tell which advertisement brought you. That happens on whichever page you land on, this one included. There are two copies and both live in sessionStorage: Larkby’s own, and PostHog’s, which is told to keep its store there rather than in the cookie and localStorage it would reach for by default. Both go when you close the tab, and nothing carries them into a later visit. The tags are never written to the database.

What is left in your browser

• __Host-larkby_booking, a cookie set when you book. It holds a random token and nothing about you, and it expires after 24 hours.
• Supabase’s sign-in cookie, set once you sign in. It is written to last 400 days rather than to the end of the browser session, and scripts on this site can read it.
• PostHog’s own store — the identifier it gives this browser, and the properties it stamps on what it sends. Larkby sets that store to sessionStorage rather than the cookie and localStorage PostHog would use by default, so it goes when you close the tab.
• The advertising tags above. Both copies — Larkby’s and PostHog’s — are in sessionStorage, and both go when you close the tab.
• One analytics: entry in sessionStorage per analytics event, holding everything sent with that event. They go when you close the tab.
• larkby:landing_engaged, set in sessionStorage on the home page once you have stayed or scrolled, so one visit is not counted twice. It goes when you close the tab.
• larkby:booking_confirmed:…, set in sessionStorage when you reach the confirmation page, so one booking is not counted twice. Your wake time, your timezone and your country are written into that name, and scripts on this site can read them. It goes when you close the tab.

Nothing expires on its own

Larkby deletes nothing on a schedule. There is no expiry job and no retention window: what is stored stays stored until someone asks for it to be removed, and the removal is done by hand. That is about the rows Larkby keeps — most of what your browser holds goes when you close the tab, as the list above says. That is the whole of it, and it is why the form below exists.

Ask for your data, or its deletion