Privacy policy
JB Hermes Workspace is a privately operated productivity integration for authorized accounts. This policy covers its use of authorized Google account data and this informational website. It is not a public service for registering unrelated users.
Information accessed
With the account owner's consent, and depending on granted permissions and requested tasks, the integration may access:
- Account identity information, such as the connected email address.
- Gmail messages, headers, sender and recipient information, attachments, and drafts.
- Google Drive file metadata and file contents, including Google Docs and Sheets.
- Google Calendar lists, event details, and availability.
- Google Contacts information.
OAuth credentials and tokens are used to maintain authorized access. The integration does not require users to provide their Google password to the assistant.
How information is used
Information is used to perform account-owner-authorized productivity tasks: retrieve and summarize content, answer questions, provide scheduling context, locate contacts, and prepare email drafts. Permissions are not permission to publish or broadly redistribute private content.
The intended operating policy is read access and draft creation. Automated sending is to remain disabled until separate recipient and approval controls are implemented and tested. Google's draft-management OAuth scope also permits sending; that scope does not itself enforce this policy.
AI processing and service providers
Selected message text, documents, attachments, calendar information, contact information, and task context may be transmitted to the external AI provider configured for the assistant handling an authorized request. Processing is not necessarily confined to the owner's computer. The provider and model can vary by assistant and configuration; contact the operator for the provider applicable to a particular workflow.
Transfers of Google user data are limited to what is necessary to provide the authorized user-facing features, consistent with Google's policies. Service providers may process request content and technical logs under their applicable terms and retention settings. No blanket zero-retention claim is made. Restricted data must not be routed to a provider without appropriate authorization and safeguards.
The operator does not sell Google user data, use it for advertising, or use or permit its use to train generalized AI or machine-learning models. Authorized inference to fulfill a user's request is distinct from model training. Provider settings and terms must support these restrictions before Google data is processed.
Storage and retention
Credentials are to be stored outside the public website and shared content stores. Selected content and generated outputs may remain in assistant conversation histories, local working files, user-requested notes, drafts in Google accounts, and backups. These can persist after the original task finishes; no automatic deletion period is promised.
The operator retains information only as needed for authorized tasks, ongoing user-requested records, security, or applicable legal obligations. Account owners may request deletion of retained application data and local credentials using the contact below. Provider-side records and backup copies may be subject to their own retention schedules and applicable obligations.
Revocation and deletion
To stop future authorized access, remove JB Hermes Workspace from Google Account connections. Revocation does not automatically delete copies already retained in assistant histories, notes, drafts, or provider systems. Request deletion separately by contacting the operator and identifying the connected account and records concerned. Do not send passwords, tokens, or sensitive document contents with the request.
Human access and security
Access is limited to the account owner and authorized operation of the integration. Human access to Google user data is permitted only where allowed by Google's policies, including affirmative user agreement to view specific data, security needs, or legal requirements. No security method can guarantee absolute protection. Sensitive workflows require appropriate consent and safeguards before use.
This website
These static pages do not contain analytics scripts, advertising trackers, sign-in forms, or application code that reads Google accounts. The hosting provider may process ordinary server access logs, such as IP addresses, request times, and browser information. Reading these pages does not grant the integration access to a Google account.
Google API Limited Use
JB Hermes Workspace'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.
Contact and changes
Authorized users can contact the operator for privacy, deletion, and support requests through the existing private communication channel used to arrange their access. Identify the connected account and request, but do not include passwords, access tokens, or sensitive document contents.
Material changes will be reflected on this page with an updated date. Additional consent will be sought where required before information is used for a materially different purpose.