Privacy Policy — ByteFit

Information we do not collect

We do not collect your name, email address, contacts, location, or any account data — because ByteFit has no accounts. No server of ours ever receives your photos, and we never see the contents of anything you resize.

Data collected by third-party SDKs

ByteFit uses two Google services to keep the app reliable. It contains no advertising SDK and no other third-party SDKs.

• Firebase Analytics — collects anonymous usage events, such as a preset or custom size being chosen, a photo being selected, a crop being applied, whether an export fit its target size or needed to fall back to grayscale, and that a save or batch export happened. These events are bare counts, dimensions, and outcome labels — they never include file names, file contents, image data, URIs, or anything that identifies what you actually resized. Firebase Analytics also collects your device's Android Advertising ID, a resettable identifier you can reset or delete in Android Settings. ByteFit shows no ads and does not use this identifier for advertising, targeting or profiling.
• Firebase Crashlytics — collects crash and error reports: a stack trace, your device model and Android version, and a short internal tag naming which step failed (for example, that an export failed to encode). It never includes file names, file contents, or image data.

These records are tied to an anonymous, resettable identifier for your app installation — not to your name, email or phone number. They are sent to Google over HTTPS, are processed by Google on our behalf, and are never sold or shared with anyone else. See Google's Privacy Policy.

App-specific data handling

The photo you pick is read only to resize, crop, and compress it — every step of that runs on your device's own processor. ByteFit never uploads the original photo or the resized result anywhere. Because the app decodes your photo to raw pixels and writes a fresh file from those pixels, no EXIF metadata from the original — including GPS location — carries into the exported file.

The finished file is saved to your own device's storage: as an image, into the shared Pictures/ByteFit folder; or, if you use the optional "Save as PDF" toggle, as a PDF into Documents/ByteFit. Either way, it's your file from the moment it's written, and ByteFit keeps no separate copy of it. A local history of your past exports — target size, dimensions, byte count, and whether it fit — is kept only in a private on-device database, so you can quickly redo a past resize at a different size; this history is never synced or uploaded. Your chosen theme, font, and onboarding state are also stored only as local device settings.

Permissions we request and why

• Photo and media access (READ_MEDIA_IMAGES and, on Android 14+, READ_MEDIA_VISUAL_USER_SELECTED; READ_EXTERNAL_STORAGE on Android 12 and below) — to let you browse your gallery and pick a photo to resize, including when you choose to share only specific photos rather than your whole library.

ByteFit does not request camera, microphone, contacts, or location access.

Children's privacy

ByteFit is not directed at children under 13, and we do not knowingly collect data from children.

Your controls

• Revoke ByteFit's photo access at any time in Android Settings → Apps → ByteFit → Permissions.
• Reset or delete your Advertising ID in Android Settings → Privacy → Ads.
• Delete everything ByteFit holds via Android Settings → Apps → ByteFit → Storage → Clear data. This removes your local export history and settings, and resets the anonymous analytics identifier. It does not touch photos you've already saved to your gallery — those are your own files.

Data retention & deletion

We hold no user data ourselves. Data collected by Google's SDKs is governed by Google's own retention policies. Uninstalling the app removes all local app data. Because there is no account, there is no account-deletion process to complete. Photos you exported remain your own files on your device unless you delete them yourself.

Ads & purchases

ByteFit is free to use. The current version contains no advertising, no advertising SDK, and no in-app purchases. If a future version introduces ads or a paid option, this policy will be updated before that version is released.

Changes to this policy

We may update this policy from time to time. Continued use of the app after an update means you accept the revised policy.

Contact

Questions about this policy? Email support@vihangaone.com.