Privacy Policy

Last updated: 25 October 2026

1. What we collect

If you create an account, we store:

• your email address and a salted hash of your password (never the password itself);
• optional profile details you choose to give us (display name, verticals, traffic types);
• your watchlist, followed networks, and any reviews or payment-proof images you submit;
• session records so you stay logged in.

If you join the Pro founding list, we store the email address you enter, which form you used, and when. If you join while signed in with your own confirmed address, we also link the entry to your account. We use it only to email you about Pro.

For all visitors we process IP addresses transiently for rate limiting and abuse prevention. Page analytics are collected by our own self-hosted, first-party Umami instance — pages viewed, referrer, browser and coarse location. We also record a small number of product actions, such as opening the offer finder, submitting signup, signing in, saving research, following a network, connecting Telegram, starting a checkout, a completed payment and its amount, and using a calculator. We also collect browser performance timings for page loading, interaction latency, and layout stability. The page/event analytics stream excludes authentication tokens, passwords, raw search text, and private calculator values. We separately store typed public search terms with their result counts, without attaching them to an account id, so we can find gaps in the offer catalog. When you are signed in, those page views are associated with your account id (an internal identifier, never your email) so we can understand how members use the product and help you when something goes wrong. You can turn that off for a browser on your account privacy page, and it is off whenever your browser sends Global Privacy Control; the page views are then counted without your account id. We do not run third-party analytics or advertising trackers.

2. Cookies

We set functional cookies: aa_session (httpOnly, keeps you logged in), aa_authed and aa_uid (signed-in hints so pages can show your account state and link analytics to your account without reading the session; aa_authed is 1, u while your email is not confirmed,p for a Pro member, or l for lifetime access, which hides the founding offer card), aa_noid (set only if you turn off account-linked page views; for one year), aa_theme (your light/dark choice) and aa_promo (remembers that you hid the offer banner, for 30 days). After a successful signup, sign-in, email verification, watch, follow, saved search, Telegram connection request or new checkout invoice, a corresponding aa_event_*receipt can exist for up to two minutes so that action is counted once. It contains only a random receipt id, not the form contents or your email. A connected Telegram account or a completed payment is counted once per browser, remembered in this browser's local storage (aa_once_*). If you arrive through a link that carries campaign tags (ref, utm_source, utm_medium, utm_campaign), aa_ref (httpOnly) keeps those tags for up to 30 days, so a Pro purchase can be credited to that campaign; it holds only the tags themselves. If you arrive through a member's referral link (/r/ followed by their code, or a link carrying invite), aa_invite (httpOnly) keeps the first referral code you arrived with and when, for up to 90 days, so a signup can be credited to that member. On the signup, pricing and checkout pages, aa_dev (httpOnly) holds a random identifier for this browser; we store only a keyed hash of it, and use it only to stop one person from taking a one-per-person offer or a referral reward twice. We use no advertising cookies.

If you buy Pro with crypto, we store the invoice (plan, price, token, network, the amount due), the on-chain payment that settled it (transaction ID, sending and receiving addresses, amount, time) and any campaign tag sent with it. Blockchain transactions are public by nature; which account a payment belongs to is known only to us. If you sign up through a member's referral link or add their code, we record the referral on your account, with keyed hashes of your signup network and device so a self-referral can be caught; that member sees only a masked form of your email address.

3. How we use your data

To operate and improve the service: authentication, password reset and verification emails, showing your watchlist and alerts, and displaying reviews you chose to publish (shown under the display name you set on your account page, or as “CPA Radar member” without one — never your email address). Aggregate analytics help us understand whether visitors find useful offers and where a journey fails.

4. Sharing and service providers

We do not sell personal data or share it with third parties, except the service providers below, which process it for us to run the product, and where required by law.

• netcup (Germany): hosts our servers and the database, including our self-hosted analytics.
• Cloudflare: delivers every page and request (it sees your IP address and browser details), runs the human check on public forms (Turnstile), protects staff sign-in, and stores our offsite database backups (R2).
• Resend: sends our email, so it receives your email address and each message, and tells us whether it was delivered.
• Sentry: when something breaks on our servers, receives the error report: what failed, in which part of the code, and the page path without its query. Never your email, account or form contents.
• Telegram: if you connect the bot, Telegram carries the alerts we send you and gives us your chat id.

To check crypto payments we read public blockchain data from Base and TRON nodes (a public Base node provider and TronGrid). We send them our receiving addresses and transaction ids, never your account or email. We use no card processor today; if card payments are added, the checkout and this list will name it first.

5. Retention and deletion

Account data is kept while your account exists. You can delete your account yourself on your account privacy page. That removes your email address, password, profile, sessions, API keys, second factor, watches, saved searches, alerts and Telegram link at once, and takes you off the Pro founding list. Kept without your name: invoices and payments (which we must keep), credits, refunds, referrals, reviews you published (shown as “CPA Radar member”) and our security log. Our database backups are replaced on a rolling schedule, so a deleted account leaves them within 35 days. You can also ask support@cparadar.com to do it from the account's email address. To leave the Pro founding list without deleting your account, email the same address from the address you joined with.

Signed-in members can download scoped account records on every plan. The page explains the included collections, paging and exclusions. This does not delete your account or change financial or offer-history records. Contact support for questions about records outside the download.

6. Security

Passwords are hashed with scrypt; session tokens are stored only as hashes; uploads are validated and served with strict content-security headers. No system is perfectly secure — if we learn of a breach affecting your data, we will notify affected users.

7. Contact

Privacy questions: support@cparadar.com.