Privacy

This page lists everything tryagentsignal.com collects, why, and who processes it. It describes what the site's code actually does. Questions or requests: agentsignal@mail.grokbot.com.

Meta Pixel (browser)

• What: Meta Pixel ID 3794504030617201. It loads only if your browser does not send a Do Not Track or Global Privacy Control signal. Automatic configuration and advanced matching are off, and we send no email, name or other identifiers to it.
• Events we send: PageView on each page; Lead when you sign up through the site's newsletter popup; InitiateCheckout when you click a checkout link (plan, price, currency, and any utm_source / utm_medium / utm_campaign / utm_content from the link that brought you here); Purchase on the Pro welcome page after payment (price, currency, product name, plan, the same UTM fields, and an event ID derived from the Stripe checkout session).
• Why: to measure and improve our ads on Facebook and Instagram.
• Who: Meta Platforms. Meta's script also receives the data any web request carries (such as IP address and browser details) and may set its own cookies (see the cookie list).

Meta Conversions API (server)

• What: after a completed Stripe checkout, our server sends Meta one Purchase event with exactly these fields: event_name (Purchase), event_time, event_id (a SHA-256 hash of the Stripe checkout session ID, so Meta can de-duplicate it with the browser event), action_source (website), event_source_url (https://tryagentsignal.com/), and custom_data with value, currency, product name, plan (monthly, yearly or fix) and content type. user_data is sent empty: no email, phone, name, IP address or browser ID.
• Why: to count purchases for ad measurement when the browser pixel is blocked.
• Who: Meta Platforms.

Vercel Web Analytics

• What: page views and these events: template downloads (file name, free or Pro), checkout clicks (plan, page, UTM fields), command copies (page, UTM fields), newsletter signups (form location, page) and signup fallbacks. Vercel Web Analytics does not use cookies.
• Why: to see which pages and templates are useful.
• Who: Vercel, which also hosts the site.

Newsletter signup (Beehiiv)

• What: when you enter your email in a signup form, popup or starter-pack form, we send Beehiiv your email, which form you used, and the page path. Beehiiv sends a welcome email. Some forms open Beehiiv's own signup page instead, where Beehiiv's policy applies.
• Why: to send the Agent Signal newsletter you asked for.
• Who: Beehiiv.

Payments (Stripe)

• What: Stripe Checkout collects your payment details directly; we never see your card number. We pass Stripe your account email and account ID (for Pro), and receive back your Stripe customer ID, subscription status, plan and billing period.
• Why: to take payment for Signal Pro and the $79 Fix, and to know whether your Pro access is active.
• Who: Stripe.

Accounts, Pro data and API keys (Supabase)

• What: your email (sign-in is by emailed magic link), your subscription record, your Pro alert preferences (which framework groups to hear about), your API keys, and any agentsignal-check reports you upload with a key (repo name, commit, framework, version and the report).
• API keys are stored hashed: we store a SHA-256 hash of each key plus a short display prefix. The full key is shown to you once and is not stored.
• Why: to sign you in and provide Pro features.
• Who: Supabase (database and sign-in emails).

Cookies

• as_pro: set by us after a Pro checkout. A signed token with your Stripe customer ID and checkout session ID, so Pro works in this browser without an account. HttpOnly, 30 days.
• sb-…-auth-token (may be split into .0, .1 parts): set by Supabase when you sign in, to keep you signed in.
• _fbp and _fbc: set by Meta's Pixel script (not by our code) when the pixel loads.

Local and session storage

• as_popup_seen (localStorage): when you last saw the newsletter popup, so it shows at most once a week.
• as_subscribed (localStorage): set after a successful signup so the popup stops showing.
• as_popup_variant (localStorage): which of two popup wordings you see.
• as_utm (sessionStorage): the UTM tags from the link that brought you here, for this tab only.
• as_purchase_… (sessionStorage): stops the Purchase event from being sent twice for one checkout.

Your choices

• Newsletter: use the unsubscribe link in any Agent Signal email.
• Meta: turn on Global Privacy Control or Do Not Track and the pixel won't load; or block it with a content blocker; or adjust your Meta ad preferences.
• Subscription: cancel in the Stripe customer portal.
• Access or deletion: email agentsignal@mail.grokbot.com to ask for a copy of your data or to have your account, keys and uploaded reports deleted.

See also the terms.