Black Friday: all 12 tools. Until 1 December.Black Friday $606.98 one by one

$606.98 one by one $49 once Save $557.98Get the SuiteGet it
Updated 2026-11-19

Privacy Policy

FLAWLESS FRANCIUM CO., LTD. · 2026-09-09

1. Data we collect

Email address, password (hashed), purchase history, license activations (account ID + timestamp), support communications. If you use TradeLens Cloud, we also store the trade history you import or sync — instruments, entry and exit prices, volumes, profit/loss, and timestamps — so the app can compute your statistics and the AI coach can review your trades. We do not collect your MT5 broker password (the optional MT5 connection is read-only; its investor password is never stored by us — it is passed once to our broker-connectivity processor, MetaApi, to establish the read-only connection and is held only by them), your live account balance or funds, or browsing data outside ProEA pages.

2. How we use data

Account access, license validation (verify your EA is on a permitted MT5 account), customer support, requested emails, product improvement and advertising measurement. We measure page visits, clicks, engagement and conversions. Optional analytics can associate activity with browser identifiers; this is not the same as anonymous aggregate reporting. Advertising measurement may send hashed contact details and event identifiers to the platforms below when enabled under the cookie choice described in §6. For TradeLens Cloud, imported trade data powers your own dashboard and AI coaching. We do not sell or rent that trade history.

3. Third-party processors

Supabase provides authentication and database storage; Stripe processes payments (card data never touches our servers); Resend delivers transactional emails and marketing emails you request; Vercel hosts the site and provides cookieless web analytics. When configured, PostHog provides product analytics and may provide session replay according to its project settings, while Meta, X and Google provide advertising measurement. These optional integrations follow the cookie choice described in §6. Only if you connect an MT4/MT5 account for auto-sync, MetaApi processes your read-only investor password and the trade history it retrieves to sync your trades.

4. Data retention

Active accounts: until you delete. After /account/delete: 30 days for legal/tax retention, then full purge. This includes any TradeLens Cloud trade history you imported. License logs are anonymized (user_id replaced with NULL) on deletion to preserve audit trail.

5. Your rights (PDPA + GDPR)

Access, rectification, deletion, data portability, withdrawal of consent. Most can be exercised in /account; for the rest, email privacy@pulltrade.app and we respond within 30 days.

6. Cookies

Essential cookies keep sign-in and privacy choices working. Optional analytics, session replay and advertising start only after you select Accept. Reject keeps them off. You can change your choice through Privacy choices in the footer. PostHog records only approved public pages, with all inputs masked; member/account pages, checkout, private trade data, browser console logs and network bodies are excluded. New replays are retained for 30 days. We discard client IP addresses after enrichment. Anonymous operational order counts remain separate from consented browsing funnels. Vercel provides cookieless aggregate analytics independently. When a page first opens in a browser tab, the tab notes where it arrived from: the kind of site (for example a search engine, an AI assistant or a social site), that site's domain or the link's utm_source tag, and the page you landed on. It's kept in the tab's session storage, which is cleared when the tab closes, and holds no identifier. Our cookieless analytics count it when you start a checkout, and it's attached to your order so we can tell which channels bring buyers: never after you select Reject, and in the EEA, the UK and Switzerland (and wherever we can't tell your country) only after you select Accept. A partner link to tradingview.com (Terms, section 9c) sets no cookie on our site; TradingView sets its own when you arrive there, under TradingView's privacy policy. TradingView learns only which of our pages you came from (the link's page label and the referring address), nothing else about you. An affiliate link to traderspost.io (Terms, section 9c) also sets no cookie on our site. It carries only our referral id, so TradersPost learns that you came from ProEA (and the referring address), and it sets its own referral cookie (90 days, its affiliate page says) when you arrive there, under TradersPost's privacy policy. A page with an FTMO partner link (Terms, section 9e) asks our server which country your connection comes from, so that a visitor in the United States gets FTMO US's link; the answer is kept only in the open tab's memory and isn't stored or logged. Our other labelled affiliate links (FXSVPS, FX Replay, Tradesyncer, ForexVPS, The5ers, edgeful and Alpha Futures; Terms, sections 9d, 9i, 9j, 9l, 9n, 9o and 9r) likewise set no cookie on our site; each carries only our referral parameter and opens that company's site, where it handles its own referral tracking under its privacy policy. Email subscriptions are a separate choice and can be cancelled using the unsubscribe link. Contact privacy@pulltrade.app for assistance. When you arrive through the link of a ProEA partner (a member of ProEA Partners, our own affiliate programme: a proea.app link with ?via= and a partner code, or a partner's own page at proea.app/p/CODE), we keep that partner's code in a first-party cookie, proea_aff, for 90 days, and attach it to your order so we can pay that partner; the last partner link you open wins. When it replaces a different partner's code, the earlier code moves to a second first-party cookie, proea_aff_prev, also for 90 days, which checkout uses only if the newer code doesn't belong to an active partner. In the EEA, the UK and Switzerland, and wherever we can't tell your country, neither cookie is set until you select Accept. If you select Reject, neither cookie is set anywhere, and no partner code is attached to your orders, including one stored before. If you buy from a partner's own page, its buy buttons also send that partner's code with your order, so the partner is credited even where no cookie was set, unless you selected Reject. Each visit through a partner link is counted for that partner without identifying you: we record the page you landed on (without its query string), the referring site's domain (not the full address), your country and your device class (desktop, mobile or tablet), and the partner can see these details for the clicks on their own link. With that count we keep a one-way hash of your IP address (for IPv6, of its network), made with a key that changes every UTC day, so the same address can't be followed from one day to the next; we keep it to check for fraud, such as a partner clicking their own link. At checkout, when a partner is credited, the same kind of hash of your address is compared with the hashes kept for the partner's own visits to catch self-referral, and only the answer (a match or not) is kept with your order. In the EEA, the UK, Switzerland and wherever we can't tell your country, these hashes are made only after you select Accept; elsewhere they are made unless you selected Reject. Your raw IP address is never stored. The cookies hold only the partner code. A partner's audience discount, when one applies to your order, is applied by our checkout and shown before you pay; it never stacks with another discount (where a sale, claim or offer price applies, you get that price instead), and it is not a code anyone can type. What we keep about partners themselves is in section 6c.

6a. Port Service projects

If you use the Port Service we store your name and email address, the script or description and the files you send (scripts, archives, screenshots), the project conversation and its attachments, the quotes (with the time you accepted one and the Terms version you accepted it under), the payment's status, amount and Stripe references (Stripe holds the card details), the delivered files, and a log of the project's steps. To stop the request form being used to send repeated emails, we also keep, for two days, a keyed one-way hash of the network a request came from (your IPv4 address, or the /64 block of an IPv6 address), never the address itself. We use these to quote, do and deliver your port, to answer you and for our accounting records. Your private project link is not stored in our database (only a one-way hash of it) and never reaches our analytics; like any web address you open, it does pass through our hosting provider's request logs (Vercel), and through our email provider (Resend) in the emails that carry it to you. Files and the pasted script are deleted 90 days after the project closes; the project record, its messages and its payment records are kept for accounting and support and deleted on request unless the law requires us to keep them. The request form, the project room and our project console are never recorded by session replay, and analytics receive no names, email addresses, code or project links: the project room loads no analytics, every way into it is a full page load, and our site analytics discard any page view of it.

6b. Pine Doctor

If you use Pine Doctor, the check and the free fix run in your browser and nothing is sent to us. If you ask to see one real change before you buy, the script is sent to our server once to run the Pro fix, only that change comes back, and the script is not stored. When you buy or unlock the Pro fix, the script is sent to our server to make the fix and to match it to your payment (a one-way hash of the script is kept with the payment at Stripe), and the script is not stored. Each time the Pro fix unlocks, the time it was first delivered and the number of unlocks are added to the payment's record at Stripe, as proof of delivery. While Stripe takes the payment, the script waits in your own browser tab (session storage); a Pass is a signed token kept in your browser (local storage). Stripe processes the payment and holds the card details. Analytics receive only which steps were used and the check's counts, never the script. If you ask to be emailed when the Pro fix opens, we keep your address and your consent for that one email (Resend sends it), never with the script.

6c. ProEA Partners: data about partners

If you join ProEA Partners, our affiliate programme, we keep your partner record: the email address of your ProEA account, your display name, your website and channel links, your audience note, your country, your payout method (PayPal or Wise) and payout address, your partner code and status, the proea.app page you applied from (its path only), the version of the Partner Agreement you accepted, your commission and payout records (each sale credited to you, its amount, your rate, its status and dates, and each payout), and a log of the programme emails we send you (which one and when; reply STOP to any of them and we stop sending them). Your display name is public: it is shown on your partner page (proea.app/p/YOURCODE), with your audience discount; nothing else from your record is. Where the cookie choice in section 6 allows it, we also keep a one-way hash of the IP address you use when you apply and when you open your partner dashboard, made with a key that changes every UTC day, never the address itself; it is compared only with the hashes of buyers credited to you, on the same day within the 30 days before a sale, to catch self-referral. The clicks on your link are recorded as section 6 describes; your dashboard shows them, never a hash. We use all this to run the programme, to pay you (PayPal or Wise receive your payout address and the amount when we send a payout) and to prevent fraud and self-referral. We keep your partner record while you are a partner. When the partnership ends, your partner page stops showing, and once your last commission is settled we delete your channel links, audience note, payout address and IP hashes on request; your commission and payout records, with the name and payout details they were paid to, are kept as financial records for as long as tax and accounting law requires. Deleting your ProEA account (section 4) does not delete your partner records by itself: email privacy@pulltrade.app to end your partnership and have erased everything the law lets us erase.

6d. Tools for AI assistants (MCP)

AI assistants can call our free calculations through proea.app/api/mcp: killzone and session times, position sizes and our killzone study's counts. It needs no account and sets no cookie. What an assistant sends (a time zone, a date, a balance, a stop distance) is used to compute the answer and is not stored by us, though our host's request logs (section 3) may briefly hold request details, as they do for any page. We count each call in our analytics by the tool's name only: the event carries no IP address, browser details or cookie. To slow floods, the server keeps the sending network's IP address in its working memory, never in storage; it is gone when that server instance restarts. Links in the answers carry utm_source=mcp, so a visit that follows one is counted like any other visit, as section 6 describes.

6e. ProEA Market Alerts on Telegram

If you start ProEA Market Alerts, our free Telegram bot (it sends forex session, ICT killzone and clock-change times, and the prop firm rule changes you choose to follow), we store your Telegram chat id, the time zone you pick, the alerts and lead time you choose, the prop firms you follow, when you started the bot, and up to when alerts have been sent to you. We don't store your name, username or phone number: Telegram sends your name and username with each message, and the bot reads only the command or the city you type and keeps none of it. We use these only to send you the alerts you chose; Telegram delivers the messages, under Telegram's privacy policy. To see how many people keep the alerts, we also count, per day and with no identifier, how many people start the bot and how many of them stop within 30 days. Send /stop to the bot to delete your chat id and settings at once; if you block the bot, we delete them the next time an alert to you fails. /now answers without storing anything. Links in the bot's messages carry utm_source=telegram, so a visit that follows one is counted like any other visit, as section 6 describes, and our host's request logs (section 3) may briefly hold request details, as they do for any page.

6f. All-Access first week

If you start an All-Access Monthly first week, we keep a record of it so that each person gets one: your account id, a one-way SHA-256 hash of your email address (not the address itself; dots and +tags that reach the same mailbox count once), your Stripe customer id, the Stripe fingerprint of the card you paid with (an identifier Stripe derives from the card, never the card number), the subscription id and when the trial ends. If that card has already had a first week, the new one is cancelled at once and its $2.99 refunded in full (you are not charged the $14), and we record that reason and when we emailed you about it. This record is kept after the first week ends, and after you delete your account (the account id is then removed from it), because its only purpose is to stop a second first week. When you start checkout we also ask Stripe whether a customer with your email address has had a subscription before. During the first week we record which products you chose to download (at most 2) and when, so the choice cannot be changed; that record is deleted with your account. When you claim the first-week price while signed in, or first use a claim at checkout, we record that claim's two deadlines (the 5 minutes and the 24-hour wait) against your account, so the wait applies to your account and not just one browser; that record is deleted with your account. About three days before your first monthly charge we email you a reminder of the date, the amount and how to cancel, and we record when we sent it so you get one.

6g. The free tools' member side

The member side of the free tools reads, on our server, whether the ProEA account you are signed in to holds a live All-Access subscription; it stores nothing new about you. Your alarms, the challenges you track and the trades you log in the risk budget are stored only in your browser (localStorage); we never receive them. Scripts you paste into the Pine merger are merged in your browser and never sent to us. Someone who bought ProEA Pro on its own before it was folded into All-Access: their browser keeps a cookie, proea_pro, that names their Stripe subscription and customer ids and until when it is on, signed so it can't be altered, with no name, email or card detail; it is deleted when that subscription has ended. We count member clicks, alarms set and alarms rung in our analytics without your email or ids, as section 6 describes.

7. Contact

Questions? Email legal@pulltrade.app or use the in-app support widget.