Privacy Policy

Effective date: October 30, 2026

This policy describes how receptionist.today handles information on its website and in customer workspaces. For privacy questions, access requests or deletion requests, contact lesleybaars@gmail.com.

Account and receptionist information

We process account identity, business configuration, contacts, appointment details, follow-up requests and conversation text needed to provide the service. Live audio is transmitted for speech processing. We do not retain raw call audio as a workspace recording. Native records are separate from optional Google Workspace integrations.

Google data we access and how we use it

Google account sign-in provides your account identifier, email address and basic profile information. Connecting a Workspace service is a separate choice. We request permissions for the service you select.

• Google Calendar: event identifiers, titles, descriptions, dates, times, time zones, availability, attendee details and conference links are used to display your connected calendar, check scheduling conflicts and create appointments you confirm.
• Gmail read access: message and thread identifiers, sender and recipient addresses, subjects, dates, labels, snippets and message text are used to display your connected inbox and sent messages. Message text is fetched when you open a message. The Gmail inbox is separate from our native Postal email service.
• Gmail send access: the recipient, subject and message you review and confirm are submitted to Gmail to send from the connected account. This permission does not authorize mailbox deletion or modification.

We use this Google data to provide the connected features you request. Google data is not sold, used for targeted advertising, used for credit or lending decisions, or transferred to data brokers. We do not use raw, derived, aggregated or anonymized Google Workspace data to train or improve generalized AI or machine-learning models. The connected Gmail inbox does not submit message content to our native email draft assistant.

Google Limited Use

The use and transfer of information received from Google APIs, including raw and derived Google Workspace user data, adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Transfers and service providers

Google receives the API requests needed to operate the Google features you authorize. Our hosting and database providers process account, authorization and saved workspace information to operate the service. Google authorization tokens and saved appointment copies are stored in our hosted application database. Connected Gmail message bodies are returned to your signed-in browser for display; they are not copied into our native Postal mailbox. Native Postal and SES delivery are separate services and do not automatically receive your connected Gmail inbox.

Voice and AI providers process the live receptionist interactions needed for the native voice service. Connecting Google does not itself authorize sending your Gmail inbox to those providers. Google Workspace data must not be transferred to an AI provider for generalized model training.

Security and human access

We use HTTPS for public application and Google API traffic, authenticated workspace access, authorization checks and protected server-side storage for Google tokens. Tokens are not exposed to browser scripts. Hosted storage uses the protections supplied by our infrastructure providers. Authorized operators may access information when necessary to investigate support or security incidents or meet legal requirements; access is limited to those purposes.

Retention, disconnection and deletion

Google connection information is retained while a connection is configured. Turning off a feature stops its use without deleting its saved authorization. Disconnecting a feature stops access through that feature. When no Google integration remains connected, the application removes its stored Google tokens and connection metadata. You may also revoke access directly in your Google Account permissions.

Gmail message bodies are fetched for display rather than maintained as a native mailbox copy. App-created appointment records, Google event references and confirmed-action records may remain in your workspace so you can retain its history. Disconnecting Google does not delete events or messages from your Google account, or erase existing native workspace records.

Workspace records are retained while needed to provide account history and service operations. The account deletion control archives the workspace and revokes account sessions; it is not an immediate purge of retained records. Contact us to request deletion of retained personal data. Deletion requests are handled by support, subject to applicable legal retention requirements.

Analytics

Website and feature analytics may include page interactions, demo outcomes, durations, timings and aggregate audio-byte or text-length measurements. Analytics must not receive Google message bodies, calendar contents, raw audio, transcripts, email addresses, phone numbers or authorization credentials. We do not use Google Workspace content to build advertising audiences.

Your choices

You can manage Google services in Settings → Integrations, revoke Google access in your Google Account, and contact us about access or deletion. Calendar, contacts and email records supplied by our native services remain separate from Google connections.