Data Safety

Last updated: 3 October 2026 · Companion to our Privacy Policy

This page summarises, in plain language, what the SaveLocal app collects and shares - mirroring the categories used in Google Play's Data Safety section, so it's easy to cross-check.

Note for whoever fills in the Play Console Data Safety form: this page reflects the App with Firebase Analytics and the Meta SDK active, Advertising ID collection on (via Meta, for install attribution), no in-app ads shown, and no in-app opt-out for the required EEA/UK/CH consent flow beyond the first-run dialog. Re-check this page and the Play Console declaration against the live build before every release - an inaccurate Data Safety form is a policy violation, not just a documentation gap.

Summary

Question	Answer
Does the app collect or share any user data?	Limited data shared with Google and Meta, for analytics and advertising/marketing
Is data encrypted in transit?	Yes
Can you request data deletion?	Yes - see below
Does the app require an account?	No
Does the app show ads?	No - nothing is displayed in the App
Does the app collect an advertising ID?	Yes - for install attribution only, via the Meta SDK

What this data is used for

We do not collect your name, phone number, email address, or anything that identifies you personally. Firebase Analytics lets us see, in aggregate, how the App is used - for example how many files are saved and whether saves succeed - so we can improve it. The Meta SDK and your device's Advertising ID (where available) let us see which Meta advertising campaign led to an install, purely for measuring our own ad spend; SaveLocal shows no ads itself. Neither tool can see your files, file names, or save history, and data does not pass through our own servers first.

Data collected

Category	Data type	Purpose	Shared with
App activity	App interactions - install, open, in-app events (e.g. save-success/failure, file count, file size in bytes)	Analytics; Advertising or marketing (install attribution)	Google (Firebase Analytics), Meta
Device or other IDs	Android Advertising ID (unless you have reset/opted out)	Advertising or marketing (install attribution only)	Meta
App info and performance	App version, OS version, device model, approximate country	Analytics; Advertising or marketing	Google (Firebase Analytics), Meta

No file names, file content, or save history are ever included in these events. Data is not sold. Processed ephemerally: no.

Data not collected

Name, email address, phone number, physical address, financial or payment info, precise location, contacts, photos or videos, files/documents, calendar, health/fitness data, messages, browsing history, search history, and account info are not collected by the App.

Data processed only on-device

What	Where it stays	How to remove it
Files you share to the App	Copied into Downloads or the folder you chose	Delete them like any other file, e.g. from the Files app
Save history (file name, type, size, destination, time)	In the App's private storage	Remove an entry, clear the history, or turn history off in the App
Settings (save location, options, analytics/attribution preference, theme)	In the App's private storage	Uninstall the App or clear its storage

Security practices

Data in transit to Firebase Analytics and the Meta SDK is encrypted (HTTPS/TLS). The App's internet use is limited to these events plus reading the Google Play Install Referrer - your files are never uploaded.
We do not operate a backend server or database that stores your personal data.
In the EU/EEA, UK and Switzerland, the App asks for your consent before Firebase Analytics or the Meta SDK collect anything; you can withdraw consent at any time in the App's Settings > Privacy. Outside those regions, this measurement is on by default.
On Android 10 and newer, no storage permission is requested; on Android 9 and older, only the standard write permission needed for the Downloads folder.
Shared files are treated as untrusted: the App copies them but never opens or runs them, and it never overwrites an existing file - duplicates are saved with a number, such as report (1).pdf.
If you use Android's device backup, Android may include the App's settings and history in your Google backup. This is handled by Google, not by us.

Requesting deletion

Because the App does not use accounts, there is no server-side profile to delete. You can:

Turn off analytics and advertising-attribution measurement at any time in the App's Settings > Privacy.
Reset or delete your Android Advertising ID in Android Settings > Privacy > Ads, which limits what Meta can associate with your device going forward.
Uninstall the App, or clear its storage from Android Settings, to remove all on-device settings and history immediately.
Delete any saved files from your device yourself; uninstalling the App does not remove them.
Email infotech.trishunya+savelocal@gmail.com with any further data questions.

This page is provided for transparency to users and app-store reviewers. The authoritative legal document is our Privacy Policy; if the two ever differ, the Privacy Policy governs.