Skip to main content

SOC 2 Type I

Sail is SOC 2 Type I compliant. You can request the independent auditor report through our Trust Center.

SOC 2 Type II

Sail’s SOC 2 Type II compliance takes effect August 25, 2026.

HIPAA and BAAs

Enterprise customers can sign a business associate agreement (BAA) with Sail for HIPAA-regulated workloads.

Master services agreements

Enterprise contracts can include a signed master services agreement (MSA).

Data processing

Retention depends on the Sail product and the data involved. The inference retention policy below does not apply to Sailbox state and checkpoints, files you upload through the Files API, or security and audit records.

Inference

Zero Data Retention (ZDR) by default

All inference prompts and outputs are processed only ephemerally in memory, for the minimum duration necessary to fulfill each request and return its output.
  • We use inference request and response data only to provide the services you request and follow your documented instructions.
  • We do not use inference request or response data to train, fine-tune, or improve models without your written consent.
  • We do not sell or share customer personal data from inference requests or responses.
  • Sail and its subprocessors do not persistently store inference prompts or outputs or retain them beyond that duration.
  • ZDR does not cover files you upload through the Files API (POST /v1/files), including LoRA adapter weights, images, and videos. Sail stores each uploaded file for your organization.
  • Our public DPA forms part of the self-service terms and written customer agreements.
Read our Data Processing Agreement for the complete terms.

Sailboxes

Sailboxes are stateful by design:
  • A Sailbox’s writable disk persists for the life of the Sailbox, including across pause, sleep, resume, migration, and recovery.
  • Temporary data used to migrate a Sailbox is retained for no more than 24 hours.
  • An explicit checkpoint handle expires after seven days by default, or after the TTL set when the checkpoint is created. Expiry controls how long the handle can start a new Sailbox. It does not set a deletion deadline for data still used by a Sailbox.
See Sailbox lifecycle for checkpoint, pause, sleep, resume, and termination behavior.

Data residency and regional processing

By default, Sail uses service providers in multiple regions, so customer data may be processed or stored outside the United States. Pro and Enterprise customers can use US-only inference. Contact support to discuss other processing or storage requirements for your workload.

Signed DPAs

Enterprise customers can sign a DPA with Sail. Self-service customers are covered by our public Data Processing Agreement.

Security controls

Our published controls include:
  • Encryption of customer data at rest and in transit
  • Multi-factor authentication for critical services and regular employee access reviews
  • Automated infrastructure security scanning and vulnerability management
  • Audit logging, monitoring, and an incident response process
  • Tested business continuity and disaster recovery plans

Trust Center

Visit Sail’s Trust Center to review our security controls, request compliance documents, and see our current subprocessors.

Report abuse

Each HTTP service published from a Sailbox gets its own address under sail.box, and the customer who owns that Sailbox controls what it serves. To report phishing, malware, or other abuse at one of these addresses, email support@sailresearch.com with:
  • the full address, such as https://sb-9c8f1e2a-3b4d-4f5a-8c7e-1d2f3a4b5c6d-8000.sail.box/login
  • what the page does
  • when you saw it

Support

Contact support@sailresearch.com with any questions.