Privacy Policy

1.About this document

This notice describes information handling for the AURQENA AI website at www.aurqena.com and companion preview features where enabled. AURQENA provides market intelligence, educational analytics and trading-behaviour coaching. Information processed only on your device is distinguished from information sent to a server.

AURQENA AI's privacy and account-support contact is support@aurqena.com. This notice does not claim that AURQENA is a regulated broker, financial adviser or a legally incorporated entity in any particular jurisdiction.

Support records can include message content, ticket identifiers, authors and timestamps. Internal support-message storage does not by itself mean that an external support email has been sent.

2.Account and authentication information

Account features process your email address, display name, account identifiers, access permissions and authentication status. Password sign-in stores a password hash rather than your plain-text password. Enabled security methods can also require verification challenges, passkey public-key records and session records.

Authentication and security records can include sign-in results, timestamps and hashed network or device identifiers to support account access, investigate failures and reduce abuse. The identity request layer hashes validated IP addresses and user-agent information; separate hosting or proxy logs may handle network information differently. Never send passwords, one-time codes, private keys or broker credentials in a support message or chat prompt.

3.Sign in with Google

If Google sign-in is enabled and you choose it, AURQENA requests only openid, email and profile access. Google identity information is used to verify who is signing in and create or resolve the corresponding AURQENA account. This sign-in flow does not request Gmail messages, Google Drive files or Google Contacts.

The current implementation stores the Google account identifier, issuer, verified-email status, email address and display name for account access. It does not store a Google profile photograph or persist the Google access and refresh tokens returned during sign-in.

The sign-in exchange is processed by Google and AURQENA's authentication service. Stored identity records are handled by the configured hosting and database services. This flow does not send Google identity records to the market-analysis AI provider. You can revoke AURQENA's Google access in your Google Account settings; revocation is separate from requesting deletion of your AURQENA account. Revoking Google access does not automatically end an existing AURQENA session; sign out or use available session-revocation controls separately.

4.MT5 account information and Copilot

Optional account-review features process the trading information you choose to submit or connect. Depending on the connection, this can include account or position identifiers, symbols, trade times, volumes, entry prices, stop-loss and take-profit levels, balance, equity and profit or loss. It is used to explain trading behaviour, identify rule-based risk patterns and prepare coaching feedback.

The current website snapshot-review mode sends your selected snapshot to a server after the in-product consent step; that review mode does not store the snapshot. The mobile snapshot-review mode evaluates its snapshot in device memory. These are different from the real-time bridge mode.

When the real-time bridge is enabled, it sends trade events to the configured backend. Pairing processes your MT5 account login and broker-server name to bind the connection; stored connection records use a hashed binding and masked account label. The backend stores coaching state, baselines, event history and discipline-score information in Redis. The current implementation does not automatically expire this state. Disconnecting a bridge revokes its ingestion key but does not delete previously stored coaching state.

These connections are for read-only analysis. Copilot does not need permission to place, modify or close broker orders. Do not submit a broker trading password in a snapshot or AI chat.

5.AI chat, coaching and voice

Chat requests are processed by AURQENA to prepare an answer. The current market explanation path can send a structured market-evidence summary to the configured Gemini or Ollama provider. That path does not forward the raw customer prompt or MT5 snapshot to that provider. Current real-time account coaching is based on deterministic rules; a planned or optional LLM capability is not evidence that every coaching message uses a third-party model.

If you attach a text file to chat, its filename and a limited text excerpt are added to your draft and processed when you submit it. Avoid adding personal, confidential or financial-account secrets to prompts. Provider routing and feature availability can change; the applicable data-use notice must be reviewed before adding a new processing purpose or sending additional account information to an AI service.

Voice features use your browser or operating system's speech services where available. Microphone input requires permission. Speech recognition may use the browser vendor's remote service; it must not be assumed to run entirely on your device. Text-to-speech output follows your browser or device settings. You can leave voice disabled and use text instead.

6.Cookies and device storage

The website uses cookies for signed-in sessions and short-lived authentication flows, including Google sign-in and verification challenges. Essential authentication cookies help maintain the account session and protect the sign-in flow. Blocking them can prevent sign-in.

Browser storage can also hold interface preferences such as the selected market, and session storage can prevent duplicate live-event processing. Native mobile features use device secure storage for their session grant and local application storage for preferences such as watchlists. These preferences are not the same as the server's account or coaching records.

Successful sign-out revokes the relevant session and clears local session credentials. If revocation or local clearing cannot be confirmed, the app displays further steps. Clearing browser or application storage removes locally held preferences. Neither action by itself is a server-side account-deletion request. Optional browser speech permissions can be revoked in browser or device settings.

7.Service providers and operational information

Vercel serves the website frontend. Google Cloud supplies the configured backend and database services. Google also processes information for Google sign-in and Google Workspace authentication email where enabled. Each provider receives information needed for its function; configuring a provider does not mean every optional feature is active. We do not sell Google sign-in information or use it for advertising.

Operational logging and optional error monitoring can process technical diagnostics, request metadata and performance traces. The optional backend Sentry integration disables request-body capture and default PII capture, but that does not mean no operational information is processed. Hosting, email, authentication and other providers may process information in countries other than your own; this preview does not promise that every copy of information remains in one country.

Native push delivery, affiliate payouts and native purchases must not be treated as connected services merely because a screen exists. Additional providers, payment terms and feature-specific notices are required before those integrations are enabled.

8.Retention, access and deletion requests

Session and verification records have expiry controls, but expiry does not necessarily remove a database row. Account records, security records, backups and optional real-time coaching state have different lifecycles. This preview does not provide a verified automatic account-erasure workflow or a fixed deletion deadline. Server-side deletion requests require manual handling, including consideration of backups and records needed for security or legal obligations.

Contact support@aurqena.com to request access, correction, export or deletion of your information, or to ask about stopping a connection. Use the email associated with your account where possible; identity verification may be needed before acting on the request. Do not include passwords or API keys. Available rights and any exceptions depend on applicable law. Signing out alone does not submit a deletion request.

Revoking Google access, disconnecting MT5, signing out and removing local app data are separate actions. In particular, disconnecting MT5 does not erase coaching state already stored on the backend.

9.Security and future changes

Access controls, password hashing and session protections are part of the implementation. No online service can promise absolute security. Report a suspected account-security issue to support@aurqena.com without including secrets.

This preview is intended for adults and is not directed at children. Contact support if you believe a child has supplied personal information. Material feature or data-use changes will be described in an updated notice and relevant in-product information before a new processing purpose is introduced. The date above identifies this version; commercial-service terms and additional operator information must be provided before paid services are launched.