busywait

What we store

The whole list, on one page

Privacy policies are written to survive lawyers. This page is written to be read. It is the same commitment in plain language, and if the two ever disagree, treat it as a bug and tell us.

The one-sentence version

We hold the times your calendars are busy, and nothing more than that unless you ask us to.

Held

What busywait keeps, and why

Your email address

To have an account at all, and to email you when a sync breaks.

Until you delete the account.

An access token per connected calendar

To read free/busy and to write the blocks. Encrypted at rest, revocable by you from either end.

Until you disconnect that calendar.

A list of your calendars, by name

So you can pick which ones take part. The name is the one piece of calendar text we hold.

Until you disconnect the account.

Start and end times of events in synced calendars

This is the sync. Without the times there is nothing to mirror.

Rolling — dropped as the events pass out of your sync window.

An opaque ID linking an event to its mirrors

So that moving or cancelling one updates the others instead of orphaning them.

For the life of the event.

Bookings made through your links

The name, email and any answers the person booking chose to give you.

Until you delete the booking or the account.

Any field you have switched on for a sync

Titles, guests, notes or locations, where you have decided a particular sync should carry them. Off unless you set it.

Until you switch it off or disconnect the calendar.

Not held by default

What never reaches us, unless you want it to

Busy-only is the floor, not the ceiling. Some syncs genuinely want more — two calendars that are both yours, or a client who should be able to tell a movable call from time you set aside. So the fields on the left can be switched on, one sync at a time, by you. The ones on the right have no switch at all.

Off until you turn it on

  • Event titlesThe name of the thing, carried across to the calendars you choose.
  • Whether a block is a meeting or your own timeLets a client see that Thursday is a call they could ask you to move, rather than focus time they should leave alone.
  • Guest lists and attendee addressesWho else is in it. Worth thinking hard about — these are other people’s addresses, not only yours.
  • Descriptions, notes and agendasThe body of the event, for the syncs where you want the full picture.
  • Locations and video conference linksSo you can join from whichever calendar you happen to be looking at.

Per sync, never per account — turning titles on between your two work calendars does nothing to the one you share with a client. Every switch says plainly what changes before you flip it, and flipping it back stops the copying from the next sync onward.

Never, at any setting

  • Recordings, transcripts or summaries — there is nothing here to record with
  • Your email, your files, or anything outside the calendars you connected
  • Anything at all from a calendar you did not tick
  • Your calendar as training data — not for our models, not for anyone else’s
  • Your data sold, shared or brokered. There is no second revenue line here

There is no toggle for these, no plan that unlocks them and no support request that will. A field we never ask for is one that cannot leak, cannot be subpoenaed and cannot be sold by whoever buys us in ten years.

In practice

An event, and the same event on the wire

In the calendar it was made in

title
Q3 budget — redundancies
start
2026-03-12T10:00:00Z
end
2026-03-12T11:00:00Z
location
Meet · abc-defg-hij
attendees
you@work.com, cfo@work.com
description
Bring the headcount model…

What crosses by default

start
2026-03-12T10:00:00Z
end
2026-03-12T11:00:00Z
status
busy

Three fields, unless you have told this particular sync to carry more. Nothing on the left reaches the other calendars because you have not asked it to — not because it is queued up behind a setting we hope you never find.

Encrypted at rest and in transit

Tokens are encrypted with keys held separately from the database. Everything moves over TLS.

Hosted in the UK and EU

Your data is held on infrastructure in the UK and EU and stays there. GDPR is the baseline it was built to, not a mode switched on for one market.

Deletion means deletion

Delete your account and the record goes, including tokens and cached times. Backups age out within 30 days.

Straight answers

What this does not protect you from

Any privacy claim that will not name its own limits is an advertisement. Here are ours.

Google, Microsoft and Apple still know everything
busywait sits between calendars you already have. It cannot reduce what your existing providers hold about you, and it does not claim to. What it can do is stop those calendars leaking into each other.
What you switch on, we necessarily hold
Turn on titles, guests or notes for a sync and those fields have to pass through us to reach the other calendar — there is no version of that where we do not touch them. Every switch is per-sync, off until you set it, and labelled with what it changes. The floor below it does not move.
Sharing guests means sharing other people
Attendee addresses belong to the people they identify, not to you, and copying them into another calendar is a decision made on their behalf. We will let you do it, we will not do it quietly, and we would think twice about it on any sync a client can see.
Access tokens are powerful things
A token that can write blocks into your calendar could, technically, read more than we ask it to. We request the narrowest scope each provider offers, encrypt the tokens at rest, and you can revoke them from Google, Microsoft or Apple directly without asking us.
Times alone still say something
A mirrored calendar shows when you are busy, and that is information. If a particular calendar should not learn even that, do not sync into it — and use a booking link instead.

The binding version is the Privacy Policy. Questions that this page does not answer go to privacy@busywait.ai.

The default is the same on every plan

Busy-only, whether you pay us or not. Paid plans let you switch fields on for a sync; no plan switches anything on for you, and no plan moves the floor.