Where is deal data stored and processed?

Deal data is encrypted at rest and in transit and isolated per organisation by row-level security in the database. Document processing is transient and keeps nothing, and your content is never used to train AI models. The Trust Center lists every subprocessor and where it operates, alongside the Data Processing Agreement.

What compliance work is in place?

SOC 2 Type II readiness: the controls are built and mapped, and the roadmap is available on request. A Data Processing Agreement with Standard Contractual Clauses is available for your vendor review, alongside a completed security questionnaire and the subprocessor list.

How should we assess Sifrsys against the Saudi PDPL or a GCC data protection regime?

With your counsel, using the facts on this page and the Trust Center: how data is protected, which subprocessors touch it, what is logged, and the DPA we provide. This page is a factual account of what the software does. It is not legal advice.

Are AI conversations stored?

Yes, in your room, on purpose. Chat history persists in your room, which is what makes the record complete and what makes an audit trail worth having. What our Trust Center states about the providers is separate: content is not retained by our AI providers and is never used to train models.

Can an AI answer leak a document a participant cannot open?

The retrieval filter runs inside the SQL query, on tenant id and a per-participant document access function, so a chunk the participant cannot open is never returned to the model in the first place. The participant identifier the filter checks is derived on the server from the session, never taken from the request. A permission rule written into a prompt is not a control, because a model can be argued out of it.

What can we get for a security review?

The subprocessor list is public on our Trust Center. The audit log exports from your own room, so you can verify the record rather than take our description of it. The permission behaviour above is one you can check inside a room you control. A Data Processing Agreement, a completed security questionnaire and our security whitepaper are available on request.

GCC Data Residency and Compliance for Data Rooms

How deal data is protected

Deal content is encrypted at rest and in transit, and each organisation's data is isolated by row-level security in the database rather than by application code alone. Document processing is transient and keeps nothing once a file is indexed. Our Trust Center lists every subprocessor and where it operates, and states that content is not retained by our AI providers and is never used to train models. We give advance notice of material changes to that list.

What happens to a document

Upload
TLS 1.3 in transit, into a private bucket
Process
Parsed and chunked, transient, not stored at rest
Index
Embeddings stored with the room, isolated per organisation
View
Server-resolved permission, watermark burned in, view written to the log

The path a document takes.

Encryption is AES-256 at rest and TLS 1.3 in transit. Buckets are private and never publicly readable, so a document URL is not a credential. Every view is written to a SHA-256 hash-chained audit log whose integrity is verified on a schedule, which means tampering with the record is detectable rather than merely discouraged. You can export that log from your own room, so the record is something you verify rather than something we describe.

The question behind the question

Gulf security reviews have started asking where the AI permission check sits, which is the right question, because the same rule is either a control or theatre depending on the layer it lives in.

In the system promptbypassable
Asking the model not to mention documents the user cannot see. A model can be argued out of an instruction.
In application code, after retrievalbypassable
The rows already left the database. A mistake in the calling code returns them.
Inside the SQL queryenforced
Filtered on tenant id and a per-participant document access function, so an unauthorised chunk is never read out.
Row-Level Security in the databaseenforced
Tenant isolation enforced below the application, so an application bug cannot cross the boundary.

Where a permission rule can sit for AI retrieval. Only the bottom two survive a bug in the layer above them.

In-query

A chunk outside the participant's permission is never selected, so no later code path can return it

Product architecture

Proving who saw what

A residency question is usually a proxy for a leak question. Watermarks are burned into the page image on the server before encoding, tiled across the page, carrying participant name, email, IP and timestamp. Two participants viewing the same page receive different bytes. Delete every overlay element in the browser and the identity is still in the pixels, because it was never an overlay. The worst of 64 sampled 25 percent crops retained 11.7 percent of the watermark ink with all four fields legible, and the mark survives JPEG quality 50 and a 50 percent downscale.

What is stored, and why

Chat history persists in your room. Some vendors say conversations are not stored. Ours are, on purpose, because a record with gaps in it is not an audit trail. What our Trust Center states separately is that content is not retained by our AI providers and is never used to train models.

The residency position, in short: every subprocessor and where it operates is published, everything that happens in a room is logged, and the audit log is yours to export and verify. The subprocessor list, and the documentation we share for a vendor review, are on our Trust Center.

Who this is right for

Cross-border processes where the counterparties are outside the region anyway. Fundraises, board portals and client portals where the constraint is confidentiality rather than jurisdiction. Deals where the documents are Arabic and Hijri-dated and no incumbent renders them properly, which is the problem the Saudi Arabia page measures, and the GCC page extends across the three-decimal dinars.

Plans are published and flat: Free, Pro at $29, Business at $79, Data Rooms at $149 with unlimited rooms, Plus at $349, Premium at $699, Unlimited at $1,499 a month, and Enterprise on a contract, with AI included rather than sold as an add-on and no per-page fees. The 14-day trial takes no credit card, so the cheapest way to test any of the above is to test it. See pricing, and /trust for the compliance table this page draws on.

Deal data, protected and verifiable.