Trust
Security
A short, plain account of how InmaEvent protects accounts and the contacts stored in them.
Last updated 2026-09-07
Encrypted in transit and at rest
All traffic runs over HTTPS. Data is stored in a managed database with encryption at rest and encrypted connections.
Sign-in required
Every page that shows or saves contact data requires an authenticated session. Public pages contain no customer data.
New sign-ups use email and password or Google sign-in; passwords are hashed and checked against known-breached password lists.
Per-account isolation
Row-level access rules in the database tie every record to the account that created it, so one account cannot read, edit or delete another account's data — even through the API.
Your AI key
If you enable the card photo reader, your API key is stored against your account only and is used solely to run your own card reads. It is never exposed to other users and you can remove it from settings at any time.
Reporting a problem
If you believe you have found a security issue, email info@inmation.ai with the details. Please do not publish it before we have had a chance to respond.