Last updated: May 1, 2026

Privacy Policy

We built ClearSlot so we never have to ask you to trust us with your data, because we never see it.

The short version

ClearSlot shows you and a friend when you are both free, without either of you ever sharing what you are actually doing. Your calendar events are never sent to our servers. We never see event titles, attendees, locations, or descriptions. We receive nothing except a temporary token that lets your device read your own calendar, and that token stays on your device.

What we collect

We collect essentially nothing. Here is the complete list:

  • Google OAuth token: A temporary access token that allows the app on your device to read your Google Calendar. This token is stored locally on your device only, using encrypted storage. It is never transmitted to ClearSlot servers.
  • Availability payload: When you share your availability, your device computes a busy/free block summary (no event details, no titles, no metadata) and encodes it. This encoded data is shared with room participants only. ClearSlot servers store it temporarily (up to 48 hours) solely to enable the room feature, then it expires automatically.

We collect no names, no email addresses, no device identifiers, no location data, and no analytics by default.

What we do not collect

To be explicit, ClearSlot never collects or processes:

  • Calendar event titles or descriptions
  • Event attendees or organizers
  • Event locations
  • Recurring event patterns
  • Any personally identifiable information from your calendar
  • Your name or email address
  • Device identifiers or advertising IDs
  • Location or IP address logs

How the availability payload works

When you share your availability, the following happens entirely on your device:

  1. Your device reads your Google Calendar using the OAuth token stored locally.
  2. Event details are immediately discarded. Only busy/free blocks (time ranges with no other information) are retained.
  3. These blocks are encoded into a Base64 string.
  4. You create or join a room. The encoded blocks are stored temporarily in our database (up to 48 hours) so your co-participants can see mutual availability.
  5. The overlap computation happens in the browser or app — never on our servers.
  6. Room data expires automatically after 48 hours and is deleted.

Google OAuth and third parties

ClearSlot uses Google OAuth to access your Google Calendar. This means Google is the only third party involved. When you connect your calendar, you are authorizing ClearSlot to read your calendar on your behalf, under Google's standard OAuth scopes. We request read-only access.

Google's privacy policy governs their handling of the OAuth authorization process. You can review it at policies.google.com/privacy.

We do not sell, share, rent, or otherwise transmit any data to any third party beyond the Google OAuth process described above.

Revoking access

You can disconnect ClearSlot from your Google Calendar at any time in two ways:

Revoking access removes the OAuth token from your device. Any room data in our database expires automatically within 48 hours.

Data retention

Room availability payloads are stored for up to 48 hours, then automatically deleted. OAuth tokens are stored only on your device and deleted when you disconnect your calendar or uninstall the app. We retain no other user data.

Children

ClearSlot is not directed at children under 13. We do not knowingly collect any information from children under 13. If you believe a child has used ClearSlot and you have concerns, contact us at the address below.

Changes to this policy

If we make material changes to this privacy policy, we will update the date at the top of this page. We encourage you to review this page periodically. Continued use of ClearSlot after changes constitutes acceptance of the updated policy.

Contact

Questions about this privacy policy? Reach us at: privacy@clearslot.net