Firebase Crashlytics: Data safety form answers

If your Android app includes Firebase Crashlytics from Google, its data counts as data your app collects. According to the vendor, it collects crash logs, diagnostics, device or other IDs (collected, not shared: the vendor acts as a service provider).

Matched dependencies: com.google.firebase:firebase-crashlytics, com.google.firebase:firebase-crashlytics-ndk.

Source

From Google’s own Play data disclosure: firebase.google.com. Checked 2026-10-26.

What to declare

Data type	Collected	Shared	Ephemeral	Purposes
Crash logs	Yes	No	No	Analytics
Diagnostics Application state and point-in-time device metadata at crash time	Yes	No	No	Analytics
Device or other IDs Crashlytics installation UUID (rotates with the Firebase installation ID)	Yes	No	No	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

Data type	When	Collected	Shared	Purposes
User IDs	Only if you attach a user ID to crash reports (setUserId)	Yes	No	Analytics

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

Automatically sends stack traces, app state and device metadata at crash time, plus a Crashlytics installation UUID. Depends on Firebase Installations and Sessions. Custom keys, logs and user IDs you attach are also sent, so declare whatever they contain.

The CSV rows this sets

These are the rows of Google’s Data safety CSV that Firebase Crashlytics 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_APP_PERFORMANCE,PSL_CRASH_LOGS,true
PSL_DATA_USAGE_RESPONSES:PSL_CRASH_LOGS:PSL_DATA_USAGE_COLLECTION_AND_SHARING,PSL_DATA_USAGE_ONLY_COLLECTED,true
PSL_DATA_USAGE_RESPONSES:PSL_CRASH_LOGS:PSL_DATA_USAGE_EPHEMERAL,,false
PSL_DATA_USAGE_RESPONSES:PSL_CRASH_LOGS:DATA_USAGE_COLLECTION_PURPOSE,PSL_ANALYTICS,true
PSL_DATA_TYPES_APP_PERFORMANCE,PSL_PERFORMANCE_DIAGNOSTICS,true
PSL_DATA_USAGE_RESPONSES:PSL_PERFORMANCE_DIAGNOSTICS:PSL_DATA_USAGE_COLLECTION_AND_SHARING,PSL_DATA_USAGE_ONLY_COLLECTED,true
PSL_DATA_USAGE_RESPONSES:PSL_PERFORMANCE_DIAGNOSTICS:PSL_DATA_USAGE_EPHEMERAL,,false
PSL_DATA_USAGE_RESPONSES:PSL_PERFORMANCE_DIAGNOSTICS:DATA_USAGE_COLLECTION_PURPOSE,PSL_ANALYTICS,true
PSL_DATA_TYPES_IDENTIFIERS,PSL_DEVICE_ID,true
PSL_DATA_USAGE_RESPONSES:PSL_DEVICE_ID:PSL_DATA_USAGE_COLLECTION_AND_SHARING,PSL_DATA_USAGE_ONLY_COLLECTED,true
PSL_DATA_USAGE_RESPONSES:PSL_DEVICE_ID:PSL_DATA_USAGE_EPHEMERAL,,false
PSL_DATA_USAGE_RESPONSES:PSL_DEVICE_ID:DATA_USAGE_COLLECTION_PURPOSE,PSL_ANALYTICS,true

Detect it automatically

data-safety-from-code finds Firebase Crashlytics 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.

Claude Code

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

Codex · Cursor · Copilot

skills CLI (works with most agents)

npx --yes skills add sanikantv/data-safety-from-code --skill data-safety-from-code -y

Copy the folder

Personal skill (or copy into your project's .claude/skills/)

git clone https://github.com/sanikantv/data-safety-from-code.git
cp -r data-safety-from-code/skills/data-safety-from-code ~/.claude/skills/

Other crash reporting SDKs

• Sentry Android SDK data safety

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.