Security
Built to keep your data yours.
Your calls contain your customers' information. Here is how the Oreniq platform is built to protect it.
How we protect it
Security in the platform's design.
Practical safeguards built into how accounts, data and access work.
Secure authentication
The customer dashboard requires sign-in, and account passwords are stored as salted one-way hashes rather than in readable form.
Server-side authorization
Permissions are enforced on the server for every action, not only hidden in the interface, so access doesn't depend on what the browser shows.
Tenant isolation
Each business's records are scoped to its own organization, and data queries are filtered by that organization so one customer's data isn't served to another.
Protected credentials
API keys and other secrets are kept in server-side configuration, out of source code and out of the browser.
Verified payment notifications
Incoming notifications from our payment providers are checked against their signatures before they can change an account.
Controlled administrative access
Internal administration is separate from customer accounts, and administrative actions are recorded in an audit log.
Have a security question, or found something we should know about? Email hello@oreniq.in and a person will reply.
Want to talk it through?
Bring your security questions to a demo call and we'll answer them directly.
