Security, described as it is built
How Zizora protects deal documents, in plain language: what each control does, and what it does not protect against. Nothing here is a certification or a promise beyond the product as it is.
Who can see what
Every decision about access is made on the server, by one piece of code, for every request.
- One permission check decides every list, search result, preview, download, export and AI citation. Levels are ordered: no access, view, print, download a watermarked PDF, download the original, upload.
- A folder that opens at a later stage is closed to a company below that stage, and nothing set inside it can reopen it.
- Before any room content, each request passes the room gate in order: membership not revoked, party not removed, room live, access window open, address on the IP allowlist, two-factor done, current NDA accepted.
- Rooms, folders and documents a person may not see answer as if they did not exist, so their existence is not confirmed.
- Your team can preview a room exactly as a company sees it. Previews are recorded and never count as that company's activity.
Companies kept apart
- A guest never receives another company's name, people, questions, NDA status, analytics or notifications.
- Guest responses leave out internal notes, assignees, draft answers, audit and analytics data, and the names of your team members who uploaded documents.
- When a room has a codename, guests see only the codename: in page titles, emails, notifications, watermarks and download file names.
Accounts and sessions
- Passwords are hashed with scrypt, need at least 12 characters, and common passwords are refused.
- A wrong email and a wrong password give the same message, and both take the same work, so sign-in does not reveal which accounts exist.
- Sessions live in a random token in a cookie that scripts cannot read (httpOnly, SameSite=Lax, Secure over HTTPS). Only a hash of the token is stored.
- Team sessions end after 24 hours idle or 7 days. Guest sessions end after 12 hours, or sooner by the room's idle timeout, 60 minutes by default. Background polling does not keep a session alive.
- Signing out ends the session on the server. Changing a password ends every other session of that person.
- Recovery cannot be used to take over a stronger account: only an owner can reset another owner, and resetting a team account takes the admin's own password too.
Two-factor and single sign-on
- Two-factor uses authenticator app codes. A code works only once, also across restarts, and ten single-use recovery codes are stored as hashes.
- Five wrong codes within 15 minutes lock two-factor for that account for 15 minutes.
- A room or a company can require two-factor for its guests; it applies at their next request. The server can require two-factor for the whole team.
- Your team can sign in through any OpenID Connect provider, with PKCE, a single-use state bound to the browser, a verified email and an allowed domain. Guests never sign in through the provider, and each team account stays bound to one identity at the provider.
Watermarks and downloads
- Watermarks are stamped on the server: the reader's name, email, IP address and the time on every page, and on downloads a footer naming who downloaded it, from which room and when.
- Guests below “download original” never receive an unstamped copy. PDFs, Office files and PNG or JPEG images are stamped before they leave the server; GIF, WebP and SVG reach them only as a stamped PDF.
- Every download is checked on the server against the reader's level, and every view, download and refused download is recorded.
- “No print” removes printing from the viewer and blanks the page in the browser's print output.
Files
- Uploads are checked against a list of allowed types and against their file signature, so an HTML file renamed to .pdf is refused, and there is a size limit.
- Every file is hashed with SHA-256 as it is stored. The hash is shown to readers and checked again on demand and in every closing archive.
- Storage locations are made by the server and never leave it. Files are served with their stored type, never as a web page, and with headers that stop browsers from guessing or running them.
- PDFs are drawn in the browser by pdf.js; scripts inside a PDF do not run. SVG is never placed inline in a page.
- Office files are converted to PDF by LibreOffice with its network access removed where the server allows it, external links and fields stripped, macros off, a fresh profile and a 60 second limit.
Share links
- A link opens one document or one folder of a live room, and nothing else.
- Passcodes are hashed. Five wrong passcodes from one address in 15 minutes are refused for a while, and 50 in an hour lock the link and tell its creator.
- An email allow list is checked only after the passcode, so outsiders cannot probe it. Before the passcode, a link shows neither its name nor the NDA text.
- A visit lasts at most 12 hours and stops as soon as the link is disabled or expires. Every visit, view and download is recorded.
The record
- Security-relevant actions, from sign-ins to views, downloads, permission changes and NDA acceptances, are written to a hash-chained activity log: one per room, and one for the workspace.
- Each entry stores the SHA-256 of the entry before it. The database refuses to change or delete entries, and “Verify chain” names the first entry that was altered, removed, inserted or moved.
- The CSV export and each closing archive carry every hash and the result of a verification. Keep the last hash outside the system: if the log were ever rebuilt, it would no longer match.
Web protections
- A strict content security policy: no inline script, no framing of the app by other sites, no plugins.
- Every request that changes something must carry a header that other sites cannot send, and requests that record a view refuse to come from other sites.
- Headers that stop content sniffing, send no referrer, isolate the window and, over HTTPS, keep browsers on HTTPS.
- Rate limits on sign-in, two-factor, invitations, password resets, share link unlocks and single sign-on.
- The address used for allowlists, rate limits, watermarks and the record is taken only from the proxy you trust, so it cannot be forged by the visitor.
Outgoing email settings
- Owners and admins set up the mail server in the app. The password is stored encrypted (AES-256-GCM) and never shown again, not even to owners.
- Changing the mail server, port or user name requires the password again, so a stored password is never sent to another server.
- The server connects only to public mail hosts on mail ports, with certificate checks on. Test emails go only to the signed-in admin, and every change is in the record, without the values.
AI assist
- Off unless it is turned on. Suggested answers are drafted only from documents the asking company may see, cite only those, are labeled as drafts and reach a guest only when a team member releases them.
- Every AI call is recorded in the activity log. When AI assist is on, the text of the documents involved is sent to the AI provider.
What it does not protect against
These limits are part of the design. Knowing them helps you decide what to put in a room and how.
- Screens and cameras. Watermarks and “no download” deter and trace leaks; they cannot stop screenshots, photos or retyping.
- What reaches the browser can be kept. A view-only reader's browser still receives the stamped pages to show them, and the watermark stays in them.
- Text, Markdown, CSV, JSON and log files are shown as text with the watermark laid over them, so their text can be copied. Put sensitive tables in PDF.
- Share link visitors type their email, and nobody verifies it. Allow lists limit what can be typed, not who types it.
- The record detects edits; it does not prevent them. Someone who owns the database could rebuild the whole chain consistently, which only a last hash kept outside the system reveals.
- Files are not encrypted by the application itself, and uploads are type-checked but not scanned for malware. On your own server, use encrypted disks and storage.
- Two-factor is optional for your team unless you require it.
- Single sign-on trusts your identity provider: whoever controls it can sign in as your team.
Certifications and hosting
- Zizora holds no security certifications today: no SOC 2 report and no ISO 27001 certificate. The controls on this page are described from the code, its security review and its tests, not from an outside audit.
- Where the hosted service runs will be published before it opens. With Enterprise you choose: your own server, or a dedicated server run for you.
Report a vulnerability
Email security@zizora.com
- Include the steps to reproduce, the version, what an attacker gains and any proof of concept.
- Do not test against rooms that hold real deal documents, and do not open a public issue.
- Give us time to fix the problem and deploy the fix before you disclose anything.
For anything else about security, such as a questionnaire, write to sales@zizora.com or use the contact form.