Trust and security
Risk register
The main risks in store-to-web subscriber migration and how Recurr controls them.
Nostos is designed around explicit risk control.
Documentation Index
Fetch the complete documentation index at: /docs/llms.txt
Use this file to discover all available pages before exploring further.
The main risks in store-to-web subscriber migration and how Recurr controls them.
| Risk | Control |
|---|---|
| Subscribers do not trust the migration path | Branded email, branded checkout, clear support path, and cohort sequencing |
| Subscribers lose access | Access continuity mapped before launch and tested before live cohorts |
| Store subscription remains active | Cancellation guidance, support routing, and overlap monitoring |
| Churn rises in migrated cohorts | Matched store-billing holdouts and cohort gates before scale |
| Support load spikes | Macros, help content, escalation rules, and cohort-by-cohort rollout |
| Payment rail issues appear | Rail readiness review, small pilot cohorts, and billing-health monitoring |
| Policy posture is misunderstood | Out-of-app default lane and documented Apple/Google policy review |
| Finance cannot reconcile fees | Clear pilot, migration, and Oikos fee mechanics before launch |
| Customer feels locked in | Customer-owned rail, existing access model, exports, and portability review |