AdNerve

Privacy Policy

Last updated: 3 October 2026

This policy describes what AdNerve ("we") collects when you use adnerve.org and the @Adnerve_bot Telegram bot, and what we do with it. The short version: we collect the minimum needed to run your account, we don't sell anything, and you can delete everything yourself in one tap.

What we collect

• Account. When you sign in with Google we receive your name, email address and profile picture. We never see your Google password.
• Telegram link. If you link a chat, we store your Telegram user ID, first name and username so briefs and alerts reach the right chat. We do not read your other Telegram messages.
• Workspace activity. Your connection requests, settings and session. Sessions use a single first-party cookie (an_session) — no tracking or advertising cookies.
• Technical logs. Standard server logs (IP address, request path, timestamp) for security and debugging, retained briefly.

What we deliberately avoid

• The Telegram bot sends aggregate metrics and signed links only — never names, emails, phone numbers, lead message contents or credentials.
• Ad-platform connections are read-only reporting scopes. AdNerve cannot change your campaigns.
• For business outcomes we prefer pseudonymous IDs over contact details — the analytics never need your leads' names or phone numbers.
• We do not sell or rent your data, and we do not use it for advertising.

Where it lives

Data is encrypted in transit (TLS everywhere, including between Telegram, Cloudflare and our servers) and stored on servers operated for AdNerve in the EU. Third parties we rely on: Google (sign-in), Telegram (bot and Mini App), Cloudflare (DNS and traffic proxying).

Retention and deletion

Your data is kept while your account exists. Settings → Danger zone → Delete account removes your account, workspace, sessions and Telegram link immediately. You can also unlink Telegram alone at any time.

Changes

If this policy changes materially we will say so on the dashboard. The "last updated" date above always reflects the current version.

Contact

Privacy questions or requests: see Contact.