Controlled-Pilot Privacy Notice

Controlled-Pilot Scope

This notice describes how Singular, a Mattom product, handles information during a controlled pilot. It is a factual product boundary, not a representation that Singular holds a certification or satisfies every law for every customer or jurisdiction. The executed pilot proposal and any signed data agreement define the customer-specific scope.

Information We Process

Singular processes the information required to operate the pilot:

• account and membership records supplied through the configured identity provider;
• the prompt and marked context needed to serve an eligible request;
• the provider response returned for that request; and
• privacy-safe operational metadata such as request identifiers, model route, token

counts, S-Core decision and reason, latency, cost estimates, release, and profile.

• first-party funnel events for a landing visit or documentation view, containing the

event type, UTC time bucket, source, coarse campaign slugs, and an unlinkable short-lived session fingerprint.

The customer decides which eligible workload and provider to use and must have the right to send that content.

What Singular Persists

Raw prompts, marked context, and raw provider responses are processed in memory and are not persisted by Singular by default. Singular does not use that raw content to train models.

Singular persists account and membership records, encrypted provider credentials, hashed Singular API key secrets, privacy-safe request metadata, evaluation summaries, and activation or rollback records needed to operate and review the pilot. Customer visible logs do not contain credential plaintext or raw request content.

Funnel measurement never stores an IP address, user-agent, arbitrary path, form values, or contact data. The random browser identifier exists only in session storage; Singular stores its non-reversible HMAC fingerprint for daily event deduplication.

Retention And Deletion

Metadata retention, access review, deletion timing, and any backup-removal expectation are recorded for each pilot before traffic is enabled. Singular does not publish a single default period that overrides the executed agreement. A pilot remains blocked when a required schedule or owner is missing.

Verified access, correction, or deletion requests can be sent to privacy@mattom.io. Mattom confirms identity and scope, then handles the request under the applicable pilot agreement and law. When a pilot ends, the parties record whether the workspace is retained for evaluation, deprovisioned, or subject to an agreed deletion handoff.

Provider Processing

Singular sends the request selected for delivery to the provider configured by the customer. Provider-side processing, retention, and model policies are governed by the customer's agreement with that provider, not by Singular's non-persistence default. Customers should qualify those terms before activation.

Infrastructure and identity services necessarily process the account or operational data needed to provide their part of the service. The pilot proposal records the approved environment and any customer-specific vendor requirement.

Your Requests

To request access, correction, deletion, or a copy of the pilot's applicable handling terms, email privacy@mattom.io from an address associated with the pilot. Do not send prompts, provider responses, API keys, or other secrets in the request. Include only the workspace, safe request identifier, and relevant date range.

Contact

• Privacy and data requests: privacy@mattom.io
• Pilot operations: support@mattom.dev
• Security incidents or vulnerabilities: security@mattom.io