Privacy Policy
Qasper ("Qasper," "we," "our," or "us") is an AI-powered workspace assistant for individuals and small businesses. This Privacy Policy describes the Google account information we access when you connect your Google account to Qasper, how we use and protect it, who we share it with, and how long we keep it.
This policy also includes the additional disclosures below for Qasper's website, public chat, ChatGPT app or connector, MCP endpoints, business profile, booking, and inquiry features.
1. Scope
This policy covers data we obtain through Google OAuth when you connect your Google account to Qasper. It applies to qasper.ai and to any application signed in with the Qasper Google client. Where this policy and our general notices conflict on the handling of Google user data, this policy governs.
2. Google Data Qasper Accesses
When you connect your Google account, Qasper requests the OAuth scopes needed for the feature you choose. You see and approve each scope on Google's consent screen, and you can revoke them at any time from Google Account Settings → Security → Third-party access.
| Scope | What Qasper accesses | Why |
|---|---|---|
openid | A unique, opaque Google account identifier. | Recognize your account when you sign back in. |
email | The email address attached to your Google account. | Identify your Qasper account and send service-related notices. |
.../auth/calendar.events | Create, update, and delete events on Google calendars you choose to use with Qasper. | Add, update, and cancel appointments and linked booking events at your direction. |
.../auth/calendar.freebusy | Read free/busy windows on Google calendars you choose to use with Qasper. | Show availability, answer scheduling questions, and prevent double bookings. |
Additional Qasper App, MCP, Booking, and Inquiry Data
When you or an AI assistant use Qasper through the website, public chat, ChatGPT app, MCP server, or another connected channel, Qasper processes the minimum information needed to complete the requested discovery, booking, inquiry, or business-agent workflow.
| Data type | What Qasper processes | Why |
|---|---|---|
| Business profile and listing data | Business name, slug, category, service area, descriptions, services, price ranges, working hours, supported languages, profile image, contact phone or email, and enabled booking or inquiry features. | Show accurate business information, compare fit, display contact options, and enable bookings or inquiries using owner-approved profile data. |
| Customer request and search context | Search terms, requested service category, location text, country code, coordinates if supplied by the client, service-mode preferences, attribute filters, and conversation context supplied by the AI assistant or user. | Search, rank, and return relevant businesses without inventing missing requirements. |
| Booking and inquiry details | Customer name, phone number, email address, service, requested appointment time, customer address when required for a service, job description, inquiry message, reference number, booking status, and cancellation link when available. | Create bookings, send inquiries, notify the selected business owner or business agent, prevent duplicate bookings, and let the customer and business track the request. |
| MCP and operational logs | MCP client identity when provided, IP-derived request fingerprint, tool name, redacted tool arguments, timing, result counts, errors, and request or fanout identifiers. | Rate-limit abuse, debug reliability issues, audit tool behavior, and confirm that Qasper reliably does what the app promises. |
| External AI assistant context | If you use Qasper through ChatGPT or another MCP client, that client sends tool inputs to Qasper and receives tool results from Qasper. | Operate the integration. Qasper does not control how the external assistant stores your chat history after it receives Qasper's tool results. |
| Billing and subscription data | Plan selection, business contact email used for Checkout, internal profile identifier, selected plan, and checkout correlation identifier sent as Stripe metadata, Stripe customer, subscription, Checkout session, price identifiers, subscription status, billing period, and cancellation flags. | Create and manage subscriptions, reconcile Stripe webhooks, enforce plan limits, and keep required billing records. |
3. How Qasper Uses Google Data
Qasper uses Google data only to provide the assistant features you have asked for. Specifically:
- Just-in-time calendar access. Each Google Calendar request is initiated by you — through chat, a booking page, or a connected channel — and is fulfilled by your dedicated, per-user agent runtime.
- Memory in service of you. Your agent may remember context that helps it serve you better next time (for example, a preferred meeting window). This is stored against your account and used only to assist you.
- No advertising. Qasper does not use Google data to serve or target advertising.
- No model training. Qasper does not use your Google account data, calendar contents, or customer booking data to train AI models — neither our own nor those of any third-party model provider.
- No human reading. Qasper staff do not read your Google Calendar contents in ordinary operations. Narrow exceptions: (a) you ask us to inspect a specific calendar issue while debugging and grant explicit consent, (b) we are compelled by valid legal process, or (c) we detect a clear security threat that requires inspection.
4. Google Limited Use Disclosure
Qasper's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
5. Sharing
Qasper does not sell Google data and does not share it with anyone for advertising. We share the minimum amount necessary in only the following cases:
- Infrastructure providers. Hosting and database providers process data under contract solely to operate Qasper. They have no independent rights to your data.
- AI inference providers. To answer scheduling questions and provide assistant outputs, your agent may send relevant request context and calendar details to a model provider (Anthropic by default; you may configure another). These providers process the content to generate the response and are contractually prohibited from using it to train their models.
- Legal process. When compelled by valid legal process or law, or when sharing is necessary to detect and prevent fraud or abuse.
- Business transfer. If Qasper is acquired or merged, your data may transfer subject to the same protections. For Google data covered by Limited Use, we will obtain explicit prior consent before any such transfer.
- Payment processors. When billing is enabled, Stripe receives the minimum checkout, customer, and internal billing metadata needed to process payment and manage subscriptions, including profile identifier, selected plan, and checkout correlation identifier.
6. Storage and Security
We use technical and organizational measures appropriate to the sensitivity of the data:
- Refresh tokens are encrypted at rest. Your Google refresh token is stored using AES encryption. The decryption key is held in our deployment environment and is not present in the database.
- Transport security. All traffic between your device, Qasper, and Google moves over TLS (HTTPS).
- Calendar contents are not retained. Qasper does not maintain a persistent copy of your Google Calendar events. Calendar data is processed in your agent runtime to fulfill a request and discarded afterwards.
- Booking records. When customers book an appointment with you through Qasper, the booking metadata (time, customer name, service) is stored on our servers so you can see your booking history. This is separate from access to your Google calendar.
- Access controls. Production database access is limited to authorized engineers under contract.
- Billing records. Stripe customer, subscription, Checkout session, price, status, billing period, and cancellation fields are stored so we can reconcile payments and enforce plan limits.
No system can be guaranteed completely secure. If we discover a breach affecting your data, we will notify you in line with applicable law.
7. Retention and Deletion
- While your account is active. We keep your Google refresh token, account email, and Google subject identifier for as long as the integration is connected. Booking records are kept while your account is active.
- When you disconnect Google. Disconnecting Google access — either inside Qasper or from your Google Account settings — deletes your refresh token within 24 hours and revokes our ability to access Google Calendar.
- When you delete your Qasper account. Email [email protected] from the address linked to your account. We confirm receipt within five business days and complete deletion within 30 days. Encrypted backups roll over within 90 days.
- Records we are required to keep. Information we are legally required to retain (for example, billing records) is kept only for the period required by law and then deleted.
8. Optional Product Analytics
Qasper uses PostHog, hosted in the European Union, for product analytics — only after you opt in via the cookie banner.
Analytics events are designed to exclude chat prompts, AI responses, agent thinking content, booking notes, customer phone numbers, customer email addresses, and access tokens.
You can withdraw consent at any time in Settings → Privacy. We do not use analytics data for advertising.
9. Your Controls
You control the connection between Qasper and your Google account at all times.
- Revoke Google access at Google Account Settings → Security → Third-party access, or from your Qasper integrations page.
- Export your data by emailing [email protected].
- Delete your account by emailing [email protected] from the linked address.
- Withdraw analytics consent in Settings → Privacy at any time.
10. Changes to This Privacy Policy
We may update this policy. Material changes are reflected in a new effective date and, where the change affects how we use your Google data, by an in-app notice before it takes effect.
11. Contact
Questions, deletion requests, or breach reports: [email protected].