The version that applies to you is the one you accept in the room. This copy is for information. "Sealroom" is the working name of the Haihtuva service.

Room Security and Processing Specification

Version 1.1 (final) Effective date: 6 October 2026

About this record

1. This is the Room-specific configuration record for one Sealroom Room. It is generated by the Room, approved by each side whose approval is required for the Room (in a Seller-Buyer Room: the Seller and the Buyer), and signed with the Room's key. It is the "Security Specification" referred to in the Sealroom Terms of Service (the "Terms").

2. It records the Room's Permitted Purpose and the technical choices approved for this Room, including: the AI model, its endpoint and region; the network destinations the Room may reach; the processing modes; the output rules; document classes (for example documents shared for viewing or for AI analysis only); recovery-save settings; storage connections; Seller-review and release settings; delivery settings for copies to the parties' own folders; and attestation and Room-key information.

3. It is a technical record, not a contract on its own. It does not replace the Terms, the Platform and Room Use Rules, the AI Use Notice or any Transaction NDA. It prevails over them only on the technical configuration of this Room.

4. The configuration is identified by a SHA-256 fingerprint of its machine-readable content. Each side's approval is recorded with that fingerprint, the approving User, organisation and time, and signed with the Room's Ed25519 key. The fingerprint and signatures identify the configuration that was accepted.

5. Any change to the approved configuration produces a new fingerprint and requires a new approval by each required side before it takes effect. Settings that a side may change alone without the other's approval (for example the Seller's own drafting model) are shown as such.

6. Statements in this record describe the configuration and the checks the Room performed when it was generated. They do not extend BSUM's obligations beyond those in the Terms.

Who sees what

To avoid exposing infrastructure details unnecessarily, the record is shown at three levels:

• All Users of the Room: the model name and type (inside the Room, hosted by BSUM, or under a party's own account), the region, the processing mode, the output and release rules, whether recovery saves and copies to own folders are on, document counts and classes, the pass or fail result of each attestation check, and the configuration fingerprint.
• Administrators of each side: in addition, the endpoint host and deployment, the permitted network destinations, the fingerprints of BSUM-provided instruction sets, the attestation evidence (processor and software measurements) and the Room-key fingerprint. Administrators may download the signed full record for evidence.
• BSUM only: infrastructure identifiers, key-release policy administration, deployment and security-test records. These are Platform Information and are disclosed to a party only where required by law or agreed for a specific dispute.

How processing works (summary)

• Documents stay in the Seller's storage. The Room reads each file on demand, read-only, into the encrypted memory of an Azure confidential virtual machine while it is viewed or analysed, and does not write documents to its disk.
• How the Room reaches the Seller's storage. Google Drive and Box: the Seller shares the folder as Viewer with the Room's own address; the provider limits the Room to that folder, and the Room refuses edit rights. Dropbox and Microsoft OneDrive or SharePoint: the Seller signs in and allows read-only access; these providers grant read access to all files the Seller can open, and the Room's software reads only the folder the Seller picks. In every case the Seller can end access at any time from their storage, the Room never writes to it, and closing the Room ends its access (Box: the Room removes itself; Google Drive: the Seller removes the Room's address).
• The Room key is released by Azure Key Vault under a release policy that requires Azure Attestation of a confidential virtual machine. The attestation checks listed in this record show which measurements were verified for this Room; protection extends to what those checks cover.
• Where the approved model runs inside the Room, analysis stays inside the Room. Where it runs outside the Room, the text needed for each request goes to the endpoint and region shown in this record, under that provider's terms.
• Room data other than documents (settings, Users, approvals, questions and answers, reports and audit trail) is held by the Room. If recovery saves are on, an encrypted copy of it, without documents, is written to the Room's own disk, readable only with the Room key, and deleted at close.
• Copies that a party saves to its own folders or downloads leave the Service and are that party's responsibility.
• At close the Room deletes its data, keys and any recovery copy, and sends both sides a signed destruction receipt. Content-free records listed in section 13.4 of the Terms are kept.

Watermarks

Protected pages show the User's name, organisation, date and time, the Room identifier and a unique access number. E-mail addresses and network addresses are not shown on pages; network addresses are kept only in the restricted security log.

What the Seller sees of Buyer activity

The Seller sees which of its documents each Buyer organisation has opened. The Seller does not see which person opened a document, which pages were viewed, time spent, the order of reading, Buyer questions, searches, notes, reports or other Buyer-private work, unless the Buyer shares them. Questions and document requests that a Buyer sends to the Seller are, by their nature, visible to the Seller. Each Buyer's administrators see their own team's access detail.

Records and retention

• Access and security logs: 12 months, or until the Room closes if earlier, except content-free records kept under section 13.4 of the Terms.
• Network addresses: 90 days.
• AI-use event logs (that a function was used, not the content): 12 months, or until the Room closes if earlier.
• Misuse alerts: 12 months.
• Acceptance evidence: 10 years after the Room closes.
• Records preserved for a suspected breach: until the matter is closed, then deleted or anonymised.

Contacts

BSUM's contact details, including the security and privacy contacts, are published at www.bsum.fi. At the effective date of this record: juhani.lahdenpera@bsum.fi, Biotech Start-Up Management Oy, Business ID 2574531-6, Vanhatie 70, 86100 Pyhäjoki, Finland.

The approved configuration

The machine-readable configuration, its fingerprint and the signed approvals follow this introduction in the Room's security summary and in the downloadable record.