Who operates this integration
Ariel Nunez operates this private integration for authorized personal and Pillarline work. Contact: ariel@pillarlinegroup.com.
Google data accessed
For each separately connected account, the integration can access email messages and their metadata; calendar events; Drive file metadata and the contents of relevant documents and spreadsheets; and contacts, according to the permissions granted to the applicable role. Google permissions can cover the connected account’s accessible files and messages. Workflows should retrieve only the information relevant to an authorized task.
The current Hermes V1 grants are read-only. The Google sign-in and consent screens are handled by Google. This information site does not collect account passwords or authorization codes.
Purpose and processing
Data is used for authorized inbox review, summaries, action items, calendar planning, document context, and preparation of drafts for human review. Personal and Pillarline accounts retain separate credential stores and operating context.
Retrieved information may be processed by configured AI model providers to perform the requested work. Task-relevant summaries and outputs may be stored in the owner’s existing Notion operating records or delivered through the owner’s configured Telegram reporting channels. These services have their own processing and retention practices. The owner controls which services and workflows are used.
Google data is not used by this integration for advertising or sold. Google API data is to be used only for the authorized functionality and in accordance with the Google API Services User Data Policy, including its Limited Use requirements.
Storage and access
Google authorization credentials are stored on the owner’s server with restricted filesystem permissions. The roles use separate credentials and routing rules. The current Hermes profiles share an operating-system user; role routing is not a separate operating-system security boundary.
Selected outputs may remain in review files, Notion records, delivery history, and backups. This deployment does not currently implement a universal automatic deletion period across those systems.
Revocation and removal
The account owner can revoke Google access through Google Account settings and can request removal of stored credentials or task outputs by contacting the operator. Revoking Google access stops future authorized API use; it does not automatically erase copies already saved in other systems or backups. Removal must be handled in those systems as applicable.
Changes
This notice should be updated before materially changing the integration’s purposes, processing destinations, or permissions. Broader Google access requires the applicable account’s consent.