Read the terms before you pay.

What you get and when.

What the purchase includes

Founding access includes one tenant API key, 90 days of access from provisioning, 1,000 review credits, the REST API and Python SDK, evaluation history, repair verification, and up to two hours of first-pipeline setup support during the first 14 days.

A standard package is up to 256 KiB, 8 files, and no images and uses 1 credit. An extended package is up to 2 MiB, 16 files, and 3 images and uses 5 credits. A full package is up to 8 MiB, 32 files, and 8 images and uses 10 credits. These limits apply to the encoded request package. The API quotes the charge before submission; requests above the full-package boundary are rejected without consuming credits.

Provisioning target

After Stripe confirms a settled payment and a complete setup form is received, the provisioning target is two business days. Checkout redirects to that form. If details are missing, the delivery window begins when the completed form arrives.

Delivery method

Access instructions and the tenant credential are delivered to the verified purchaser contact through a secure channel. API keys are shown only at provisioning and must not be sent through the public forms.

Service period

The 90-day period begins when the tenant key is provisioned, not when the checkout opens. Founding access is not a recurring subscription and does not renew automatically.

Refunds for unused access.

Eligible requests

A full refund is available when requested within seven calendar days of purchase and no evaluation has been submitted with the provisioned tenant key. A full refund is also available for a duplicate payment or when TUC cannot provision access within two business days after both settled payment and complete intake.

After use or seven days

After the first paid evaluation is submitted or the seven-day window has passed, unused credits and remaining access time are not automatically refundable. Requests involving a verified service failure are reviewed individually. Rights required by applicable law are not limited by this policy.

How to request a refund

Use the private contact form, choose “Billing or refund,” and provide the email used at checkout plus a short explanation. Do not provide full card or bank information. Approved refunds are returned through Stripe to the original payment method; bank processing time varies.

Cancellation

There is no recurring subscription to cancel. A refund does not preserve access; the associated tenant key is revoked when the refund is issued.

What we collect and why.

Information collected

• Checkout and transaction records supplied by Stripe, including purchaser contact and payment status. TUC does not receive full card numbers.
• Fit and setup details: email, optional name and organization, workflow description, work types, integration method, and expected volume.
• Contact requests: email, optional name and organization, request category, and message.
• Basic site usage: page visits and button clicks. We use these counts to improve the site. They are not tied to a person.
• Free-preview inputs: artifact text, the original task, and requirements are processed in memory to return a deterministic result. The application does not write preview inputs or results to evaluation, usage, audit, or account storage, and the preview does not call an external model.
• Authenticated product data: submitted artifacts and evidence, evaluation results, repair records, usage, audit events, and request details needed to operate the service.

Why it is used

Information is used to verify payment, provision and secure tenant access, run requested evaluations, provide support, prevent abuse, measure quotas, investigate failures, improve the service, and satisfy legal or accounting obligations.

Service providers

Stripe processes checkout and payment data. Fly.io hosts the public private-beta service. If a customer deployment enables a model-backed evaluator, submitted work and evidence may be sent to the configured model provider to perform the evaluation. The current public preview uses fixed checks and does not call an external model.

Retention and sharing

Site usage counts are kept for up to 90 days. Preview inputs and results are not saved. Other information is kept as needed to provide the service, support customers, secure accounts, and meet accounting or legal obligations. It is not sold or used for third-party targeted advertising. It may be shared with service providers working on TUC's behalf, when required by law, or to protect the service and its users.

Your requests

Use the private contact form and choose “Privacy request” to ask for access, correction, or deletion. Identity may need to be verified. Some payment, fraud-prevention, audit, or legal records may be retained when required.

Service terms.

Use of the service

The Ultimate Critic checks submitted work against the task, requirements, constraints, rubric, references, and evidence supplied by the customer. It returns verdicts and findings for use in a software workflow. The customer remains responsible for release decisions and downstream use.

Account and credential responsibility

One founding purchase covers one tenant. The purchaser must keep tenant credentials confidential, restrict them to authorized users and systems, and promptly report suspected compromise. Credentials may not be resold, publicly shared, or used to bypass the evaluation limit.

Acceptable use

Customers must have the right to submit the materials they provide. The service may not be used to violate law, infringe rights, distribute malware, probe systems without authorization, expose personal data, or interfere with service operation.

Evaluation limits

Private-beta output can be incomplete, uncertain, or wrong. A pass is not a guarantee of correctness, security, legal compliance, safety, performance, or business outcome. “Insufficient evidence” means the submitted package did not support a reliable decision. Customers must independently review high-risk decisions.

Availability and changes

The service is offered as a private beta and may change during the access period. Reasonable efforts are made to preserve the purchased 90-day/1,000-review-credit entitlement. Maintenance, provider failures, and security incidents can temporarily affect availability.

Suspension

Access may be limited or suspended to protect the service, investigate abuse or credential compromise, comply with law, or address a material violation of these terms. Where practical, notice and an opportunity to correct the issue will be provided.

Warranty and liability boundary

The service is provided on an “as available” private-beta basis. To the maximum extent permitted by applicable law, implied warranties are disclaimed and liability arising from founding access is limited to the amount paid for that access. This does not exclude rights or liabilities that cannot legally be excluded.

Policy updates

Material updates are posted here with a new effective date. Terms stated at purchase continue to govern that founding access unless a change is required by law or is accepted by the customer.