Privacy Policy

01Who we are

The Screener is operated by the developer of ArbScreener. For any privacy request, contact us at the address in Section 11. (The operator's legal identity will be updated here if and when the project is incorporated.)

02What we collect

• Email address — required for both Free and Pro access: Free access is issued one per email address, and your Pro License Key is delivered to the address you provide. We store a salted hash of your email (to check "one Free signup per address" without keeping it in plain text for that check) and, separately, an encrypted copy (to be able to resend your License Key); we do not store your email in plain text.
• Telegram chat ID & alert preferences — if you subscribe to alerts, so the bot can message you with the thresholds/opportunities you chose.
• Pro purchase data — your on-chain payment transaction (which is public on the blockchain) and the License Key we issue, to activate and verify your access.
• Acceptance record — when you accept the Terms / confirm you are not an Excluded Person, we record the fact, the version of the Terms, and a timestamp.
• Technical & security data — IP address, browser user-agent, and a dashboard access credential (session cookie), used to serve the site, keep it secure, prevent abuse, and apply the jurisdictional access restrictions in the Terms. See Section 8 for how long this is kept.
• Interface settings — your own preferences (e.g. sort order, filters, refresh settings, and a Telegram chat ID you type into the subscribe form) stored in your browser (see Section 5).
• Basic usage events — we record first-party events on our own server (for example, that a sign-up or a Telegram subscription happened, with a timestamp and, if you arrived through a campaign link, the campaign tag taken from that link's address, captured into a first-party cookie — see Section 5). These events are not linked to your IP address, browser, or identity, and no third-party analytics or advertising service is involved.

What we do NOT collect or do: we do not connect to, control, or custody your wallet or funds; we do not ask for your name, address, or government ID; we do not run third-party ad/analytics trackers; and we do not sell or rent your personal data to anyone.

03Why we use it (purposes)

• to operate the Screener and show you redemption spreads / cross-chain opportunities;
• to deliver the Telegram alerts you subscribed to;
• to activate, deliver, and verify Pro access and License Keys;
• to secure the Screener, prevent abuse, and debug problems;
• to apply our access restrictions and comply with sanctions and other legal obligations;
• to keep a record that you accepted the Terms;
• to understand, in aggregate, which campaigns bring visitors who actually sign up or subscribe — not to identify you individually.

04On-chain payments are public

Pro is paid on-chain. Blockchain transactions are public, permanent, and outside our control: the paying address, amount, and time are visible to anyone, and we cannot edit or delete on-chain records. When you pay for Pro and give us an email for your License Key, we may be able to associate that payment with your email/Key. Consider this before paying from an address you wish to keep unlinked.

05Cookies & local storage

Everything the Screener stores in your browser falls into three categories:

• Strictly-necessary cookies. A session_id cookie that keeps you signed in (HttpOnly, Secure, SameSite=Lax, kept up to 30 days — see Section 8), and, for the operator only, a separate admin_tok cookie scoped to the admin area (HttpOnly, Secure, SameSite=Strict, 8-hour lifetime). Neither is readable by JavaScript, carries tracking, or is shared with third parties.
• Functional interface settings (local storage). Your own display choices — such as sort order, filters, and refresh settings — and the Telegram chat ID you type into the subscribe form, kept only in your browser so the interface remembers how you left it.
• First-party attribution cookie. If you arrive via a campaign link (one carrying utm_source), we set a first-party arb_attr cookie (HttpOnly, Secure, SameSite=Lax) holding only the campaign tag from that link, for up to 30 days, so that a sign-up or Telegram subscription you complete later — even on a different page — can still be credited to the campaign that brought you. It is never overwritten by a later visit (first touch only), is read only by our own server, is not used for advertising or cross-site tracking, and is not linked to your identity.

We do not place any third-party cookies, and we run no third-party analytics or advertising trackers. Because every cookie we set is first-party, is either strictly necessary or used solely for our own internal campaign reporting, and the Screener already excludes EU/EEA/UK visitors under the Terms, we do not display a cookie-consent banner. You can clear any of this at any time in your browser settings: clearing local storage resets your display preferences, and clearing cookies signs you out and clears any stored attribution.

06Who we share it with

We do not sell your data. We share the minimum necessary with the service providers that make the Screener work, who process it on our behalf or as independent controllers under their own policies:

• Telegram — to deliver alerts (your interaction with the bot is also governed by Telegram's own privacy policy);
• Render — our hosting / infrastructure provider, which runs the website and database (see Section 7);
• Market-data, DEX-aggregator, RPC & indexer providers — the public data sources the Screener reads from (these receive technical request data, not your identity).

We may also disclose data where required by law, to comply with sanctions, or to protect the Screener's or others' rights and security.

07Where your data is processed

The Screener's website and database are hosted with Render, in its Frankfurt, Germany region, and the operator is based outside the Excluded Jurisdictions. By using the Screener you understand your data may be processed in the locations where those providers operate. (Hosting infrastructure being located in the EU does not change who may use the Screener — see the Terms' Excluded Jurisdictions.)

08How long we keep it

• Telegram chat ID & preferences — until you unsubscribe (or ask us to delete them), plus a short period to action the removal.
• Email & License Key — for the duration of your Subscription and a reasonable period afterwards for records and support.
• Acceptance records — kept as long as needed to evidence your agreement to the Terms.
• Session technical data (incl. IP, user-agent) — a session is deleted once it has been idle for 30 days (the same window as the session cookie's own lifetime); checkout-related IP/user-agent data is similarly cleared after 30 days.
• Attribution cookie — expires automatically after 30 days.
• On-chain payment data — permanent on the blockchain and outside our control (Section 4).

09Your choices & rights

• Alerts: you can unsubscribe at any time via the bot; this stops messages and lets us remove your chat ID.
• Access / correction / deletion: contact us (Section 11) and we will action reasonable requests about the data we hold, subject to records we must keep and to data that cannot be deleted (on-chain records — Section 4).
• Where mandatory data-protection law gives you additional rights despite the Screener not being offered in your jurisdiction, we will honour those that apply.

We will not discriminate against you for exercising any of these choices.

10Security & children

We apply reasonable technical measures to protect the Screener and the limited data we hold, but no method of transmission or storage is 100% secure, and we cannot guarantee absolute security. You are responsible for safeguarding your own Telegram account and your License Key.

The Screener is not intended for anyone under 18, and we do not knowingly collect data from minors.

11Contact & changes

Questions or privacy requests: arbscreenerdefi@gmail.com · X: @ArbScreenerDeFi.

We may update this Privacy Policy from time to time; changes take effect when posted, with an updated "Last updated" date above. Material changes will be indicated by updating that date.