Convra
v1.0 · Updated Jul 2026
PRIVACY POLICY

Your photos never leave your phone.

Convra converts image formats — JPG, PNG, HEIC, WEBP, PDF, SVG — entirely on your device. This page explains exactly what that means, in plain language first, then in full.

HOW A CONVERSION ACTUALLY MOVES THROUGH YOUR DEVICE On-device processing boundary A photo you pick, the conversion process, and the converted file all stay inside a dashed boundary labeled "on this device." Nothing crosses out of that boundary unless you tap Share, shown as a separate solid-line path to an external app icon. ON THIS DEVICE Photo picked Converted locally Saved as new file only if you tap SHARE App you choose

Everything inside the dashed line

happens in your phone's memory. No network request, no upload, no background sync.

Everything outside it

only happens when you personally tap Share — and you pick which app receives the file.

No photo uploads

Conversion runs on-device. Your images are never sent to us or any server.

No account needed

Open the app and convert. Nothing to sign up for, nothing tied to your identity.

You control sharing

Convra never shares a file on its own. Sharing only starts when you tap Share.

01 · WHAT CONVRA DOES

How the app actually works

Convra lets you pick a single image from your gallery, using Android's built-in photo picker, and convert it between formats — JPG, PNG, HEIC, WEBP, PDF, and SVG. The conversion is performed by code running inside the app, on your device's processor. The result is written to a new file that stays on your device until you decide what to do with it.

If you choose to share a converted file, Convra hands it to Android's native share sheet — the same system dialog every app uses — and you choose which app receives it. Convra has no visibility into what happens after that; it isn't involved once the file leaves through Share.

02 · WHAT DATA WE COLLECT

Data collection, category by category

This table reflects exactly what's declared in Convra's Google Play Data Safety section — the two should always match.

CategoryCollected?Details
Photos & images Not collected Read into memory only for the duration of a conversion, then discarded. Never transmitted anywhere.
Account info / identity Not collected Convra has no sign-up, login, or user profile of any kind.
Precise or approximate location Not collected The app never requests location permissions.
Advertising ID If ads are enabled Used only by the advertising SDK to serve and measure ads, per its own privacy policy — see the Third-Party Services section below.
App diagnostics / crash logs Basic, anonymized Standard crash and performance diagnostics that help fix bugs. Not linked to your identity.
EDIT BEFORE PUBLISHING — If Convra ships without ads or crash reporting, delete the corresponding row above and its matching entry in the Play Console Data Safety form. Whatever this table says must equal what's declared there, word for word in substance.
03 · WHAT WE NEVER DO

Boundaries we don't cross

04 · PERMISSIONS, EXPLAINED

What the app actually asks your phone for

Convra picks images using Android's system Photo Picker, which does not require any storage or media permission — you choose one photo, and the app only ever sees that photo. Sharing a converted file uses Android's native share sheet, which likewise requires no special permission; Convra briefly hands the file a secure reference so your chosen app can read it.

In short: Convra does not request broad access to your photo library, contacts, location, microphone, or any other sensitive system permission.

05 · THIRD-PARTY SERVICES

Services Convra relies on

Convra may use Google AdMob to display ads that support the app's development. AdMob can collect an advertising identifier and basic device information to serve and measure ads, governed by Google's own Privacy Policy. This processing is separate from, and unrelated to, how Convra handles your photos.

EDIT BEFORE PUBLISHING — Name every SDK actually integrated (AdMob, AppLovin MAX, Firebase Crashlytics, etc.) and link each one's privacy policy. Remove this section entirely only if Convra ships with zero third-party SDKs.
06 · CHILDREN'S PRIVACY

Not directed at children

Convra is not directed at children under 13, and we do not knowingly collect personal data from children. If you believe a child has provided us data, contact us using the details below and we'll address it promptly.

07 · CHANGES TO THIS POLICY

If this policy changes

If Convra's data practices change — a new SDK, a new feature that touches user data — this page will be updated and the "last updated" date at the top will change accordingly. Significant changes will also be reflected in the app's Play Store listing.

Version history matters here. Keep this page and the Play Console Data Safety form in lockstep — updating one without the other is one of the most common causes of a review flag.
08 · CONTACT

Questions about this policy

Reach out at sajjadtech647@gmail.com with any questions about how Convra handles data, or to request more information.