Data handling
Unbiased Data Policy
This page explains the Pareto-specific practices that sit alongside the Circuit & Chisel, Inc. Privacy Policy and Terms.
What the service processes
- API credentials. Today's public checkout does not require a third-party provider key. If a separate comparison evaluation does, the key-handling terms and controls will be disclosed before it is provided.
- API call content. Prompts and Pareto responses pass through Circuit & Chisel infrastructure to operate the guided evaluation.
- Comparison workflows. If separately agreed during onboarding, prompts and responses may be evaluated against another model under disclosed handling terms.
- Comparison data. Quality scores, workload classifications, model identifiers, cost metadata, and other derived evaluation data may be retained to produce an agreed evaluation report and improve the service.
- Usage metadata. Timestamps, model identifiers, token counts, latency, workload class, and cost may be collected for service operation, billing, and reporting.
- Account and payment information. Circuit & Chisel uses account information to provision access. Stripe processes payment information; Circuit & Chisel does not store raw card data.
How data is used
- Operate Pareto access, agreed evaluation workflows, reporting, billing, and account provisioning.
- Use derived quality and workload data to improve comparisons and the service.
- Comply with applicable law and valid legal process.
What we do not do
- We do not sell member data.
- We do not use member call content for advertising.
- We do not train Pareto on raw member prompts or responses without explicit member consent.
- We do not share member data except with service providers needed to operate the service or as required by law.
Access and security
Do not send provider credentials through the public contact form. Before any evaluation requires a customer API credential, the applicable storage, access, logging, deletion, and support-access controls will be disclosed in writing. Site and API traffic is protected in transit using TLS.
Retention
API credentials are retained while needed to provide the service and are scheduled for deletion after access ends. Usage, billing, and derived comparison records may be retained for reporting, legal, accounting, and service-improvement purposes.
The retention window for raw prompts and responses is not yet published because the technical architecture and customer agreement are still being finalized. A member-specific retention commitment will be disclosed before applicable onboarding.
Member choices
Members may request access to account and usage data, request deletion of eligible personal data, withdraw a prior training opt-in prospectively, or request a machine-readable export of available usage and reporting data.
Questions
Send data questions or requests to info@unbiased.ai.