Intralinks trains people to run VDRPro. Sifrsys expects nobody to be trained.

Every data room with AI now returns text. The question a buyer's counsel asks next is where the number came from, and the answer to that is not a feature bullet. It is a property of what the assistant hands back.

The same distinction applies to permissions. Sifrsys filters retrieval inside the SQL query using tenant_id and participant_can_access_document, so restricted rows are never fetched. That exclusion is structural rather than empirical: CI reads the deployed function out of pg_proc.prosrc and fails the build if either predicate is missing, and a denial suite calls the function from the published anonymous key and counts only SQLSTATE 42501 as a pass. What we have measured is the failure that prompted the lockdown: before July 2026 an unrelated signed-in user retrieved 30 chunks across 13 documents of verbatim deal text, because the caller controlled the participant identifier the filter was checking. Intralinks does not publish where its retrieval filter runs, which makes it a question for the security review rather than a row you can fill in from a website.

Finish the deal you are on. Rooms are per transaction and moving one mid-process costs more than it saves. For the next deal, export the folder tree and the originals, upload them, and the parser indexes PDF, DOCX, XLSX, and PPTX on arrival. The work that takes judgement is the permission map, because a room configured by someone with VDRPro certification usually encodes conventions nobody wrote down. Walk the folder tree with whoever built it before you rebuild it. For the first ten paying companies Sifrsys does that mapping at no charge and locks the signup price for the life of the subscription.