Privacy Policy — ByteFit

Information we do not collect

We do not collect your name, email address, phone number, contacts, files, 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. ByteFit never asks for your device's location; the approximate location mentioned under the ad services below is estimated by them from your IP address.

Data collected by third-party SDKs

ByteFit uses Google's Firebase and AdMob services, and Google Play's in-app update feature (see Updates, ratings and feedback). It contains 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. It also records when the "Internet needed" message was shown and what you did with it, when an app-update prompt was shown and whether you accepted it, your answer to "Enjoying ByteFit?", taps on "Rate" and "Send feedback", and when an ad failed to load. 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.
• 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.
• Google AdMob — shows the ads in ByteFit: a banner on the home screen, native ads on the Saved and Recent screens, and an occasional full-screen ad after a save. To serve and measure ads, limit how often you see them, and prevent ad fraud, AdMob collects your Android Advertising ID and app set ID, your IP address (which may be used to estimate your general location), your interactions with ads and the app (such as app launches, taps and video views), and app performance information. How Google uses this data is described in How Google uses information from sites or apps that use our services.

In the European Economic Area, the UK and other regions where it is required, you are asked for consent before ads are personalised to you. Elsewhere, ads may be personalised unless you opt out in Android settings (see Your controls). ByteFit never passes your photos, file names or exported files to any ad network.

Analytics and Crashlytics records are tied to an anonymous, resettable identifier for your app installation — not to your name, email or phone number — and are processed by Google on our behalf. Ad data is collected by Google under its own policies. All of it is sent over encrypted connections. We do not sell your data. 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 — and when ByteFit last reminded you to update or to rate it — are also stored only as local device settings.

Updates, ratings and feedback

ByteFit uses Google Play's in-app update feature to tell you when a newer version is available and, if you haven't updated after a few days, to ask you to install it. The check is carried out by the Google Play Store app on your device, under Google Play's own terms and privacy policy; ByteFit learns only whether an update is available. To time its reminders, ByteFit remembers on your device when it last offered an update and how long a newer version has been available.

Once you've saved a photo and used ByteFit on a few different days, it may ask whether you're enjoying it, and then send you to ByteFit's page on Google Play to leave a rating, or offer to email us if something isn't working. To time this, ByteFit keeps a list of the calendar days you opened the app, and whether you tapped through to Google Play, on your device only. ByteFit cannot see whether you actually leave a rating. "Send feedback" and "Report a bug" open your own email app with a message addressed to support@vihangaone.com — "Report a bug" pre-fills your device model, Android version and the app version so we can reproduce the problem, and you can edit or delete any of it. Nothing is sent unless you send it.

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.
• Internet access, network state and the Advertising ID — to load ads, to check whether you're online (ByteFit asks you to connect before it opens, because ads keep it free), and to send the analytics and crash reports described above. Google's ads SDK also declares Android's ad-services permissions, which it uses for ad measurement and, where you allow it, interest-based ads.

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.
• Where your ad consent was asked for (for example in the EEA or the UK), change your choice at any time in the app under Settings → Ad privacy options.
• Reset or delete your Advertising ID in Android Settings → Privacy → Ads. Once it's deleted, ads can no longer be personalised using it.
• 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 and your ad consent choice. 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, including AdMob, 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 and supported by ads from Google AdMob, as described above. Because ads keep it free, ByteFit asks you to connect to Wi-Fi or mobile data when it opens, and waits until you are online; resizing itself still happens entirely on your device. ByteFit never passes your photos, file names or exported files to any ad network. ByteFit has no accounts, subscriptions, or in-app purchases of any kind.

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.