Security & privacy in Omnis Helix.

A research pilot starts with a pinned software candidate and an agreed evaluation environment. Confirm these details before sharing project data.

Evaluation environment

Start with synthetic inputs in a customer-controlled environment. Review the selected build, configuration, integrations, and diagnostic settings before introducing project data.

Agree what information may be shared with support before sending a diagnostic bundle.

Offline verification

Evidence bundles can be checked offline with the required verifier and dependencies. Confirm that the selected workflow and model assets are available locally before planning a disconnected evaluation.

Offline verification does not establish that every workflow or integration runs without network access.

Build integrity

Request the pinned build identifier, checksums, dependency inventory, and verification instructions for your pilot candidate. Platform signing and notarization status must be checked for that specific artifact.

Unsigned evaluation candidates must be identified explicitly; a checksum alone does not authenticate the publisher.

Pilot data handling

Before transferring project data, agree the recipient, access controls, storage location, retention, deletion, and permitted use in the pilot terms. Keep sequence datasets and confidential details out of the intake form.

The intake form collects contact and qualification information. Storage and handling commitments depend on the agreed deployment and terms.