1. Overview
TidyByte’s iPhone photo-library tools use Apple’s Photos, Vision, and AVFoundation frameworks on your device. TidyByte has no account system or developer-operated server. The optional Google Photos source, when enabled in your build, communicates directly with Google and is described below.
Learn more about all cleanup features or download TidyByte.
2. Data we collect
TidyByte does not collect app-usage analytics or advertising data and does not operate a server that receives photos. Local iPhone photo cleanup does not send your library to TidyByte. In builds with Google Photos enabled, the app sends requests directly to Google for sign-in, storage quota, and only the media items you pick. Google returns selected previews to your device for on-device scanning. The App Store privacy label currently reads “Data Not Collected”; this policy also explains the optional requests made directly to Google.
3. How the app works
All processing happens on-device using Apple’s system frameworks:
- Photos framework — reads from and writes to your local photo library.
- Vision framework — generates feature prints for near-duplicate detection and analyzes image quality (blur, exposure).
- AVFoundation — compresses videos and re-encodes photos on-device.
- SwiftData — stores local app records (swipe decisions, compression history) in a sandboxed database on your phone.
TidyByte ships no third-party SDKs. Every line that touches your local library is auditable in the public source repository.
4. Permissions the app requests
Photo Library (read & write)
Required for the iPhone cleanup tools. TidyByte uses Apple’s Photos framework to read your local library and write compressed videos or converted Live Photos back to it. Those local-library photos are not sent to TidyByte.
Google Photos (optional)
This source is available only in builds configured for Google Photos. If you choose to connect it, Google handles sign-in and the app calls Google directly to read your storage quota and the media items you select in Google Photos Picker. TidyByte requests file-size information and downloads small previews from Google to your device for local scanning; it does not upload photos to TidyByte or delete items from your Google Photos account. Google processes the account and API requests under its own privacy policy. OAuth tokens are stored in this device’s Keychain. Signing out asks Google to revoke the token and removes it from the device.
Notifications
Optional. Requested only if you enable “Cleanup Reminders” in Settings. Used solely to schedule local reminders via the iOS notification system.
5. Data storage on your device
TidyByte stores a small amount of local data using SwiftData to power features and history:
SwipeRecord— asset local identifiers and your keep/delete decisions. The actual photo data is never copied.CompressionRecord— bookkeeping for video and photo compression jobs.StorageSnapshot— cached storage breakdown used by the dashboard.
This data never leaves your device and can be cleared at any time via Settings → Reset Swipe History inside the app.
6. Children’s privacy
TidyByte is not directed at children under 13. We do not knowingly collect app-usage or advertising data. If a build with Google Photos enabled is connected to a Google account, the direct Google requests described above apply.
7. Open source
TidyByte’s source code is publicly available under the MIT License. Anyone can audit the claims on this page. If you find something that contradicts this policy, please open an issue.
8. Changes to this policy
If we change anything material on this page, we’ll update the date above and note it in the changelog. We do not operate a server that receives your photos or app activity.
9. Contact
Questions? Email contact@sakshammittal.com or open an issue on GitHub.