Skip to content

Security & privacy

Your images never reach our servers.

SchweizerIMG was designed so that we cannot see your images — not because we promise not to look, but because they never leave your device. Here is how that works, what we do store, and where the limits are.

  • Images processed on your device
  • connect-src 'self'
  • Swiss data protection law
  • No third-party trackers, no advertising

How a tool run works

The image stays. Only the tool name travels. Two short messages per run — and no image among them.

Processed on this device: three photos are processed by the image engine in the browser; the only request to the server names the tool, and the server never receives the images.
  1. 01

    You open an image

    The file is read by your browser — from your disk, a folder or the clipboard. It is not sent anywhere.

  2. 02

    Your device does the work

    The image engine runs in your browser with WebAssembly and saves the result where you choose.

  3. 03

    Our server counts the run

    One request when the tool starts (which tool), one when it ends (finished, failed or cancelled). That is all a run tells us.

What we can and cannot see

Your images stay. Here is what we hold.

None of the image data below is ever sent to us — not in a request, a log, an error report, our visit statistics or a cookie. What we do store is listed on the right, as in our data inventory.

Never leaves your device

Processed locally
  • PixelsThe image data of your files and every result.
  • File namesNames often reveal more than people think.
  • Sizes and dimensionsPlan limits are checked by the engine in your browser.
  • Location and camera dataGPS, capture times, serial numbers and history — also when you view or edit them.
  • Thumbnails and previewsDrawn in your browser; no thumbnail, hash or fingerprint is made for us.
  • ResultsHanded to you as downloads. We keep no copy.

No third-party trackers

No third-party analytics, no advertising, no tracking pixels and no third-party scripts, fonts or CDNs. Our own visit statistics stay on our servers in Switzerland and never include anything from your images.

What our server stores

No image data
  • AccountE-mail address, optional name, optional password (only as a hash), language and settings.Until you delete your account
  • SessionsA session token and your browser's device description, so you can end sessions.30 days, or until you log out
  • OperationsOne record per tool run: which tool, its status and the time.13 months, then deleted automatically
  • BillingPlan, subscription status and Stripe customer reference — never card details.As long as the account and the law require
  • E-mailsA log of the transactional e-mails we sent you.90 days
  • Security logsAudit entries and rate-limit counters, some with the IP address.IP addresses removed or expired within 90 days
  • Visit statisticsPages visited, how the visit started, device, browser and country — pseudonymous, no IP address, nothing from your images.13 months after the visit

That is all of it. The privacy policy names every recipient, such as our e-mail provider and Stripe.

The technical guarantee

A browser rule, not a promise.

Every page of SchweizerIMG is delivered with a strict Content Security Policy. It tells your browser which servers the page may talk to — and the answer is: only ours.

connect-src 'self' means scripts on the page and the image engine's workers cannot open a connection to any other server. If a script tried, your browser would block it.

Content Security Policy (excerpt)

Content-Security-Policy:
  default-src 'self';
  connect-src 'self';
  worker-src 'self' blob:;
  img-src 'self' blob: data:;
  object-src 'none';
  frame-ancestors 'none'; …

No third-party connections

No third-party analytics, no advertising, no tracking pixels, no external fonts or CDNs. All assets, including the engine and its codecs, are served by us; our own visit statistics go only to our own server.

A fixed, minimal API

The usage endpoint accepts exactly two fields — the tool and the status — and rejects any request that carries more.

Errors without content

If a tool fails, we record an error code. Error messages can quote file names, so they are never sent.

No images stored in the browser

Images are kept in memory only while the tool is open — never in local storage, IndexedDB or a cache.

Where data lives

Images on your device. Accounts in Switzerland.

Only your account data and our own visit statistics leave your device — never your images — and they stay with a few named providers.

Zurich's old town from above, with the Limmat, its bridges and church towers

Honest limits

What the architecture does not do

  • Your browser and device

    Browser extensions with access to all websites can read what a page displays. Use a trusted, up-to-date browser and device for confidential work.

  • Blurring is final — in the copy

    Blurred or pixelated areas cannot be recovered from the result. The original file on your device is unchanged: keep or delete it deliberately.

  • Sharing still needs care

    Removing metadata and blurring faces protect what is in the file. Where and with whom you share it remains your decision.

  • Device memory sets the limit

    Very large images and long batches need memory. Phones may refuse images a computer handles easily.

  • Limits are checked in the app

    Plan limits are enforced by the app in your browser. A modified client could bypass them — it would affect our accounting, never anyone's images.

  • We are not certified

    SchweizerIMG holds no security certification. We prefer to explain the architecture openly instead of quoting badges.

Your data

Delete it, keep it short, nothing to export.

  • Delete your account

    Settings → Account → Delete account. Account, sessions, tool-run history and subscription records are deleted immediately; visits in our visit statistics lose their link to the account.

  • Kept only as long as needed

    Tool-run records are deleted after 13 months, visit statistics 13 months after the visit, e-mail logs after 90 days, IP addresses in security logs within 90 days.

  • Nothing to export

    Your images and results never reached us — they are where you saved them, on your own devices.

Documents

In writing, not only on this page.

The privacy policy explains what we process; business customers can rely on a data processing agreement.

Data processing agreement

Swiss law · nDSG

  • States that images are not processed by us at all
  • Lists the sub-processors for account data and e-mail
  • Sets out deletion and retention periods
  • Assistance with data subject requests and security incidents
  • Swiss law, place of jurisdiction Pfäffikon SZ

Privacy policy

Every category of personal data we process, why, for how long and who receives it — under the nDSG, and the GDPR where it applies.

What we don't claim

  • A security certification such as ISO 27001 or SOC 2
  • An audit by an independent third party
  • End-to-end encryption — there is no image on our side to encrypt
  • Protection against a compromised device or browser extension
  • Automatic detection of faces or number plates
  • Anonymity — your account e-mail address is known to us

We prefer to explain the architecture openly instead of quoting badges.

Technical details

For the IT department

The engine runs in your browser and builds on widely used open-source libraries, compiled to WebAssembly and served from our own domain.

FAQ

Security questions

Keep private images private.

Start with the free plan and see for yourself that your images stay where they are.