Data processing addendum

One-pager. Replace the operator details before production use.Pulse acts as processor for analytics events collected from the controller's websites. Processing is limited to providing the Pulse service: ingest, aggregation, dashboards, billing of the controller's Pulse subscription, and optional Stripe revenue attribution configured by the controller.

Data

Page path (no query string), referrer origin, coarse device and browser, country/city from the edge, UTM fields, custom event names, a non-reversible daily visitor hash, and — if enabled — a hashed attribution UUID plus payment amounts from Stripe webhooks. No raw IP, no email, no name, no payment-customer PII in analytics tables.

Subprocessors

Hosting: Cloudflare Workers (ingest) and Neon (Postgres). Payments for the Pulse SaaS: Stripe. The controller's own Stripe account sends webhooks to Pulse when revenue attribution is enabled.

Retention and deletion

Events are retained for the life of the workspace unless the controller deletes the site or account. Deletion of a site removes events, payments, funnels, and secrets for that site.

Security

Daily hashing secrets rotate at 00:00 UTC. Site tokens are stored hashed. Attribution identifiers are hashed before insert. TLS in transit.