Privacy Policy

Hermes API · Effective 30 October 2026

This policy describes Hermes API’s Google Ads and Google Workspace integrations, operated by Omar Abd Alaziz. The application is used by the operator and authorized users to research advertising keywords, analyze performance, and carry out instructed advertising and Workspace tasks. This public information website does not offer account registration.

1. Data we access

• Account identity: the Google account identifier and email address needed to identify the connected account.
• Authorization credentials: OAuth access and refresh tokens used to maintain the connection. Google passwords are not requested or stored by this integration.
• Advertising data: accessible customer and manager account identifiers, account settings, campaigns, ad groups, ads, keywords, budgets, and performance metrics, as needed for a requested task and permitted by the connected account.
• Planning inputs and results: seed keywords, website URLs, locations, languages, keyword ideas, historical metrics, and forecasts, where Google makes these available.
• Workspace content, when connected: Gmail messages, headers, attachments, labels and settings; Drive files and activity; Docs, Sheets and Slides content; Calendar events; contacts; tasks; Forms and responses; Google Chat messages, spaces and memberships; Meet spaces; and Apps Script projects and deployments. Access is limited by the granted scopes and the user’s underlying account permissions.
• Operational records: user instructions, generated reports, conversation history, and diagnostic records needed to operate and troubleshoot the assistant.

2. Why we use it

We use this data to identify the connected account, answer advertising questions, produce research and reports, prepare campaign recommendations, and execute explicitly instructed account changes. For connected Workspace services, we also use data to search and summarize information, organize files and messages, prepare or send instructed communications, edit documents, manage schedules, and perform other user-directed tasks in the connected service. Google permissions can permit management as well as reading; actual actions remain limited by the authorizing account’s permissions and the operator’s instructions.

3. AI processing and sharing

Hermes is an AI-assisted service. Relevant task instructions, advertising data, and requested Workspace content may be sent to the configured AI service, currently OpenAI, to generate the requested analysis or response. When users interact through Telegram, their messages and the responses sent there are processed by Telegram. Users should authorize only accounts and data they are entitled to use with these services.

Hosting and storage providers process data needed to operate the service. The assistant runs on infrastructure hosted by Hostinger; encrypted recovery backups may be stored in the operator’s Google Drive. The public information pages are hosted through OpenAI Sites and its hosting infrastructure. Service providers may process data in countries different from the user’s location.

We do not sell Google user data, use it for unrelated advertising, or use it to build or train our own generalized AI models. Access by the operator or authorized support personnel is limited to operating the requested service, troubleshooting, security, and legally required purposes. Relevant data may also be disclosed when required by law.

4. Google API data

Hermes API’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google data is used to deliver the user-directed functionality described in this policy.

5. Storage and security

Connection credentials are kept in restricted server-side storage. Recovery backups are encrypted. Access controls and transport encryption are used to protect operational data. No online system can guarantee absolute security. This information website does not embed account credentials, advertising reports, Workspace content, or live account connections in its public pages.

6. Retention and deletion

Credentials are retained while a connection is in use. Reports, conversation records, and operational data may be retained for ongoing work, troubleshooting, and recovery until the operator removes them or a deletion request is fulfilled. Historical encrypted backups are retained without automatic expiry under the operator’s backup settings.

To request disconnection or deletion, email omarabdlaziz.work@gmail.com with the relevant account email and the scope of the request. Do not send passwords or access tokens. We may verify your authority before acting. We will identify the relevant active records and retained backup copies and confirm the deletion steps and any legal or technical limits. Removing live data does not automatically remove historical backups; backup deletion must be addressed as part of the request.

7. Your controls

You can revoke Google access at any time through Google Account connections. Revocation stops future authorized access but does not itself delete previously stored reports or backups. Contact the operator to request deletion, correction, or information about stored data.

8. Website visits

These static pages do not include analytics scripts, advertising pixels, forms, or application-set cookies. The hosting provider may process IP addresses and request metadata for delivery, security, and operational logging.

9. Updates and contact

Changes will be published here with an updated effective date. Material changes to the use of Google data will require updating the relevant disclosures and obtaining any required authorization before the new use begins.

Operator: Omar Abd Alaziz
Contact: omarabdlaziz.work@gmail.com