Skip to content
Decision Cloud

Privacy Policy

This policy explains what Decision Cloud handles to provide accounts, prepaid credits, and CSV evaluations, and how operational records are removed.

Last updated September 25, 2026

Information Decision Cloud handles

  • Account information. Auth0 authenticates your account. Decision Cloud stores an internal account ID linked to the Auth0 issuer and subject, and may store your email address and verification status.
  • Billing information. Stripe processes checkout. Decision Cloud stores Stripe customer, checkout-session and payment-intent IDs, the hosted checkout URL, purchase amount, $1 service fee, currency, payment status and timestamps, webhook event IDs, credit balance, and credit-ledger entries. Its purchase records also contain the success and cancel return URLs. Stripe customer metadata includes the internal Decision Cloud user ID. Checkout and payment metadata include internal user and purchase IDs and the credit amount, fee, and total. Decision Cloud does not store card numbers or security codes. Webhook payloads are checked in request memory; the database stores event identifiers and limited payment metadata, not the full payload.
  • CSV and evaluation input. During an evaluation, Decision Cloud downloads and parses the CSV for that request. The file, its URL, question and context text, and model answers are not written to Decision Cloud's PostgreSQL account, billing, or job tables.
  • Job and usage information. PostgreSQL stores the account ID, model, job status and timestamps, record and judgment counts, batch and attempt status, token counts, computed usage cost, safe error codes and categories, provider request IDs, and credit reconciliation status. It does not store CSV rows, file URLs, question text, answers, or OAuth tokens in these records.
  • Support messages. If you email support, we receive the information and attachments you choose to include. Please do not send CSV data, passwords, card details, or access tokens.

How evaluation data moves

  1. Your MCP client sends an evaluation request to Decision Cloud. The request can include a temporary file download URL, shared context, and questions for each CSV row.
  2. Vercel runs the Decision Cloud web application. The application downloads and parses the CSV while the request is running. It keeps the CSV in request processing rather than writing it to Decision Cloud's PostgreSQL tables.
  3. Decision Cloud writes content-free job, batch, attempt, and usage metadata to PostgreSQL as the evaluation runs. It sends the relevant row data, context, and questions through OpenRouter to TypeSafe's Jev service, which produces typed judgments. Both providers receive the content needed to process the request.
  4. Decision Cloud returns structured judgments and complete source rows to your MCP client. The host AI or application then handles any interpretation or further processing.

For payments, Stripe hosts checkout and processes card data. Decision Cloud receives a signed payment event and stores the payment status, transaction identifiers, and credit-ledger metadata in PostgreSQL. It does not store the full webhook payload or card numbers. Vercel, the PostgreSQL host, Auth0, Stripe, OpenRouter, and TypeSafe process information under their own services, agreements, settings, and retention practices. Their logs or backups may have separate retention. We do not claim zero retention by those providers.

Service providers

  • Auth0 provides account authentication and identity services.
  • Stripe processes credit top-ups and payment events.
  • Vercel hosts the website and server-side application routes.
  • PostgreSQL and its database host store account, payment, credit, and operational job metadata. The configured database host may change; this policy does not name a hosting region.
  • OpenRouter routes evaluation requests to TypeSafe, whose Jev service performs the typed judgments.

Each provider's handling of data is also subject to its own privacy information, contract, and configured service. Decision Cloud does not control independent provider retention, logs, or backups.

How information is used

Decision Cloud uses account information to authenticate you and associate evaluations with your account. Billing and ledger metadata support checkout, credit balances, payment reconciliation, and dispute handling. Job and usage metadata support evaluation status, usage accounting, reconciliation, service operations, and security. Support messages are used to respond to your request.

Retention

  • CSV and evaluation content. Decision Cloud does not persist CSV rows, file URLs, question text, or model answers in its PostgreSQL tables. Processing occurs while the evaluation request runs. This statement does not set the retention period of Vercel, OpenRouter, or TypeSafe.
  • Completed job metadata. The daily scheduled cleanup deletes completed evaluation jobs after 90 days. The database cascades that deletion to the job's batch and provider-attempt records. The clock starts at job completion, not creation.
  • Unresolved usage. A job stays in the operational database while its credit reservation or provider usage needs reconciliation. Once resolved, the next daily cleanup can delete it if 90 days have passed since completion.
  • Purchases and credit ledger. These financial records are not part of the job cleanup. Decision Cloud keeps the minimum payment and ledger metadata needed to administer credits, reconcile payments, handle disputes, and meet recordkeeping obligations. This policy does not set a fixed deletion date for those records.
  • Provider records and backups. The cleanup removes eligible records from the live PostgreSQL database. It does not delete copies in database backups, Vercel logs, or records held by Auth0, Stripe, OpenRouter, or TypeSafe. Those providers set their own retention schedules.

Your choices and deletion requests

Contact support to request account information, a correction, or account deletion. We verify requests before acting. A deletion request is handled by support and does not run an immediate automatic deletion. Financial purchase and ledger records may remain for the reasons listed above. A request to Decision Cloud does not automatically delete separate records held by Auth0 or Stripe.

See the account deletion stepsor read the Terms of Service.