TRION

Privacy Policy

Last updated: 2026-06-01

This Privacy Policy explains how TRION collects, uses, stores, shares, and protects personal information in connection with the TRION closed beta. TRION may accept users globally, including users in the United States and the European Union/European Economic Area.

This policy matches TRION's current beta boundary:

  • TRION Beta is simulation-only and paper-only.
  • TRION Beta is not a live trading system.
  • TRION Beta does not connect to brokers.
  • TRION Beta does not place real orders.
  • TRION Beta does not provide investment, legal, tax, or financial advice.
  • TRION's AI features are advisory and assistive only.

1. Who We Are

TRION is an AI-assisted trading research, validation, market-intelligence, and simulation workstation currently being prepared for a closed beta.

For the closed beta, TRION is operated by:

Kim Berthilson, operating the TRION project as a private individual.
Contact: info@usetrion.com
Operator details will be updated when the TRION company is registered.

For privacy questions or requests, contact info@usetrion.com.

2. Scope of This Policy

This Privacy Policy explains how TRION collects, uses, stores, shares, and protects personal information in connection with:

  • the TRION desktop application;
  • TRION beta services;
  • TRION-managed hosted AI/LLM services;
  • beta feedback, support, and troubleshooting;
  • product improvement and security monitoring;
  • legal acceptance records.

This policy applies to closed beta users who have been invited to test TRION.

3. Closed Beta and Local App Model

TRION's first beta is expected to be a local desktop application without normal public account registration. Even without a normal user account, TRION may process data centrally to support the beta, improve the product, debug issues, manage AI usage, and provide user-request tools.

TRION may use a beta participant identifier, invite identifier, installation identifier, or similar technical identifier to connect app activity with a specific beta user or installation.

4. Information We May Collect

4.1 Beta participant information

We may collect:

  • name or display name;
  • email address;
  • invitation status;
  • beta participation status;
  • support and feedback messages;
  • legal document acceptance records.

4.2 Application and device information

We may collect:

  • installation identifier or beta participant identifier;
  • app version;
  • operating system and device information;
  • language/region settings;
  • crash reports and error diagnostics;
  • logs needed to troubleshoot the application;
  • timestamps, request IDs, and correlation IDs.

4.3 Strategy and research data

Depending on beta features used, we may collect or store:

  • StrategyDrafts;
  • strategy descriptions and user instructions;
  • strategy revisions;
  • backtest requests and results;
  • validation results;
  • learning/refinement records;
  • market-context settings selected by the user;
  • user-created notes or research inputs.

4.4 AI prompts, chat messages, and AI outputs

TRION may collect and store:

  • prompts submitted to TRION AI features;
  • Strategy Builder chat content;
  • AI-generated responses;
  • structured AI outputs and draft strategy proposals;
  • safety and validation outcomes related to AI outputs;
  • usage, quota, rate-limit, and cost-related metadata.

TRION stores this information for debugging, product improvement, safety review, support, abuse prevention, and quality control.

4.5 Market and trading research context

TRION may process:

  • selected symbols and timeframes;
  • market context requested by the user;
  • candle/import status;
  • StrategyContextSnapshot usage;
  • TradeQuality assessment usage;
  • paper/simulation-only workflow metadata.

TRION does not collect broker credentials in beta and does not support live trading or broker execution.

4.6 Legal and consent records

We may collect:

  • accepted legal document type;
  • accepted document version;
  • acceptance timestamp;
  • beta participant identifier;
  • app version;
  • locale;
  • technical proof of acceptance such as hashed IP address or hashed user-agent, where appropriate.

4.7 Communications and support

We may collect information you provide when you:

  • contact support;
  • submit bug reports;
  • provide product feedback;
  • request data export, deletion, correction, or other privacy actions;
  • communicate through email, forms, chat, or community channels.

5. Information We Do Not Intend to Collect in Beta

TRION Beta should not collect:

  • broker account credentials;
  • exchange execution API keys;
  • real trading account login details;
  • real-money order details;
  • payment card data;
  • government ID documents;
  • special-category personal data such as health, biometric, religious, or political data.

Users must not submit sensitive personal information, broker credentials, exchange execution credentials, payment details, or secrets into TRION prompts, chat fields, feedback forms, or support messages.

6. How We Use Information

We may use collected information to:

  • provide and operate the closed beta;
  • enable TRION app functionality;
  • provide AI-assisted Strategy Builder and research features;
  • debug and troubleshoot technical issues;
  • improve product quality, reliability, usability, and safety;
  • monitor usage, rate limits, quotas, and AI costs;
  • detect abuse, misuse, unauthorized access, or security issues;
  • maintain legal acceptance records;
  • respond to privacy and support requests;
  • comply with legal obligations;
  • prepare aggregated or de-identified product analytics.

TRION does not use beta data to sell personal information or for cross-context behavioral advertising.

7. Legal Bases for EU/EEA/UK Users

Where EU/EEA/UK data protection law applies, we rely on one or more of the following legal bases:

Processing purpose Legal basis
Providing the beta app and hosted services Contract or steps before contract
AI feature operation Contract or legitimate interests
Debugging, reliability, security, abuse prevention Legitimate interests
Product improvement based on beta feedback and logs Legitimate interests or consent, depending on implementation
Legal acceptance records Legal obligation or legitimate interests
Optional analytics or non-essential cookies Consent
Responding to privacy requests Legal obligation

8. AI and Hosted LLM Processing

TRION Beta uses TRION-managed hosted AI/LLM services. Beta users should not need to provide their own OpenAI or other provider API key.

When you use AI features, TRION may send relevant prompts, instructions, context, and metadata to TRION's hosted LLM gateway and its configured AI provider(s), such as OpenAI or another provider used by TRION.

TRION does not send provider API keys to the desktop app, frontend, user configuration, logs, contracts, or API responses.

AI processing is used for advisory research and product features only. AI output is not investment advice, not a trading instruction, and not execution authority.

9. Sharing and Subprocessors

TRION may share information with service providers that help operate the beta, such as:

  • cloud hosting providers;
  • database/storage providers;
  • AI/LLM providers;
  • email or communication tools;
  • analytics or telemetry tools, if enabled;
  • crash/error monitoring providers, if enabled;
  • legal, accounting, or professional advisors.

TRION maintains a separate Subprocessors document listing provider names, purposes, locations, and links to provider terms where appropriate.

TRION does not sell personal information in the closed beta.

10. International Transfers

Because TRION may accept users globally and may use service providers in different countries, personal information may be processed outside your country or region.

Where required, TRION uses appropriate transfer safeguards, such as contractual protections, adequacy mechanisms, or other lawful transfer tools.

11. Retention

TRION keeps personal information only as long as needed for the purposes described in this policy, unless a longer period is required or permitted by law.

Data type Retention approach
Beta participant contact details Duration of beta + reasonable follow-up period
Legal acceptance records As long as needed to prove acceptance and defend legal claims
AI prompts/chats Limited period for debugging and product improvement, e.g. 90–180 days, unless user keeps history or support case requires longer
Debug logs Short period, e.g. 30–90 days, unless needed for security/support
StrategyDrafts/backtests Until user deletes them, beta ends, or retention period expires
Support communications Reasonable support and legal retention period
Security/audit logs Reasonable security retention period

12. Your Rights and Choices

Depending on your location, you may have rights to:

  • access personal information;
  • request a copy/export of your data;
  • correct inaccurate information;
  • delete information;
  • restrict or object to certain processing;
  • withdraw consent where processing is based on consent;
  • opt out of certain analytics or marketing if used;
  • complain to a data protection authority.

TRION intends to provide export, deletion, and correction request tools in the UI from the start of the closed beta.

Requests can also be sent to info@usetrion.com.

Some information may need to be retained where required for legal, security, fraud prevention, dispute, or beta integrity purposes.

13. Cookies and Analytics

For the first closed beta, TRION does not use non-essential cookies, marketing pixels, or analytics tracking unless a proper consent mechanism is implemented.

If analytics or cookies are later enabled, TRION provides:

  • a Cookie Policy;
  • a consent banner where required;
  • a way to reject non-essential cookies;
  • a way to change or withdraw consent;
  • a list of analytics providers and purposes.

14. Security

TRION uses reasonable technical and organizational measures appropriate for a closed beta, which may include:

  • limited beta access;
  • access controls;
  • secret management;
  • hosted provider credentials kept server-side;
  • logging and monitoring;
  • secure development practices;
  • data minimization where possible.

No system is perfectly secure. Users should not submit secrets, broker credentials, exchange API keys, payment details, or highly sensitive information into TRION.

15. Age Restriction

TRION Beta is intended only for users who are at least 18 years old. TRION does not knowingly invite or allow minors to participate in the closed beta.

If TRION learns that a minor has provided personal information, TRION will take reasonable steps to remove that information and terminate beta access.

16. Changes to This Policy

TRION may update this Privacy Policy as the beta evolves. If material changes are made, TRION will notify beta users and may require renewed acceptance before continued use.

The app stores the accepted policy version and timestamp.

17. Contact

For privacy questions, requests, or legal notices, contact info@usetrion.com.