Privacy Policy
How Trenchers AI collects, uses, shares and protects your information across our website, web app, mobile app and APIs.
Trenchers AILast updated
This Privacy Policy (the “Policy”) explains how Trenchers AI (“we”, “us”, “our”) collects, uses, shares and protects information about you when you use:
- our websites at
trenchers.ai,www.trenchers.ai,beta.trenchers.aianddocs.trenchers.ai(the “Site”); - the Trenchers AI web application, including the terminal, Pulse/Trenches feeds, AI Agents, Rewards, the Arena and the wallet surfaces;
- the Trenchers AI mobile app for iOS and Android;
- our APIs and real-time data services; and
- any related tooling, notifications, support channels and on-chain programs we operate
(together, the “Services”). “You” and “your” mean you as a user of the Services.
Please read this Policy carefully. By accessing the Site or using the Services you agree to the collection, use and disclosure of your information as described here. If you do not agree, please do not use the Services.
Trenchers AI is a non-custodial trading interface, not a bank, broker or exchange.
We do not hold your funds in the way a custodian does, and — except where §2.1 (Information you give us) says otherwise — we do not hold your private keys. Trading digital assets is risky and you may lose everything you put in. Nothing here is financial advice.
1. The short version
This summary is for orientation only; the sections below govern.
We never ask for your seed phrase or private key
Sign-in runs through our authentication provider, Privy. If you import an external wallet, the key is encrypted in your browser and sharded inside Privy’s secure enclave — it never reaches our servers. We will never ask you for it, and neither will our support team.We do collect your wallet addresses and trading activity
Addresses, trades, positions, bot configuration and portfolio history are core to the product, and much of it is already public on Solana.We record product sessions
Session replay is on and unmasked on the web app. Screens showing balances, wallet addresses and PnL are captured. See §5 (Session recording and product analytics).AI chat leaves our systems
Messages you send to the AI agent or AI support are sent to third-party model providers. On mobile this requires your explicit consent first. See §6 (AI features).We do not sell your personal information
We run no advertising networks and share no personal information for cross-context behavioural advertising.On-chain data cannot be deleted
Deleting your account deletes our records. It cannot delete the Solana blockchain. See §4 (Blockchain data is public and permanent).You can delete your account in-app
Settings → Delete account, on web and mobile, with a data export first. See §12 (Deleting your account).Questions
2. Information we collect
We collect information from three directions: what you give us, what we observe as you use the Services, and what we receive from third parties and from public blockchains.
2.1Information you give us
Account and identity
- Email address
- Collected through our authentication provider when you sign in with email. Used for your account, one-time sign-in codes, account-deletion confirmation codes and service notices.
- Third-party sign-in identifiers
- If you sign in with a social or platform account (for example Google, Apple or X), we receive the identifier and basic profile fields that provider releases to us.
- Username and display name
- Chosen during onboarding. Your username is public on leaderboards and other shared surfaces.
- Avatar / profile image
- Where you set one. Avatars may be generated or resolved through third-party avatar services.
- Language, currency and display preferences
- Stored so the app looks the same on your next visit.
- X (Twitter) account link
- If you verify an X account, we store the X user id, handle and verification timestamp, which unlocks X-linked rewards and features.
- Referral code
- If you arrive through a referral link, we store the code so the referrer can be credited.
Wallets and keys
- Wallet addresses
- Your embedded trading wallet address, your funding/deposit wallet, any external wallet you connect, any wallet you import, and the addresses of wallets created for your AI agents and bots. All are public Solana addresses.
- External wallet connections
- If you connect a browser or hardware wallet (for example Phantom, Backpack, Ledger, Trust, Coin98) we see its public address and the signatures you approve.
- Imported private keys
- We never receive these. Import happens entirely in your browser: the key is encrypted client-side and sharded inside the authentication provider’s secure enclave. Our backend only ever receives the resulting wallet id and public address, and verifies with the provider that the wallet is yours.
- Trading-session delegation
- If you enable one-tap trading, you grant a session signer so trades can execute without a pop-up each time. We record that the grant exists, when it was made, and its scope.
- Bot and agent wallet keys
- Agent and bot wallets are different: these keys are held by us, encrypted with envelope encryption (a per-bot key encrypted under a wrapped data-encryption key) and decrypted only in memory while a bot is running. See §14 (Security).
- Session wallet material stored on your device
- A browser-local session wallet may be stored in your browser’s IndexedDB. It lives on your device, not on our servers.
Trading, agents and configuration
- Orders, swaps, fills, cancellations, slippage and priority-fee settings, and the wallet each instruction came from.
- Positions, balances, realised and unrealised PnL, deposits, withdrawals and internal transfers.
- Paper-trading activity, which is simulated but recorded the same way.
- AI agent and bot configuration: strategy parameters, filters, gates, budgets, paper/live mode, schedules and lifecycle events (created, started, paused, resumed, archived).
- Watchlists, saved filters and presets, tracked wallets and copy-trade targets (including the third-party wallet addresses you choose to follow), tracked X handles, and alert and notification preferences.
Content and communications
- AI chat: the messages you write to the in-app AI agent and to AI-assisted support, and the agent’s replies. See §6 (AI features).
- Support conversations: messages, attachments and metadata you send through in-app support, email or our community channels, including as a signed-out guest.
- Shared content: profit-share cards and any other content you publish or share. A share card is stored at a public URL and bound to your account — see §8 (Public surfaces).
- Anything else you choose to send us: bug reports, feedback, survey answers, and correspondence with our team.
Waitlist and surveys on the Site
- Waitlist: if you join the waitlist or verify your email address on the Site, we store that email address, a one-time verification code (cleared once you verify), your waitlist referral code and, if you arrived through someone’s referral link, who referred you.
- Surveys: if you answer a research survey we send you, we store your answers and any X (Twitter) or Telegram handle and country you choose to give us. With each response we also record the country derived from your IP address and your browser’s user-agent string.
2.2Information we collect automatically
When you use the Services we and our providers collect:
- Device and connection data
- IP address, browser type and version, operating system, device model, screen and viewport size, language, time zone, and (in the mobile app) the app version and build.
- Approximate location
- Derived from your IP address, at roughly city or country level. We do not collect precise GPS location; the web app explicitly disables the browser geolocation permission, and the mobile app requests no location permission.
- Usage and product analytics
- Pages and routes viewed, features opened, clicks, and a defined catalogue of product events — for example sign-up, onboarding steps, trade submitted, order created or cancelled, bot created or started, deposit address copied, withdrawal submitted, tracker added, AI message sent, wallet import outcome. Events carry properties such as token mint, side, amount, slippage, order type and whether the action was paper or live.
- Session replay
- Video-like reconstructions of your session on the web app. See §5 (Session recording and product analytics).
- Performance and reliability data
- Page-load and route-transition timings, web vitals, chart first-paint timings, WebSocket connection health, and real-user-monitoring telemetry.
- Error and crash reports
- Stack traces, the URL or route where the error happened, browser and OS, a build identifier, and failed API calls you experienced.
- Security and abuse signals
- Authentication attempts and failures, rate-limit events, and an append-only audit log of administrative and internal access to user data (who accessed what, when, from which IP, under which role).
- Email engagement
- For emails sent from the Site — such as waitlist verification codes and survey and beta-access invitations — whether each message was delivered, bounced, failed or was marked as spam, and, for campaigns where we measure it, whether it was opened or a link in it was clicked.
We take deliberate steps to keep sensitive values out of these streams: query strings are stripped from analytics URLs, DOM element attributes are masked in click capture, private-key input fields are excluded from session recording, and vendor error text is replaced by fixed categories rather than forwarded. These are engineering controls, not guarantees — see §14 (Security).
2.3Information we receive from other sources
- Our authentication provider
- Your account identifier, verified email, linked accounts and the list of wallets on your account. We treat only the identifier from your browser as trusted; every other attribute is re-read from the provider’s server-side API.
- Public Solana data
- Transactions, signatures, slots, timestamps, token transfers, balances, holder distributions, liquidity and pool state for the wallets and tokens you interact with or track. We receive this through blockchain data providers and streaming services.
- Market and token data providers
- Prices, oracle feeds, routing quotes, pair and liquidity metadata, token metadata and images, holder and security analyses (including rug and honeypot checks), and trader rankings.
- X (Twitter)
- For handles you subscribe to: public profile identity and follower statistics. For profit-share rewards: we search public X posts for the share link generated by your session, so a public post can be credited to you.
- Fiat on-ramp partner
- If you buy crypto with fiat through our on-ramp partner, that purchase happens on their platform under their terms and privacy policy, and they perform any identity verification. We receive confirmation and transaction metadata, not your identity documents or card details.
- Public sources and community channels
- Anything you post publicly on our Discord, X or other community surfaces.
2.4What we do not collect
- We do not collect seed phrases, recovery phrases or private keys for your personal wallets. No Trenchers AI employee, agent or support channel will ever ask for them. Any message that does is fraudulent — report it to support@trenchers.ai.
- We do not collect payment card or bank account details. Fiat purchases go through our on-ramp partner.
- We do not run our own KYC or identity verification, and we do not collect government identity documents.
- We do not collect biometric data. Where you use Face ID, Touch ID or a passkey, the biometric stays on your device and we receive only the result.
- We do not collect precise location, contacts, photos, microphone or camera data.
- We do not knowingly collect information from anyone under 18. See §16.1 (Children).
2.5De-identified and aggregated information
We may de-identify or aggregate information so it can no longer reasonably be linked to you, and use it for any purpose — including volume statistics, market research, benchmarking and product analysis. Where we hold such information we maintain it in de-identified form and do not attempt to re-identify it, except to test that our de-identification works.
3. How we use your information
We use information to run and improve the Services. Where the GDPR or a similar law applies, the legal basis is shown alongside each purpose.
- Provide the Services
- ExamplesCreate and maintain your account; authenticate you; show your portfolio and positions; route, quote and execute trades; run agents and bots; stream real-time market and wallet data; deliver alerts and notifications.
- Legal basisPerformance of a contract
- Payments, fees and rewards
- ExamplesCalculate and collect platform fees; compute points, ranks, streaks, rakeback and referral earnings; process claims.
- Legal basisPerformance of a contract
- Support
- ExamplesAnswer your tickets, reproduce the problem you reported, and keep a history so you don’t have to repeat yourself.
- Legal basisPerformance of a contract; legitimate interests
- Security, fraud and abuse prevention
- ExamplesRate limiting; detecting bots, farming and multi-account abuse; screening for illicit on-chain activity; investigating incidents; keeping an audit trail of internal access.
- Legal basisLegitimate interests; legal obligation
- Product analytics and improvement
- ExamplesUnderstand which features are used and where users get stuck; measure funnels; fix bugs; test performance changes.
- Legal basisLegitimate interests (or consent where required)
- Session replay
- ExamplesWatch real sessions to understand a confusing flow or reproduce a defect.
- Legal basisLegitimate interests (or consent where required) — see §5 (Session recording and product analytics)
- AI features
- ExamplesAnswer your questions, explain and apply agent configuration, and draft support replies.
- Legal basisPerformance of a contract; consent where we ask for it
- Communications
- ExamplesSign-in codes, deletion confirmation codes, security and service notices, and — where you have opted in or where permitted — product news.
- Legal basisPerformance of a contract; consent; legitimate interests
- Legal and compliance
- ExamplesRespond to lawful requests; comply with tax, financial and sanctions obligations; produce tax reports you request; enforce our Terms; establish or defend legal claims.
- Legal basisLegal obligation; legitimate interests
- Corporate transactions
- ExamplesDiligence for a merger, acquisition, financing or reorganisation.
- Legal basisLegitimate interests
Where we rely on legitimate interests, we have weighed those interests against your rights and consider the processing proportionate. You can object — see §11 (Your privacy rights).
4. Blockchain data is public and permanent
This is the most important thing to understand about privacy in a Solana trading app.
- Solana is a public blockchain. Every transaction we submit on your behalf, and every transaction you sign yourself, is broadcast publicly, is permanently recorded, and is visible to anyone in the world, forever. That includes the wallet address, the token, the amount, the counterparty program and the time.
- We cannot delete, alter or hide on-chain data. No one can — not us, not you, not any regulator. If you exercise a deletion or erasure right, we delete what is in our systems; the chain is untouched.
- Addresses are pseudonymous, not anonymous. Anyone who links your address to your identity — through an exchange deposit, a public post, a share card, a leaderboard entry, or chain analysis — can then see your entire trading history on that address.
- Our own records of on-chain activity are retained indefinitely, because they duplicate information that is already permanently public and are needed to keep the product working, to report accurately, and to prevent fraud.
If on-chain visibility is a concern for you, treat your address as public information and consider using separate wallets for separate purposes.
5. Session recording and product analytics
We record sessions on the web app, and the recordings are not masked.
We want to be plain about this because it goes further than many products:
- Session replay is enabled in the Trenchers AI web app. It reconstructs what happened on screen — page content, navigation, clicks, scrolling and typed input — so we can see exactly how a flow behaved.
- Recording is deliberately unmasked: screens showing wallet addresses, balances, positions, PnL and AI-agent conversations are captured as rendered.
- Two protections are built in, and they are the boundaries of what we capture:
- Fields that can hold private-key material (the wallet-import inputs) are explicitly excluded from recording, so a pasted key is not captured. Password fields are masked by default, and the private-key export flow runs inside a cross-origin frame the recorder cannot see, so exported keys never enter a recording.
- Network request and response bodies and headers are not recorded.
- Recordings are stored by our analytics provider (see §7.1 (Service providers (processors))) and are used for product and support purposes only.
- Session replay runs on the web app only. The mobile app does not record sessions.
Alongside replay we collect the analytics events described in §2.2 (Information we collect automatically). Analytics identify you by your Trenchers AI user id once you are signed in; before sign-in, anonymous traffic is not built into a person profile. Full URLs are stripped of query strings before they reach analytics, so referral codes, addresses and one-time tokens in a link are not forwarded.
If you would rather not be recorded or measured, see §11 (Your privacy rights) and §10.3 (Your choices).
6. AI features
The Services include AI features: an in-app AI agent that advises on and configures trading agents, AI-assisted insights, and AI-assisted customer support.
What leaves our systems. When you use an AI feature, the content of your request is sent to a third-party AI model provider over their API. Depending on the feature this can include:
- the free-form text you type;
- the conversation history for that thread;
- context about the thing you are asking about — for example an agent’s configuration, its recent trades, positions and account state; and
- for AI-assisted support, a read-only context pack about your account (profile, wallets, deposits, positions, bots and points) so the answer is grounded in your actual situation rather than guesswork.
Who processes it. Our primary AI provider is Anthropic. Our infrastructure supports additional providers (for example OpenAI, Google and DeepSeek), and we may route requests to them. These providers process the data as our service providers under their API terms, and we do not authorise them to use your content to train their models.
Consent on mobile. In the mobile app you must give explicit consent before the first AI request is sent, and no AI feature will transmit anything until you do. You can withdraw that consent at any time in app settings. The app remains usable without AI. If what we share with AI providers materially changes, we will ask again rather than rely on your earlier consent.
Please don’t paste secrets into AI chat.
Never type a seed phrase, private key or password into any chat — AI or human. AI output can be wrong: it is information, not financial advice, and you are responsible for the trades and configurations you approve.
8. Public surfaces
The following are visible to other users, or to anyone on the internet:
- Leaderboards and Rewards
- Your username, rank, points, and trading-versus-referral breakdown.
- The Arena
- Entrant standings, configurations, trades and equity curves for house-run bots, and — where you clone an entrant — the fact of the clone’s provenance. The Arena is readable without signing in.
- Profit-share cards
- A share card you generate is stored at a public URL (
/s/{id}) that anyone with the link can open. It shows the trading result you chose to share. Sharing is your choice; the link is public once created. - Share-reward verification
- If you post a share link publicly on X, we search public X posts for that link in order to credit the reward to the account that generated it.
- Deletion status page
- The
/deletion-status/{receipt}page is public to anyone holding the receipt id, so you can check a deletion after you have signed out. It shows deletion status only. - Community channels
- Anything you post in our Discord, X or other public channels.
- On-chain activity
- Everything in §4 (Blockchain data is public and permanent).
Choose a username you are comfortable being seen with, and remember that a username plus a public wallet address ties your trading history to your identity.
9. Third-party services and links
The Services link to, embed and interoperate with third-party sites and services — block explorers, token analytics panels, wallet providers, the fiat on-ramp, social platforms and others. When you follow a link or use an embedded panel, that third party receives your request (including your IP address) and handles your information under its privacy policy, not ours. We do not control those services, are not responsible for their practices, and including a link is not an endorsement.
Integrations you initiate yourself — connecting a wallet, linking a social account, using the on-ramp — will share information with that provider by design. Review their terms before connecting.
11. Your privacy rights
Depending on where you live, you may have some or all of the following rights. Some apply only in certain circumstances, and all can be limited by law.
Access / know
What personal information we hold, how we use it, and who we share it with.Correct
Inaccurate or outdated personal information.Delete
Personal information we hold about you (see §12 (Deleting your account) and the on-chain limits in §4 (Blockchain data is public and permanent)).Portability
A copy of information you provided, in a portable format. The in-app Download my data export does exactly this.Restrict or object
To processing based on our legitimate interests, including profiling and analytics.Withdraw consent
Where we rely on consent, at any time and without affecting prior processing. Mobile AI consent is withdrawable in app settings.Opt out of marketing
Via the unsubscribe link in any marketing email. We will still send transactional and security messages.Non-discrimination
We will not deny you service, charge you a different price or give you a lower quality of service for exercising these rights.Complain
To your supervisory authority or regulator. We would rather you came to us first at support@trenchers.ai.
How to exercise them. Email support@trenchers.ai, or use the in-app account-deletion and data-export flows. We may need to verify your identity before acting — typically by confirming control of the email address or wallet on the account. An authorised agent may act for you with written proof of authorisation, and we may still verify with you directly. We respond within the period the applicable law requires.
11.1European Economic Area, United Kingdom and Switzerland
Our legal bases are set out in §3 (How we use your information). You have the rights above under the GDPR and UK GDPR, including the right to lodge a complaint with your local data protection authority.
The controller of your personal data is Trenchers AI, which you can contact at support@trenchers.ai.
11.2California
For purposes of the CCPA/CPRA, “personal information” includes “sensitive personal information”.
In the preceding 12 months we have collected, and disclosed for a business purpose, the following categories:
- Identifiers (email, user id, wallet address, IP address, device identifiers);
- California Customer Records information (name or username, email);
- Commercial information (trading and transaction activity, fees, rewards);
- Internet or other electronic network activity (usage, analytics, session recordings, support and AI conversations);
- Approximate geolocation (from IP);
- Inferences (product segments and engagement); and
- Account access credentials* (authentication tokens and, for bot wallets, encrypted key material).
* Denotes sensitive personal information, which we use only for the purposes permitted by the CCPA and not to infer characteristics about you.
Sources, purposes and disclosure recipients are described in §2 (Information we collect), §3 (How we use your information) and §7 (How we share your information); retention criteria are in §13 (Data retention).
We do not “sell” or “share” personal information as those terms are defined by the CCPA, and we have not done so in the preceding 12 months. We do not have actual knowledge that we sell or share the personal information of consumers under 16 years of age.
California’s “Shine the Light” law lets California residents request details of personal information disclosed to third parties for those parties’ direct marketing purposes. We do not disclose personal information for that purpose.
California residents under 18 with a registered account may request removal of content they posted publicly on the Services. Removal cannot be complete or comprehensive — others may have republished it, and archives we do not control may retain copies. In any event, the Services are not available to anyone under 18 (§16.1 (Children)).
11.3Other US states
Residents of Virginia, Colorado, Connecticut, Utah, Texas and other states with comprehensive privacy laws have rights of access, correction, deletion, portability, and opt-out of targeted advertising, sale and certain profiling. We do not conduct targeted advertising, sell personal data, or engage in profiling that produces legal or similarly significant effects.
If we decline your request you may appeal by replying to our decision or emailing support@trenchers.ai with “Appeal” in the subject line. We will respond in writing within the statutory period, and if we deny the appeal we will tell you how to complain to your state Attorney General.
11.4India
Where the Digital Personal Data Protection Act, 2023 applies, you have rights of access, correction, completion, updating, erasure and grievance redressal, and the right to nominate another person to exercise your rights in the event of death or incapacity. To exercise them or raise a grievance, contact support@trenchers.ai.
Our tax reporting features — including the Indian financial-year summary and Schedule VDA export — are computed from your own trade history at your request. They are a convenience, not tax advice, and we do not file anything on your behalf.
11.5France
If you live in France, you may give general or specific instructions about the retention, deletion and communication of your personal data after your death, appoint someone to carry them out, and modify or withdraw them at any time.
12. Deleting your account
You can delete your Trenchers AI account from within the app: Settings → Delete account (/settings/delete-account on web, and the equivalent screen in the mobile app).
Before you delete, move your money.
The flow shows a live checklist of what stands between you and deletion — open positions, running bots, funded bot wallets, unclaimed rewards, and any balance we cannot read. Some items block deletion until you resolve them; others you must acknowledge as lost. You are responsible for withdrawing your funds first. We cannot recover funds from a wallet after the account that surfaced it is gone.
Take your data with you. “Download my data” produces a JSON file with your profile and your trade history before you proceed.
What deletion does
- We verify it is really you: a code emailed to your address, or a fresh re-authentication if you have no email on file.
- You confirm by typing a confirmation word and acknowledging what will be lost.
- We give you a receipt id and a public status page so you can check progress after signing out.
- Optionally, we clear Trenchers AI data from the device you are on. The browser-local session wallet is only cleared when the checklist confirms it holds nothing — because that key is the only way to move what it holds.
- Your account is closed. Every authenticated request afterwards is refused, your live sessions are disconnected, and signing in again with the same identity does not restore the account — it creates a new one. Your username is retired and not reissued to you.
What deletion cannot do
- It cannot delete anything from the Solana blockchain (§4 (Blockchain data is public and permanent)).
- It cannot remove content already republished or archived by others.
- It does not delete records we must keep by law, for tax, accounting, sanctions, fraud-prevention, security or dispute purposes; nor records held under a legal hold. We retain those for the periods in §13 (Data retention) and then delete or de-identify them.
- Backups roll off on their own schedule; deleted data can persist in backups until they are overwritten.
Can’t get into the app? Request deletion by email.
13. Data retention
We keep personal information only as long as we need it for the purposes in this Policy, and we weigh whether we still need it to provide the Services, maintain security and integrity, prevent fraud, comply with legal obligations, resolve disputes and enforce our agreements.
- Account and profile data
- For the life of your account, then deleted or de-identified after closure, subject to the exceptions below.
- Public blockchain data (addresses, signatures, on-chain transactions)
- Indefinitely — it is permanently public and is needed to operate and report accurately.
- Trade, order, fee, reward and balance records
- For as long as financial, tax and regulatory reporting obligations require, and as long as needed to investigate fraud.
- IP addresses, session and security logs
- For as long as needed for security, abuse prevention, integrity and compliance.
- Analytics and usage data
- For the retention period configured with our analytics provider.
- Session recordings
- For the recording retention period configured with our analytics provider.
- AI conversations
- For as long as needed so a conversation continues across sessions and so we can investigate incorrect answers.
- Support conversations
- For as long as needed after the ticket is resolved, so you don’t have to repeat yourself if the problem returns.
- Error and crash reports
- For as long as needed to diagnose and fix the underlying problem.
- Internal access audit log
- Append-only, and retained for as long as security and compliance require, because its value is that it cannot be edited.
- Backups
- Until they are overwritten by our backup rotation.
Aggregated and de-identified information may be retained indefinitely.
14. Security
We implement commercially reasonable technical and organisational measures to protect information, including:
Encryption in transit
TLS everywhere, HSTS with preload, and a Content Security Policy restricting where the app may connect.Encryption at rest
For databases and object storage.Key custody
Your personal wallet keys are held by our authentication provider’s secure enclave infrastructure, not by us. Agent and bot wallet keys that we do hold are protected with envelope encryption: a per-bot key encrypted under a data-encryption key that is itself wrapped by a secrets manager, decrypted only in memory while a bot is running and zeroised when it stops. A database compromise alone does not expose spendable keys.Short-lived sessions
Our application session token is short-lived and re-issued, and sessions are revoked server-side on deletion or compromise.Least privilege
Role-based access control on internal endpoints, a read-only database role for AI-assisted support, and an append-only audit log of internal and administrative access to user data.Rate limiting and abuse controls
Across authentication, trading and read-heavy endpoints.Isolation of sensitive input
Private-key entry fields are excluded from session recording, and key export runs in an isolated frame.
No system is perfectly secure. We cannot guarantee the security of information transmitted to or from the Services, and you transmit it at your own risk. Protect your own side too: use a strong, unique password on your email account, enable two-factor authentication, keep your devices patched, and do not share your account access.
Beware of phishing.
We will never ask for your seed phrase, private key, password or one-time code. If you receive such a request, do not respond — report it to support@trenchers.ai.
If we become aware of a breach affecting your personal information, we will notify you and the relevant authorities where the law requires it.
15. International transfers and where data lives
Our core infrastructure runs in Microsoft Azure in the European Union (Germany). Some providers we rely on — including our analytics provider and AI model providers — process data in the United States, and CDN and edge services may process request metadata in the region closest to you.
Wherever you are, your information may be transferred to, stored in and processed in countries whose data protection laws differ from your own. Where we transfer personal data out of the EEA, the UK or Switzerland to a country without an adequacy decision, we rely on appropriate safeguards — typically the European Commission’s Standard Contractual Clauses (with the UK Addendum where applicable) — together with supplementary measures where needed. You may request a copy of the relevant safeguards at support@trenchers.ai.
16. Other things you should know
16.1Children
The Services are not intended for anyone under 18, and we do not knowingly collect personal information from children. By using the Services you represent that you are at least 18. If we learn that we have collected information from a child, we will take commercially reasonable steps to delete it. Parents and guardians can contact us at support@trenchers.ai.
16.2Mobile app specifics
The iOS and Android apps follow this Policy, with these differences:
- No session replay. The mobile app does not record sessions.
- Explicit AI consent. Nothing is sent to an AI provider until you agree, and you can withdraw consent in settings (§6 (AI features)).
- In-app account deletion is available in settings (§12 (Deleting your account)).
- Platform permissions. The app requests no location, camera, microphone, contacts or photo-library access. Device biometrics and passkeys are handled by the operating system; we receive only the authentication result.
- Feature availability differs by platform for regulatory and app-store reasons; some trading and rewards features are available only on the web.
- Our App Store privacy details and Google Play data safety disclosures are derived from this Policy.
16.3Automated decision-making
We do not make decisions producing legal or similarly significant effects about you based solely on automated processing. AI agents execute trades according to the configuration you set and approve; that is automation you control, not a decision we make about you.
16.4Changes to this Policy
We may update this Policy. When we do, we will change the “Last updated” date at the top. If we make material changes to how we collect, use or share personal information, we will make reasonable efforts to notify you in advance — by in-app notice, email, or another method the law requires. Your continued use of the Services after an update takes effect means you accept the revised Policy. Material changes to what is shared with AI providers will re-prompt for consent where we rely on consent.
16.5Language
Except where the law says otherwise, if there is any discrepancy between the English version of this Policy and a translation, the English version prevails.
16.6Contact us
Questions, requests or complaints about this Policy or our privacy practices:
- support@trenchers.ai
- Support
- In-app support, or support@trenchers.ai
- Company
- Trenchers AI