Account access is operational. Broker connectivity, broker-authoritative market data, and order execution are not currently operational or authorized through this website.
Account information
Gold Ops OS registration collects a name, email address, and password so Supabase can create and authenticate an account. Email confirmation, session refresh, sign-in, sign-out, and an owner-isolated account profile are operational.
Passwords are handled by the authentication provider and are not intended to be stored in Gold Ops OS application source or public logs. Do not submit broker passwords, API secrets, OAuth tokens, or other trading credentials through public forms.
Sessions, profiles, and technical records
Authentication sessions use browser cookies and server-side verification. The approved Supabase project stores authentication records and owner-isolated profile data.
Hosting, authentication, browser, and network infrastructure may create ordinary technical records such as request times, IP or device information, user-agent data, security events, and error diagnostics. Gold Ops OS does not claim that infrastructure use is log-free.
Aurum product-guide messages
The public Aurum Guide answers from local typed product knowledge. Questions and responses remain in browser component memory for the current page session and disappear when the page reloads.
Public-guide messages are not sent to an external AI provider and are not written to the Gold Ops OS account database by this interface.
TradingView market reference
The public XAUUSD chart is embedded from TradingView. Loading or using it sends browser requests to TradingView, which handles those requests under its own policies.
The TradingView XAUUSD widget is a third-party public market reference and is not broker-authoritative.
Broker and trading data
No cTrader, FP Markets, or other broker account is currently connected to Gold Ops OS. Gold Ops OS therefore does not currently collect broker credentials, broker account balances, positions, orders, or broker-authoritative market data through the public website.
Any future broker connection would require separate authorization, security review, updated disclosures, and verified user controls before activation.
Data choices and current contact limitation
Use accurate account information and protect your credentials. A verified public workflow for account export, correction requests, deletion requests, or direct privacy contact is not currently available.
No fixed public retention period or deletion turnaround is promised until those procedures are formally established. The missing request workflow remains a public-release requirement.