Skip to content

Privacy

Short version: your files stay on your device. Here is the longer version, without the legalese.

This policy covers everything we make: the website, the API, the browser extension and the IncognitoShare iPhone app. Where the app behaves differently from the website — it does, and in your favour — it says so below.

Your files never leave your device

When you add a file on the check page, it is read by code running inside your own browser. It is not sent to us, because there is no server of ours that accepts files.

The checking runs in a background thread — a web worker — which keeps the page responsive and keeps your file in a part of the browser that has no connection to the network. The code that reads your file makes no network requests of any kind. That is a rule we enforce automatically: our checker library is tested and linted on the condition that it cannot make one.

If you close the tab, your file is gone. We never had it. Nothing is written to a disk, a database or a log anywhere on our side.

What we do collect on the website

After a check finishes on this website, we send ourselves one small, anonymous message so we know which detectors are earning their keep. It contains exactly five things:

  • that the check came from the website (rather than the app or extension)
  • the kind of file — “image”, “pdf”, “excel”
  • which categories of thing we found — “gps_location”, “document_author” — but never what they were
  • the overall risk level we showed you
  • whether you downloaded a cleaned copy

It contains no filename, no file content, no previews, no hashes and no account identifier. There is no cookie attached to it. We cannot tie two of these messages together, or to you.

Your web server logs will record that your browser contacted us, including your IP address, in the ordinary way that every website works. We do not join that to anything else.

The iPhone app does not send this message, or any other. It has no analytics of any kind.

The iPhone app: everything runs on your phone

Checking a photo, scanning your gallery, covering a face, stripping metadata — all of it happens on the device, using Apple’s own on-device Vision and image frameworks. Your photos are never uploaded. There is no server of ours that accepts one, and no account to sign in to.

The app makes exactly one network request, and it is not about you: it fetches the current rule pack — the list of what to check for and the wording used to describe it — from this site, the same list the browser extension uses. That request carries no photo, no identifier and no information about you. If it fails, the app falls back to the copy of the list bundled inside it and carries on working offline.

The same is true of the two extensions that ship with the app: the share-sheet action receives the image bytes directly from whichever app shared them and checks them in place, and the Safari extension reads the file you picked in the page before the site uploads it. Neither sends anything anywhere.

What the iPhone app stores, and where

In the app’s own storage on your device, and nowhere else:

  • A scan record per photo you check — which photo in your library it was, when it was checked, which categories were found (“has a face”, “has GPS data”) and the overall risk level. This is what lets a rescan skip photos that have not changed.
  • Your preferences — cover style and strength, rounded corners, and any checks you have switched off.
  • A cached copy of the rule pack, so the app works with no connection.
  • Whether you have seen the intro, so it is not shown twice.

No photo, and no value found inside one, is ever stored. The scan record holds category labels and nothing else — there is no field on it that could carry a card number, an address or a name, which is deliberate rather than incidental.

All of it lives in this app’s own storage, reachable by the app and its own extensions and nothing else. It is not synced to iCloud. It is included in your device backup exactly like any other app’s data. It is gone the moment you delete the app — there is nothing on our side to ask us to delete.

Why the app asks for your photo library, and what it does with it

The app asks for photo library access because it has to read a photo’s original bytes — GPS tag and all. The standard iOS photo picker strips location data before an app ever sees the file, which would leave the app unable to show you the one thing you most likely opened it for.

That access is used for two things only: reading the photos you ask it to check, and saving a cleaned copy back when you ask for one. A cleaned copy is saved as a new photo; your original is never modified or overwritten. The app can delete an original afterwards, but only when you choose that explicitly, and iOS asks you to confirm it a second time.

Camera access, if you use the in-app camera, works the same way: the photo you take is checked in memory and is not saved to your library at all until you pick which version to keep.

If you leave a tip in the app, the payment is handled entirely by Apple. We never see your card, your name or your address — only an anonymous count of purchases in our App Store sales reports.

What we do not do

  • No required account — everything on this page works signed out. If you do sign in, we store your email address and which plan you are on, and nothing else. The iPhone app has no sign-in at all.
  • No advertising scripts, and no analytics loaded from other companies’ domains. We count page views through our hosting provider, served from our own address — no cookies, no cross-site tracking, and only ever a page route, never anything about your files. The iPhone app goes further: no analytics at all, and no third-party code of any kind inside it.
  • No selling or sharing of anything, because we do not have anything to sell.
  • No training of models on your files. We never receive them.

The waitlist

The waitlist form on the home page is not connected to anything yet, and it says so when you use it. When it is, your address will be used for one message about the launch and nothing else.

What we cannot promise

We can only report what we can detect. A result of no issues found means our checks did not match anything — not that a file is safe to share. We deliberately never use the word “safe”, because no tool can know what is risky in your particular situation.

Cleaning removes hidden data: metadata, comments, edit history, attachments. It does not rewrite the visible content of a document. If a card number is typed into a paragraph, we will point at it, but taking it out is your decision and your edit.

Pictures are the exception, and only because you drive it: in the iPhone app and in the redaction studio here, anything found in the image itself can be covered — and anything the checks missed can be covered by you, by hand. What gets covered is always your call, not a model’s.

Getting in touch

Questions, or something here that does not match what you observe? privacy@incognitoshare.com. If you find a case where a file does leave the device, we want to hear about it before anyone else does.