What we keep, and why.

• Account: your name, email address, username and timezone.
• Scheduling settings: teams, event types, weekly hours, date overrides, buffers and limits you configure.
• Bookings: for each booking, the invitee's name, email, timezone and optional notes, the time, the meeting link and its status.
• Calendar connections: the OAuth tokens (Google, Microsoft) or app-specific password (Apple iCloud) needed to reach your calendar. These are encrypted with AES-GCM before they are stored.
• Security records: sign-in sessions, one-time login codes and API keys. We store only hashes of these, never the secrets themselves.
• Waitlist: the email, name and note you submit while Tempi is in private beta.
• Payments: for paid event types, the price and Stripe identifiers for the payment. Card details go directly to Stripe; we never see or store them.

When you connect a calendar we use it for two things only:

• Checking when you are busy so we only offer free times. We read free/busy ranges when someone views your booking page. We do not store the titles, attendees or contents of your existing events.
• Creating, updating and deleting events for bookings made through Tempi, including a video link where your provider supports it. We never touch other events.

Disconnecting a calendar in Settings deletes its stored credentials straight away. You can also revoke access at any time from your Google, Microsoft or Apple account settings.

Tempi requests the Google scopes calendar.freebusy, calendar.events and your basic profile (name, email). Google user data is used only to provide the scheduling features described above.

Tempi's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not transfer Google user data to third parties except as needed to provide the service, to comply with law, or with your consent. We do not use it for advertising, and humans do not read it unless you ask us to for support or it is needed for security or legal reasons.

Tempi lets AI agents read availability and make bookings through its API and MCP server. An agent acting for an invitee sees only what your public booking page shows: your event types and free times, never your calendar events. An agent acting for you needs an API key you created, and can do only what you can do in the app. Revoke a key in Settings to cut off access.

• Cloudflare hosts the app and its database.
• Google, Microsoft and Apple hold your calendars and, if you use them, your sign-in.
• Stripe processes payments for paid event types, through your team's own Stripe account.

Each handles data under its own privacy policy. We share nothing with anyone else.

A session cookie keeps you signed in, and a short-lived cookie protects the Google or Microsoft sign-in flow. There are no analytics or advertising cookies and no trackers.

We keep your data while your account exists. Cancelled bookings stay in your history until you delete your account. To delete your account and everything linked to it, or to get a copy of your data, contact hello@meettempi.com. We act on requests within 30 days.

If this policy changes in a meaningful way, we will update the date above and tell signed-in users in the app. For questions, contact hello@meettempi.com.