Privacy Policy
Last updated: 2026-10-30. This policy covers Personal AI Workspace, a personal, single-user project run by an individual developer ("we", "the developer"), and this website (personalaiworkbench.com). Contact: [email protected].
1. Who uses the application
The application is intended for use by its owner only, with the owner's own Google account. It is not offered to the public and no other person's Google data is intentionally accessed. This website itself has no accounts, forms, advertising, analytics or tracking cookies.
2. Google user data we access
With the owner's explicit consent through Google's OAuth consent screen, the application requests read-only access to the following data in the owner's Google account:
- Google Drive (files, read-only; scope
drive.readonly) - to find and read files to answer the owner's questions. - Gmail (messages, read-only; scope
gmail.readonly) - to search and summarise the owner's email on request. - Google Calendar (events and calendar list, read-only; scopes
calendar.events.readonly,calendar.calendarlist.readonly). - Google Contacts (read-only; scope
contacts.readonly). - Google Docs / Drive file access (scopes
documents,documents.readonly,drive.file) - only when the owner connects a Docs or Drive tool, and only for documents the owner chooses. - Basic identity (
openid,email) - to confirm which Google account is connected.
3. How we use Google user data
Google user data is used only to provide the user-facing features described above: answering the owner's own requests. It is not used for advertising, profiling, selling, credit or lending decisions, or to train generalized AI or machine-learning models. No human reads the data other than the owner.
4. Storage and retention
- The applications (Hermes Agent and OMP) run on computers controlled by the owner. OAuth tokens are stored locally on those computers, protected by the owner's operating-system account permissions (for Hermes, a file readable only by the owner's user account; for OMP, its local credential database).
- Content read from Google is held in memory to answer a request. Hermes Agent has a local long-term memory feature that can keep short notes derived from conversations, which may include information originally read from Google services. This memory is stored on the owner's computer and can be inspected and deleted by the owner at any time. Conversation history kept by these tools is also stored locally.
- We operate no server that collects or stores Google user data. This website is static, stores no user data, and sets no cookies. The cloud provider that serves the website (Cloudflare) may keep standard web server logs of requests to the site.
5. Sharing and AI model providers
We do not sell or share Google user data with third parties. The assistants use an AI language model to compose answers. Hermes Agent can run on a model hosted on the owner's own hardware or on a hosted AI provider, and is currently configured to use a hosted provider (OpenAI). OMP, as a coding agent, also uses hosted models. When a hosted provider is used, the portions of Google data relevant to a request are sent to that provider solely to generate the answer, under that provider's own terms and data policies; the owner chooses which providers to enable and is responsible for choosing providers whose terms are acceptable. We do not use Google user data to train or improve AI models and do not otherwise transfer Google user data, except as required by law or to protect against abuse.
6. Compliance with Google policy
Personal AI Workspace's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
7. Revoking access and deleting data
The owner can revoke the application's access at any time at myaccount.google.com/permissions, and can delete locally stored tokens and notes from the computers where the application runs. After revocation the application can no longer read Google data. To ask about or request deletion of any data related to this project, contact [email protected].
8. Security
Access is limited to read-only scopes wherever possible, tokens are kept in owner-only files, and the application runs on the owner's own infrastructure. No system is perfectly secure, and we will update this policy if our practices change.
9. Changes
If this policy changes, the updated version will be posted on this page with a new date.