Security & Privacy

Privacy you can audit.

At this moment we do not save images on our servers. Detectiks keeps the detection pipeline visible: local scans stay in your browser, and API scans only persist hashes and verdict metadata for caching, billing, and customer history.

Account basics

We keep your email, password hash, plan status, and payment metadata so you can sign in and manage billing without us ever seeing your actual password.

Detection summaries

Each scan record stores the verdict, confidence, model name, processing time, and a few hashes so repeat checks show up instantly. The original picture never leaves your device unless you explicitly upload it.

Performance helpers

Caches and usage logs help the service stay fast and fair. They record only derived metadata and request status so we can enforce limits and spot abuse without exposing personal files.

Local control

The recent-scan list is stored in your browser storage and can be cleared with the "Clear history" button. Anything labeled local keeps pixels on your device unless you choose to share.

Detection flows

How local and API scans differ

Both approaches use the same detection engine. The table below shows how the data travels when you stay local versus when you lean on the cloud helpers.

Local detection (default on the website)

  • Runs inside your browser so the pixels never leave your device unless you explicitly upload them.
  • We keep only the verdict, score, and a few hashes when you let us save your history; nothing more is shared.
  • The Chrome extension offers the same experience, and you can point it at your own server for extra peace of mind.

Cloud-assisted detection

  • Uploads go through a validation step before analysis, but only cloud-derived summaries ever reach our servers.
  • Caches make repeat scans faster, and usage logs (status, timestamp, IP) help keep the service reliable without keeping images.
  • Everything is internal to our ops team—these logs exist for rate limiting and diagnostics, not for advertising or sharing.

Retention & security posture

  • We do not save your pictures on our servers. Only a few hashed metadata points stick around so we can spot duplicates and keep caches warm.
  • Cached entries refresh after each scan, so older ones naturally fall away as they are reprocessed.
  • Usage logs exist only for rate limiting and diagnostics; they never contain personal files.