Shrinko does NOT collect, store, transmit, or sell any personal information or sensitive user data.
No User Accounts: You can use all features of the application without signing up, logging in, or providing any personal details (such as your name, email, phone number, or location).
No Analytics or Trackers: We do not integrate third-party analytics SDKs, tracking pixels, crash reporting tools that collect identifiers, or usage tracking scripts.
No Advertisements: Shrinko does not contain behavioural or targeted advertising frameworks.
All core features of Shrinko—including image compression, dimension resizing, and format conversion (JPG, PNG, WebP)—are performed locally on your device.
No Cloud Uploads: Your photos and images never leave your device and are never uploaded to any remote server or cloud service.
Local Cache: Temporary image files generated during processing are stored strictly in your device's isolated local app cache and can be cleared at any time.
Shrinko utilises standard Android system permissions with strict privacy compliance:
Android Photo Picker: We use Android’s native system Photo Picker. This ensures the app only has access to the specific images you actively select.
Saving Images: When you save processed images, Shrinko uses the Android MediaStore API to save the output directly into your public Pictures/Shrinko folder on your device.
Shrinko complies fully with Google Play’s Families Policy and the Children’s Online Privacy Protection Act (COPPA):
We do not knowingly collect any personally identifiable information from children of any age.
The app does not contain age-inappropriate content, external links, or third-party tracking.
Because Shrinko does not collect any user data, we do not share, sell, rent, or disclose your information to any third parties.
We prioritise the security of your data by processing everything locally within your device's secure sandbox environment. No data transmission occurs over the internet.
We may update our Privacy Policy periodically. Any updates will be reflected with a revised "Effective Date" at the top of this document.