Google Workspace privacy and Limited Use disclosure

Qyra lets you connect a Google account so the assistant can perform the Google Workspace tasks you request. This is separate from using Google to sign in to Qyra, and the two accounts do not need to match.

Effective July 22, 2026

The short versionQyra processes only the Google data needed for your requested feature. It does not build a permanent content index, sell Google data, use it for advertising, or use it to train or improve a shared model.

Google data Qyra can access

With your consent, Qyra may:

search and read Gmail messages and threads;
create Gmail drafts, replies, and sent messages;
search and read supported files in Google Drive;
create and edit Google Docs that Qyra creates or that you authorize it to edit;
list accessible calendars and events; and
create calendar events, including attendees and Google Meet details when you request them.

Google shows the permissions requested before you connect. Qyra shows the connected account, services that are ready, and permissions that are missing.

How Qyra uses Google data

Qyra uses Google data only to provide or improve the user-facing feature you request—for example, summarizing a selected thread, preparing a reply, creating a brief, or finding a calendar conflict. Email, file, attachment, document, and calendar text is treated as untrusted content. It cannot change your autonomy settings, create goals, authorize recipients, or instruct Qyra's tools.

The minimum content needed for a request may be processed on Qyra's servers and by Qyra's configured model provider to generate the requested result. Qyra does not use Google user data for advertising, sell it, use it to train or improve a shared model, or permit unrelated human access. Human access requires your affirmative consent except where narrowly required for security, legal compliance, or abuse investigation.

Storage and retention

Qyra stores encrypted authorization credentials, the connected Google account identity, permission records, provider IDs, synchronization cursors, idempotency receipts, and user-visible action summaries. Qyra does not build a permanent index of email bodies, attachments, or Drive contents. Source content is processed live for the requested task and cleared after processing.

A fact derived from Google content is saved to Qyra's durable memory only after you explicitly confirm that it should be remembered.

Sharing and security

Qyra transmits Google data only to service providers needed to operate the requested feature, under contractual confidentiality and security controls. Qyra uses encrypted transport, encrypts stored credentials, separates tenant data, and keeps Google provider APIs behind its private agent service.

Qyra's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements, and the Google Workspace API User Data and Developer Policy.

Your controls

You can reconnect, switch the connected Google account, or disconnect at any time in Qyra → Settings → Connections → Google Workspace. Disconnecting always deletes Qyra's local Google credentials. Qyra also asks Google to revoke access and reports whether Google confirmed remote revocation.

You may additionally revoke Qyra in your Google Account's third-party access settings. See Delete account or Google connection data for deletion instructions.

Contact

Questions, privacy requests, and deletion requests: [email protected].