Privacy

Your images stay on your device

Every conversion and edit runs inside your browser, using code your browser downloaded from this site. Your images are read from your device, processed in memory and written back to your device.

They are not uploaded to ImageForge, because there is nowhere to upload them to: the application has no server that receives files. The site is a set of static files, and there is no backend that processes images.

What happens, step by step

It is easier to trust a description that is specific, so here is every step of ordinary use and what each one does.

• You open a page. Your browser requests the HTML, the stylesheet and, on a tool page, the application code. Nothing about you is recorded by the application.
• You switch the theme. The value light or dark is written to your own browser under the key imageforge-theme. It is never sent anywhere.
• You choose an image. The file is read from your device by your browser. It is not transmitted. Its first bytes are inspected to identify the real format, and the dimensions are read from the header to check the image will not exhaust your device memory.
• You convert it. If the format needs a codec your browser does not have, that codec is downloaded once from this same site and then runs locally. The pixels are decoded, your edits applied and the result encoded, all inside a worker thread on your device.
• You download the result. The converted file exists only in your browser memory until you save it. The link points at a blob URL, which is a reference to that memory and is not reachable from the network.
• You convert several files. The same thing happens for each, a few at a time so your device does not run out of memory. Nothing about the batch is recorded.
• You download a ZIP. The archive is assembled in your browser from files already in its memory. No server builds it and none receives it.

What the hosting provider sees

This is the one place where data does leave your device, and saying otherwise would be false.

Requesting any page on the internet means connecting to a server, and that server necessarily sees your IP address, the address you requested, your user agent and similar technical details. ImageForge is served as static files through Cloudflare Pages, so Cloudflare handles those requests, and its own privacy policy and data processing terms govern what it records and for how long.

That is infrastructure data, not application data. ImageForge does not read it, does not receive a copy of it, and adds no logging or analytics of its own on top. If the hosting provider ever changes, this page will be updated to name the new one.

Storage on your device

One preference is stored locally, in your browser, under the key imageforge-theme: whether you chose the light or the dark appearance. Choosing to follow your system setting removes it.

Nothing else is stored. This site sets no cookies, and uses no session storage, no IndexedDB, no cache storage and no service worker. It holds no database of any kind.

Why there is no consent banner

Consent banners exist because sites store or read things on your device that you did not ask for: advertising identifiers, analytics cookies, third-party tags. None of that happens here.

The single item stored is the appearance you chose, written only at the moment you click Light or Dark, and removed when you choose to follow your system. It identifies nobody, is never sent anywhere, and exists solely to do the thing you just asked for.

Showing a banner for that would ask you to consent to your own preference, and would train people to dismiss a dialogue that elsewhere matters. If advertising or analytics is ever introduced, this decision will be revisited before anything goes live.

No third-party services

No analytics service, tag manager, advertising network, tracking pixel, external font, hosted script or embedded widget is loaded by any page. This is checked automatically every time the site is built.

The only external address that appears anywhere in the site is schema.org, which is an identifier used inside structured data to name a vocabulary. Nothing is ever requested from it.

Photo metadata

Photographs often carry metadata such as the camera model and, sometimes, the location where they were taken. ImageForge reads this to show you useful details about your file. Location data is deliberately never read or displayed, only reported as present, and metadata is not carried into exported files by default.

None of it leaves your device in any case, because none of the file does.

Accounts and children

There are no accounts. The application does not ask who you are and has no way of knowing. It collects nothing from anyone, of any age.

Applicable law and your rights

ImageForge is run from Uruguay, where the protection of personal data is governed by Law No. 18.331 of 2008 and its regulations, by articles 37 to 40 of Law No. 19.670 of 2018, and by Decree No. 64/020 of 2020. The supervisory authority is the Unidad Reguladora y de Control de Datos Personales (URCDP).

That framework gives people rights over their personal data, including the right to be informed about its processing, to access it, to have it corrected when inaccurate, to have it deleted, and not to receive unwanted advertising.

Those rights are set out here because they exist, not because ImageForge holds anything to exercise them against. There is no account, no database and no stored personal data, so a request to access or delete your data would be answered by explaining that none was ever held. Infrastructure data such as server logs is held by the hosting provider under its own terms.

ImageForge does not process sensitive data, does not carry out profiling, and does not process personal data on anything approaching the scale that would require a designated data protection officer under article 10 of Decree 64/020.

Future changes

This page describes what ImageForge does today, not what it might do one day. Keeping those two things separate is the only way a policy stays useful.

Advertising may be introduced later to fund the project, and analytics may be added to understand which tools people use. If either happens, this page will be updated before it goes live, it will name the specific services and describe what they receive, and any consent mechanism those services require will be in place first.

What will not change is the part that matters: images are processed on your device, and there is no plan to upload them.

Contact

Questions about this page, or about anything else, can be sent to [email protected].