Data handling and privacy basics

RocketCheckout uses merchant configuration, event payloads, operational logs, and support communications to deliver tracking, recovery, routing, and support services. The legal source of truth remains the Privacy Policy and Terms pages.

Common data categories

• Store configuration and platform connection details
• Event payloads required for analytics, recovery, routing, and validation
• Hashed identifiers where required for destination matching
• Delivery logs and operational troubleshooting data
• Support requests and implementation communications

Identity and signal handling

RocketCheckout should normalize identity data before dispatch and hash sensitive fields where required by destination rules. Signal quality depends on consistent email hash, phone hash, external ID, click IDs, IP, user agent, event ID, value, and currency where permitted.

Good operational practice

• Enable only the destinations you actually use
• Keep credentials current and rotate them when needed
• Review consent handling before enabling new routing paths
• Use the latest connector package when installing on a new platform
• Confirm data appears for the selected store before making optimization decisions