Privacy policy
Last updated 2026-10-15
outcometick has no user accounts. You hold API keys, and what we record is tied to those keys and to your payments. This page lists what that is.
When you browse the site
The site uses Google Analytics 4, which sets cookies and records pages viewed, approximate location and device type. We use it to see which pages are read; we do not use it for advertising.
Our servers keep standard access logs (IP address, time, requested URL, user agent) for operations and abuse handling. They rotate and are deleted on a short schedule.
When you buy
Card and wallet payments are handled by Stripe. We never see card numbers. Stripe gives us the email address you entered at checkout, a customer reference and the payment status; we use the email to deliver your key and to contact you about your purchase.
Keys are emailed through Brevo. We store only a hash of each key, so we cannot show it to you again; a lost key is revoked and reissued.
Stablecoin payments are matched by amount and transaction hash. Those, and the paying address, are public on the blockchain; we store them with the order.
After a purchase we may ask how you found us. The answer is stored with the purchase reference only.
When you use an API key
For each key we record, per day, the IP addresses and networks it was used from, request counts and bytes served. This is how we enforce the key's terms and spot a leaked key. These rows are deleted after 90 days.
We record when a key was created, last used and revoked.
When you run a backtest
We store the strategy files you submit, the run record (status, credits, timing), the IP address and user agent of the submission, and the email address you give for the report.
Submitted strategy source is kept, without a fixed deletion date, so it can be reviewed if a submission is suspected of abuse. It is not shared and not used to build anything of ours.
Report archives stay downloadable for 7 days.
When you connect an AI client (MCP or OAuth)
If you connect a client such as Claude or ChatGPT through OAuth, we store the client registration it sends (its name and redirect addresses), which of your keys you approved, and hashes of the tokens we issue. With OAuth the client never receives your key; you can see and disconnect connected apps at outcometick.com/connections, revoking the key ends their access at once, and the tokens also expire on their own.
If you instead put your key into a client's settings (an Authorization header), that client holds the key, and how it stores it is up to the client.
Requests made through a connected client are recorded against your key exactly as direct API calls are. What the client does with the data it receives is governed by that client's own policy.
Who processes data for us
Stripe (payments), Brevo (email delivery), Google (analytics), Cloudflare (DNS and file storage), Telegram (internal notifications) and the hosting providers that run our servers. Each receives only what its job needs. We do not sell personal data or share it for advertising.
We send ourselves internal notifications through Telegram: a purchase notice can include the buyer's email address and the amount, and a backtest notice can include the purchaser reference, email address, the run's scope and a summary of its result or failure.
Our support channels on Telegram and Discord are run by those platforms under their own policies.
How long we keep it
Payment and key records are kept for as long as they are needed for the purchase, for accounting and to answer disputes. Usage rows and report archives follow the windows above.
Your choices
Email support@outcometick.com to ask what we hold about you, to correct it, or to delete it. We will delete what we are not required to keep (payment records for accounting) or need for abuse review. You can block analytics cookies in your browser without losing access to anything.
The service is not directed at children.
Changes
When this policy changes, the date at the top changes with it.