Privacy

Last updated 15 September 2026

NetBack helps you measure whether AI answer engines send you traffic that converts. This page explains what we collect, why, and how it’s handled. Questions: tc@netback.ai.

What we collect

• Public brand signals — for the free scan we query public AI answers about a brand and category. No private data is required to run a scan.
• Account information — if you sign up, your email address and workspace/brand details.
• Connected revenue data — only if you choose to connect it: Google Analytics metrics, a read-only Stripe key (charges, checkout sessions, customers), and conversion events sent by the NetBack pixel.
• Pixel data — if you install the pixel, a first-party visitor id, the referring AI source, and the conversion values you pass to nb.convert(). Emails passed to the pixel are SHA-256 hashed in the browser before they reach us.

How we use it

• To produce your visibility scorecard and attribute AI-sourced revenue.
• To operate, secure and improve the service.
• We do not sell your data, and we never share or publish one brand’s connected data with another.

Service providers

We use a small set of processors to run NetBack: LLM providers (via OpenRouter) to generate scans, Supabase (database and authentication), Vercel (hosting), and — only if you connect them — Stripe (read-only) and Google Analytics. Each processes data only to provide their part of the service.

Retention and your choices

We keep account and connected data while your workspace is active. You can request access, correction, export or deletion of your data at any time by emailing tc@netback.ai. You can disconnect Stripe or GA and remove the pixel at any time.

Security

Access to connected integrations is read-only where offered (Stripe cannot be used to move money). Data is encrypted in transit. Access is limited to what’s needed to run the service.

Changes

We’ll update this page as the product evolves and revise the date above. Material changes will be communicated to signed-in users.