Google API Services — Limited Use Disclosure

Last updated: May 28, 2026

Compliance Statement

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

What This Means in Practice

When you connect a Google account to Krowd (Google Calendar, Google Sheets, Google Docs, Google Drive, or Gmail), the data we read from those Google APIs is used only to provide the user-facing feature you enabled — for example, showing your real-time calendar availability to a booking visitor, populating a webshop catalog from a linked spreadsheet, or using a Google Doc as the system prompt for your AI agent.

We do not:

• Use Google User Data to train, fine-tune, or evaluate generalized AI/ML models.
• Sell Google User Data.
• Transfer Google User Data to third parties for advertising or unrelated purposes.
• Allow humans to read Google User Data, except (a) with your explicit consent for specific messages, (b) when required for security investigations or to comply with applicable law, or (c) when the data has been aggregated and anonymized for internal operations.

AI Provider Segregation

Krowd supports multiple AI providers (OpenAI, Anthropic Claude, Google Gemini, xAI Grok, DeepSeek, Groq). Because some third-party AI providers reserve the right to use submitted content to train their general models, we enforce strict data segregation:

DeepSeek is never sent Google User Data. Any widget that reads data from a Google API (Google Doc system prompt, linked Google Sheet, Calendar function) cannot be served by our platform DeepSeek fallback. The widget owner must configure their own OpenAI, Anthropic, or Google AI API key — providers whose enterprise terms forbid training on API-submitted content.

Enforcement is technical, not promissory: the segregation is implemented in our API-key resolver, our platform-chat endpoint, our fallback LLM dispatcher, and the Google API readers themselves (which tag returned data with a runtime marker the dispatchers check before invoking any prohibited provider).

Scopes We Request

Depending on the dashboard tools you activate, Krowd will request access to the following permissions:

• https://www.googleapis.com/auth/calendar
  To list calendars, check free/busy availability, and create booking events on your behalf for the Calendar Booking feature.
• https://www.googleapis.com/auth/calendar.events
  To read and write calendar events for the bookings you create.
• https://www.googleapis.com/auth/spreadsheets
  To read product catalogs, data sources, and write conversation/contact data to spreadsheets you select.
• https://www.googleapis.com/auth/drive.file
  To access only the specific Google Docs / Sheets files you pick using the Google Picker.
• https://www.googleapis.com/auth/userinfo.email and userinfo.profile
  To show which Google account is connected.

Data Retention & Deletion

OAuth tokens are stored encrypted at rest. You can revoke Krowd's access at any time from your account settings (disconnect button) or directly via your Google Account permissions page. Revocation immediately invalidates our tokens and stops all further reads. Cached data fetched from Google APIs (e.g., short-TTL spreadsheet caches) is purged within 10 minutes of revocation.

Questions

For questions about how we handle Google User Data, contact us at hello@getkrowd.com, or review our baseline Privacy Policy and Terms of Service.