Privacy policy

What the connector accesses

You authorize each account separately through Google. The connector requests identity information and read-only access to Gmail, Calendar and Drive. Its supported reads include:

• Account identity: your Google account identifier, email address, chosen account label and granted permissions.
• Gmail: thread and message identifiers, headers, snippets, message text, labels and attachment metadata. Version 0.1 does not make separate attachment-download requests. Gmail message responses may include inline MIME data; the connector returns bounded message text and attachment metadata.
• Calendar: calendar names and identifiers, event details, descriptions, attendees, time zones and availability.
• Drive: file names and metadata, plus limited text from supported text files and Google Docs. Unsupported file types return metadata only.

Google’s permission grants may cover more information than a particular request needs. The connector makes supported, bounded read requests for the selected account. Version 0.1 cannot send email, create drafts, edit calendar events or files, or change sharing permissions.

How data is used and shared

Google data is used to provide the requested Hermes features, such as finding an email, answering a question about a document or checking a schedule. The connector returns the requested information to Hermes.

When you ask Hermes to use Google information, relevant content can be included in requests to the model provider configured in Hermes. That provider processes the content to generate the answer. Review its terms, data controls and your Hermes configuration before using sensitive information. Provider retention and processing vary; this policy does not promise zero retention or identical data practices across all providers.

The connector does not sell Google user data, use it for advertising or ad targeting, or train generalized AI or machine-learning models with it.

Where information is stored

OAuth credentials, including renewable access credentials, are stored in a private local account store on the computer running the connector. Local file permissions restrict access to its operating-system user. Account identity, labels, permissions and connection status are stored alongside those credentials. Credentials are not returned in connector tool results.

The connector does not maintain a separate mailbox or document archive. Information returned to Hermes can be retained in conversation history, logs or memory according to Hermes settings and use. Local backups may also contain retained records. A configured model provider may retain request data under its own terms and settings.

Connection records remain locally until removed. Hermes records and backups follow their separate retention and deletion controls; revoking Google access does not erase information already retained there.

Your account and deletion controls

You can revoke the connector’s Google authorization at any time in Google Account connections. This stops future access under that authorization.

Disabling an account locally prevents this connector from using it. Disabling does not revoke the Google grant or delete the local credentials. To remove local connection records or address information retained in Hermes, contact the operator or use the relevant local storage and Hermes controls. Version 0.1 has no automated account-record deletion command.

Removing the connector’s records does not delete the original mail, calendars or files in Google. To delete content retained by an external model provider, use that provider’s controls or contact that provider.

Google API Limited Use

Idlecore Google’s use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements. Google data is used for the disclosed, user-facing connector features. Any transfer needed to provide those features requires the user’s consent and must remain consistent with that policy.

This website

These are static information pages. They contain no analytics scripts, advertising trackers, forms, Google sign-in or OAuth callbacks. The connector does not send Google account credentials or retrieved Google content to this website.

Vercel hosts these pages and may process standard web request metadata, such as your IP address, requested URL, browser information and request time, to deliver and protect the site. That hosting activity is separate from the locally running connector.

Contact and changes

For questions about this policy, access or local deletion, contact Osman Egal at ozman.egal@gmail.com.

This policy will be updated when the connector’s data practices change. New data uses or permissions will be disclosed and require appropriate consent before they are enabled.