Privacy information
Matt Personal Assistant (MattGPT) runs locally with Hermes Agent. This page explains the application’s current data practices.
Google data accessed and used
The assistant uses its owner’s authorized Gmail messages to answer email questions, find reservation details and prepare briefings. Email is being migrated to Hermes’s Himalaya skill using Google IMAP and an owner-created app password. This allows mailbox reading and saving owner-requested unsent drafts without a Google OAuth email client. Calendar continues to use a separate Google OAuth authorization. Calendar access supports reading visible calendars and preparing approved event additions or edits. Basic Google identity information verifies the connected account. Access is intended for the account owner only.
The configured email adapter exposes only reading and saving unsent messages into Gmail Drafts. No SMTP sending backend is configured. An app password is a mail credential with broader potential access than the operations exposed by this adapter. Its owner reviews and sends saved drafts manually. During migration, the older OAuth draft adapter also blocks send endpoints.
The application does not sell Google user data, use it for advertising or contain a custom model-training pipeline. Matt Personal Assistant’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Storage and processing
Google authorization tokens and the email app password are stored locally using Windows account-bound encryption. The email CLI retrieves its password through a local credential command; the password is not written into its configuration file. Conversations, retrieved content, notes and operational logs may also be stored locally by Hermes; those records are not all encrypted by the application’s token vault. The owner controls the Windows account and local installation.
Relevant content may be sent to the configured OpenAI service to answer the owner’s requests, subject to that account’s applicable terms and settings. Telegram carries conversations between the owner and the assistant. If spoken replies are enabled, reply text may be processed by Microsoft’s speech service. Reservation providers receive details as part of owner-authorized booking steps. These services have their own privacy policies. The Nous managed Google connector is not connected in the current deployment.
Retention, deletion and control
Local records remain until the owner removes them or the relevant Hermes retention settings delete them. The owner can revoke access in Google Account settings and remove locally stored authorization records. Revocation prevents future access but does not automatically erase prior conversations, logs, saved drafts or calendar events. The owner can manage those separately in Hermes and Google.
For questions or a data-deletion request, contact mattcabrices@gmail.com. The application owner manages the local installation and its records.
Changes
This page will be updated when the application’s data practices change. The effective date above identifies the current notice.