Privacy Notice
Stratlate is built to know as little about you as possible: no analytics scripts, no advertising, no tracking. It is not built to know nothing. Converting your own script requires an account, and every conversion is saved against it — that is how your allowance is counted and how you get a history. This page says exactly what is kept, for how long, and what it is and is not used for.
1. The code you submit
Validation, linting and the feasibility check need no account. Their text is sent to our servers, processed in memory in a serverless function, and returned in the same response; nothing is written down and when the request ends it is gone.
A conversion is different, and this changed on 6 September 2026. When a conversion succeeds we store a record of it: against the account that made it, or, for a conversion made without an account, against a one-way hash of the network address it came from. The only conversion that runs without an account is the worked example published on the site, which is a demonstration and counts against no allowance. The record holds the source code you submitted, the converted output, the warnings and errors the engine raised, the languages and the version of the engine that ran, and the time. It is stored encrypted and it is deleted automatically 12 months after it is written.
If you submit a conversion critique, we store its text and any text attachment with that conversion so you and our support team can review the reported problem. Critiques expire with the conversion. You can separately allow us to use the critique and its conversion to improve the engines; that choice is recorded with each submission.
AI review (from 15 September 2026). After a conversion made with your account succeeds, an automated AI review may try to improve it. For that review your submitted source code, the converted output and the engine's diagnostics are sent to our AI model provider, OpenAI, which processes them to produce a revised script. OpenAI's API terms state that data sent through its API is not used to train its models by default and is kept only for a limited period for abuse monitoring. The revised script, and never your original source code, is sent to TradingView's Pine Script compiler solely to check that it compiles. The review's result is stored with the conversion and deleted with it. The published example is never reviewed.
We do this for three reasons, and no others: so you have a history of your own conversions; so your conversion allowance can be counted against your account rather than your network address; and so that when a conversion comes out wrong we can look at the exact input and the exact output instead of guessing. These records are never sold, published or redistributed.
We also use these records to test and improve the conversion engines, as described in section 2. That is a real use of your code and it is stated here rather than assumed.
2. Optional corpus contribution
We use your stored conversions internally to test and improve the converter and its engines. A conversion that came out wrong is the single most useful thing we can look at, and this is how the tool gets better. Until 10 September 2026 this required ticking a box labelled "Help improve Stratlate"; that box is gone and the use is now described here and in the Terms instead of being buried in a checkbox almost nobody read.
The limits are unchanged and they are the ones that matter: these records are never sold, never published, never redistributed, never shared outside our own development, and never used to build anything other than this Service. They are deleted 12 months after they are written. If you would rather your code were not used this way, do not submit it — validation, linting and the feasibility check need no account and are not stored, and the published example converts without an account.
Nothing that identifies you is stored with the copy: no account, no email address, no IP address, no browser identifier. Your choice is remembered in your own browser and you can untick the box at any time; unticking stops future copies but cannot recall a copy that was already anonymised, because we have no way to connect it back to you.
3. Accounts, free-tier counting and API keys
Signing in creates an account with Amazon Cognito, which holds your email address and sign-in credentials. Conversions are counted against that account. Converting your own script requires one; the only conversion that runs without an account is the worked example published on the site, and its record is keyed by a one-way hash of your network (IP) address, never by the address itself, and counts against no allowance. The counter records only the number of conversions in the current month, and nothing about the code you converted.
Where you came from. When a new account is created we record two domains with it, once: which of our addresses you arrived on (stratlate.com, mql2pine.com or pine2mql.com) and the domain of the site that linked you here, such as google.com — never the full address, the page or anything you searched for. It tells us which channels bring people; it is not tracking, it uses no cookie, and it is deleted 12 months after sign-up like conversion records.
If you have a paid plan, your API key identifies your subscription and your usage is counted against it. If you save the key in the converter it is stored only in your browser's local storage; we do not receive it except when you make a request.
4. Payments
Paid plans are handled through Stripe. Stripe collects and processes your payment details under its own privacy policy; we never see your full card number. We receive from Stripe the information needed to run your subscription, such as its status and the customer identifier it assigned.
5. Browser storage and cookies
We do not use tracking cookies or analytics. The site uses your browser's local storage for a few conveniences only: whether you have accepted the current Terms of Use, whether the corpus-contribution box is ticked, and a saved API key if you chose to save one. For the duration of a browser tab it also holds the two domains described in section 3, until a sign-in sends them or the tab closes. Clearing your browser's site data removes all of them.
6. Deleting what we hold
Conversion records delete themselves 12 months after they are written. If you want yours removed sooner, or your account and everything under it deleted, ask us through the contact form and we will do it. Anonymous corpus copies made under section 2 cannot be removed on request, because nothing connects them to you — that is the point of anonymising them, and it is stated there too.
7. Server logs
Our hosting provider (Amazon Web Services) keeps standard technical logs for the serverless functions, such as request timestamps, response codes and error messages, for 14 days for troubleshooting. These logs do not contain the code you submitted.
8. Email
If you email us, we keep the correspondence for as long as needed to deal with your request and any follow-up.
9. Who is responsible, and your rights
The controller for any personal data processed through the Service is the operator of stratlate.com, established in Geneva, Switzerland. Processing is governed by the Swiss Federal Act on Data Protection (FADP). If you are in the European Economic Area or the United Kingdom, the GDPR or UK GDPR may also apply to you.
You have the right to ask what personal data we hold about you, to have it corrected or deleted, and to object to its processing. For an account that means your email address, your conversion count, and your conversion records with the code in them. Ask us through the contact form and we will respond. You may also complain to the Swiss Federal Data Protection and Information Commissioner (FDPIC) or, in the EEA, to your local supervisory authority.
Our servers are operated by Amazon Web Services. Depending on the region in use, data may be processed outside Switzerland; where that happens it is under safeguards recognised by Swiss law.
10. Changes
If we change what we collect, we will update this page and its effective date.