Privacy Policy

Last updated: 2026-08-01

This policy describes what Pareta Inc. ("Pareta", "we") collects when you use the Pareta platform, why, how long we keep it, and who else processes it. We have tried to write it the way the system actually works, without vagueness. If anything here is unclear, ask us at support@pareta.ai.

1. What we collect and why

Account data

Email address, name, and a hash of your password (we never store the password itself), plus a record of which Terms of Service version you accepted and when. Used to operate your account. Kept for as long as your account exists.

API inputs and outputs

The requests you send — full prompts, including any documents or images in them — and the responses returned are stored for up to 30 days, then deleted automatically. This applies to API traffic and playground use. We keep them for two reasons:

There is currently no opt-out from this retention. If your use case requires zero retention, contact us before sending production traffic.

Benchmark and evaluation data

Datasets you upload for benchmarking (including documents) and the results of evaluation runs are stored until you delete them — they exist so you can re-run and compare over time. Deleting a dataset deletes its items, uploaded files, and run results.

Usage and billing metadata

Per-request metadata — timestamps, token counts, latency, status, cost, and the routing decisions taken — without prompt or response content. Kept indefinitely for billing integrity, audit, and service analytics. Your organization's audit log (logins, key creation, admin actions, and any staff access to stored request content) is likewise kept.

Support

If you contact support, we keep the correspondence.

Marketing site

Our public pages (pareta.ai) collect anonymous usage statistics — page views and button clicks, with the referring site's domain. No cookies, no advertising identifiers, and no third-party analytics: events go only to our own servers, and your IP address is not stored with them.

2. Where your requests are processed

Pareta routes each request to the model that serves it best. That means your inputs are processed by:

3. Subprocessors

ProviderPurposeSees request content?
Google CloudHosting, storage, databasesYes (infrastructure)
ModalGPU model servingYes (inference)
OpenAIFrontier serving + quality gradingYes (routed/sampled requests)
AnthropicQuality grading; frontier servingYes (routed/sampled requests)
Google AI (Gemini)Quality grading; evaluation runsYes (routed/sampled requests)
StripePaymentsNo (billing data only)
ResendTransactional emailNo (email address only)
CloudflareBot protection on signupNo
Pydantic LogfireOperational telemetryNo (metadata only — no prompt content)
SlackSupport channels (opted-in orgs)No (what you post there)

4. What we don't do

5. Security

Traffic is encrypted in transit (TLS). Passwords are stored hashed; API keys are stored as hashes and shown to you exactly once. Access to stored request content by Pareta staff is restricted and recorded in your organization's audit log. No system is perfectly secure; report suspected vulnerabilities to support@pareta.ai.

6. Your rights and choices

Depending on where you live, you may have additional statutory rights (for example under GDPR or CCPA); we honor requests to the extent the law requires. Contact support@pareta.ai.

7. Data location

Pareta operates primarily from the United States (us-central1). If you use the Service from elsewhere, your data is transferred to and processed in the US.

8. Children

The Service is not directed to children and may not be used by anyone under 18.

9. Changes

We will update this policy as the system evolves and note the date above. For material changes we will notify you before they take effect.

Contact

Pareta Inc. · support@pareta.ai