Security
Designed for confidential legal work
JURINEZ is designed to hold confidential and potentially privileged information. The controls on this page are planned. They are not a certification, and they are not a claim that a control is already operating in production.
JURINEZ does not claim SOC 2, ISO 27001, or any other security or privacy certification. No such certification is in place. The controls are designed with a future independent assessment in mind.
Encryption in transit
Designed to require TLS 1.2 or higher on every connection, with TLS 1.3 preferred, including traffic between internal services.
Encryption at rest
Planned for databases, backups and stored files, with additional field encryption for highly sensitive values such as identification details, notes, messages and integration credentials.
Separate firm workspaces
Each firm is a tenant. The design isolates one firm’s records from another’s at several layers, including the database, so a request cannot simply name another firm and read its files. This will be tested before any production release.
Multi-factor authentication
Planned for staff and available for client-portal users. A firm will be able to require it. Passkeys are planned after the first release.
Sessions
Designed as server-side sessions in cookies that are not readable by script, with idle and absolute timeouts, and revocation when a password, role or account changes.
Least privilege
Roles and matter-level permissions, including ethical walls, are planned to be enforced on the server. The screen may hide a control. The server still refuses the action.
Audit logs
Planned as an append-only record of sign-in, permission changes, access to sensitive records, downloads, shares, exports, integration events and AI use. The database role that writes the log is designed without permission to change or delete it.
Uploads
Designed so every upload is type-checked, size-limited, scanned, and held back until the scan succeeds. Previews are planned to be rendered in isolation. Uploaded files are not executed.
Platform staff
Designed so Nezuna Technologies operators have no default access to a firm’s confidential records. A later break-glass path, if built, would require the firm’s approval, a time limit and a full log.
Backups and residency
Encrypted backups and a recovery drill are planned. Canada is the first data region. A firm’s records are designed to stay in the region selected for that firm.
What this page is not
- It is not a penetration-test report. Independent testing is planned before launch.
- It is not a statement of compliance with any statute. Canadian privacy law is part of the legal review still to be completed.
- It is not a promise that a specific control has been audited.
Ask for early access
Tell us who you are and where you practise. If early access opens in Canada, we will use that address to write to you. There is no public launch date.
Join the early access waitlist