Privacy policy
1. Who we are and what this covers#
The AQREVI service (app.aqrevi.com and aqrevi.com) is provided by its author as an individual — Rodion; no legal entity is registered yet, and its details will be published here once it is, who is also the controller of personal data.
Version 2.6 · effective 13 November 2026
The AQREVI service (app.aqrevi.com and aqrevi.com) is provided by its author as an individual — Rodion; no legal entity is registered yet, and its details will be published here once it is, who is also the controller of personal data. Questions about data and requests about your rights — legal@aqrevi.com. This policy covers the website, the web app, the AqreviExec EA, the bridges for trading terminals and the emails we send.
2. What data we receive#
The waitlist (before launch): your email address, the page language, which button you came from, the inviter's code if there was one and — if you answer — where you trade, a short note on where you lose, and your answer to “How did you hear about us?” (a platform from the list and, if you remember, which video).
The waitlist (before launch): your email address, the page language, which button you came from, the inviter's code if there was one and — if you answer — where you trade, a short note on where you lose, and your answer to “How did you hear about us?” (a platform from the list and, if you remember, which video). Whether you agreed to product news. The IP address is not written to the list (the server's request log has it, as for any request, for no more than 7 days).
Account: email address, name (if you sign in with Google, Microsoft or Apple), the date and version of the terms you accepted, your choice on product news, settings, sign-in method, sessions and the second factor; at sign-up, an optional answer to “How did you hear about us?”.
Journal: what you enter or import — trades, notes, screenshots, daily journal, dossier and rules, playbook, tiers, boards, scenarios, alerts, AI chats.
Connections: the broker credentials and model keys you provided (stored encrypted and shown on no page), and what connections send: trades, balance, and for the AqreviExec EA — account number, server, balance and open positions.
Payment: order number, plan, amount, status. Card and wallet details are handled by the payment service — they never reach us.
Community — if you use it: a public profile (handle, name, bio, colour, avatar, cover), posts, reactions, replies, bookmarks, poll votes, stories, follows and blocks, direct messages, crews and crew tournaments, the discipline rating row, uploaded backgrounds, prop-firm cases and votes, reports. A problem report from the site — with your email, the page and the browser.
Technical: IP address, browser, request times and paths — for sign-in, protection against brute force and overload, and investigating failures. The server's request log keeps the IP address, the time, the page address with keys and codes removed, and the server's answer — no browser and no cookies; it is how we notice brute force and overload. The security event log is kept for the same 7 days: the time, the IP address, a pseudonymous account number, a short browser fingerprint (a hash, not the string itself) and the event type — sign-in and wrong codes, new sessions, switching off the second factor, MCP connections, exports and deletions; our watch uses it to notice a break-in. To notice a sign-in from a new country we remember, per account, only the country codes and browser fingerprints of past sign-ins — for 90 days, without IP addresses; the country comes from a local database and the address is not sent anywhere. An address blocked for an attack stays on the block list for no more than 7 days. If error monitoring is switched on, a server error report goes to Sentry — without email addresses, cookies, tokens or request content. An error in your browser goes to Sentry the same way, without personal data: only the error text, the stack and the page address pattern, with no query string and nothing about you. Visitor analytics runs only if you agreed to it (the cookie banner or Settings → Data): our own counting on our own server — which pages and sections are opened, where you came from (referring site, UTM tags, the search query if the search engine passed it), clicks on buttons and menus, video plays and how far they were watched, time on page and scroll depth, browser, system, device type, window width, country and city, API response times in the app and page load speed (web vitals) — and, if switched on, Plausible on the site. No cookies are set. The IP address is not stored: during the request it gives the country and city and a visitor hash with a daily salt, and the salt is deleted every day. After you sign in, app events are tagged with your account (to see which sections people return to), and where the account came from on its sign-up day is kept; the content of trades, notes and AI conversations never goes there. With the same consent your browser keeps (in localStorage) up to the last 10 arrivals carrying a UTM tag or coming from another site — only the tags and the referring site's address, for no more than 90 days — and sends them once, together with joining the waitlist or signing up: that is how we see which video or post brought someone. This chain is stored with the conversion record (under the invite code or the account number, without the email address) and is erased from the browser if you withdraw consent. Separately, without consent, we count only the number of clicks per day on prop-firm affiliate links and on our own short links aqrevi.com/go/…, with no visitor attached. We also mark the days an account was active (to count active users) and each model call — section, model, tokens, time, cost and outcome, without the text of the question or answer. There is no advertising tracker.
3. Why, and on what legal basis#
To provide the service you chose (performance of a contract): keep the journal, compute metrics, sync accounts, copy trades, answer AI questions, take payment.
To provide the service you chose (performance of a contract): keep the journal, compute metrics, sync accounts, copy trades, answer AI questions, take payment. The waitlist — to write to you about the launch, which is what you asked for (also performing your request).
For security and reliability (legitimate interest): protection from intrusion and abuse, backups, fixing errors. For legal obligations: payment records, answering lawful requests. A public feed profile — on your consent, which you withdraw by switching the profile off.
4. Emails#
Service emails go to everyone because the service cannot work without them: the sign-in code, the payment receipt, data-retention warnings and important changes to the terms.
Service emails go to everyone because the service cannot work without them: the sign-in code, the payment receipt, data-retention warnings and important changes to the terms. You cannot unsubscribe from them while you have an account — and they carry no advertising.
Notifications you switched on yourself in Settings → Notifications (copier, alerts, agents) arrive with an unsubscribe link at the bottom: it switches email off as a notification channel in one click.
Product news — only if you ticked the separate box yourself when joining the list (and confirmed it from the email we send) or signing in; it is never pre-ticked. Every such email carries an unsubscribe link, and you can change your mind in Settings → Data. News emails go only to those who agreed to them; without that consent you get none.
In news emails we count opens and clicks, to learn which emails are useful and which are not. An open is a 1×1 image from our server; a click is a link that goes through our server and straight on. We keep: which email, your address, the time of the first and last open or click, how many there were, the clicked link's address and the kind of mail app (for example Gmail or Apple Mail). We keep no IP address and no country, and we pass none of it to other people or ad networks. Kept 90 days. The count is approximate: some mail apps load images by themselves. Service emails and notifications are not tracked this way, and the unsubscribe link and links to these documents are never tracked. If you do not want opens counted, switch off image loading in your mail app — we respect that; if you want no emails at all, use unsubscribe.
5. AI features#
When you use AI, the model receives your question and the context the engine assembled.
When you use AI, the model receives your question and the context the engine assembled. Without your own key the platform model answers through OpenRouter with data collection denied; with your own key, the provider you chose, under their rules. We do not train models on your data. In detail — in the “AI in AQREVI” document.
6. Who we share data with#
Only with processors the service cannot run without (server, email, backups, payment, AI) — plus, where switched on, error reports and site analytics with your consent — and services you connected yourself.
Only with processors the service cannot run without (server, email, backups, payment, AI) — plus, where switched on, error reports and site analytics with your consent — and services you connected yourself. The full list, with what each one gets and where it is located, is in “Subprocessors”.
We do not sell data or “share” it for cross-site advertising. We may disclose data on a lawful demand by authorities, to protect against fraud, or if the service passes to a new owner — with the same level of protection and a notice to you.
7. Cookies#
We set only strictly necessary ones: sign-in, session, sign-in protection.
We set only strictly necessary ones: sign-in, session, sign-in protection. The one optional category is analytics: our own counting on our own server and, if switched on, Plausible on the site; neither sets cookies, and both load only if you switched “Analytics” on in the banner or in Settings → Data. There is no marketing, and if any appears it stays off until you agree. We treat the browser's Global Privacy Control or “Do Not Track” signal as a refusal. In detail — “Cookies and browser storage”.
8. What others can see#
By default, nothing: the journal is visible only to you.
By default, nothing: the journal is visible only to you. If you created a public profile, users of the service see your handle, name, bio and posts. A trade post publishes R, the date, the setup and the tier — without the entry price or account size; money only if you allowed it. The snapshot in a post does not change after publishing; a post can always be deleted.
9. How long it is kept#
For as long as the account exists.
For as long as the account exists. A free account nobody has signed in to for 12 months is deleted after emails 30, 7 and 1 day before; a paid one is not deleted for inactivity. A deleted account is erased at once — its database and files, profile, posts, reactions, replies, direct messages, follows, crews and tournament entries, stories, backgrounds, prop-firm cases, reports, rating row, public links and referral code — and its copies in the backup store within the following day. Only a moderator ban and other people's blocks on the account remain: otherwise deleting and signing up again would lift them. Payment records are kept as long as accounting law requires. The waitlist — until the launch and the email about it, or until you ask us to delete it. Analytics events, and opens and clicks in news emails — 90 days, daily totals without visitors — 25 months; activity days and model-call rows — 13 months; where an account came from, the “How did you hear about us?” answer and the sign-up touch chain — as long as the account exists, but no more than 25 months; the same for a waitlist entry — 25 months. The server's request log and the security event log — no more than 7 days; countries and browser fingerprints of past sign-ins — 90 days; other technical logs — for the limited time needed to investigate failures.
10. How we protect data#
Every account has a separate database; broker and model keys are encrypted; connections are TLS-only; nightly copies are encrypted before they leave for storage; there is a second factor and a list of active sessions you can revoke.
Every account has a separate database; broker and model keys are encrypted; connections are TLS-only; nightly copies are encrypted before they leave for storage; there is a second factor and a list of active sessions you can revoke. The operator technically has access to the server and enters an account's data only at your request to support or when the law requires it. In detail — “Security”.
If a breach occurs that threatens your rights, we will tell you and the supervisory authority within the time the law requires.
11. Your rights: export and deletion#
You can export everything we hold about you yourself: Settings → Data → “Everything about my account” — one JSON file with every table of your database, your records in the shared feed and your public links.
You can export everything we hold about you yourself: Settings → Data → “Everything about my account” — one JSON file with every table of your database, your records in the shared feed and your public links. Keys and passwords are left out: a mark says they exist instead. The same place offers a copy of the whole database and CSV.
You can delete the account in the same place, at once and for good. Correct data directly in the service. For anything else — access, restricting or objecting to processing, portability, withdrawing consent, removing a waitlist entry — write to legal@aqrevi.com from the address in question; we answer within 30 days and free of charge. If we cannot confirm the address is yours, we will ask you to confirm with a code sent to it — we will not ask for other documents.
12. EEA and the United Kingdom#
GDPR and UK GDPR apply to you: the legal bases are listed above; your rights are access, rectification, erasure, restriction, portability, objection and withdrawal of consent, plus the right to complain to your country's supervisory authority (in the UK, the ICO).
GDPR and UK GDPR apply to you: the legal bases are listed above; your rights are access, rectification, erasure, restriction, portability, objection and withdrawal of consent, plus the right to complain to your country's supervisory authority (in the UK, the ICO). The service makes no decisions based solely on automated processing that have legal effects on you. If the law requires us to appoint a representative in the EU or the UK, we will appoint one and name them here.
13. California and other US states#
We do not sell personal data or share it for cross-context behavioural advertising — there is nothing to opt out of, but we honour the Global Privacy Control signal as an opt-out anyway.
We do not sell personal data or share it for cross-context behavioural advertising — there is nothing to opt out of, but we honour the Global Privacy Control signal as an opt-out anyway. Residents of California (CCPA/CPRA) and of states with similar laws (Virginia, Colorado, Connecticut, Utah, Texas, Oregon and others) may learn which categories of data we collect and why (listed above), obtain a copy, correct and delete it, without being discriminated against for doing so. We honour these requests even where the state law does not formally apply to us under its thresholds.
14. Georgia, Kazakhstan and other countries#
If you are in Georgia, you have rights under the Law on Personal Data Protection, including the right to apply to the Personal Data Protection Service.
If you are in Georgia, you have rights under the Law on Personal Data Protection, including the right to apply to the Personal Data Protection Service. In Kazakhstan and other CIS countries local personal-data laws apply; we honour rights of access, correction and deletion for everyone alike — by email at legal@aqrevi.com.
15. International transfers#
Databases are stored in the EU.
Databases are stored in the EU. Some processors are outside the EU (for example OpenRouter and model providers in the US); transfers rely on the EU standard contractual clauses or other mechanisms the law requires. With your own model key you choose yourself which country a request goes to.
16. Connected and third-party services#
This policy does not cover services you connect or open through a link yourself: your broker, a trading platform, a prop firm, TradingView, a model provider on your own key, websites from posts and profile links.
This policy does not cover services you connect or open through a link yourself: your broker, a trading platform, a prop firm, TradingView, a model provider on your own key, websites from posts and profile links. What they do with data is governed by their rules. You can disconnect at any time: new data stops arriving, and what was already imported stays in the journal until you delete it.
A partner link to a prop firm passes the firm only the programme code it uses to credit the purchase; the firm gets neither your journal, nor your trades, nor your address from us.
17. Age#
The service is only for people aged 18 and over; you confirm this when you first sign in.
The service is only for people aged 18 and over; you confirm this when you first sign in. We do not knowingly collect data of minors; if we learn of such an account we will delete it.
18. Changes to this policy#
A new version appears here with a new number and date; the history is in the “Change log”.
A new version appears here with a new number and date; the history is in the “Change log”. Changes to what we collect or who we share it with are emailed to you in advance.