Payments

Privacy Policy for Apps Using RevenueCat

RevenueCat manages in-app purchases and subscriptions across the App Store and Google Play. It receives purchase and device identifiers to attribute and sync entitlements, which your privacy policy should disclose.

Create My Privacy Policy

Last updated July 8, 2026

Why this affects your privacy policy

To keep a user’s subscription in sync across devices and platforms, RevenueCat processes app user identifiers, purchase receipts, and device information. Because this is a third-party service processing user data, both App Store and Play Store expect it to be reflected in your policy and data-safety disclosures.

Data typically processed

Data type	Details
App user ID	An identifier that links a user to their subscription entitlements.
Purchase receipts	Store receipts validated to grant or revoke access.
Device identifiers	Platform-provided IDs used to attribute purchases.
Subscription status	Trial, active, expired, or refunded state.

What to disclose

That a third-party service manages your subscriptions and in-app purchases.
The identifiers sent to it (app user ID, device ID, purchase receipts).
That subscription status data may be transferred internationally.
That the service may be used for purchase attribution and analytics.

Example wording

Subscriptions. We use a third-party subscription-management service to process and synchronise in-app purchases and subscriptions across your devices. This service receives identifiers such as an app-specific user ID, device identifiers, and store purchase receipts in order to validate your purchases and grant you access to paid features. It does not receive your payment card details, which are handled by the app store.

Sample language only — adapt it to your actual data practices.

Best practices

→ Use an anonymised app user ID rather than an email or real name where possible.
→ Mirror this disclosure in your App Store and Play Store data-safety forms.
→ If you enable RevenueCat integrations (analytics, attribution), disclose those flows too.

Generate a policy that already covers RevenueCat and host it at a permanent URL.

Host Your Policy

Frequently asked questions

Does RevenueCat see the user’s credit card?

No. The app store processes the actual payment; RevenueCat validates receipts and manages entitlements. Your policy should make that distinction clear.

Do I still need Apple/Google privacy disclosures?

Yes. RevenueCat is in addition to — not a replacement for — the App Store Nutrition Label and Play Data Safety section.

Related guides

This guide is for general informational purposes only and is not legal advice. Your privacy policy should reflect your actual data practices and applicable legal requirements, which vary by jurisdiction and platform.

Create and host your privacy policy

Fill out a short form, get a permanent HTTPS URL for your app submission.

Create My Privacy Policy