Privacy Policy

Last updated: June 5, 2026

The short version: MeetSlot has no server. It runs entirely inside your browser and talks only to Google’s APIs, using the access you grant, to do the scheduling you ask for. It does not sell, share, or transmit your data to anyone else.

This policy explains what information the MeetSlot browser extension (“MeetSlot”, “we”) accesses, how it is used, and the choices you have. By installing and using MeetSlot, you agree to this policy.

1. We don’t run a server

MeetSlot is a client-side browser extension. There is no MeetSlot backend, database, or analytics pipeline. All processing — reading availability, calculating common free slots, and creating events — happens locally in your browser. The only network requests MeetSlot makes are directly between your browser and Google’s APIs, authenticated with a token Google issues to you.

2. Information MeetSlot accesses

When you connect your Google account, you are asked to grant the following access. MeetSlot uses each only to provide the feature it powers:

Basic profile (email, name, profile photo) — to show which account you’re signed in with and let you switch accounts.
Calendar free/busy and events — to read the busy times of you and the people you invite so it can find open slots, and to create the meeting you choose to schedule.
Contacts and directory — to power the invitee autocomplete (matching names to email addresses as you type).

3. How that information is used

To calculate and display time slots when all selected attendees are free.
To create the calendar event and send invitations you explicitly confirm.
To populate the invitee picker with matching people.

MeetSlot does not use your data for advertising, profiling, or training models, and does not transfer it to any third party other than Google as strictly necessary to perform the action you requested.

4. Data retention and storage

MeetSlot keeps your Google access token only in temporary browser session storage so you don’t have to re-authorize on every action; it is discarded when the session ends, and re-authorization happens through Google. Meeting details you enter (title, description, attendees, time) are sent to Google Calendar to create the event and are not retained by the extension afterward. MeetSlot stores no copy of your calendar, contacts, or events.

5. Google API Services Limited Use disclosure

MeetSlot’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, data obtained through Google APIs is used only to provide and improve the user-facing scheduling features described above, is not sold, and is not used for advertising or any unrelated purpose.

6. Your choices and controls

Revoke access at any time at myaccount.google.com/permissions.
Switch accounts from within the extension before scheduling.
Uninstall the extension to remove it entirely; no data remains because none is stored off-device.

7. Children

MeetSlot is intended for workplace and general scheduling use and is not directed to children under 13 (or the equivalent minimum age in your jurisdiction).

8. Changes to this policy

If this policy changes, the “Last updated” date above will change and, where appropriate, we will note the update within the extension or on this page.

9. Contact

Questions about privacy? Contact privacy@example.com.

Note for the publisher: this document is a starting template that reflects how MeetSlot is built. Replace the contact address and have it reviewed for your jurisdiction before publishing — it isn’t legal advice.