Privacy

AppVerix Track is built to send events, not to keep customer profiles.

What we process

Storefront events (page, product, collection, search, cart, checkout, purchase) and order webhooks. Destination credentials you paste. Optional hashed email and phone for enhanced matching, only after you turn the toggle on and protected data access is approved.

What we store

Encrypted destination config. Encrypted outbox payloads without raw email or phone. Daily aggregates for 13 months. Sessions for the embedded admin. Error logs without personal data.

What we do not store

Raw email, phone, name, or address. Payload bodies are deleted after delivery or seven days.

Consent

The pixel reads the Customer Privacy API. Marketing destinations do not fire without marketing consent. GA4 receives Consent Mode v2 signals. In the EEA, UK, and Switzerland we default to no consent until the banner records a choice.

Subprocessors

Cloudflare (Workers and D1). Google (GA4 Measurement Protocol, Google Ads API when connected). Meta (Conversions API). Resend, if you set an alert email.

Mandatory requests

customers/data_request: we have no customer profiles to export. customers/redact: pending outbox rows are dropped. shop/redact: all shop data and sessions are deleted. Uninstall deletes sessions immediately; shop data waits for shop/redact.

Contact

privacy@appverix.com