Stripe's mobile SDK sends user data to Stripe, Inc. Any app that takes a payment through Stripe transfers payment and contact data to a third party, and that has to be disclosed. Generate a full privacy policy with this clause built in →
Does Stripe need a privacy policy disclosure?
Stripe's iOS, Android, and React Native SDK (PaymentSheet, card fields, PaymentIntents, Stripe Radar) collects the payment method the user enters and tokenizes card details so the full card number is sent directly to Stripe and never stored on your servers. This is what keeps your PCI DSS scope small, typically SAQ A. Along with the token, Stripe receives the cardholder name, email, phone, billing and shipping address, device information, and IP address.
This is a third-party transfer, so disclose it. For processing the payment Stripe acts as your service provider. For fraud prevention (Stripe Radar), risk management, and its own legal and regulatory obligations as a licensed payment processor, Stripe acts as an independent controller and may share transaction data with financial partners. Stripe states the SDK data is never used for advertising and is not used for tracking, so Stripe is not "tracking" under Apple's ATT rules or Guideline 5.1.2. Note Apple's Guideline 3.1.1: digital goods and content consumed inside the app must use Apple's in-app purchase, not Stripe — Stripe is for physical goods, real-world services, and donations.
What data does Stripe collect?
| Data type | Purpose | Linked to the user? | Used for tracking? |
|---|---|---|---|
| Payment method info (card number tokenized, expiry, last4, brand; or bank / wallet details) | Process the payment | Yes (to the transaction or Stripe Customer) | No |
| Name, email, phone, billing and shipping address | Payment, receipts, fraud checks, tax | Yes | No |
| Device info (model, OS version) and IP address | Fraud prevention (Stripe Radar), 3D Secure, analytics | Device usage linked; IP used for fraud, not linked to identity by Stripe | No |
| Stripe SDK interaction and usage events | Analytics and fraud prevention | Yes | No |
| 3D Secure authentication data | Sent to the card issuer for strong customer authentication | Depends on the issuer | No |
The exact list depends on which SDK components you use, whether you attach a Stripe Customer object, and whether you collect shipping. Do not label raw card numbers as data you store — with the standard SDK you never receive them.
Copy-paste privacy policy clause for Stripe
Payment processing (Stripe)
We use Stripe, provided by Stripe, Inc., to process payments in this app.
When you enter payment details, Stripe's SDK collects your card or
payment method information and tokenizes it, so that full card numbers
are transmitted directly to Stripe and are not stored on our servers.
Stripe also receives your name, email address, phone number, billing and
shipping address, device information, and IP address. Stripe uses this
data to process the transaction and, as an independent controller, to
prevent fraud (Stripe Radar), manage risk, and meet its legal and
regulatory obligations as a payment processor, which can include sharing
transaction data with financial partners. Stripe does not use this data
for advertising and does not sell it. For payment processing Stripe acts
as our service provider; for fraud prevention and compliance Stripe acts
as an independent controller. See Stripe's Privacy Policy at
https://stripe.com/privacy.Adapt this: name the Stripe products you actually use, drop shipping address if you do not collect it, and if you save cards for future payments (Stripe Customer / Link) say that payment methods are stored with Stripe.
App Store "App Privacy" label answers
In App Store Connect, declare the following for Stripe:
- Financial Info > Payment Info — purpose "App Functionality". Linked to the user: Yes. Used to track you: No.
- Contact Info > Name, Email Address, Phone Number, Physical Address — purpose "App Functionality". Linked: Yes. Used to track you: No.
- Identifiers > User ID — if you use Stripe Customer IDs or ephemeral keys. Purpose "App Functionality". Linked: Yes. Used to track you: No.
- Usage Data > Product Interaction — purposes "Analytics" and "App Functionality" (fraud prevention). Linked: Yes. Used to track you: No.
- Diagnostics > Crash Data / Other Diagnostic Data — only if you forward SDK errors. Purpose "App Functionality".
Stripe does not require the ATT prompt for its SDK. Stripe publishes "iOS SDK Privacy Details" and ships a privacy manifest with the SDK.
Google Play Data Safety answers
For the Play Console Data safety form:
- Financial info > Payment info — Collected: Yes. Shared: Yes (Stripe acts partly as an independent controller and shares with financial partners). Purpose: App functionality. Not processed ephemerally.
- Personal info > Name, Email address, Phone number, Address — Collected: Yes. Shared: Yes. Purposes: App functionality, Fraud prevention and security.
- App activity > App interactions — Collected: Yes. Shared: Yes. Purposes: Analytics, Fraud prevention and security.
- Device or other IDs — Collected: Yes (IP and device signals for Radar). Shared: Yes. Purpose: Fraud prevention and security.
- Users can request deletion through you, but Stripe and you must retain transaction records for financial and tax law, so payment data generally cannot be fully deleted on request.
Stripe-specific gotchas
- Apple IAP rule (3.1.1). Using Stripe for digital goods, subscriptions, or content consumed in the app gets your app rejected. Stripe is for physical goods and real-world services.
- Do not call Stripe "just a processor" in the EU. Your DPA with Stripe reflects a dual role; Stripe is an independent controller for fraud, risk, and compliance.
- PCI scope. The SDK keeps you in SAQ A only if you use Stripe's UI components or tokenization and never touch the raw card number. Custom fields that handle the PAN expand your scope.
- Radar runs in test mode too. IP address and device fingerprinting for fraud detection happen on every SDK call, including test payments — disclose it.
- Record retention beats deletion. You usually cannot honor a full "delete my payment data" request because transaction records must be kept.
- Link wallet. If you enable Link, Stripe may store the customer's details for reuse across other merchants — that is Stripe operating as a controller, and worth a sentence in your policy.
- You are responsible for the accuracy of your disclosure. This clause is a template, not legal advice.
Related
See the sibling clauses for RevenueCat, Superwall, Supabase, and Google Sign-In. Build the full document with the privacy policy page generator, and see the Firebase privacy policy guide if your app also uses Firebase.