Privacy policy.
Plain English. Last updated 20 October 2026.
Who we are
Deepwick is a brand of EV Trading Labs, which decides how your data is used (the “controller”). For anything about your data, write to privacy@deepwick.com.
This policy covers deepwick.com: the public site, the platform you use after signing in, and the emails, alerts and notifications it sends.
What we collect
Your account. Your email address and language. If you sign in with Google or Apple, they tell us an account ID that does not change, your email address and whether it is verified (with Apple you can hide your real address behind a relay address). Sign-in links are valid for 15 minutes and we keep only a hash of them. A session lasts 30 days. If the link that brought you to sign up carried campaign tags (utm_source and similar), we note those tags and the page it pointed to, and we note when you first run a strategy, so we can tell which channels bring people who use the product.
Your public profile, if you fill it in. Handle, display name, bio, avatar, website, location and your X and GitHub handles. Your profile page, who follows you and what you publish are public.
What you create. Watchlists, chart layouts and drawings, scripts and their versions (private, protected or public, as you choose), ideas, comments, likes and follows, backtests, paper trading, your journal, competition entries and the reports you send us. Backtests stay private unless you create a share link, and share links expire. Results of public competitions are public.
Messages. Direct messages are visible to you and the person you write to. Community chat is visible to every signed-in user. If something is reported to us, a moderator may read it to decide what to do.
Alerts. The rules you set and a log of each delivery. If you send alerts to Telegram, Discord or your own webhook, we store what you give us for that: a Telegram bot token and chat ID, a Discord webhook address, or your webhook's address and signing secret.
Push notifications, if you turn them on. The push address your browser gives us, its encryption keys and your browser's user agent.
The MT5 bridge, if you connect it. A label, the broker name, a hashed connection token, the permissions you grant, the orders you send and the trades your terminal reports (symbol, side, size, prices, profit, commission and swap).
The AI assistant, if you use it. Your conversations with the assistant (your questions, its answers and the symbol you pinned to the chat) are stored so you can come back to them, until you delete the conversation. If you add your own MiniMax, OpenAI or Anthropic key, it is stored encrypted and used only to send your requests to that provider. Screenshots you attach to a message are sent to that provider with the message and are not stored.
AI quality logs. When an AI answer goes wrong (a change to your chart could not be made, the assistant ran out of steps before finishing, or you rate the answer 👎), we keep a separate record of that answer to improve the assistant: your question, with email addresses, keys and tokens, wallet addresses, phone numbers and long numbers removed, cut to 500 characters; the chart's symbol, exchange, timeframe and indicator types; the tools the assistant used and what they returned, with the same details removed and without price data or script code; the model, the language, what went wrong, your rating and comment (cleaned up the same way) and the app version. It is pseudonymised: instead of your account we store a keyed hash of it, and the record does not contain your email, your name or your account ID. We delete it 30 days after it was recorded.
Trade imports and linked accounts, if you use them. When you import your MT5 trades into the journal we match them to your journal entries; trade files you upload are deleted after 7 days. If you link a broker account, we store its label, the broker and the credentials you give us to sync your trades.
Support. What you write to the support form or the help assistant, and your answers to “was this helpful?”.
Error reports. When the app fails in your browser we record the error, the page, your browser's user agent and, if you are signed in, your account. We keep these for 30 days.
Onboarding and preferences. The markets, instruments and alert channels you pick when you start, and settings such as your theme and email preferences.
The waitlist from before launch. Email, language, your optional answers, where you came from (UTM parameters and the referring site) and when you gave consent.
Security. To limit abuse we count requests against a salted hash of your IP address. We never store your raw IP.
Payments, if you subscribe. Stripe sells the subscription and handles your card. We receive your Stripe customer ID, the plan, its status and the renewal date, never your card number.
Referral parameters. When you arrive through a partner link we keep the referral code and the campaign parameters it carries, so we can tell which partner brought you. The broker on the other end of that link receives the same code, and applies its own privacy policy to the account it opens for you.
We do not collect your precise location, your contacts, device fingerprints or advertising identifiers.
What we use it for
- To run the platform and do what you ask it to do: sign you in, save your work, run backtests, deliver alerts and show your public profile. This is necessary to provide the service you signed up for.
- To send you email: sign-in links, the alerts you configure, test messages you request and, now and then, a product email such as tips to complete your profile. Every product email has a one-click unsubscribe link.
- To keep Deepwick secure, prevent abuse and enforce our community rules. This is our legitimate interest.
- To improve the AI assistant, with the AI quality logs described above. This is our legitimate interest; you can object to it at any time (see “Your rights”).
- To count page views in aggregate with Cloudflare Web Analytics, which sets no cookies.
- If you accept analytics cookies, to see which pages and features people use, with Google Analytics. This is based on your consent, which you can withdraw at any time.
- Push notifications and the waitlist are based on your consent, which you can withdraw at any time.
We do not sell or rent your data, we do not show ads and we do not build advertising profiles.
Signing in with Google
If you choose “Continue with Google”, we use what Google tells us only to sign you in and recognise you next time. We don't receive your Google password, your contacts or any other data from your Google account, and we don't share what we receive with anyone. Our use of it follows the Google API Services User Data Policy, including the Limited Use requirements.
You can disconnect Deepwick at any time from your Google Account (Security → Your connections to third-party apps & services).
Who else handles it
Only the services needed to run Deepwick, each for its own part:
- Cloudflare: hosting, database, the email address you write to, and page counts.
- Resend: sending our emails.
- Google and Apple: only if you sign in with them.
- Telegram, Discord or your own server: only if you send alerts there; they receive the content of each alert.
- Your browser's push service (Google, Apple or Mozilla): only if you turn on push notifications.
- MiniMax, OpenAI or Anthropic: only if you use the AI assistant with your own key from that provider. It receives your question, the context of the chart you are looking at and any screenshot you attach.
- Stripe: only if you subscribe to a paid plan.
- The broker you open an account with: only if you follow one of our partner links. The link carries a referral code so the broker knows the account came through us; the broker then applies its own privacy policy and terms to that account.
- Google Analytics: only if you accept analytics cookies. It receives the pages you visit, your browser and device type, and an approximate location worked out from your IP address, which it does not store. Google signals and advertising features are off.
We fetch market prices from providers such as Binance and VT Markets; they receive no personal data about you. Some of the services above are based in the United States or run worldwide. Those transfers rely on the EU–US Data Privacy Framework or the standard contractual clauses in each provider's data processing terms.
How long we keep it
- Account data and what you create: while your account is open. When you ask us to close it, we delete your account and its data without undue delay and within one month, unless the law requires us to keep something longer.
- Sessions: 30 days. Sign-in links: 15 minutes.
- Community chat: 90 days. Direct messages: until you or a moderator deletes them, or your account is closed.
- AI assistant conversations: until you delete them, or your account is closed.
- Help assistant exchanges: 90 days. Error reports: 30 days. AI quality logs: 30 days. Uploaded trade files: 7 days.
- Push subscriptions: until you turn notifications off or your browser cancels the subscription.
- Google Analytics: visit data for 2 months; its cookies last up to 2 years unless you withdraw consent.
- Waitlist entries: until you ask us to delete them, or 24 months after your last interaction.
Copies of open-source scripts that other people made before you left belong to them.
Your rights
Under the GDPR and similar laws, you can ask us to:
- show you the data we hold about you;
- correct it;
- delete it, including your whole account;
- restrict how we use it, or object to a use (for example, product emails);
- give it to you in a portable format.
Write to privacy@deepwick.com and we will reply within one month. You can also complain to the data protection authority where you live or to the Spanish one (AEPD, aepd.es).
Cookies and local storage
We always set three first-party cookies, all needed for the site to work:
dw_sessionkeeps you signed in for up to 30 days.dw_oauthprotects a sign-in with Google or Apple and lasts a few minutes.dw_chart_uiremembers how you left the chart page (trade panel and account panel open or closed, tab and view).
A fourth first-party cookie, dw_aff, is set only when you open an affiliate link (?via=) while the affiliate programme is active, you are not signed in and the code belongs to an approved affiliate. It lasts 30 days. What it holds and what we do with it is explained under “Affiliate programme” below.
The app keeps your chart layout, appearance, theme and similar preferences in your browser's local storage, and the waitlist form remembers where you came from in session storage. We do not run Meta Pixel or any advertising tracker. Cloudflare Web Analytics sets no cookies and does not fingerprint your device.
If you accept analytics cookies in the banner, Google Analytics also sets _ga and _ga_1B5CTVK87V to tell visits apart. They last up to 2 years. If you reject or ignore the banner, Google Analytics does not load at all. Your choice is kept in your browser's local storage.
Affiliate programme
This section applies when the affiliate programme is active.
If you arrive through an affiliate link. When you open a Deepwick page with ?via= and a code, you are not signed in, your browser is not a crawler or link-preview bot and the code belongs to an approved affiliate, we add one to that affiliate's daily click total (a count per day, with no IP address, user agent or other identifier stored with it) and set the dw_aff cookie. The cookie holds the affiliate's code and the time of your click. It is first-party, HttpOnly (scripts on the page cannot read it), Secure and SameSite=Lax, and lasts 30 days. If you open another affiliate's link, the last click replaces it.
When you create an account. If dw_aff (or a ?via= that travelled in your sign-in link) points to an approved affiliate, we record once, on your account, which affiliate it was, the time of your click and of your sign-up, and a status (valid, flagged for review or rejected). To spot people referring themselves, we compare your account and your email address, with case, the part after “+” and, for Gmail, dots ignored, with the affiliate's. We store a salted hash of that email address and a salted hash of your IP address at that moment, not the values themselves. We do not store a hash of your user agent. The affiliate never sees any of this: affiliates only see totals (clicks, sign-ups, balances), never your name, email address or account.
If you subscribe to a paid plan. For each payment we record a commission linked to your account: the invoice and charge references, the amount paid without VAT, the commission and its status. No card details.
If you are an affiliate. We keep your code, your application status, the payout method you choose (Deepwick credit or manual), the terms version you accepted and when, and what our administrators do on your account (approvals, reversals, payouts, with who and when). When a payout is registered we record its amount, date, method and a reference our team writes. The application form does not ask for bank or PayPal details. Our administrators can see the affiliates' and referred accounts' handles in the admin panel and in the monthly export, which does not include the referred person's identity.
Your choices. You can delete the dw_aff cookie in your browser at any time. For access, correction or deletion of any of the data above, write to privacy@deepwick.com, as described under “Your rights”.
Security
Everything travels over HTTPS. Sign-in links, MT5 connection tokens and two-factor recovery codes are stored as hashes, AI keys are encrypted, and only administrators can reach the database. No system is perfectly secure; if you find a problem, please tell us at privacy@deepwick.com.
Children
Deepwick is not meant for anyone under 18.
Changes
When this policy changes we update the date at the top. If a change affects how we use your data, we tell you by email before it applies.
Contact
Questions, deletions or complaints: privacy@deepwick.com. We aim to reply within 48 hours on European business days.