Nuboc holds the general ledger for the businesses that run on it. That makes the integrity and confidentiality of your data the product, not a feature of it. This page describes the controls we operate. Where a control is still being built or audited, we say so rather than rounding up.
Our SOC 2 Type II observation window is underway. We are not yet able to provide a completed Type II report, and we will not describe ourselves as certified until one is issued. Our Trust Center shows live control monitoring in the meantime.
Tenant isolation
Nuboc is multi-tenant, and separation between customers is enforced in the database rather than in application code alone. Every tenant-scoped record carries its owning organization, and the database refuses to return rows outside the caller's tenant context regardless of what a query asks for.
The control that matters most is the one that fails closed: if a tenant-scoped model is ever added without its corresponding isolation policy, the application refuses to start in production. A missing policy is a failed deploy, not a silent data leak. Administrative operations that legitimately cross tenants run under a separate, explicitly named role and are logged.
Encryption
All traffic to Nuboc is served over TLS, and non-TLS requests are redirected rather than served. HSTS is enabled.
Beyond transport, particularly sensitive fields are encrypted at the application layer with AES-GCM, so they are unreadable in database backups and to anyone with raw table access. That includes tax identification numbers, bank account numbers and IBANs, contact details, per-tenant storage keys, license keys, and the IP addresses and user agents retained with login sessions. Encryption keys are held outside the codebase.
Access control
Permissions are expressed as explicit capabilities rather than broad roles, and they can be granted at the organization, entity, location, or department level. Every privileged action in the product checks for the specific capability it requires.
- Access can be deactivated for an entity without deleting the person's account or their history.
- Sessions can be locked behind a PIN, lock automatically after inactivity, and enter a cooldown after repeated failed attempts.
- Devices used to reach an account are tracked and can be reviewed.
- Role and permission changes are recorded with the identity of the person who made them.
When our staff need to look at your data
Nuboc support cannot browse your data at will. Access requires a grant that you approve, is scoped to what was asked for, expires on a timer, and can be revoked at any time. An expiring grant stops granting access the moment it runs out, including mid-session. Every use of support access is written to your audit log, so the record of who looked at what belongs to you rather than to us.
Audit logging
Security-relevant events — authentication, permission changes, administrative actions, and support access — are written to an append-only audit log. Entries are cryptographically chained to the ones before them, so altering or removing a past record breaks the chain and is detectable rather than silent. The chain can be verified independently of the application that wrote it.
Secure development
Changes are reviewed before merge and run through automated tests and static analysis in continuous integration. Dependencies are monitored and updated on a continuous basis. We run periodic security review of the codebase, including adversarial review targeting authorization gaps, injection, and tenant-boundary weaknesses; findings are tracked to remediation and re-verified against the code.
We treat security fixes as ordinary engineering work rather than events to announce. Our changelog records that security improvements shipped without itemizing the specific weaknesses they closed, since that detail is more useful to an attacker than to a customer.
Reporting a vulnerability
If you believe you have found a security issue in Nuboc, please write to security@nuboc.com. Tell us what you found and how to reproduce it, and give us a reasonable window to fix it before disclosing publicly. We will acknowledge your report, keep you updated while we work, and credit you if you would like to be credited. We will not pursue legal action against good-faith research that respects customer data and avoids service disruption.
Questions from your security team
Our Trust Center is public and is the fastest way to see our current control status. For a completed security questionnaire, our subprocessor list, or a walkthrough of our architecture under NDA, contact hello@nuboc.com and we will get your team what it needs.
This page is reviewed at least annually and updated when our practices change. If anything here is unclear or appears inconsistent with what you observe, tell us at security@nuboc.com.