Sparra — home

Privacy

Last updated: 30 October 2026.

Sparra answers calls and forwards requests to the business. Sparra Agenda is an optional integration: the owner can connect a Google account to offer and book appointments. This connection is separate from signing in to Sparra.

Google data accessed and stored

The connection receives the Google account identifier and email address, together with calendar identifiers, names, time zones and access roles. Sparra accesses busy intervals to find slots and the identifiers, states, dates, times and correlation references of Sparra appointments to verify their outcome. Google responses may contain other fields; not every received field is stored.

Sparra stores connection data and OAuth tokens, the selected calendar, booking rules, slot offers and booking command follow-up records. Busy intervals are used to calculate offers without being stored in Sparra’s Calendar tables.

How Google data is used

The owner selects a writable calendar and configures services, durations and working hours before enabling booking. Google data is used to connect the account, select the calendar, check availability, offer slots, book after explicit confirmation and verify the outcome shown in the private inbox.

Google event permissions (calendar.events) are broader than the selected calendar; Sparra uses the chosen calendar for its appointments. A created event contains the service, dates and times, and a private Sparra reference with a link to the request. It contains no caller contact details, full transcript or artificially added guest.

Recipients and external processing

Google receives account authorization exchanges and the calendar requests and data needed for the integration. Telnyx receives telephony data and call audio. The external AI processing for transcription, dialogue and speech synthesis all passes through OpenRouter, which receives and routes the data needed for those tasks.

Through OpenRouter, Microsoft Azure receives audio for transcription and text to be read for speech synthesis; Baseten or Together receives dialogue text. Necessary service and slot information, including information derived from Google availability, may enter dialogue text and spoken audio and be sent to these providers according to their role. OAuth tokens and Google account or calendar identifiers are not automatically sent to voice models.

Cloudflare provides the HTTPS entry to the Sparra site and processes the requests, responses and technical metadata that pass through it, including calendar information displayed in the private workspace.

Sparra does not use data received from Google APIs for advertising or to train or improve general AI models. Transfers to providers serve the processing necessary for the service; they are not a general guarantee about those providers’ own training, logging or retention policies.

The application and its main database are hosted in France. External providers’ processing is not represented as taking place exclusively in France.

Data protection

Public exchanges with Sparra and exchanges with Google use HTTPS. OAuth tokens are encrypted server-side with AES-256-GCM, bound to the relevant workspace and connection. Private data access requires an authenticated owner and respects isolation between workspaces. This token encryption does not mean that all ordinary metadata is encrypted by the application.

Retention and deletion

Call content, including the transcript and, when enabled through the intended information and choice process, the audio recording, is accessible for 30 days and is then deleted through cleanup operations. The business can also erase a request from its workspace. This period is separate from Google data retention. A slot offer is valid for five minutes; this validity period is not a deletion deadline.

A successfully completed disconnection disables booking, revokes authorization and clears tokens and the Google account identifier and email. The selected calendar, rules and follow-up records remain stored. While revocation is still pending or uncertain, this erasure is not guaranteed. If Sparra detects access withdrawn within Google, booking is disabled and reconnection may be needed, without immediate local erasure.

Erasing a call deletes its slot offers and completed or never-sent commands. For uncertain operations that may have been sent to Google, minimal Google identifiers, dates and times are retained to reconcile and resolve the outcome. No general maximum deadline for deleting all Google data is stated.

Disconnection does not delete events already created in Google Calendar. Their retention is independent of the 30 days for call content; the owner manages them directly in Google Calendar. To request deletion of Google data remaining in Sparra, use the contact below. Such a request does not mean instant deletion of the account or all backups.

The use and transfer to other applications of information received from Google APIs comply with the Google API Services User Data Policy, including its Limited Use requirements.

Contact and requests

For questions about your data, access, correction or deletion: [email protected]. If your call concerns a business using Sparra, identify that business so your request can be directed appropriately.

My workspace