CalZen

Privacy & Security

Effective 3 September 2026

CalZen is scheduling software: it publishes your availability, takes bookings, and, if you ask it to, sends a notetaker into the call. This page lists every outside company involved in running it, what each one receives, and why.

The list below is the whole list. It reflects what actually runs in production, each provider is limited to processing data on our instruction, and we do not sell personal data or use it to train anyone’s models. There are no analytics, advertising or session-recording scripts on this site. The only script that runs before the page does is the one that remembers whether you prefer dark mode.

Meeting summaries are written on our own servers. When CalZen turns a transcript into a summary and a list of action items, that runs on hardware we operate, not through a third-party AI provider. Nothing said in your meetings is sent to an outside model.

What we collect

Your name, email address and password (stored hashed, never in readable form). The event types, schedules and bookings you create. For people who book with you: their name, email address, timezone and anything they type into the booking form. If you connect a calendar, the busy windows it reports, not the contents of your entries. If you use the notetaker, the recording, transcript and summary of the calls you point it at.

Google user data

If you connect Google, CalZen asks for four things and uses each for one purpose. Your email address identifies the connected account. The list of your calendars lets you choose which one bookings are written to. Free and busy times let us work out which slots to offer, and returns only time ranges, never the titles, guests or contents of your existing entries. Calendar events lets us create the meeting for a booking, attach a Google Meet link, add the host and the invitee to the guest list, update it when a booking is rescheduled, and delete it when a booking is cancelled.

How we handle Google user data

CalZen’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the scheduling features described above, which are the features you see in the product. We do not sell it, we do not transfer it to anyone except as needed to run those features, we do not use it for advertising, and we do not use it to train AI models. No person at CalZen reads it, except where you have asked us to, where it is needed for security or to comply with the law, or where the data has been aggregated and de-identified. Access and refresh tokens are encrypted at rest with AES-256-GCM. Disconnecting Google in the app revokes our access with Google and deletes the tokens.

Your rights

You can ask for a copy of your data, correct it, or have it deleted. Email team@calzen.io and a person will action it. If you are in the UK, EU or a US state with its own privacy law, these rights are yours by statute and we do not require you to explain why you are exercising them.

Keeping and deleting things

Bookings and their emails are kept while your account is open, because they are the record of what was agreed. Recordings, transcripts and summaries stay with us until you delete them or close your account. When you close an account we remove your data within 30 days, except anything we are legally required to keep. The recorder holds its own copy of the audio and video for seven days so we can retrieve the transcript, then deletes it; only our copy remains after that.

Where data goes

Our infrastructure runs in the United States. If you are in the UK or EU, using CalZen means your data is transferred there. Our hosting provider participates in the EU/US and Swiss/US Data Privacy Frameworks; the other providers listed above set out their own transfer terms in their policies, linked on each card.

Security

Traffic is encrypted with TLS, and data is encrypted at rest by our hosting provider. Calendar and conferencing tokens are encrypted before they are stored. Passwords are hashed with Argon2. Access to production data is limited to people who need it to operate the service.

Changes

When this page changes we update the effective date at the top. If a change materially affects what we do with your data, we will say so by email rather than relying on you to notice.

Who to contact

PowerBrix LLC, registered in Washington State, United States, is the company behind CalZen and the controller of the data described here. Reach us at team@calzen.io.

Independent attestations held by our providers

These attestations are held by the providers named on each badge, and are not issued to PowerBrix LLC. Each links to the source it was read from. Last verified 3 September 2026.