This section applies to all data that archmax Cloud receives through Google APIs, for example from Gmail, Google Drive, Google Sheets, Google Docs and Google Calendar (Google user data).
archmax Cloud'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: https://developers.google.com/terms/api-services-user-data-policy
Which data we access: When you connect a Google service, archmax Cloud only requests the permissions for that service:
- Gmail: read emails and settings, manage drafts, send emails on your behalf and retrieve your email address,
- Google Drive: see, download, create, edit and delete files in your Google Drive,
- Google Sheets: see and edit spreadsheets, and see and manage files in Google Drive in order to find spreadsheets,
- Google Docs: see and edit documents, and see and manage files in Google Drive in order to find documents,
- Google Calendar: see calendars and events, and create, change and delete events.
Which of this data an agent actually accesses is determined, within these permissions, by the workflow the customer defines.
How we use it: We use Google user data solely to provide the features of archmax Cloud that you or your organization use. An agent reads, creates or changes data in Google when a workflow, a chat or a test calls for it, and the results appear in the respective session. We do not use Google user data for advertising, marketing, profiling or analytics, we do not sell it, and we do not use it to develop, improve or train generalized or non-personalized AI or ML models. Statistics we compile about the use of archmax Cloud do not contain Google user data.
Who receives it: Google user data is only received by:
- the language model the customer has configured for its agents, to the extent an agent needs the data for its task (see section "AI processing by language models"),
- the design agent's language model at Amazon Bedrock in the EU, when you use the design agent and it reads results of earlier sessions or, with your approval, tries out a connection,
- the members of your organization, who can use the connection and see the sessions of its agents, and people to whom the customer makes an agent available through a chat, webhook or MCP endpoint,
- our hosting provider as processor (see section "Hosting"),
- authorities, where we are legally required to disclose it.
In the event of a sale of our business or a comparable transaction, we only transfer Google user data with your prior explicit consent.
Who at archmax can access it: Our staff only read Google user data if you have explicitly agreed to this for specific content, for example as part of a support request, if it is necessary for security purposes such as investigating abuse, or if the law requires it.
How we store and protect it: We store the access tokens issued by Google encrypted with AES-256-GCM. They never reach your browser or a language model; archmax Cloud uses them solely on the server to call Google APIs. Data an agent retrieves from Google is stored as part of the respective session in our database and object storage in the Netherlands. When the customer deletes the session, the agent or the organization, this data immediately becomes inaccessible to everyone.
How to end access: You can revoke archmax Cloud's access at any time in your Google Account at https://myaccount.google.com/connections. archmax Cloud can then no longer access your data at Google, and the stored access tokens become ineffective. You can request the deletion of the access tokens and your Google user data at any time at info@archmax.ai; we then delete them within 30 days, unless statutory retention obligations apply.