Privacy Policy
ConvertMyPic converts your images entirely inside your own browser. Every decode and encode step runs on your device using WebAssembly — there is no server that receives your files, so your images are never uploaded, never stored, and never logged. This page explains, in plain terms, exactly what happens to your data when you use the tool, what we do and do not collect, and how you can verify the on-device claim yourself. Last updated: 30 May 2026.
What runs in your browser
When you drop an image into ConvertMyPic, the file is read directly from your device into your browser tab. Decoding uses the browser's built-in Canvas API and, for formats the browser cannot open natively such as HEIC, an in-browser libheif decoder compiled to WebAssembly. Encoding to your chosen output format runs through the real reference codecs — mozJPEG for JPG, oxiPNG for PNG, libwebp for WebP, and libaom / libavif for AVIF — each compiled to WebAssembly and executed inside a Web Worker so the work happens off the main thread. All of this is local computation. The converter does not POST your image to a backend, because there is no backend to send it to. ConvertMyPic is a static front-end application: the codecs do the heavy lifting on your own CPU. You do not have to take our word for it. Open your browser's developer tools, switch to the Network tab, then convert an image and watch the requests. You will see the initial page load fetch the app shell and the WebAssembly codec modules, and after that, zero outbound requests carrying your image data during the conversion itself. The file you dropped in stays on your machine from start to finish.
What we do and do not collect
We do not collect your images. Because conversion is on-device, the bytes of your photos and graphics never reach us, and there is nothing on our side to store, inspect, sell, or leak. We also do not require an account, so there is no name, email address, password, or profile associated with your use of the tool. We do not run third-party advertising networks, behavioural trackers, fingerprinting scripts, or session-replay tools. There is no analytics product silently watching what you convert. The one category of data that necessarily exists is ordinary web-server request logs for the static files that make up the site. When your browser fetches the page and the codec modules, the host serving those files records the same basic technical information any web host records — for example a timestamp, the requested file, and a truncated or hashed IP for abuse prevention and uptime monitoring. Those logs concern delivery of the application itself; they never contain your images or anything about what you converted, because that activity happens locally and is never transmitted. We do not use those logs to build a profile of you.
Cookies and local storage
ConvertMyPic does not set advertising or tracking cookies. The app installs a service worker that caches the application shell and the WebAssembly codec modules in your browser's Cache Storage so the tool loads instantly on repeat visits and keeps working offline as a Progressive Web App after the first load. That cache is a copy of our public, static program files — not your data — and it lives only on your device. You can clear it at any time through your browser's settings (clearing site data or cache), and the app will simply re-download the program files the next time you visit. If the tool remembers small interface preferences between visits, those values are held in your browser's local storage on your own device and are never sent anywhere. Nothing about the images you convert is written to persistent storage by the converter.
Third parties
We keep the third-party surface deliberately small. Web fonts are self-hosted and served from the same origin as the application, so loading a page does not hand a font provider a record of your visit. The static files — HTML, JavaScript, the WebAssembly codec modules, and assets — are served over a content delivery network (CDN) so the app loads quickly and reliably worldwide. A CDN edge node sees the standard request metadata required to deliver a file (such as the requested URL and the connecting IP), as described in the request-logs section above. It does not and cannot see your images, because your images are never sent over the network. We do not embed ad networks, social media tracking pixels, or analytics SDKs.
Installing as a PWA and the share target
ConvertMyPic can be installed as a Progressive Web App from a supported browser, which adds it to your home screen or app launcher and lets it run offline. Installing does not change the privacy model: the installed app contains the same on-device codecs and still performs every conversion locally. When installed, the app may register as a share target so you can send an image to it from your operating system's share sheet. An image shared this way is handed to the local app and processed on-device exactly like a file you drop in manually. It is not uploaded to a server as part of being shared into the app.
Changes to this policy and how to reach us
ConvertMyPic is designed to be private by default — the architecture, not a promise, is what keeps your files on your device. If this policy changes, we will update the text on this page and revise the "Last updated" date above. Because the application is versioned and shipped as static files, material changes ship alongside the code rather than through a separate notice. This policy describes how the tool is built and behaves. It is written to be accurate rather than expansive: we do not claim formal certifications or compliance with specific regulations beyond what the on-device, no-upload design straightforwardly provides. If you have a question about how ConvertMyPic handles your data, the most reliable answer is the one you can observe yourself in the Network tab — but you are welcome to reach out through the contact link on the site.