| 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 the Google / Firebase SDKs and download resolving transmit data. |
| 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. Media, vault contents and app data live only on the device and are removed on uninstall.
Device or Other IDs
What: Advertising ID, Firebase installation ID, push token and related identifiers used by Google Mobile Ads (AdMob) and Firebase.
Shared with: Google / Firebase.
Purposes: Advertising or marketing, Analytics, App functionality, Fraud prevention, security, and compliance.
Required or optional: Ads identifiers are required for ad-supported operation; push identifiers are used when notifications are enabled.
App Activity - App Interactions
What: Ad impressions/clicks and aggregate product-interaction signals from the Google Mobile Ads and Firebase Analytics SDKs.
Shared with: Google / Firebase.
Purposes: Advertising or marketing, Analytics, Fraud prevention, security, and compliance.
App Info and Performance - Diagnostics
What: Diagnostic / performance information handled automatically by Google Mobile Ads and Firebase components.
Shared with: Google / Firebase.
Purposes: Analytics, App functionality, Fraud prevention, security, and compliance.
Note: Only select Crash logs if Firebase Crashlytics (or another crash SDK) is actually enabled.
Location - Approximate Location
What: Approximate location may be inferred from IP address by Google Mobile Ads. The app does not request Android precise or coarse location permissions.
Shared with: Google.
Purposes: Advertising or marketing, Analytics, Fraud prevention, security, and compliance.
Purchase History
What: The Premium entitlement / purchase token from Google Play Billing. We store only a local "Premium" flag; payment is handled entirely by Google Play.
Note: Purchases through Google Play Billing are generally covered by Google's own disclosures. Declare Purchase history only if your final Play Console guidance requires it for the billing integration.
Not collected by this app - do not select these (all media stays on-device):
- Data safety form submitted using the data types above.Play Console > App content > Data safety
- Advertising ID declaration = Yes. Purpose: Advertising/marketing, Analytics, Fraud prevention. Add the
com.google.android.gms.permission.AD_IDpermission.Play Console > App content > Advertising ID - Privacy policy URL is live and linked —
https://www.thekemlowcapital.com/smm-privacy-policy.html— in the app (Settings) and in Play Console.Play Console > App content > Privacy policy - Permissions declaration for media permissions. Explain that
READ_MEDIA_IMAGES,READ_MEDIA_VIDEO,READ_MEDIA_AUDIOand selected-photos access (READ_MEDIA_VISUAL_USER_SELECTED) support local media management, status saving, duplicate finding, cleaner scanning, thumbnails and on-device OCR. - EEA/UK consent flow enabled. Integrate Google User Messaging Platform (UMP); initialize ads only after consent resolves.
- In-app purchases / subscriptions configured in Play Console for the Premium upgrade (Google Play Billing).Play Console > Monetize > Products
- No broad all-files access. Do not add
MANAGE_EXTERNAL_STORAGE; the app uses scoped media permissions and SAF.
Update this page when SDKs or behavior change. If Firebase Crashlytics, login/accounts, cloud backup/upload, or a new ad/push SDK is added, the Data safety answers may need to change. Conversely, if the build ships without ads/Firebase, switch the answers to "No data collected".
Last reviewed: 14 June 2026 · aligned with the Privacy Policy dated 13 June 2026.