freeslotPrivacy policy
freeslot is a Chrome extension that finds free time in your Google Calendar, formats it for sharing, and converts times between time zones. This policy explains what it does with your data. The short version: your calendar data never leaves your browser, and we do not sell or share personal data.
What the extension accesses
When you sign in with Google, freeslot asks for these permissions:
| Permission | Why |
|---|---|
calendar.events.readonly | Read when your events start and end so it can work out when you are free. Event titles are shown only to you, in the extension. |
calendar.calendarlist.readonly | List your calendars so you can choose which ones count as busy. |
calendar.freebusy | Ask Google whether the people you add as contacts are free or busy. Google returns only busy time ranges, never event details. |
userinfo.email | Only for the Pro subscription: identify your Google account to the billing service. Requested separately, the first time you subscribe or restore a purchase. |
Calendar data is requested directly from Google by your browser, used to compute free time on your device, and is not sent to us or to any third party. We do not operate a server that receives your calendar.
What is stored on your device
Your settings (working hours, time zones, contacts you add, chosen calendars) and a cached Pro status are kept in your browser's local extension storage. They stay on your device. Uninstalling the extension removes them.
What our billing service receives
Pro features are a paid subscription. When you subscribe, restore a purchase, or open the extension's Pro features, the extension sends a Google sign-in token that has only the email permission to our billing service (a Supabase Edge Function). The service verifies the token with Google and learns:
- your Google account ID and email address.
It uses these to look up your subscription with our payment provider, and does not store them in a database. The service never receives a calendar token, and rejects any token that includes calendar access. Our hosting provider (Supabase) may keep standard request logs.
How we protect your data
freeslot is built to hold as little of your data as possible, and to protect what it does touch.
- Calendar data stays on your device. Events and free/busy answers go from Google to the extension and are processed in your browser. They are never sent to a server we operate, so there is no copy on our side that could leak.
- Encryption in transit. Every request the extension makes, to Google, to our billing service and to Polar, uses HTTPS (TLS).
- Least access. All Google permissions are read-only: freeslot cannot create, change or delete your events. The calendar permissions and the email-only permission used for billing are requested separately, and the billing service rejects any token that includes a calendar permission.
- Sign-in tokens. Google sign-in tokens are issued and held by Chrome. We do not store them. The billing service uses the email-only token only to ask Google who you are, and does not save it or write it to logs.
- A billing service that stores nothing. It has no database. It identifies you only through Google's own token check, ties your subscription to your stable Google account ID, can show or change only your own subscription, and limits the rate of requests to resist abuse.
- Secrets kept out of the code. The keys that let the billing service talk to Polar are stored as Supabase function secrets, with only the permissions they need.
- Who can access data. No one at freeslot can read your calendar data. Access to the billing service's settings is limited to the operator.
- No remote code. The extension runs only the code in its own package, and its fonts and scripts are bundled with it.
Payments
Payments are handled by Polar, the merchant of record. Polar collects your payment details and email at checkout, handles tax, and sends receipts. We never see your card number. Polar's own privacy policy applies to that data.
Email drafts
If you ask a contact to share their calendar, freeslot opens a Gmail compose window with a prefilled message. Nothing is sent until you press Send in Gmail.
What we do not do
- We do not sell personal data.
- We do not use calendar data for advertising or to train AI or machine-learning models.
- We do not let humans read your calendar data. We cannot: it never reaches us.
- We do not use analytics or tracking in the extension.
Google API Services disclosure
freeslot's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Data retention and deletion
We hold no Google user data on any server we operate, so there is none for us to retain or delete. This table shows where each kind of data lives, how long it is kept, and how to remove it.
| Data | Where | How long | How to delete it |
|---|---|---|---|
| Calendar events and free/busy results from Google | The extension's memory on your device | Only while the extension window is open. Not saved to disk. | Close the extension window. |
| Google sign-in tokens | Chrome | Until they expire or you revoke access. | Revoke freeslot at myaccount.google.com/permissions, or remove the extension. |
| Settings, contacts you add, chosen calendars | The extension's storage on your device | Until you change or remove them, or uninstall. | Edit or remove them in the extension, or uninstall it. |
| Cached Pro status | The extension's storage on your device | Replaced each time the status is refreshed. | Uninstall the extension. |
| Your Google account ID and email, as seen by the billing service | The billing service's memory only | About a minute, then discarded. Never written to a database. | Nothing to delete. |
| Subscription and payment records | Polar, the merchant of record | As long as Polar must keep them for tax and legal reasons. | Cancel from Settings → Plan, or email us to ask for deletion (see below). |
| Hosting request logs | Supabase | Standard short-lived logs kept by Supabase. We do not write tokens or calendar data to them. | Managed by Supabase. |
When you revoke freeslot's access or uninstall the extension, freeslot can no longer read your Google data. To ask us to delete billing-related data, email freeslot.support@gmail.com from the address you used to subscribe. We will reply within 30 days. Data held by Polar is also subject to Polar's own policy.
Your choices
- Revoke freeslot's access any time at myaccount.google.com/permissions.
- Cancel a subscription from Settings → Plan → Manage subscription in the extension, or from the Polar customer portal.
- Remove all local data by uninstalling the extension.
- To ask about or delete any billing-related data, contact us at the address below.
Changes
If this policy changes, we will update the date above. Material changes will be noted in the extension's release notes.
Contact
freeslot is operated by Pavan Kumar Rachapally. Email freeslot.support@gmail.com.