Controlled-Pilot Terms
Pilot Scope
These terms describe the minimum operating boundary for a Singular controlled pilot. They do not replace an executed pilot proposal, order form, DPA, NDA, or other signed agreement. If this page conflicts with a signed agreement, the signed agreement governs. No production expansion is authorized solely because a pilot succeeds.
Supported Service Boundary
Singular is a context-optimization layer that can reduce marked context before an LLM provider call. The current pilot contract is text-only, OpenAI-compatible chat completion, non-streaming, and one completion per request. The pilot proposal names the qualified workload, route, model, S-Core release, profile, thresholds, and traffic slice.
If optimization cannot safely proceed, an eligible supported request may use its original form. Unsupported or unsafe request contracts fail with an error, and a provider failure remains a provider failure. A provider request already dispatched cannot be recalled.
Customer Responsibilities
The customer must protect its credentials, control access to its workspace, have the right to process the submitted content, qualify its chosen provider, maintain an original-request baseline, and name an approver and rollback contact. Both parties must keep customer content and secrets out of support tickets and shared evidence.
Use is limited to the agreed workload and lawful purpose. A change in workload, data classification, route, model, environment, or retention boundary requires renewed review before optimized traffic resumes.
Data And Provider Boundary
Raw prompts, marked context, and raw provider responses are processed in memory and are not persisted by Singular by default. Privacy-safe metadata, evaluation summaries, and activation records may be retained under the pilot's agreed schedule. Provider processing and retention are governed by the customer's provider agreement.
See the privacy notice and security overview for the factual product boundary.
Fees And Duration
Pilot duration, traffic ceiling, fees, taxes, payment handling, and any extension are defined only in an executed pilot proposal or order form. This page does not publish a public price, discount, or outcome guarantee.
Suspension And Exit
Either party may request containment or stop the pilot under the executed agreement. Singular may suspend optimized traffic when a privacy, security, quality, provider, evidence, or operational gate is unsafe. Reactivation is never silent: it requires current evidence and the recorded approvals defined for the pilot.
At exit, the parties record the decision, revoke or rotate access as agreed, and complete the applicable retention or deletion handoff. Warranty, liability, indemnity, governing law, and dispute terms—when required—belong in a document reviewed and signed by authorized representatives.
DPA And NDA Path
Requests for a DPA, NDA, security questionnaire, or contract review begin at sales@mattom.io and are coordinated with legal@mattom.io. Any document required for the approved workload must be executed and recorded before pilot traffic is enabled.
Contact
- Pilot and commercial intake: sales@mattom.io
- Legal review: legal@mattom.io
- Privacy requests: privacy@mattom.io
- Security incidents: security@mattom.io