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.

Sealroom AI Use Notice and Acceptance

Version 1.3 (final) Effective date: 12 October 2026

Summary

1. Nature and limitations of AI output

1.1 Generated output

Reports, answers, briefs, findings, drafts and other Customer Results may be generated or assisted by AI models.

Customer Results may contain:

An AI model may also:

1.2 Verification

Users must verify material Customer Results against the source materials before relying on them.

Citations and page references assist verification but do not guarantee that:

1.3 Professional responsibility

Customer Results are generated analytical materials and do not by themselves constitute legal, financial, investment, tax, regulatory or medical advice from BSUM.

Customer Results:

1.4 Decisions concerning individuals

Customer Results must not be used as the sole basis for a decision based solely on automated processing that produces legal effects concerning an identifiable person or similarly significantly affects that person, except where:

Where a Customer Result informs a decision concerning an identifiable person, the Customer must:

1.5 Human responsibility

The Customer and its Users remain responsible for:

1.6 Regulated life-science use

Unless expressly agreed in an Order, Sealroom and Customer Results:

Use in a regulated workflow does not by itself make Sealroom validated or compliant for that workflow.

1.7 Scientific and technical limitations

Customer Results may not identify all:

Users must apply suitably qualified subject-matter review appropriate to the Permitted Purpose.

1.8 Warranty and liability

BSUM does not warrant that Customer Results will be accurate, complete, current, error-free or suitable for a particular decision.

BSUM’s warranties and liability are governed by the Terms.

2. Room-specific AI configuration

2.1 Required approvals

Before Transaction Information or other protected Customer Content is submitted to a model, the configuration must be approved by each Customer or Room side whose approval is required under:

The Security Specification identifies the required approvers for each processing mode.

2.2 Security Specification

The Security Specification records the approved configuration and identifies, where relevant:

The Security Specification does not disclose protected prompts or other Platform Information merely because it records their fingerprint or identifier.

2.3 Changes

A material change to an approved configuration requires new approval before the changed configuration is used for protected Customer Content.

A change is material where it may reasonably affect:

A change to any of the following may be material even where the commercial model name remains unchanged:

New approval is not required for routine maintenance that does not materially change the approved configuration or risk profile.

2.4 Side-specific settings

AI settings that affect only one side’s private work may be separately identified in the Security Specification.

Examples include:

Approval of one side’s private output does not grant the other side access to that output.

2.5 Processing outside the Room

Where an approved model runs outside the Room’s confidential-computing boundary, the information required for the request is transmitted to the endpoint identified in the Security Specification and processed under the applicable provider terms and configuration.

The Security Specification identifies:

BSUM does not represent that a provider performs zero retention, zero logging or zero human review unless that conclusion has been verified against the applicable technical configuration and contractual terms.

Where BSUM selects or contracts with the provider, BSUM remains responsible for complying with its obligations concerning that provider under the Terms and applicable data-processing arrangements.

Where the Customer selects and controls the provider through its own account, the allocation of responsibilities is identified in the Security Specification.

3. Training, retention and operational data

3.1 No model training by BSUM

BSUM does not use Customer Content, Transaction Information, Customer Results or the substance of User questions to train or fine-tune a general-purpose or customer-facing AI model unless the Customer has separately and expressly instructed that use in writing.

Where BSUM selects the model provider, BSUM will use the available contractual and technical configuration intended to prevent the provider from using that information to train or fine-tune general-purpose foundation models.

Any provider-side retention, human review, abuse monitoring or service-improvement processing that cannot be disabled must be disclosed in the Security Specification before approval.

For models BSUM provides on Microsoft Azure, Microsoft's abuse monitoring for Azure AI services applies under Microsoft's terms unless Microsoft has approved an exemption for BSUM's deployment; the Security Specification states which applies to the Room's model. Models processed outside the EU/EEA (Claude models provided by BSUM are processed in the United States) are marked as such in the Security Specification and are used only after both sides approve it.

3.2 Operational telemetry and statistics

BSUM may use content-free telemetry and operational statistics to:

Such telemetry and statistics must not contain:

Where operational statistics remain personal data, BSUM processes them in accordance with its privacy notice and applicable law.

BSUM may use Feedback as permitted by the Terms.

3.3 Customer-controlled model accounts

A Customer that chooses to use a model through its own provider account is responsible for that account’s:

The Security Specification identifies:

BSUM does not guarantee settings that it cannot control or verify.

4. Customer Results and Platform Information

4.1 Customer Results

Section 10 of the Terms governs Customer Results.

The Customer may use Customer Results as permitted by:

No rights are transferred in Transaction Information, third-party material or Platform Information merely because that information is contained in or reflected by a Customer Result.

4.2 Protected Platform Information

The following non-public elements implemented or supplied by BSUM are Platform Information:

Ordinary report headings, commonly used due-diligence categories and Customer Results delivered to the Customer are not Platform Information merely because Sealroom generated them.

Receipt of a Customer Result does not grant access to or rights in the underlying:

4.3 Protection against extraction

Users must not attempt to extract, reveal, copy, reconstruct or systematically derive BSUM-provided prompts, system instructions or other Platform Information.

Users must not:

4.4 Competitive use

The Customer and its Users must not use:

to train, reverse engineer, benchmark for product development, develop or improve a product or service competing with Sealroom.

This restriction does not prevent the Customer from internally evaluating the quality and suitability of Customer Results for its own Permitted Purpose, provided that the Customer does not:

The independent-development and mandatory-law provisions in the Terms apply.

4.5 Unexpected protected output

BSUM does not guarantee that an AI model will never generate content that resembles a protected instruction, system message or other Platform Information.

A User who encounters or suspects such output must:

4.6 Unauthorised information disclosure

A User who suspects that a model has revealed:

must stop further attempts, avoid further use or disclosure and notify the Customer administrator and BSUM without undue delay.

5. General provisions

5.1 Permitted Purpose

Permitted Purpose has the meaning given in the Terms and is identified for each Room in the applicable Order or Security Specification.

5.2 Rooms without a Transaction NDA

Where no Transaction NDA applies, references in this notice to rights or restrictions under a Transaction NDA do not apply.

Access and use remain subject to the Terms, applicable Order, Permitted Purpose, Security Specification, applicable law and valid Room-specific confidentiality and use conditions.

5.3 No waiver through visibility

Observation of a feature, workflow, output format, analytical structure or system behaviour through authorised access does not:

5.4 No residuals right

No residuals right or licence is granted.

Retention of Platform Information in unaided memory does not authorise its use or disclosure in breach of the Terms, the Room Rules or this notice.

This does not restrict general professional knowledge, experience and skills that do not disclose, reproduce or materially incorporate Platform Information.

5.5 Mandatory law

Nothing in this notice excludes or restricts an activity or right that cannot lawfully be excluded or restricted by agreement.

Information obtained through such an activity may be used only within the scope and for the purpose permitted by applicable mandatory law.

5.6 Order of precedence

The documents apply as follows:

The Security Specification does not override or reduce the platform-protection, confidentiality, acceptable-use or intellectual-property restrictions in the Terms, the Room Rules or this notice.

5.7 Survival

The provisions concerning:

survive termination or loss of access to the extent stated in the Terms or required by their nature.

6. Acceptance

6.1 Separate acceptance

Each User accepts this notice electronically and separately from the Terms and the Platform and Room Use Rules, as described in section 15 of the Terms.

6.2 Acceptance record

The acceptance record identifies:

6.3 Applicable terms

Finnish law and the dispute provisions in the Terms apply.

The English text prevails over any translation.