Omaya security and data: privacy, isolation, access and audit
A platform that knows where people are has to earn the right to. In Omaya a tag is a number until you bind it to a person, phones and other unknown devices are counted as footfall but never identified, and nobody needs an app.
Each organisation's data lives in its own database. You choose how long history is kept and older data is removed automatically, and requests to see or erase a person's data are handled in the console. Roles have per-page permissions and can be limited to people and assets with chosen labels. Administrators can sign in through your identity provider with single sign-on, and two-factor sign-in and password expiry are available for direct logins. Every administrative change is recorded with who, what and when.
Omaya AI sees one organisation through read-only views with secrets removed, and applies nothing without a person's approval.
Controls
Anonymous by default
A database per organisation
Retention you set
Single sign-on with Microsoft Entra ID, Okta, Google Workspace or any OpenID Connect provider
Audit trail of every administrative change
Frequently asked questions
Where is our data kept?
Omaya runs as a managed service. Each organisation has its own database, and the AI assistant only reads that organisation's data, through read-only views.
What happens if the network drops?
A gateway that loses its link stops sending; Omaya logs the outage to the minute and alerts you. Reports mark the gap as missing rather than zero.
Is tracking people a privacy problem?
Tags are anonymous until you bind one to a person, unknown phones are counted but never identified, you set how long history is kept, and every administrative change is recorded.