Google API Data Use

1. Data Mirynna may access

Depending on the permissions the user grants and features they enable, Mirynna may access Gmail messages and metadata, Calendar events and calendar lists, Drive files and metadata, Google Docs and Sheets content, Google Tasks, Google Contacts/People data, and Google Chat spaces or messages.

2. Why Mirynna accesses it

Mirynna accesses Google Workspace data only to provide visible productivity features requested by the user, such as finding relevant email or files, summarizing requested business context, displaying schedules and tasks, helping organize work, and preparing or executing approved actions.

3. Retrieval and storage

Mirynna is designed to retrieve a limited amount of relevant Google Workspace content in response to a user request. Retrieved content is treated as external, untrusted data and is not intended to become a permanent copy in Mirynna merely because it was retrieved. Mirynna may store user-created results such as a task, approved action, note, or memory when the user intentionally creates or saves that object.

4. AI processing

Relevant Google Workspace content may be transmitted to an AI service provider when necessary to fulfill a user-requested AI feature. Mirynna does not use Google Workspace data to create, train, or improve a general-purpose AI or machine-learning model and does not authorize service providers to use that data for unrelated model training.

5. No advertising or sale

Mirynna does not sell Google Workspace data, transfer it to data brokers, or use it for advertising, retargeting, interest-based advertising, creditworthiness, or lending decisions.

6. Human access

Mirynna personnel should not read Google Workspace content except with the user's affirmative permission for support, when necessary to investigate security or abuse, when required by law, or in another circumstance expressly allowed by Google's policies.

7. Authorization and revocation

Users connect Google through OAuth and can revoke authorization through Mirynna or their Google Account security controls. Mirynna stores provider authorization credentials server-side and encrypts stored Google OAuth tokens at the application layer.

8. Limited Use commitment

9. Security

Mirynna uses HTTPS, server-side authentication, organization authorization checks, Google Cloud Secret Manager, encrypted stored OAuth tokens, and separated development/production projects. Additional restricted-scope security requirements are being completed before public OAuth verification.

10. Contact

For questions about Mirynna's use of Google API data, privacy, access, or deletion requests, contact privacy@mirynna.com. General product support is available at support@mirynna.com.