How HermesGEX (hermesgex.com) collects, uses, shares and protects your personal data — the account, payment, usage and cookie information we process, why we process it, and the privacy rights and choices available to you.
2026/05/23
Last updated: May 23, 2026
Hermēs (referred to herein as "we," "our," or "us") respects and is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and protect your personal information when you access hermesgex.com, our terminal app, APIs, Discord channels, and related services (collectively, the "Service").
This policy applies together with our Terms of Service and Disclaimer. By using the Service you consent to this policy.
Authentication data — OAuth identifiers returned by Google or GitHub when you sign in via those providers.
Payment & subscription data — processed by Waffo (our Merchant of Record); we retain only transaction metadata (plan, status, customer ID) and never store full card numbers or CVV.
Activation codes — records of codes you redeem or that are issued to you.
User content — trade journals, alert templates, custom parameters, and notes you create in the terminal.
Support & community communications — emails, contact-form submissions, Discord direct messages you send us.
Device & log data — IP address, browser type, OS, device fingerprint, timestamps, referrer, error stack traces.
Usage data — pages visited, click events, API call records and frequency, feature-usage patterns.
Cookies & local storage — for session persistence, theme/timezone memory, A/B experiments, and analytics (see Section 6).
MT5 / MotiveWave / Bookmap integration metadata — when you opt into these third-party integrations we collect only the minimal binding identifiers (account ID, broker, server name); we do not read your live positions or order content unless you explicitly enable a corresponding module.
For specific operational tasks Hermēs may engage third-party processors (e.g., automated content classification, narrative review of pushed materials). When such processing applies:
We send processors the minimum input necessary to complete the task (e.g., a current GEX summary, market regime label).
We do not transmit personally identifiable information such as your email, name, or payment data to those processors.
Processors handle inputs and outputs under their own privacy and retention policies. Where the processor offers that option, we have requested via API contracts that they not use your inputs to train their models.
We disclose your information only in the following situations:
Service providers (data processors) — cloud hosting (Vercel/Cloudflare/AWS), databases (Postgres/Redis), email (Resend), analytics (Plausible), AI models (OpenAI/Anthropic/Google), payments (Waffo, our Merchant of Record). Each is bound by a data processing agreement (DPA).
Legal requirements — to comply with subpoenas, court orders, or lawful government/regulatory requests; to protect the rights, property, or safety of us or others.
Business transfers — if Hermēs undergoes a merger, acquisition, or asset sale, your information may be transferred as part of the business assets; we will notify you by email or in-app notice before the change.
Your consent — any other disclosure with your explicit consent.
We do not sell or rent your personal information for marketing purposes.
The Service is not directed to children under 13 (or a higher age where applicable law requires). We do not knowingly collect information from children under 13. If we discover such collection we will delete it immediately.
Hermēs operates primarily from the United States. If you access the Service from the EU, UK, or other jurisdictions, your information will be transferred to U.S. servers and the locations of the service providers identified above. We rely on Standard Contractual Clauses (SCCs) and similar mechanisms to ensure lawful cross-border transfers.
We may update this Policy from time to time. Material changes will be communicated by email or in-app notice at least 30 days in advance. The updated Policy takes effect upon posting.