App privacy · October 20, 2026
Your information in Anomalies Observatory
This notice covers the AO member platform and Anomalies Observatory iOS app, operated by Tether AI Inc. under the Anomaly’s Observatory brand. It describes information handled when you use enabled member features, including Academy, community, trading-account tools and the assistant.
For support and privacy requests, email joshua@tetherai.ca.
Account and membership information
We use your name, email address, profile and account identifiers to sign you in, maintain your account and determine which workspace features you can access. Membership, subscription and entitlement records are associated with your account even when you use the free iOS download.
WorkOS provides authentication. Convex stores and serves application records and uploaded files. Your device also keeps sign-in state and preferences. The iOS app stores its authentication session in the device Keychain.
Connected trading accounts
When you connect a trading account, the platform processes connection details and the account information needed for the features you use. This can include broker and account identifiers, balances, equity, positions, orders, execution history, risk settings and trading performance.
MetaApi and your broker process information needed to connect to and operate supported MetaTrader accounts. Connection credentials are handled as part of that connection process. The platform also stores connection metadata and trading records. Removing a connection does not itself delete your membership, journal or all historical records.
Messages, learning and other content
Enabled features can store community posts, direct messages, attachments, journal entries, chart captures, strategy material and notes that you submit. Academy features store lesson progress, study activity and learning notes.
Content posted to a shared space is available to the audience of that space. Direct messages are addressed to their recipients. Authorized operators may access records when needed to administer the service, investigate a reported problem or provide support. Do not put passwords or brokerage credentials into messages, notes or uploads.
AI assistant and document processing
When you use the assistant, your question, relevant conversation history, selected images or documents, and information retrieved for your request can be sent to OpenRouter and the model provider used for that request. Relevant context can include authorized account metrics, market data, learning material and notes. Responses and conversation records are stored so you can continue your work.
Where document and media processing is enabled, uploaded material may be processed by LlamaParse for document extraction, Voyage AI for search and retrieval, and OpenRouter or OpenAI for transcription. These services receive the material needed for the selected feature. External providers apply their own processing and retention terms. Avoid submitting information you do not want processed by those providers.
Service operation and diagnostics
The service uses technical records such as request times, errors, connection status, processing activity and security events to operate the platform and investigate faults or misuse. Hosting and processing providers may also handle network and device information when servicing requests.
Application services use hosted databases, file storage and supporting services. Depending on the feature, these include Convex, Railway-hosted services and storage, and diagnostic providers such as Axiom and LangSmith where configured. Diagnostic records can contain information about the operation that failed. Providers may process data outside your country, where laws can differ.
Payments, external media and websites
Membership payment processing uses Stripe where billing is enabled. The platform can receive customer, subscription, invoice and payment-status records. Payment details supplied to a payment provider are handled under that provider's terms.
Lesson videos and links can open YouTube or another external service in an in-app or system browser. Those services receive information when you visit or play their content and apply their own privacy practices. Website and waitlist data are described in the separate website privacy policy linked below.
Retention and deletion
Account and workspace records are stored to maintain your access, saved work and history. Available delete controls remove the particular item they describe; deleting a message, disconnecting a broker or uninstalling the app is not the same as deleting your platform account.
Email the support address below to request account deletion or ask about the records associated with your account. We verify the request and assess the affected records and services. Some transaction, security, dispute or legally required records may need to be retained. Backups and records held independently by external providers may have separate retention periods. We will explain any applicable limits when handling your request; this notice does not promise immediate removal from every system.
Your choices and requests
You can contact us to request access to, correction of, a copy of, or deletion of your personal information, and to ask about withdrawing consent for optional processing. Your rights depend on where you live and the processing involved. We may need to verify your identity before acting on a request.
You choose whether to connect a brokerage account, submit content, use the assistant or open external media. Choosing not to use a feature can limit the corresponding functionality. Signing out removes access to the current app session; it does not erase hosted records.
Security and changes
The platform uses authenticated access, role-based permissions and protected connections to its services. No internet service can guarantee absolute security. Contact support promptly if you believe someone has accessed your account without permission.
We will update this notice when the described practices change and revise the date above. A change requiring additional consent must be presented before that processing begins.