Privacy policy

Sharing, transfers and disclosure of Google user data

SlotDesk uses Google user data to provide its meeting scheduling, calendar management, profile suggestions and travel features. The following recipients receive data for these purposes:

• Google: SlotDesk reads calendar lists, events and availability directly from Google Calendar. When you confirm a new invitation or meeting change, SlotDesk sends the reviewed details to Google to perform that action. Google makes event details available to invited guests and people with access to the selected calendar according to your calendar and event-sharing settings. Guests receive the notifications you confirm.
• Vercel, our hosting provider: the SlotDesk sign-in service processes Google authorization codes, access tokens and refresh tokens to connect your account and refresh access. Vercel also processes onboarding registration requests and connection metadata such as IP addresses, request headers and URLs. Calendar event reads and writes go directly between your browser and Google; event bodies and busy schedules are not routed through the SlotDesk sign-in service.
• Neon, our registration database provider: Neon stores the name, email address, timezone, browser label, setup-completion time, updates choice and onboarding identifier submitted during registration. Name or email fields may originate from Google or a calendar-based suggestion before you confirm them. Neon does not receive full calendar event records, event titles or descriptions, busy schedules, Google tokens, saved trips or other people's profiles.
• Speedy: authorized project operators can access submitted registration records. If you choose to include calendar information in an email to support@buildwithspeedy.com, the support team receives that information to handle your request. SlotDesk does not give the team routine access to the calendar contents held in your browser.
• Cloudflare, our public website provider: Cloudflare processes website request information when you visit buildwithspeedy.com, including this privacy page. The website does not receive the calendar data used inside the extension.

SlotDesk does not sell Google user data or transfer it to advertisers or data brokers. It does not use Google user data for advertising, credit or lending decisions, or training AI or machine-learning models. Event titles, event descriptions and busy schedules are not used for registration analysis or email updates. Any disclosure required by applicable law is limited to that legal requirement.

SlotDesk's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

How we protect Google user data

• Encrypted connections: requests to Google and SlotDesk's hosted services use HTTPS to protect data in transit.
• Google authorization: SlotDesk uses OAuth and does not ask for or store your Google password. The hosted sign-in service keeps its client secret server-side, validates the sign-in state and proof key, and binds sessions to the extension origin that initiated sign-in. Refresh-session envelopes are encrypted with AES-256-GCM and require the corresponding session proof.
• Credential separation: the normal cross-browser connection keeps access tokens and the encrypted refresh-session envelope in browser memory/session storage, separate from saved workspace settings. Tokens are excluded from normal profile exports and backups and are not stored in the registration database.
• Restricted service access: the registration database uses authenticated server-side credentials. Those database credentials are not bundled into the extension. Registration access is limited to authorized services and project operators. The application does not intentionally log Google tokens, calendar contents or registration request bodies; hosting request logs may still contain callback codes and request metadata as explained below.
• Local storage limits: saved settings, calendar-derived profile or travel details, drafts and recovery records stay in your browser's extension storage, separate from ordinary website storage. SlotDesk does not add encryption to this local data or to exported files. A person with access to your device or browser profile may be able to read them. Protect your device and browser profile, and keep exported files private.

Retention and deletion of Google user data

• Loaded calendar data: full fetched calendar lists, event records and free/busy results are cached in memory while the relevant SlotDesk session is open. Disconnecting or closing that window clears its loaded calendar data. SlotDesk does not keep a server-side database of those event records.
• Google credentials: for the normal cross-browser connection, disconnecting removes the saved session credentials; browser session storage is also cleared when the browser session ends. The encrypted refresh session expires within seven days, or sooner if Google requires it. Legacy Chrome authorization uses Chrome's managed token cache; disconnecting asks Chrome to clear those cached sign-in tokens. Removing local credentials does not revoke the permission grant held by Google.
• Calendar-derived data saved locally: names, email addresses, calendar/event identifiers, profile mappings, linked-flight titles, locations and times, alert details, drafts and recovery records may remain in your browser after disconnecting. Saved profiles and trips remain until you delete or clear them. Familiar-face suggestions have a sliding 30-minute expiry and expired entries are removed on the next read; disconnecting and Clear data also remove this cache. Confirmed completion clears ordinary pending operations. Calendar-change alerts keep the latest 20 records until dismissed, replaced or cleared. Manual recovery history has no automatic expiry. The detailed sections below describe these records.
• Registration information: submitted name, email and other registration fields have no automatic expiry. To request access, correction or deletion of registration records and managed contact copies, email support@buildwithspeedy.com. We verify your authority over the address before removing the matching records. Clearing browser data or disconnecting does not remove records already submitted to the service. Deleted records may remain in provider recovery copies until those copies expire under the provider's retention settings.
• Exports and service logs: files you download remain wherever you save them until you delete them. Hosting providers retain request logs and recovery copies under their own policies and configured retention periods; we do not promise a fixed deletion period for those provider-controlled copies. Requests about hosted personal data can be sent to the support address above.

To remove local Google-derived data: use Settings → Clear data for the connected account after resolving any unfinished calendar operation. Display preferences are stored separately. Removing the extension or clearing its browser storage also removes its local data, but does not remove files you exported or submitted registration records.

To stop Google access: remove SlotDesk's access through your Google Account connections. Revoking access stops future authorized requests but does not erase saved local information. Clearing SlotDesk or revoking access does not delete appointments already held in Google Calendar; manage those appointments in Google Calendar.

Contact

SlotDesk is made by Speedy, Nina Banai and Yoav Fried. For support, privacy questions, data correction/removal or updates opt-out, email support@buildwithspeedy.com. Website: buildwithspeedy.com.

What stays in your browser

Email guests without saved profiles, their confirmed meeting-only timezones and participant-specific preferences are saved with the unfinished draft and cleared after confirmed creation or starting a new draft. During your own-profile setup, SlotDesk may suggest your name from organizer or attendee details matching your email in selected calendars. You can edit the suggestion before continuing. This uses the existing Calendar permissions. Your saved profiles include names, email addresses, confirmed timezones, calendar mappings and any availability, travel, working-time or event-treatment rules you enter. SlotDesk also saves preferences, your selected participants and the invitation details you enter in review, including title, times, calendar, Meet choice, description and location. This lets you continue an unfinished meeting in another SlotDesk window or after reloading. Account settings are kept separately for each connected Google account; time display and appearance are shared across SlotDesk in the browser.

Decline alerts retain limited guest response and dismissal metadata, occurrence identifiers and expiry. Appointment follow-ups retain calendar/event identifiers and the chosen interval to protect during replacement searches. A pending reschedule retains account/calendar/event identifiers, the current version and before/after times, without the fetched title, description, guest list or video link. A pending detail edit saves your newly entered text and explicit guest additions/removals/role changes, with target identifiers, version, unchanged time and verification fingerprints. It does not save the fetched original title, description or full guest metadata. Completion removes the pending edit. Calendar-change alerts retain the meeting title, calendar/event and operation identifiers, verification status, check timing and a short result message. The latest 20 are kept; completed alerts can be dismissed. Unconfirmed changes are checked automatically only while SlotDesk is open and connected. Checks do not resend calendar changes. If you resolve an uncertain action manually, recovery history keeps the exact outgoing operation and your reported result. A manual report is labelled separately from Google confirmation and is never an automatic resend.

If a send needs confirmation, the prepared outgoing invitation is saved so SlotDesk can check the same event instead of creating a duplicate. This may include its title, recipients, dates/times, description, location and calendar/event identifiers. It is removed from the saved workspace after completion is confirmed.

These settings use local browser storage. SlotDesk does not encrypt them. Someone with access to the same browser profile or device may be able to access them, so use a protected browser and device for sensitive scheduling information.

Calendar data and Google access

Calendar lists, fetched events and free/busy information are held in session memory while you work. During setup and in Settings → Calendars, you choose which calendars SlotDesk can use. Events and free/busy data from calendars you leave out are not loaded or used for scheduling, suggestions or alerts. Calendar names remain available to change your selection. Existing meetings loads and caches your selected workspace calendars for the chosen dates; its calendar picker only filters that cache. Calendar selection and display-timezone changes use that memory cache; date changes and Refresh meetings load it again. Full fetched event records are not saved in SlotDesk’s settings. Limited calendar-derived information, including saved profile contacts, linked-flight details and alert titles, can be retained locally as described above. Familiar-face suggestions cache only derived names, emails and ranking counts/timestamps locally, separated by account and selected calendar scope. Their 30-minute expiry extends whenever Manage profiles is entered before expiry; expired candidates are discarded on the next read. Disconnect, Clear data, changed source selection and confirmed access loss remove this candidate cache. Full event bodies are never included. Disconnect clears this cache in affected windows. Calendar details can include appointment titles, attendees, locations and descriptions where Google grants access.

Windows in the same browser share saved workspace changes and the connection status. Opening another SlotDesk window can use the already authorized Google connection; each window checks the connected account through Google Calendar. The saved connection status contains the account and a connection flag, not an access token.

The independent Google connection uses a SlotDesk service hosted on Vercel to exchange an authorization code and refresh Calendar access. The client secret stays on that service. Access tokens and an encrypted refresh-session envelope with its proof stay in browser memory/session storage, not workspace settings, backups or the leads table. They clear when the browser closes; reconnect to continue. The service caps sessions at seven days. While that service is inactive, the legacy Chrome connection uses Chrome’s managed token cache. SlotDesk does not save passwords. Workspace selection limits what SlotDesk uses; it does not narrow Google’s underlying permission grant. The configured permission allows viewing and managing events on accessible Google calendars. Existing users confirm their selection after upgrading; an already reviewed unfinished operation may read its exact target for recovery before that selection is completed. The current application creates reviewed new events and can change the start/end or supported details/guests of one existing appointment after review. Recurring changes affect one occurrence only. It has no event deletion or calendar-move feature.

Local backup and profile files

Backup and export create local JSON files containing the selected saved profiles, calendar assignment references and all their scheduling/travel settings. A full backup also contains workspace/display preferences and global time rules. These files are not encrypted. They exclude Google credentials, loaded appointment content, registration records, meeting drafts, calendar-change recovery and suggestion caches. Temporary flight/travel forms are never stored for later completion. The separate Download saved data action shown for an unreadable workspace exports the raw local workspace for recovery. That file may contain unfinished invitation details, registration metadata and recovery history. Treat it as sensitive; it is different from an ordinary backup.

Import/restore reads the file on your device and may check calendar metadata with Google to identify access problems. It does not change calendar appointments or sharing, upload the file or submit another person’s registration. Restore replaces local setup after confirmation; an optional current backup can be downloaded first. A temporary rollback record exists only while replacement completes or recovers from interruption.

What is sent and where

SlotDesk makes authenticated Calendar API requests to Google to read available calendars and events, check availability, create the invitation you review and apply an individual meeting change you confirm. Create & send invitations sends the reviewed event to the selected calendar and asks Google to notify every retained participant. Google Meet is requested when you enable it for a new meeting. Reschedule & notify guests sends only the selected event’s start/end change and asks Google to notify its retained guests. Edit meeting sends only changed title/location/description and, when explicitly edited, the verified complete guest list. Retained guest responses and other untouched details are kept. Guest removal withdraws that invitation and may remove it from the guest’s calendar; the organizing appointment remains. Existing video fields are kept. Decline alerts update when calendars are read/refreshed; they do not move meetings automatically or poll in the background.

SlotDesk has a separate registration intake component, described below. It has no cloud settings sync, email-reading feature or LLM service. Full calendar event records, event titles and descriptions, and busy schedules are not sent to the registration database or a model provider. The confirmed registration name and email may originate from Google or a calendar-based suggestion. Google authorization codes/tokens pass transiently through the separate sign-in function on the same Vercel hosting project for exchange/refresh. That function does not store tokens in Neon or intentionally log credential payloads. Calendar reads and reviewed writes go directly to Google. The new sign-in path can authenticate delivery of the registration fields described below; it does not add event titles, event descriptions or busy schedules to that record. Copy meeting details places those details on your clipboard when you choose that action.

Hosting request information

Vercel processes connection information such as IP addresses, browser request headers and request URLs. Hosting logs may include the short-lived authorization code and encrypted state in a Google sign-in callback URL. SlotDesk does not intentionally write Google tokens, registration bodies or calendar contents to application logs. Short-lived, per-instance request counters limit repeated requests; these are separate from the leads table. Hosting providers apply their own infrastructure logging and retention policies.

Your onboarding registration

When you finish setup, SlotDesk saves the email, name and chosen timezone you confirmed, the browser name reported by your browser, the UTC setup-completion time generated by the app, and whether you checked the optional SlotDesk-updates box. The checkbox is unchecked by default. In Chrome and Edge, a registration is recorded whether or not you choose updates. In Firefox, sharing the registration record is optional and off by default. SlotDesk asks for Firefox’s data-collection permission when you opt in; calendar use does not depend on it. The updates checkbox remains separate.

These fields are used to understand registrations and improve the product. They are sent over HTTPS to a private SlotDesk leads table hosted on Neon through Vercel. If the service is unavailable, the registration stays queued in your browser. Settings shows whether the registration has been saved by the service or is waiting to be sent. Failed submissions keep the original setup time and retry without blocking calendar use. In Firefox, retries require both your saved sharing choice and current browser permission. You can turn off future sharing in Settings → Registration sharing or Firefox’s add-on permissions. This does not remove an already submitted record or revoke an earlier updates choice; email support@buildwithspeedy.com for removal or opt-out.

Access to the private registration table is restricted to authorized project operators and service providers as described above. Each completed onboarding creates a separate record, including when you use the same email in another browser or installation. Retries of the same submission reuse its onboarding identifier and do not create extra records. Later profile edits do not change saved leads. A random onboarding identifier distinguishes submissions; it is not a device identifier. Only the browser name is saved, without its version or full identification string. A browser that hides its brand may be recorded as Chromium or Unknown. Older registrations without browser information show Unknown. No calendar appointments, Google access tokens, other people’s profiles, travel rules or meeting drafts are included. The service does not send emails. If you opted in, the owners may use your address for occasional updates about SlotDesk; you can opt out at any time by emailing support@buildwithspeedy.com.

Registration records have no automatic expiry. Removal requests also cover managed copies; deleted records may remain in provider recovery history until its retention window expires. Email support@buildwithspeedy.com to request a correction, removal or opt-out. Clearing browser data or disconnecting Google does not remove a record already saved in the private leads table. Browser data removal can remove an unsent queued registration.

Disconnecting and removing saved data

The exit icon beside your email disconnects Google, closes editors and clears loaded calendar/review information from the current SlotDesk window. It clears the background Google session and memory-only credential storage. For the legacy Chrome connection it also asks Chrome to clear its cached sign-in tokens. Other open SlotDesk windows for the same account receive the disconnect and clear their displayed session too.

Disconnect keeps saved profiles, preferences and unfinished invitation details for recovery. Settings → Clear data removes the connected account’s saved workspace. An unfinished send or meeting change must be resolved first to avoid losing duplicate-send protection. This action does not delete calendar appointments. Display preferences are stored separately.

Disconnect does not revoke the app’s existing Google consent grant. Remove that grant through your Google account’s app-access controls if you want to revoke it.

Trips

Saved trips, flight times, locations, timezone changes and links to matching calendar entries stay in this browser as profile settings. Linked flights also retain the calendar name and a source-event signature containing the title, location, status and start/end times. Dismissed flight suggestions may retain these source signatures; the latest 2,000 are kept without automatic expiry until cleared. Backups and exported profiles include those settings. Flight estimates use bundled airport data locally; no flight service receives your route. Possible-flight and source-change checks use the selected calendars already available to SlotDesk. Trip actions never change calendar appointments.

Connection support

Help → Connection details shows the build, browser capabilities, package identity and connection-service readiness. Copying these details does not send a report and includes no account email, Google tokens or calendar contents.

Using a work account

Use SlotDesk with workplace calendars only when your organization permits the extension, requested Google permissions and local data handling. Email support@buildwithspeedy.com if you have questions about SlotDesk’s configuration.