Briq — Google API Services Disclosure

Last updated: August 13, 2026

This page describes how Briq ("we," "our," "us"), the platform available at briq.ai, accesses, uses, stores, and shares Google user data, in accordance with the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.

Limited Use Statement

Briq's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

Google Workspace user data is never used to develop, improve, or train generalized or foundational artificial intelligence (AI) or machine learning (ML) models — whether our own or any third party's.

What Google Data We Access

When you choose to connect a Google account to the Briq platform, we request the following OAuth scopes:

  • gmail.readonly — read-only access to your Gmail mailbox, used solely to retrieve business documents (such as invoices, purchase orders, order acknowledgments, delivery tickets, and credit memos) from senders, subjects, or labels that you explicitly configure for automated import.
  • userinfo.email and userinfo.profile — your email address and display name, used only to identify the connected account within your workspace.

We do not request or access any other Google user data. Connecting a Google account is optional and is never required to use Briq.

How We Use Google Data

Google user data is used exclusively to provide the user-facing document ingestion feature you configure:

  1. Retrieving emails and attachments that match your configured filters.
  2. Extracting structured business information (e.g., vendor, amounts, line items) from those documents so they appear in your workspace.
  3. Displaying connection status and sync history to you.

We do not use Google user data for advertising, and we do not sell Google user data to anyone.

Use of AI/ML in Processing

Where AI models are used to extract structured fields from documents retrieved from Gmail, the data is processed transiently through paid, stateless API inference calls to the following providers: Google Gemini API (paid tier), OpenAI API, Anthropic API, and Groq API. Under the terms of the plans we use, these providers do not use our API inputs or outputs to train or improve their models. Google user data is never transferred to any AI service that would use it for model training.

We do not operate any self-hosted or offline AI models. All AI processing occurs via the provider APIs described above.

Storage and Security

OAuth tokens and imported documents are stored encrypted at rest and in transit, isolated per customer workspace. Access is limited to the systems required to provide the feature described above.

Sharing

We do not transfer Google user data to third parties except as necessary to provide the feature you configured (the inference API calls described above), to comply with applicable law, or as part of a merger or acquisition with prior notice to you. Humans do not read your Google data except with your explicit permission (e.g., a support request), for security purposes, or where required by law.

Retention and Deletion

You can disconnect your Google account at any time from [Settings → Email Sources], which revokes our access and deletes stored tokens. You may also revoke access via your Google Account permissions page. To request deletion of imported data, contact us at support@briq.ai.

Contact

Questions about this disclosure: privacy@briq.ai