Skip to main content
Legal and procurement usually review Recurr across six areas:
  • Scope of services
  • Data processing
  • Store-policy posture
  • Payment rail ownership
  • Commercial and vendor onboarding
  • Termination and portability
Recurr is a managed migration and growth-platform vendor. It is not the payment processor by default.

​
Policy posture

Recurr’s default migration lane operates outside the app binary through owned channels and web surfaces. The app continues granting access through the customer’s existing stack. See Apple policy posture and Google Play policy posture.

​
Payment rail

Stripe is the default customer-owned rail. Paddle can be scoped where merchant-of-record coverage is required. Legal should confirm which entity owns the billing relationship, which agreements apply with the rail, and how Recurr’s services sit on top.

​
Procurement review

Procurement should expect the pilot fee to be credited in full against migration fees as the program continues. Preferred pricing may apply for design partners and is documented in the agreement.

​
Data

Legal should review:
  • Subscriber data shared with Recurr
  • Processing purposes
  • Retention
  • Security posture
  • Subprocessors
  • Export and deletion rights
  • DPA terms

​
Portability

Recurr should not become the only place the billing relationship exists. The payment rail and access model should remain part of the customer’s operating stack.