Data handling - Recurr

Recurr needs enough data to operate migration and Oikos intelligently. It should not become the only place the customer’s subscriber truth exists.

Data Recurr may process

Subscriber identifiers
Email or contactability status
Plan and subscription state
Store versus web billing status
Cohort assignment
Payment outcome events
Support and migration workflow status
Lifecycle motion outcomes
Aggregated reporting metrics

Why the data is needed

Purpose	Examples
Cohort selection	Decide who should be included in a pilot or migration cohort
Access continuity	Match web billing state to app access
Reporting	Show movement, retention, billing health, and support signal
Kairos decisioning	Choose the next approved motion for the subscriber
Support	Diagnose subscriber migration and billing questions

What remains in customer systems

The payment rail, access model, warehouse, analytics stack, and support system can remain customer-owned. Recurr integrates with those systems rather than replacing them by default.

Diligence topics

Security and legal teams should review data categories, processing purposes, subprocessors, retention, deletion, exports, and incident response in the DPA and security materials.