Privacy at co.day

Last updated 3 October 2026

co.day is a place where people book time to help each other, and take that call. This page says what we collect, why, where it goes, and how to get rid of it.

Who we are. co.day is run by Buzzy Pty Ltd in Sydney, Australia. Reach us at mike@co.day. co.day is for adults. We don't knowingly collect anything from people under 16.

What we collect

• When you sign in with Google: your email address, your name, your Google account id and the web address of your Google profile photo, which you can use as your booking-page photo or replace with one you upload. Signing in asks only for openid, email and profile.
• If you set up a booking page: your hours, your types of help, a photo if you add one, and, if you connect a calendar, what the next section describes.
• When you book or take a call: the time, the type of help, what you wrote in answer to the questions, and whether the call happened. What is said on the call is transcribed (see "Calls and AI"). Chat messages and anything the call produces are kept with that call.
• If you apply to a group: what you filled in, including your phone number if you gave one.
• If you answer a feedback collection: your name and email, whatever you record, and a transcript of it.
• If you turn on notifications: the address your browser gives us to reach you, and your quiet hours.
• Email: mail we send you leaves a delivery record with Brevo. Mail sent to a name@co.day address leaves a log of who it was from and to, and its size, never its contents.
• Email to an agent address (name@agents.co.day): we keep the whole message, including any attachments, with Cloudflare, so the person the agent acts for (for a community's agent, the member who looks after it) can read it and reply. For now that person writes every reply themselves; it is sent from the agent's address and says who asked for it to be sent, and their replies are kept too. No other co.day member can see the conversation, and it is not sent to any AI model. The people who run co.day can reach it to keep the service working. We log who each message was from and to, and its size, and the person gets a notification showing the sender's name.
• If you list your agent on agents.co.day: its card is public, for people and AI tools to read: your first name, your agent's address and name, what it helps with, a short note, whether it is taking requests, the date you listed it, and your communities and booking link if you tick them. co members also see the card inside co. Unlisting takes the page down at once and stops new mail, though search engines and archives may keep copies for a while. Conversations your agent already had stay with you.
• How the site is used: ordinary server logs. No advertising trackers. Our pages load fonts from Google and a code library from jsDelivr, so those two see your IP address.

Your Google calendar data

Connecting a calendar is optional and only needed if you want people to book you. We ask for three calendar scopes, alongside the sign-in scopes you already granted, and nothing wider:

• See when you are busy (calendar.freebusy). We read the start and end of your busy blocks for the dates someone is looking at, and subtract them from the hours you published. Of the events on your calendar we see only when they start and end, never their title, guests, location or contents. We don't store your busy times: they are read when someone opens your page, and then discarded.
• See the list of your calendars (calendar.calendarlist.readonly). Only so you can tick which calendars count towards your availability. Names and ids, never events.
• Manage the events co.day itself creates (calendar.events.owned). When someone books you we create that one event, move it if the booking moves, and delete it if it is cancelled. It gives us no access to events anyone else created. The only event whose details we hold is the one we made.

What we store: the Google address of the connected account, which calendars you ticked, which permissions you granted, the last error Google gave us if a call failed, and the id of each event we created. The token that lets us reach your calendar is encrypted (AES-256-GCM) before it is stored, and decrypted only inside the code that calls Google. It is never sent to a browser.

What goes into that event: the type of help, the time, the join link and what the person booking wrote in the booking questions, because that is what makes the invitation useful. Google emails the invitation to them, and to any co-hosts.

What we never do: read the contents of your other events, use your calendar data for advertising, sell it, or use it to train AI models. Nothing from your calendar is ever sent to an AI model.

Turning it off: use Disconnect on your booking page, or remove co.day at myaccount.google.com/permissions, or email us and we will delete the stored token and calendar list the same day. Disconnecting stops us reading your calendar; the bookings themselves, and the ids of the events we created for them, stay in your co.day record, and events already on your calendar stay there for you to keep or delete.

co.day's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. We do not use data obtained through Google APIs to develop, improve or train generalised or non-personalised AI or machine-learning models.

Calls and AI

Calls are transcribed by default, so co can take notes and follow what is happening. Each person can switch transcription off for themselves at any point in the call, and while it is off their speech is not transcribed or kept.

To do that, speech is turned into text by a speech model running on Cloudflare Workers AI, and the text is sent to Anthropic (Claude) and to open models hosted by Cloudflare so co can write notes and answer in the call. They process it to answer that request and do not train on it. Transcripts and chat stay with that call on co.day.

Who else sees it

• The people you book with: your name, the type of help, the time, and what you wrote.
• Google: sign-in, and your calendar if you connected one, including the invitation it emails.
• Cloudflare, which runs the site, the database, the file storage and the speech and open models, and sends agent replies.
• Anthropic, for the notes and answers described above.
• Brevo, which sends our email: the recipient's name and address, and the contents of that email.
• The person whose agent you email: your message, your name and your address.
• Your browser's push service (Google, Apple or Mozilla), if you turn notifications on.
• Nobody else. We do not sell personal information, and there are no advertising networks here.

These providers are outside Australia, in the United States and Europe, so your information is handled overseas.

How long we keep it

Your account, your bookings, the record of who helped whom, and call transcripts stay while your account exists: a record both people can see is the point of co.day. Calendar access is kept until you disconnect. Email delivery records are kept by Brevo under their own retention. We keep agent conversations until the agent's owner, or the person who wrote, asks us to delete them.

Your choices

There is no self-service delete button yet. Email mike@co.day and we will delete your sign-in details, your booking pages, your calendar connection, your photo, and your agent's listing, name and conversations within 30 days, and tell you when it is done. If you wrote to someone's agent, you can ask us the same way to delete your messages and our copy of your name. A notification the agent's owner already received, and replies already sent to you, can't be recalled. You can also ask to see, correct or export what we hold. Bookings and calls you shared with someone else stay in their record, with your name on them, because it is their record too.

Changes

If this page changes in a way that matters, we will say so on it, with the date at the top.