| Does your app collect or share any of the required user data types? | Yes |
| Is all of the user data encrypted in transit? | Yes Network calls use HTTPS where user data is transmitted by Google/Firebase SDKs and app download resolving. |
| Do you provide a way for users to request that their data is deleted? | Yes |
| Data deletion request method | teraflopspeedapps@gmail.com |
The app does not create user accounts. Advertising ID can be reset or deleted by the user in Android settings. Notification permission is optional on supported Android versions.
Device or Other IDs
What: Advertising ID, Firebase installation ID, and related app/device identifiers used by Google Mobile Ads, Firebase Cloud Messaging, and Firebase Installations.
Shared with: Google / Firebase.
Purposes: Advertising or marketing, Analytics, App functionality, Fraud prevention, security, and compliance.
Required or optional: Ads-related identifiers are required for ad-supported app operation. Push notification identifiers are used when notification functionality is enabled or permitted.
App Activity - App Interactions
What: Ad impressions, ad clicks, and product interaction signals handled by the Google Mobile Ads SDK.
Shared with: Google.
Purposes: Advertising or marketing, Analytics, Fraud prevention, security, and compliance.
App Info and Performance - Diagnostics
What: Diagnostic information automatically handled by Google Mobile Ads and Firebase SDK components.
Shared with: Google / Firebase.
Purposes: Analytics, App functionality, Fraud prevention, security, and compliance.
Note: Do not select Crash logs unless Firebase Crashlytics or another crash-reporting SDK is actually enabled.
Location - Approximate Location
What: Approximate location may be inferred from IP address by the Google Mobile Ads SDK. The app does not request Android precise or coarse location permissions.
Shared with: Google.
Purposes: Advertising or marketing, Analytics, Fraud prevention, security, and compliance.
Note: Keep this declaration conservative unless your active AdMob configuration and Google SDK disclosure clearly show location is not collected for your release.
Not collected by this app - do not select these unless behavior changes:
-
Data safety form submitted using the selected data types above.Play Console > App content > Data safety
-
Advertising ID declaration = Yes. Purpose: Advertising or marketing, Analytics, and Fraud prevention, security, and compliance where shown by Google SDK disclosure.Play Console > App content > Advertising ID
-
Privacy policy URL is live and linked. The app should link to its privacy policy in the app and in Play Console.Play Console > App content > Privacy policy
-
Permissions declaration for media permissions. Explain that
READ_MEDIA_IMAGES,READ_MEDIA_VIDEO, andREAD_MEDIA_AUDIOsupport local status saving, duplicate finding, cleaner scanning, thumbnails, and file management. -
EEA/UK consent flow is enabled. The app includes Google User Messaging Platform, and ads should initialize after the consent flow resolves.
-
No broad all-files access declaration unless added later. Do not add
MANAGE_EXTERNAL_STORAGEunless the app truly qualifies and the Play declaration is updated. -
Child safety standards URL is separate. Use the app's public child-safety page for Google Play's child safety declaration, not this data-safety reference page.
Update this page whenever SDKs or app behavior changes. For example, if Firebase Analytics, Firebase Crashlytics, login/accounts, cloud backup, in-app purchases, user uploads, or a new ad/push SDK is added, the Play Console Data safety answers may need to change.
Last reviewed: 7 June 2026.