tempo. Back to Tempo
TEMPO · LEGAL

Privacy Policy

What we process, why we need it, and the choices you have.

Last updated: 18 September 2026
On this pageWho this policy coversInformation we processWhy we use informationGoogle Calendar and Google MeetZoom, Microsoft and other integrationsSharing and email deliveryCookies and sessionsSecurityRetention and deletionYour choices and rightsContact and policy updates

01Who this policy covers

This policy explains how Tempo processes personal information when you use its scheduling platform, create a workspace, connect an integration, or make a booking. Tempo provides the software; the business or individual receiving your booking is responsible for the appointment and their own use of your information.

For account administration and platform security, Tempo determines how information is used. For customer records managed by a workspace, Tempo processes information to provide scheduling for that workspace. The workspace’s own privacy notice may also apply. Contact that business about its service or customer records.

Meet TempoBivak 1, 8333 DD Steenwijk, The NetherlandsKvK number: 95929223info@meettempo.app

02Information we process

  • Accounts and workspaces: name, email address, password hash, timezone, workspace membership and role, plan entitlement, profile details, invitations, and authentication or verification records.
  • Bookings and customers: customer name and email, optional notes, selected service or event, duration, price where applicable, timezone, appointment time, location, assigned staff, booking history, and cancellation reasons. A workspace may maintain contacts and manual staff names, email addresses, phone numbers and availability schedules.
  • Business settings: business name, description, address, phone, website, uploaded images, branding, service descriptions, pricing and availability rules. Information configured for public booking is visible to visitors.
  • Integration data: connected account identity, authorized calendar metadata, busy times, meeting identifiers and links, encrypted authorization tokens, and synchronization status.
  • Technical records: session and verification identifiers, security and audit events, delivery and retry records, and request information needed to operate the service. Hosting infrastructure may record IP addresses, browser/request details and errors.

Do not place medical records, payment card details, passwords, or other unnecessary sensitive information in booking notes or descriptions. Tempo does not need those details to schedule an appointment.

03Why we use information

We use information to create and secure accounts, enforce workspace access permissions, calculate availability, prevent conflicting bookings, manage appointments, display the correct service price and staff, synchronize connected calendars, deliver service emails, and investigate failures or abuse.

Where data protection law requires a legal basis, account and scheduling processing is used to provide the requested service; security and operational processing supports legitimate interests in running and protecting the platform; optional account connections require your authorization; and information may be retained where a legal obligation applies. A workspace is responsible for identifying the appropriate basis for its own customer processing.

04Google Calendar and Google Meet

When a host connects Google, Tempo accesses the authorized account identity and email, calendar list, calendar identifiers and settings, and availability from calendars selected to block bookings. It creates, updates and deletes Tempo booking events in the selected destination calendar. When supported and requested, it creates a Google Meet conference link.

Availability checks normally use free/busy intervals. During rescheduling, Tempo may read event records in the relevant calendar to distinguish the existing Tempo event from other conflicts. Public visitors receive available time slots, not other calendar events or their private details.

Tempo uses Google calendar data only to provide scheduling and calendar functionality. Google user data is not sold, used for advertising, or used to train generalized AI models. Access and transfers are limited to delivering authorized features, security investigations, or legal requirements; human access is limited to user-authorized support, security, or legal necessity. Tempo’s use and transfer of Google API information follows the Google API Services User Data Policy, including its Limited Use requirements.

Tokens are stored encrypted on the server. Disconnecting Google in Integrations removes stored authorization credentials and stops further authorized synchronization; you can also revoke access in your Google Account connections. Disconnecting does not automatically erase existing bookings or copies of events already in Google Calendar. Integration mappings and booking history may remain; contact us to request deletion.

05Zoom, Microsoft and other integrations

When a host connects Zoom, Tempo processes the Zoom account identity, encrypted tokens, meeting identifiers, join links, and synchronization records. For enabled automatic Zoom bookings, it sends appointment details to Zoom to create, update or delete the meeting. Host-only start information is restricted to the authorized host. Disconnecting removes Tempo’s stored credentials; existing provider-side meetings and historical booking records are not automatically erased.

Microsoft Calendar, Outlook calendar synchronization and Microsoft Teams automation are not implemented in this version. Coming-soon marketplace cards do not connect accounts or collect provider data. If those integrations are introduced, their access and use will be explained before authorization. Manually supplied meeting links do not authorize Tempo to read that provider’s calendar.

The customer’s “Add to calendar” actions are separate: Google and Outlook links pass appointment details to the selected provider when opened; Apple / ICS downloads a calendar file. Customers do not need to connect a calendar account to Tempo. Providers handle information under their own policies. Tempo does not record or transcribe meetings in this version.

06Sharing and email delivery

Booking information is shared with the receiving workspace and assigned staff as needed to provide the appointment. Authorized workspace members can access records according to their role. Private workspace records are not made available to other customer workspaces.

Tempo uses hosting/database infrastructure and Resend for transactional email delivery. Emails may contain names, addresses, appointment details and secure management links. Delivery records and an outbox support retries. Connected Google or Zoom accounts receive the information needed for the enabled integration. We may also disclose information where required by law or necessary to protect the service against abuse.

Provider processing locations may differ from your location. Applicable transfer requirements and safeguards must be assessed for the providers and hosting arrangements used; this notice does not promise that all information stays within a particular country. Contact Tempo for information about the applicable arrangements.

A public booking URL is intended to be shared. A private booking management link can authorize viewing, rescheduling or cancelling that booking: keep it private and do not forward it unnecessarily.

07Cookies and sessions

Tempo uses the essential tempo_session cookie to keep account holders signed in. It is HttpOnly, uses SameSite=Lax, and is marked Secure on HTTPS. It expires after up to 14 days; signing out clears it and ends that session. Login cannot work normally if you block this cookie.

The current application does not add advertising cookies or activate analytics or marketing trackers merely because their cards appear in the marketplace. External providers may use their own cookies when you visit their pages. Your browser settings control cookies on your device.

08Security

Tempo uses password hashing, server-side access checks, workspace-scoped authorization, hashed session credentials, encrypted integration tokens, and server-side booking validation. API secrets and OAuth tokens are not included in public pages. These controls reduce risk; no software or transmission method can guarantee absolute security.

Use a unique password, protect management links and connected accounts, and tell us if you suspect unauthorized access. Workspace owners are responsible for granting appropriate member access and keeping public business information accurate.

09Retention and deletion

Account, booking, contact and integration records are kept while needed to provide the service, maintain appointment history, resolve issues, or meet applicable obligations. Cancelling an appointment changes its status and preserves its history; removing staff does not remove historical bookings. The current application does not automatically erase every record after a fixed number of days.

Expired authentication links stop working when they expire, but expiry is not a promise that every associated database or log record is immediately erased. Delivery, security and backup copies may require separate handling. Retention depends on the record’s purpose and applicable requirements; contact us for the details relevant to your request.

For deletion or account closure, contact Tempo using the details below. For a business’s customer records, also contact that workspace. We may verify your identity and authority, and explain any information that must be retained. Disconnecting a provider or cancelling a booking is not the same as deleting your account.

10Your choices and rights

You can update supported profile details, disconnect integrations, and use the private management link to cancel or reschedule an eligible booking. Depending on applicable law, you may request access, correction, deletion, restriction, portability, or object to certain processing. You may withdraw authorization for optional connections without changing processing already performed. You may also complain to the data protection authority responsible for your location.

Send requests through the contact details below. Include enough information to identify your account or booking, but never send passwords, OAuth tokens, or your full private booking-management link. We may need to verify the request before acting.

11Contact and policy updates

For Tempo privacy questions, access or deletion requests, and security concerns:

Meet TempoBivak 1, 8333 DD Steenwijk, The NetherlandsKvK number: 95929223info@meettempo.app

For appointment changes or the service itself, contact the business shown on your booking. We will update this page when the described processing changes, and seek additional authorization where required before using connected account data for a new purpose.

© 2026 Tempo
Privacy Policy·Terms of Service