ClicInSitu's privacy doesn't rest on a promise written into a contract: the app is built that way from the ground up. The app has no server that could receive your data.
Your photos, voice memos and details are stored in the app's private space, on your phone. When you send, they go directly from your phone to the recipients you chose: your email app, your own sending server (silent sending), or your company's automation. Every send is encrypted in transit (TLS) — Gmail, Outlook or any other mail server (SMTP), as well as your automation: the app refuses any unencrypted address.
There is no account, no sign-up, no publisher cloud, no third-party SDK, no analytics in the app. We don't know who you are, or what you send — and that's deliberate.
It's verifiable: a network capture of the phone shows that no connection goes out to a publisher server. We've done the exercise; you can redo it.
ClicInSitu doesn't alter your photos: no compression, date and location data intact — from the gallery as from the camera, by email as by silent sending.
The password used for silent sending is stored encrypted on the phone, in Android's protected storage. It is only sent to your mail server, over an encrypted connection, to sign you in — not to ClicInSitu.
Timestamped, geolocated photos, My sends (the log of everything that went out), and in Business a SHA-256 control checksum for each photo and report. Enough to trace what went out, when and from where — without claiming any "legal value".
Photos that have already been sent can be cleaned up automatically from the app's storage, based on the setting you choose. You stay in control.
All the details are in our privacy policy. The template file format is public: the .clicinsitu file format.
Found a security flaw in ClicInSitu? Write to us — we take every report seriously, and we commit to the following timelines:
Describe the issue, the steps to reproduce it and the app version. We'll keep you posted until it's fixed.