What is protected, from whom, and what isn't.
Written for the person in your organisation who has to approve this. Technical details, including protocols and library versions, are in the documentation.
What the server can and cannot read
End-to-end encryption covers specific kinds of data, not everything. This is the split.
| DATA | PROTECTION | WHAT THE SERVER SEES |
|---|---|---|
| Messages | End-to-end encrypted | That a message was sent, by which device, to which channel, when, and its size. |
| Photos and files | End-to-end encrypted | File size and when it was sent. |
| Incidents, tasks, map objects | Encrypted in transit and at rest | The content, so the node can sync it between devices and sites and raise alerts on it. |
| Positions | Encrypted in transit and at rest | Positions of members who are sharing, so geofences and the operator view work. |
| Accounts and membership | Encrypted in transit and at rest | Who belongs to which operation, their role and their devices. |
No home-made cryptography
Sinkaos uses established, published protocols and widely reviewed open-source libraries. We did not invent our own. The documentation names them and their versions.
Every device has its own keys
Each phone or browser generates its own key pair when it joins. The private key stays on that device. Adding a device to your account is something you approve from a device you already have.
Revoking a device
Revoke a lost phone from any of your other devices or ask the operator to do it. A revoked device can no longer sync or decrypt anything new. What it already stored remains protected by its screen lock and local encryption.
Data on the phone
The local database, mission packs and queued changes are encrypted at rest. Leaving an operation removes its data from the device.
Location is visible to the person sharing it
A member always sees when their position is being shared and with whom. Sharing can be limited to the operation’s duration or to certain roles.
Signing in
Passwords, passkeys and authenticator-app codes, or your organisation’s single sign-on. No phone number is needed.
Recovery without a back door
Accounts are recovered through a trusted device or an encrypted recovery package. Recovery never gives us access to your old messages. If your organisation needs compliance access, it shows up as a visible participant, never as a hidden key.
Wiping a device
Anyone can wipe Sinkaos data from their own device on the spot. A remote wipe can be requested, and you see whether the device has confirmed it. A phone that never comes back online can’t confirm, and we say so.
Audit trail
Sign-ins, device changes, roles, policies, integrations, exports and admin actions go into a tamper-evident log. Administrators manage the system without getting access to encrypted content.
AI is optional and yours to control
AI features can be switched off entirely, or pointed at a provider or self-hosted model you approve. Retrieved content is treated as data, never as instructions, and what an assistant may do is enforced outside the model.
Audits and certifications
We list an audit or certification here only when there is a report or certificate you can check.
Your responsibilities
Encryption doesn't help if an unlocked phone is left on a car seat. A few things stay with you.
- Screen locks on every device that joins an operation.
- Revoking lost or replaced devices straight away.
- Choosing who gets which role, especially for guests.
- On your own servers: updates, backups and access to the machines.
Found a vulnerability?
Email us before publishing anything. We reply within three working days and keep you updated until it's fixed. We won't take legal action over good-faith research.
- hello@sinkaos.si
- Policy
- /.well-known/security.txt
Need answers for a security review?
Send us your questionnaire. We answer them ourselves, in writing.