Resize Kit privacy policy.

1. App and operator

Resize Kit: Photos & PDFs is an Android application operated under the MuskiiT brand by an individual developer.

2. File content and on-device processing

The current design states that image and PDF processing occurs entirely on the device and that photo or document content is not uploaded to a server. File operations are designed not to depend on network connectivity.

3. Account and usage information

The app uses Firebase Authentication for optional Google Sign-In and Cloud Firestore for lifetime usage quotas, user profiles and app-level controls. The documented profile fields include Firebase user ID, email, display name, photo URL, tier, device ID and last-login information. Usage records include counters and device/account linkage information. Device identifiers are used for device-level quota enforcement.

4. Usage limits and identifiers

The current design describes an anonymous device allowance and an account allowance for Google Sign-In. It uses Android ID as the Android device identifier, with a locally persisted random identifier as a fallback if platform lookup fails. These identifiers and usage records are used for quota enforcement and abuse prevention.

5. App controls

Firestore is also used for a remote app enable/disable setting and device/account blocking controls. The design specifies that a Firestore outage should not prevent local file processing; the startup control check fails open when Firestore is unreachable.

6. Permissions and local files

Confirm and list the exact permissions used by the release build, including image/document selection and saving outputs to Downloads. Explain how selected files, temporary files, cached results and exported files are stored and removed. The design references Android MediaStore for saving files.

7. Third-party SDKs

The project document lists Firebase Core, Firebase Auth, Cloud Firestore and Google Sign-In, along with image/PDF processing and file-picker libraries. Before release, review the full dependency tree and disclose any analytics, crash reporting, advertising, billing or other SDKs that are actually included.

8. Retention, security and deletion

Document the retention and deletion behaviour for Firebase user profiles, usage counters, device identifiers and local files. The current design includes server-enforced monotonic quota counters and admin-controlled blocking fields. Confirm the deployed Firestore rules and access controls before release.

9. Children's privacy

Define the intended audience and applicable age-related practices before public release. Review relevant app-store requirements and applicable law.

10. Contact and updates

For privacy questions, contact support@muskiit.com. This policy will be updated before public release.