Hyperia Privacy Policy

Effective October 19, 2026

This policy describes the Hyperia AI OS service and its ChatGPT integration. The publisher and service contact is Pavel Simakov, reachable at pavel-simakov80@yandex.ru.

Information processed

Hyperia processes account identifiers, profile information and authorization settings; content you submit, such as messages, drafts, files and knowledge sources; data returned by services you connect, such as permitted emails, Threads content and analytics or selected Telegram history; and technical records needed to run, secure and diagnose the service. Features may also use saved public posts and their available metrics as references.

Purpose and access

Data is used to provide requested searches, summaries, drafting, editing, analytics and authorized actions, and to maintain the service. Access is scoped to the signed-in account and its permissions. Connecting the ChatGPT plugin does not grant access to another user's private workspace or mailboxes. Mailbox permissions are selected separately in Hyperia.

AI processing and third parties

Depending on the feature and configured processing settings, AI processing may run on locally hosted models or external AI services. Relevant input and context may be sent to the configured external provider when that feature uses one. Model choice is not a guarantee that every service component runs locally.

When you use Hyperia through ChatGPT, requests and tool results pass between Hyperia and OpenAI. Results may include the account information or content needed for the action you request, such as a selected draft, permitted email or knowledge excerpt. OpenAI and other connected services process information under their own terms and privacy policies. Hyperia does not include account passwords, OAuth client secrets or provider access tokens in normal AI tool results.

Credentials and security

Integration credentials are held in protected credential storage. Access controls and audit records support account isolation and authorized operations. Do not place passwords, access tokens or other secrets in prompts.

Retention and deletion

Saved posts, metrics and user content may remain stored until deleted or a retention rule applies; they are not automatically erased when a browser session ends. Disconnecting a service stops its authorization but does not necessarily delete previously saved drafts, reference material or technical records. Request access, correction, export or deletion by contacting pavel-simakov80@yandex.ru. Account ownership is checked before handling private data requests. Limited records may be retained where required for security or legal obligations.

Your choices

You can review or revoke connected-service permissions, adjust mailbox grants and disconnect the plugin. Before approving external actions, review the content and destination. Requests concerning copies of information already held by OpenAI or another connected service must also follow that service's controls.

Changes and contact

This policy may be updated when features or data handling change. Privacy requests: pavel-simakov80@yandex.ru.