Your work stays private, understandable, and yours.

Connecting Google Calendar is optional and separate from signing in to Quipsly. Quipsly asks only to read the list of calendars available to you and to view and manage events on calendars you own. You choose the owned calendar and the Quipsly production or coaching lane before any event is written.

Quipsly uses this access to show your selected calendar in Quipsly, create or update the events you explicitly project, detect scheduling conflicts, and reconcile later changes so you can review them. Quipsly stores the selected calendar identifier, encrypted refresh credentials, provider event identifiers, synchronization cursors, and audit receipts needed to keep that connection reliable. Short-lived Google access tokens are not stored.

Google Calendar data is not sold, used for advertising, or used to train general-purpose AI models. It is not shared with other Quipsly members unless you deliberately place the resulting schedule information in a shared workspace. Infrastructure providers may process the minimum data needed to operate Quipsly under their service agreements. Quipsly's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Connecting Google Drive is optional and separate from signing in or connecting Calendar. Quipsly requests the selected-file drive.file permission so you choose which files become available to Quipsly; it does not request normal access to browse every file in your Drive.

Quipsly stores the selected file identity, revision and checksum evidence Google provides, file metadata, current download capability, encrypted refresh credentials, and audit receipts. Short-lived access tokens are sent only to the signed-in browser for Google Picker and are not stored. Provider locators and resource keys are withheld from shared editor responses.

Originals can remain in Google Drive. Quipsly may create a bounded proxy, thumbnail, waveform, transcript, or output only when the user requests that work. Google Drive data is not sold, used for advertising, or used to train general-purpose AI models. Quipsly's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including Limited Use requirements.

Quipsly uses Google Analytics 4 and an app-owned event ledger to understand whether people can complete important workflows and where the product needs improvement. Analytics events use a fixed vocabulary and redacted route categories. Quipsly does not send session titles, resource identifiers, names, email addresses, notes, transcripts, recordings, or other creative and coaching content to Google Analytics.

Advertising storage, advertising personalization, and Google Signals are disabled. Analytics storage begins denied; you can allow or decline analytics cookies in the product and change that choice here. Quipsly's own authenticated event receipts remain limited to operational product events needed to run, support, secure, and improve the service.