Firebase Authentication: Data safety form answers
If your Android app includes Firebase Authentication from Google, its data counts as data your app collects. According to the vendor, it collects user IDs (collected, not shared: the vendor acts as a service provider).
Matched dependencies: com.google.firebase:firebase-auth.
What to declare
Section titled “What to declare”| Data type | Collected | Shared | Ephemeral | Purposes |
|---|---|---|---|---|
| User IDs Generated Firebase Authentication user ID |
Yes | No | No | App functionality; Account management |
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 |
|---|---|---|---|---|
| Email address | Only with email/password, email link, or a federated provider that returns an email | Yes | No | App functionality; Account management |
| Phone number | Only with phone auth, phone as a sign-in method, or SMS second factor | Yes | No | App functionality; Account management |
| Name | Only if you set a display name or a federated provider returns one | Yes | No | App functionality; Account management |
The skill lists these under Needs your review and checks the code for the condition (for example a setUserId call) before you include them.
Always collects the device IP address (security and abuse prevention during sign-up and sign-in) and a generated Firebase Auth user ID. Other data depends on the sign-in methods you enable. Federated providers may also return profile/contact info depending on the scopes you request.
The CSV rows this sets
Section titled “The CSV rows this sets”These are the rows of Google’s Data safety CSV that Firebase Authentication 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_PERSONAL,PSL_USER_ACCOUNT,truePSL_DATA_USAGE_RESPONSES:PSL_USER_ACCOUNT:PSL_DATA_USAGE_COLLECTION_AND_SHARING,PSL_DATA_USAGE_ONLY_COLLECTED,truePSL_DATA_USAGE_RESPONSES:PSL_USER_ACCOUNT:PSL_DATA_USAGE_EPHEMERAL,,falsePSL_DATA_USAGE_RESPONSES:PSL_USER_ACCOUNT:DATA_USAGE_COLLECTION_PURPOSE,PSL_APP_FUNCTIONALITY,truePSL_DATA_USAGE_RESPONSES:PSL_USER_ACCOUNT:DATA_USAGE_COLLECTION_PURPOSE,PSL_ACCOUNT_MANAGEMENT,trueDetect it automatically
Section titled “Detect it automatically”data-safety-from-code finds Firebase Authentication 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.
/plugin marketplace add sanikantv/data-safety-from-code/plugin install data-safety-from-code@data-safety-from-codeclaude plugin marketplace add sanikantv/data-safety-from-codeclaude plugin install data-safety-from-code@data-safety-from-codenpx --yes skills add sanikantv/data-safety-from-code --skill data-safety-from-code -ygit clone https://github.com/sanikantv/data-safety-from-code.gitcp -r data-safety-from-code/skills/data-safety-from-code ~/.claude/skills/Other sign-in SDKs
Section titled “Other sign-in 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.