Legal
Privacy Policy
This explains what RoboticEA collects about you, why, who else sees it and how long we keep it. It is written plainly on purpose.
Last updated 11 August 2026
The short version
We collect the minimum needed to run an account and bill it. We do not sell or rent personal data, and we do not build advertising profiles or show you retargeted ads. We use Google Analytics to understand how the site is used — in the EEA, UK and Switzerland only if you accept it in the consent banner, and anywhere else you can switch it off in Cookies.
We do advertise RoboticEA on Google Search, and we measure whether an ad click led to a sign-up or a subscription — so we know which ads are worth paying for. That measurement sets a cookie only outside the EEA, UK and Switzerland. Inside those countries no advertising cookie is set at all, whatever you choose on the banner.
We never receive your broker credentials, because the product never connects to a broker.
1Who is responsible
Konvert Technologies Oy is the data controller for personal data processed through RoboticEA. Our full identity and contact details are at the bottom of this page. You can reach us about anything in this policy at [email protected].
2What we collect, and why
| Data | Why we have it | How long |
|---|---|---|
| Email address and a hashed password | To create your account and let you sign in. Passwords are stored only as a one-way hash. We cannot read yours. | Until you delete your account |
| Google account identifier (only if you choose Google sign-in) | To sign you in without a separate password. | Until you delete your account |
| Your strategies, backtests, validations and saved settings | They are the product. We store them so they are there when you return. | Until you delete them or your account |
| Plan, subscription status and usage counters (tokens, generations used) | To apply the right limits and bill the right amount. | Until account deletion; billing records kept as long as accounting law requires |
| A device identifier recorded at sign-up | To detect one person opening many free accounts to bypass the free allowance. It is used for abuse prevention only, never for advertising or profiling. | Until you delete your account |
| Session records (which sessions are active, last seen) | To keep you signed in and to enforce the limit on simultaneous sessions per account. | Rolling; old sessions expire automatically |
| Server logs (IP address, timestamps, errors) | Security, debugging and keeping the service up. | Short-term operational retention |
| Analytics events (pages viewed, approximate location, device/browser) via Google Analytics, only if you consent | To see which pages and features are used so we can improve them. Collected pseudonymously; we do not use it to build an advertising profile of you or to show you retargeted ads. | Handled by Google under its own retention; declined by default until you accept |
| Ad conversion measurement (that a visit came from one of our ads, and that it later led to a sign-up or subscription) via Google Ads — outside the EEA, UK and Switzerland only | To find out which of our ads actually bring people who use the product, so we stop paying for the ones that do not. It measures the ad, not you: it is not used to profile you, to retarget you, or to decide anything about your account. | Handled by Google under its own retention; never set in the EEA, UK or Switzerland |
We do not collect special-category data, we do not ask for your identity documents, and we do not build advertising profiles or run retargeting. Ad personalisation is switched off for every visitor, everywhere — the only advertising signal we use is whether a click turned into a sign-up.
3What happens when you use the AI features
If you use a feature that turns a written description into strategy settings, the text you type is sent to our AI provider (OpenAI) so it can produce a response. It is sent to generate that answer and for no other purpose.
We do not store your prompt text. Our records of AI use keep only which account made a request, which strategy it produced and when — enough to apply your plan limits, and no more. Please avoid typing personal or confidential information into those boxes; a strategy description does not need it.
4Where your strategies actually run
Backtests, validations and replays run on our own trading engine, software we wrote in C++ and operate on our own servers. Your strategies are simulated there against historical market data. Nothing about a backtest touches a broker, a live account or real money.
The engine is also what makes the MetaTrader export possible: it is built so that a strategy can be expressed both as something our engine runs and as a MetaTrader 5 expert advisor, and we test the two against each other so the exported file behaves consistently. The internal design of the engine, the strategy generator and the translation between them is our proprietary technology and is not described here.
Market data used for testing is historical price data we license or source ourselves. It is not personal data and does not come from your broker or your account.
5MetaTrader and your broker
RoboticEA is not affiliated with MetaQuotes. We are not a partner, licensee, agent or authorised distributor of MetaQuotes Ltd, and we are not endorsed by them. MetaTrader and MetaTrader 5 are registered trademarks of MetaQuotes Ltd, used here only to describe compatibility.
We never trade in MetaTrader on your behalf, and we never run your strategies live. RoboticEA produces a strategy file that you may choose to install in your own MetaTrader terminal, under your own broker account, at your own discretion. We hold no credentials for your broker or your terminal, we place no orders, and we have no ability to do so. The only time we run anything in MetaTrader is on our own machines, for testing: to check that an exported strategy behaves the same way there as it does in our engine.
Because of this, we never hold broker logins, account numbers, balances or positions. If you run an exported strategy yourself, whatever happens in your terminal stays between you and your broker. We do not receive it.
6Our legal basis (GDPR)
- Performance of a contract: running your account, storing your strategies, providing the features you signed up for.
- Legal obligation: keeping billing and accounting records.
- Legitimate interests: keeping the service secure, preventing abuse of the free tier, and diagnosing faults. We use the least identifying data that achieves this.
- Consent: analytics. Google Analytics runs only after you accept it in the consent banner, and you can withdraw that consent at any time (see Cookies). We have not asked for consent to advertising cookies, so in the EEA, UK and Switzerland none are set — our ad measurement is switched off there rather than bundled into your analytics answer.
7Who else processes data
We keep this list short on purpose. Each provider acts on our instructions:
- Stripe: payments and subscriptions. Stripe receives your billing details directly; we never see or store your full card number.
- OpenAI: processes the text you submit to the AI features, as described above.
- Google: Google Analytics (only after you consent), Google Ads conversion measurement (outside the EEA, UK and Switzerland only), and Google sign-in (only if you choose it).
- Our hosting and infrastructure providers: who operate the servers the product runs on.
Some of these operate outside the EU/EEA. Where personal data is transferred abroad, it is protected by an approved transfer mechanism such as the European Commission’s Standard Contractual Clauses.
9Your rights
Under the GDPR you can ask us to give you a copy of your data, correct it, delete it, restrict or object to processing, or provide it in a portable form. You can delete your account yourself at any time, which removes your strategies and personal data except records we must keep for accounting.
Write to [email protected] and we will respond within the time the GDPR allows. If you believe we have handled your data wrongly you may complain to your national supervisory authority. In Finland, that is the Office of the Data Protection Ombudsman (Tietosuojavaltuutetun toimisto).
10Security and retention
Passwords are stored hashed. Access to production data is restricted to those who need it to operate the service. Backups are taken so that an outage does not lose your work. No system is perfectly secure, and we will tell you and the regulator if a breach occurs that requires it.
11Children
RoboticEA is not intended for anyone under 18, and we do not knowingly collect data from children.
12Changes to this policy
If we change how we handle your data we will update this page and the date above, and announce anything material in the product. Our Terms of Service govern use of the product itself.
Company information
Konvert Technologies OyRuukintie 93 b7
60100 Seinäjoki
Finland
[email protected]
Konvert Technologies Oy operates RoboticEA. Written questions about these terms, your data, or a request to exercise your data-protection rights can be sent to the address or email above.

