Confidential Workspace Addendum

This addendum applies when you start or use a confidential workspace on the Clairwave web platform. It adds to the Terms of Use, which still apply. Where this addendum and the Terms of Use differ, this addendum governs the workspace. Where your organisation has a signed licence agreement with Clairwave, that agreement prevails over both. You accept this addendum in the app before your first workspace; if we change it, we ask you to accept the new version before your next one.

1. What a confidential workspace is

A confidential workspace is a private, short-lived copy of Clairwave that runs only for your account, for the time you choose (up to 8 hours), in the location you choose from those offered to your account:

• Clairwave's servers, Canada: in its own isolated container on Clairwave's servers; or
• a cloud location (currently the Netherlands, Paris or Singapore): on a confidential virtual machine with Intel TDX memory encryption, which Clairwave creates for your workspace in Google Cloud and deletes when it ends (a "cloud workspace").

It opens in its own browser tab with a red globe. Inside it:

• simulations, results and the terrain you load are held in the workspace's memory only, are not written to our storage or databases, and are not included in backups;
• requests, positions and results inside the workspace are not written to our access or activity logs;
• the workspace makes no calls to third-party map, weather, forecast or vessel-tracking services, so features that depend on them (live AIS, satellite imagery, ocean forecasts) are not available;
• when the workspace ends — at its end time, when you press End now or End, or if it stops — the container, or for a cloud workspace the virtual machine, its disk and its internet name, and everything in them are deleted and cannot be recovered by you or by us.

2. Who can use it

Confidential workspaces are enabled by Clairwave for individual accounts; they are not part of any public plan. We may enable or withdraw access for an account at our discretion. A workspace can be opened only by the account that started it, on a desktop or laptop computer; mobile phones and tablets are not supported. A cloud workspace also accepts connections only from the internet address (IPv4) from which it was launched.

Accounts with confidential workspaces must use a second sign-in factor: a passkey (for example Windows Hello, Touch ID, your phone or a security key) or a code from an authenticator app. Set one up in your account's sign-in settings before we enable access. We ask for it each time you sign in, and again before you start or open a workspace if you last confirmed it more than 8 hours ago.

3. Your responsibilities

• Download anything you need before the workspace ends. We cannot restore a workspace or its results.
• The one-time link for opening a workspace in a private (incognito) window is for your own use on your own computer. Do not send it to anyone; it works once, for 2 minutes.
• Keep the device that holds your passkey or authenticator app to yourself. If you lose it, contact us: we confirm it is you before resetting it, and you are e-mailed when it is reset or when a passkey or code app is added to or removed from your account.
• Keep the computer and browser you use secure. Confidentiality on our side does not protect data you download, screenshots, or a device that others can use.
• The acceptable-use rules, usage limits and export-control provisions of the Terms of Use (sections 3, 4 and 8) apply inside the workspace. Choosing a cloud location decides only where the workspace runs; it does not change those provisions or your own export-control obligations.
• If you rely on the hardware attestation of a cloud workspace, have it checked independently with the verifier published at www.clairwave.com/workspace-verify/. The "attested" indicator inside the workspace is a convenience, not proof.

4. What we keep

To run the service, prevent abuse and meet legal obligations we keep a small record for each workspace: the account that started it, its identifier, the location chosen, when it started and ended, the duration chosen, and when a one-time private-window link was created or used. We also record which version of this addendum you accepted and when, and keep an audit record of any attempt to get into or change the workspace through our cluster's management interface (who, what, when and the result — never what is inside). These records contain no positions, simulation inputs or results, and are kept for 12 months, like other activity logs. Your visit to the main Clairwave site, including starting and ending a workspace, is logged as described in section 9 of the Terms of Use. For a cloud workspace, Google Cloud also records, in Clairwave's Google Cloud project, that the virtual machine was created and deleted, with its location, network addresses (including yours) and launch settings, but no simulation inputs or results; and its certificate, which shows only a random name and a time, is listed in public Certificate Transparency logs.

5. Limits of confidentiality

• Workspaces on Clairwave's servers run in Canada. Traffic between your browser and the workspace is encrypted and passes through our network provider (Cloudflare), as for the rest of the platform.
• Cloud workspaces run outside Canada, on Google Cloud, which acts as our hosting provider. Your browser connects directly to the workspace machine, with encryption that ends inside it; Cloudflare and Clairwave's servers are not on that path. Launching the workspace and the one-time ticket that opens it go through the main Clairwave site as usual. The machine's memory is encrypted by the processor (Intel TDX), and the processor signs a report of what the machine booted, which Clairwave checks before the workspace starts and you can check independently. This protection depends on Intel's hardware and keys and on Google's virtual-machine firmware, and has the limits stated in Clairwave's Data Handling Statement (section 7), including checks the verifier does not yet perform. Attestation shows which published image runs; it is not a warranty that the image is free of faults.
• Clairwave staff do not access a running workspace. A cloud workspace has no remote login, console login or management agent; Clairwave can delete it but cannot open it. For workspaces on Clairwave's servers, opening a shell in it, attaching to it, forwarding its ports, adding a debugging container to it or changing it are blocked, for administrators too, and so is reaching the service that issues the keys that open workspaces. The only exception is emergency access, to protect the service or where the law requires it, through a deliberate override. Every such access through our cluster's management interface is recorded in an audit log, and the account holder is e-mailed automatically, unless the law prevents it. You are also e-mailed automatically when that key service or our web server's access rules for workspaces are changed while your workspace runs, and when an administrator signs in as you or changes your account's sign-in details.
• For workspaces on Clairwave's servers, someone with full control of the underlying servers or of our sign-in service could bypass these controls without such a notice. Cloud workspaces use confidential-computing hardware so that the host cannot read their memory, but who may open them is still decided by Clairwave's sign-in service and workspace controller; changes made to a cloud workspace machine through Google's management interface are not yet notified to you.
• A confidential workspace is an engineering safeguard, not a security certification. It is not approved for classified or government-protected information unless a signed agreement with Clairwave says so.

6. Availability

The number of workspaces that can run at the same time is limited, so a workspace may not be available on demand. We may end a workspace early for maintenance, security or abuse; where we can, we warn you first. Results lost when a workspace ends are not compensated. A cloud workspace takes about 1–2 minutes to start and may have to wait for capacity at Google Cloud; Google deletes the machine shortly after the chosen end time even if Clairwave's systems are unavailable. Section 7 (Liability) of the Terms of Use applies.

7. Contact

Clairwave Inc., Halifax, Nova Scotia, Canada · [email protected]