Stripe · Platform guide
Privacy policy for apps that take payments (Stripe, Razorpay)
If your app takes payments through a processor such as Stripe or Razorpay, your privacy policy should say that payment details are collected and processed by that provider, what transaction data you keep yourself, and link the provider’s privacy policy. Stripe’s own policy calls your customers “End Customers” when it processes their data for your business.
What Stripe requires
Stripe Privacy Policy — End Customers
“When you are not directly transacting with Stripe, but we receive your Personal Data to provide Services to a Business User, including when you make a purchase from a Business User on a Stripe Checkout page or receive payments or other services from a Business User, we refer to you as an “End Customer.””
Source: stripe.com verified 2026-10-30
What common SDKs collect
| SDK / API | Data it collects | Source |
|---|---|---|
| Stripe Checkout / Payments |
| Source: stripe.com |
Everything in this table must appear in your policy if the SDK ships in your build.
Where to put the URL
- 3.1Checkout page and site footer.
- 3.2Store listings, if the app is on the App Store or Google Play.
Sample clause
§ 4.1 · Payments
Payments are processed by Stripe. When you pay, you enter your card details directly with Stripe; we never see or store your full card number. We receive and keep the payment amount, date, your email and the last four digits of your card for receipts and refunds. See Stripe’s privacy policy at stripe.com/privacy.
Questions
- Do I need to mention Stripe in my privacy policy?
- Naming your payment processor and linking its policy is the clearest way to disclose that third party, as both app stores ask you to disclose third-party sharing.
- Does PrivacyPage use a payment processor?
- Yes. PrivacyPage takes payments through Razorpay.