Skip to content
data-safety-from-codeData safety from code

RevenueCat: Data safety form answers

If your Android app includes RevenueCat Purchases SDK from RevenueCat, its data counts as data your app collects. According to the vendor, it collects purchase history (collected, not shared: the vendor acts as a service provider).

Matched dependencies: com.revenuecat.purchases:purchases*.

What to declare

Section titled “What to declare”
Data type Collected Shared Ephemeral Purposes
Purchase history Yes No No App functionality; Analytics

Whether each type is required or optional for users depends on your app: optional only if users can turn it off and the app honors that.

Only declare these if they apply

Section titled “Only declare these if they apply”
Data type When Collected Shared Purposes
Name Only if you store it in customer attributes Yes No Choose yours
Email address Only if you store it in customer attributes Yes No Choose yours
Phone number Only if you store it in customer attributes Yes No Choose yours
Device or other IDs Only if you use integrations that rely on advertising identifiers (GAID, Android ID) Yes No Choose yours

The skill lists these under Needs your review and checks the code for the condition (for example a setUserId call) before you include them.

Notes

Section titled “Notes”

RevenueCat collects purchase history (not optional, not ephemeral) and acts as a service provider. Mark it shared too if you forward data to non-service-provider integrations. Locale and currency are collected but are not location. No crash logs or diagnostics.

The CSV rows this sets

Section titled “The CSV rows this sets”

These are the rows of Google’s Data safety CSV that RevenueCat turns to true (or false for the ephemeral question). Columns: question ID, response ID, value. You also answer the required/optional row for each type.

PSL_DATA_TYPES_FINANCIAL,PSL_PURCHASE_HISTORY,true
PSL_DATA_USAGE_RESPONSES:PSL_PURCHASE_HISTORY:PSL_DATA_USAGE_COLLECTION_AND_SHARING,PSL_DATA_USAGE_ONLY_COLLECTED,true
PSL_DATA_USAGE_RESPONSES:PSL_PURCHASE_HISTORY:PSL_DATA_USAGE_EPHEMERAL,,false
PSL_DATA_USAGE_RESPONSES:PSL_PURCHASE_HISTORY:DATA_USAGE_COLLECTION_PURPOSE,PSL_APP_FUNCTIONALITY,true
PSL_DATA_USAGE_RESPONSES:PSL_PURCHASE_HISTORY:DATA_USAGE_COLLECTION_PURPOSE,PSL_ANALYTICS,true

Detect it automatically

Section titled “Detect it automatically”

data-safety-from-code finds RevenueCat in your build.gradle or version catalog, adds these answers with a link to the source, and merges them with every other SDK and with what your own code sends. You get a CSV to import and a report showing where each answer comes from.

Inside a Claude Code session
/plugin marketplace add sanikantv/data-safety-from-code
/plugin install data-safety-from-code@data-safety-from-code
Or from your shell
claude plugin marketplace add sanikantv/data-safety-from-code
claude plugin install data-safety-from-code@data-safety-from-code

Other payments SDKs

Section titled “Other payments SDKs”

Related: collected vs shared · how to fill the Data safety form · all SDKs

Want the form filled from your own code, with evidence? Install the skill. If this page helped,star the repo on GitHub.

Built by Sanikant. Set in Google Sans Flex (SIL Open Font License), icons from Material Symbols (Apache 2.0). Google Play is a trademark of Google LLC; this project is not affiliated with Google. Output is a draft for review: you are responsible for your Data safety declaration.