Delivery, scope, and acceptance

The one-business-day clock starts only when the work is fundable and testable.

Effective September 20, 2026

Submission, review, and payment sequence

First, the buyer or authorized agent submits a sanitized description of one bounded problem, purchasing authority, available samples, and a measurable acceptance test. Automated rules check whether the request fits a published fixed-scope offer. A passing result produces a locked quote and Stripe-hosted checkout route; it is not human review of customer files, proof of payment, or authorization to begin work. A request that is incomplete, outside scope, missing authority, or unsuitable for the fixed offer receives no checkout route and is held for follow-up. After Stripe confirms payment through a signed event, the payer opens the private order workspace, provides only the authorized minimized inputs, and Zinvyl reviews them for scope and safety before starting the delivery clock.

When the delivery clock starts

The stated one-business-day target begins after cleared funding, a complete sanitized intake, written scope confirmation, and measurable acceptance criteria. Weekends and United States federal holidays are excluded.

What delivery contains

The delivery package is the evidence bundle shown on the selected offer: findings, tested behavior, failure or review conditions, limitations, and the agreed implementation artifact where applicable. Delivery occurs through the agreed secure channel.

Acceptance test

Before work, buyer and Zinvyl confirm the input set, expected output or reproduced failure, pass/fail conditions, and exclusions. After delivery, the buyer records acceptance or identifies an unmet written criterion. One scope-conforming revision is included when requested within three business days.

Order workspace and evidence

A live paid order receives a private status page for limited file transfer, delivery evidence, and acceptance. The payer email must match the verified payment record. Delivery is not complete merely because a file exists: Zinvyl records the delivery summary and SHA-256 evidence digest, and the customer can accept or identify the unmet written criterion during the revision window. Keep the order URL private.

Buyer dependencies and pauses

The delivery target pauses while required inputs, access, decisions, or responses are missing, or when a third-party system needed for the agreed test is unavailable. Zinvyl will identify the blocker and the item needed to resume. A pause does not expand scope.

Safe access and production changes

Customer access must be least-privilege, time-limited, and provided through the agreed secure channel. Unless the service order expressly includes implementation, Zinvyl does not deploy into production. The customer is responsible for backups, approvals, change windows, rollback authority, and final production decisions.

Confidential and trade-secret material

The service terms impose mutual confidentiality duties on both the customer and Zinvyl. Public intake remains a sanitized scoping channel, not a repository for confidential files or trade-secret substance. When protected material is essential to the purchased work, the written scope should identify its category without unnecessary disclosure and confirm who may access it, the approved processing tools and providers, the permitted use, and the retention or deletion requirement before transfer. Labeling information confidential does not by itself establish trade-secret status; each owner remains responsible for the reasonable protective measures required for its information.

Out of scope

Additional workflows, undocumented objectives, production credentials in public intake, deployment into customer systems, legal or compliance certification, OCR accuracy guarantees, and unlisted third-party costs are excluded unless a written service order adds them.

Events outside reasonable control

Neither party is responsible for delay caused by events outside its reasonable control, including widespread provider outages, government actions, disasters, or Internet failures. The affected party will communicate promptly and resume when practical.