Security

Your business data is yours alone.

Security isn't a feature we bolted on. It's how Operalo is built, from the database layer up.

Tenant isolation

Every record belongs to exactly one business. All reads and writes pass through a single data layer that pins your workspace id onto every query, so there is no code path that can return another business's records. Automated tests check this on every change.

Passwords & sessions

Passwords are hashed with bcrypt (cost 12). Sessions are random 256-bit tokens in HttpOnly, SameSite cookies; only a hash is stored, so sessions can be revoked instantly, and changing your password signs out every other device.

Abuse protection

Sign-in is rate-limited per account and per network, signup and AI usage are throttled, and limits are enforced across every server, not per process.

Roles & least privilege

Five roles from Owner to Viewer, enforced on the server for every request. Sensitive modules can be hidden from individual people.

Audit trail

Creates, updates, deletes, exports, sign-ins and settings changes are logged with who, when and which fields changed.

Hardened by default

Strict Content Security Policy, HSTS, clickjacking protection, origin checks against cross-site requests, input validation on every field, and spreadsheet-formula neutralisation in CSV exports.

AI with guard-rails

Operalo AI can only read what your account can read, through the same permission checks. It cannot change data. Anything it drafts is reviewed by a person before it's saved.

Payments

Card and UPI payments are handled by Razorpay. Plans activate only from cryptographically verified payments; Operalo never sees or stores card numbers.