Security is how KeroIQ is built — not something bolted on after.

Data protection & isolation

Every business's data is walled off from every other business's — at the database itself.

• Database-level tenant isolation. Row-level security enforces separation in the database, fail-closed — a request scoped to one business can never return another’s records, regardless of any bug in the app above it.
• Continuously tested against itself. Automated tests run on every change attempt cross-business reads and role escalation directly against the database, bypassing the application layer entirely — every attempt returns zero rows.
• Encrypted in transit. HTTPS is enforced end-to-end (TLS 1.2 and 1.3); the native app refuses cleartext connections. Session tokens live in HttpOnly, Secure cookies that page scripts cannot read.
• One source of truth. A single primary database, no read replicas — you never see stale or inconsistent data, and there is one clear place every record lives.

Access control & accounts

The right people see the right things, and a compromised account can be shut off instantly.

• Role-based access, least privilege. Owner, manager, and staff roles each see only what their job requires; destructive and financial actions are restricted to owners.
• Instant kill-switch. A compromised or departing account can be disabled and disconnected in real time, mid-session — not at the next login.
• Login audit trail. Every sign-in is recorded and visible to owners, so an unexpected access is something you can actually see.
• Brute-force resistance. Authentication is rate-limited per account and per network, with forced password rotation available on demand.

Infrastructure & availability

Hosted on managed, hardened infrastructure, with your data recoverable to the minute.

• Managed database with point-in-time recovery. Runs on a managed PostgreSQL service that can restore to a specific moment, so an accident or corruption is recoverable, not catastrophic.
• A full backup before every schema change. A complete database snapshot is taken and integrity-checked before any migration, on top of automated daily backups — there is always a clean point to roll back to.
• Edge protection. A web application firewall sits in front of the platform, and the origin is locked so it can only be reached through that protective layer.
• Monitored, with on-call alerting. Automated health monitoring watches the live system and pages a human when something is wrong — problems are caught proactively, not reported by customers.

How the software is built

The engineering process is itself a security control.

• No direct-to-production changes. Every change is reviewed and passes automated checks before it can ship; the protection applies even to administrators. There is no back door around it.
• Automated security scanning. Every change is scanned for known-vulnerable dependencies, exposed secrets, and insecure code patterns, and the results are reviewed before release.
• Adversarial review on the money path. Payment, refund, and permission changes get a deliberate "try to break it" review and a tested rollback before release — this has caught real defects before any customer was affected.
• No third-party tracking scripts. The app loads no external analytics or advertising code, so there is no third-party with a view into your data.

Privacy

We collect what a business needs to operate — and nothing to sell.

• Minimal collection, no data sales. We store only what running the business requires — orders, loyalty, staffing, payroll — and never sell or share it with advertisers.
• Sensitive data stays out of logs. Passwords, tokens, card numbers, and personal identifiers are kept out of application logs, enforced through code review.
• Data access & deletion on request. On request, we can export a business’s customer, order, and menu data today. Individual data-deletion requests are fulfilled manually within our support window, in line with California privacy law (CCPA/CPRA); a self-service deletion tool is on our roadmap.

Compliance

Where we stand today, stated honestly.

KeroIQ's controls are built to align with the SOC 2 Trust Services Criteria — security, availability, and confidentiality. We are not yet formally SOC 2 certified; that audit is on our roadmap and pursued as we take on larger customers. If your organization needs it to move forward, tell us — because the underlying controls are already in place, certification is a formality we can schedule, not a system we have to build.

Email security@keroiq.com and a human will answer. We are happy to walk your security team through any of the above.

KeroIQ · Last updated September 2026. This page describes controls in place at the time of writing; roadmap items are labeled as such.