Privacy Policy

Last updated: October 26, 2026

1. Who we are

affpapa.org is operated by an individual developer. We provide free tools for the affiliate and iGaming industry: NeAhrefs (SEO monitoring), NeBlask (demand index), NeTGStats (Telegram channel catalogue), NeMail (disposable email) and related services. The one paid section is NeTOP.

2. Data we collect

2.1 Account data (NeAhrefs)

When you sign in to NeAhrefs (seo.affpapa.org) via Google OAuth, we receive:

• your name, email address and profile picture from your Google account;
• an OAuth token granting read-only access to your Google Search Console data.

We request the webmasters.readonly scope: NeAhrefs can read your Search Console data but never modify it.

2.2 Search Console data

When you connect a site in NeAhrefs, we fetch and store on our server:

• search analytics (clicks, impressions, positions, CTR);
• crawl data from our own crawler (up to 2,000 pages per session);
• Core Web Vitals from the Google PageSpeed Insights API;
• keyword and backlink data.

2.3 Disposable email (NeMail)

NeMail generates temporary email addresses. Emails received at these addresses are stored briefly and deleted automatically. No account or personal data is collected.

2.4 Analytics and logs

We keep standard server access logs: IP address, user agent, requested URL, timestamp.

Three third-party analytics services count visits: Google Analytics 4 (measurement ID G-TK3NFL2ZDF), Yandex Metrica (tag 110935639) and Microsoft Clarity (project ywgmybqn3k). They set their own cookies and collect usage data such as pages visited, approximate location, device and browser. How they process this data is described in the Google Privacy Policy and the Yandex Privacy Policy. We use the data only in aggregate to understand site traffic; we do not sell it or use it for advertising.

2.5 Session recording (Microsoft Clarity)

Clarity goes further than visit counting: it records how pages are used. It captures mouse movement, scrolling, clicks and taps, window size and the pages you move between, and replays them as a session recording; it also builds heatmaps of clicks and scroll depth. We use this to find broken layouts and dead ends in navigation, not to identify individuals.

Clarity masks text input by default: what you type into fields is not recorded. We do not use it on pages behind sign-in. Microsoft processes this data as described in the Microsoft Privacy Statement and retains recordings for up to 30 days. If you prefer not to be recorded, block the domain clarity.ms in your browser or an ad blocker, or refuse analytics cookies as described in section 8; the tools work the same either way.

2.6 NeTOP orders

When you create an order in NeTOP, we store what you entered: title, link, description, category, logo and, if given, a Telegram contact. For the Telegram category the channel avatar is fetched from t.me. A hash of your IP address (SHA-256 with a server secret; the address itself is not stored) is kept with the order to rate-limit submissions; the same hash lets the click counter on participant links ignore repeat clicks from one address within a day. We read the payment from the TRON blockchain and keep its public data: transaction hash, sender address, amount and block time. The management token and the IP hash are never exposed.

Joining the NeAgent or NeCard waiting list goes through the bot @AffPapa_Bot: like any Telegram bot, it sees your Telegram ID and profile name and uses them to send the launch notification. Send /stop to the bot to unsubscribe.

3. How we use your data

• to provide the services you use (SEO monitoring, email, NeTOP);
• to display your Search Console data within NeAhrefs;
• to maintain and improve the site.

We do not sell, rent or share your personal data with third parties, and we do not use it for advertising.

4. Google API Services — Limited Use Disclosure

NeAhrefs' use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• we only use Google user data to provide and improve the NeAhrefs service;
• we do not transfer Google user data to third parties except as necessary to provide the service, with user consent, or as required by law;
• we do not use Google user data for advertising purposes;
• a human reviews Google user data only when you request support, with your consent, for security purposes, or to comply with applicable law.

5. Data storage and security

Your data is stored on a dedicated server (Hetzner, Germany, EU) in a PostgreSQL database. Server access is by SSH key only and limited to the site operator. Google OAuth tokens are stored server-side and used only to refresh your Search Console data. All connections use HTTPS.

6. Data retention and deletion

You can delete your NeAhrefs account and all associated data at any time by contacting us. On request we remove your account record and Google OAuth tokens, and all sites, crawl data, keyword data and analytics associated with the account. Server access logs are retained for up to 30 days for security purposes.

7. Your rights

• access your personal data;
• request correction of inaccurate data;
• request deletion of your data;
• revoke Google OAuth access at any time via Google Account Permissions.

8. Cookies

Signing in to NeAhrefs relies on one first-party session cookie; without it you cannot stay signed in. We set no advertising or cross-site tracking cookies of our own.

The analytics services named in sections 2.4 and 2.5 — Google Analytics 4, Yandex Metrica and Microsoft Clarity — set their own cookies to count visits and tie a recording to one session. You can refuse or remove them through your browser's cookie settings, and Google offers a browser opt-out add-on for Google Analytics. Blocking analytics cookies does not affect the tools themselves.

9. Changes to this policy

We may update this policy. Changes are posted on this page with an updated date. Continued use of the services after changes constitutes acceptance.

10. Contact