A G.B. Industry companyWhat is live, what is gated, and how Zinvyl checks the difference
A dated public record of Zinvyl's controlled-launch marketplace, service catalog, automated systems, payment boundaries, and verification evidence.
Effective October 23, 2026
Report snapshot: October 23, 2026. Live gateway: 1.9.494. Published offers: 14. Platform terms: 2026-10-23.6. Provider agreement: 2026-10-23-provider-v7.
Operator and business model
G.B. Industry LLC, doing business as Zinvyl, operates the service from Arizona. Zinvyl sells bounded business consulting services directly and operates a controlled marketplace for funded business work. Marketplace applications and work requests are available for review; an application, match, proposal, or delivery does not by itself authorize work, establish employment, prove payment, or release a provider payout.
Catalog and customer-tax classification
All 14 currently published offers are recorded as human-led business consulting services with client-specific outputs incidental to the service. Under tax policy 2026-10-23.3, Zinvyl does not add Arizona transaction privilege tax to those currently published scopes. This is a catalog classification, not a universal no-tax rule. A changed scope, software or content license, SaaS or storage access, standardized digital product, tangible property, customer jurisdiction, or registration footprint requires a new determination before checkout.
Provider information reporting, withholding, worker classification, and payout eligibility are separate from customer sales-tax classification. Live provider payouts therefore remain gated even though the current customer catalog has an Arizona consulting-service classification. International intake does not mean every cross-border transaction is cleared; customer location, service classification, payment rail, sanctions/export, privacy transfer, and applicable VAT, GST, sales-tax, invoicing, and registration rules are checked before funding where required.
Payments, subscriptions, and provider payouts
Stripe hosts customer payment collection and provider Connect onboarding. Zinvyl does not store full card numbers, bank-account credentials, or provider identity-document images. A quote, approval, checkout page, subscription setup, or payment attempt is not proof of funding; only a reconciled Stripe record can create paid state. The U.S.-business monthly option requires separate recurring consent, Stripe-hosted terms acceptance, address and tax calculation, and a verified paid invoice for every 30-day cycle; customers can cancel future renewal through the authenticated Stripe billing portal. Provider applications and Stripe onboarding do not activate assignments or payouts. Live provider payouts remain disabled pending the separate provider reporting, withholding, classification, country, dispute, and manual-release controls.
Identity, provider review, and work acceptance
Human access uses verified email sessions, organization membership, explicit roles, and step-up multi-factor controls for privileged actions. Provider access is individually reviewed for identity, authority, operating model, capability evidence, service-risk lane, agreement, tax readiness, and payout eligibility. Zinvyl evaluates work against the written scope and observable acceptance criteria. That evidence can support acceptance, correction, rejection, or escalation; it cannot guarantee that work is error-free, fit for every unstated purpose, or free of every vulnerability.
Agents and automated decisions
Public agents may discover and qualify sanitized needs without purchasing. A purchase path requires exact offer, amount, currency, current terms, safe scope, and existing delegated authority; an agent cannot invent authority, mark payment complete, widen scope, or release provider funds. Automated analytics may identify a funnel bottleneck and recommend an allowlisted, reversible presentation change. It cannot change prices, legal terms, products, payment controls, tax policy, provider activation, or payout status without the required authorization and evidence.
Data and retention
Zinvyl minimizes public intake and prohibits credentials, payment-card data, protected health information, and confidential or trade-secret substance in public channels. Accepted-order input and deliverable bytes are scheduled for deletion 14 days after recorded acceptance unless a documented dispute, legal hold, or security investigation pauses deletion. Bounded transaction, consent, tax, security, acceptance, digest, and deletion evidence may be retained longer where needed for accounting, fraud prevention, disputes, and legal obligations.
Release and quality evidence
The October 23, 2026 release passed 684 automated tests. Its outside-in HTTP audit passed 428 of 428 checks across 61 pages, 98 links, 142 assets, and 6 registry digests. Its desktop, tablet, and mobile render audit passed 99 of 99 checks covering 261 rendered images and 15 rendered video instances from 2 unique video assets. These are bounded checks of the tested release, not a guarantee of uninterrupted service or defect-free operation.
Zinvyl now runs a source-contract consistency gate before every build and again before predeployment. The gate compares the canonical platform, network, and provider agreement versions with active application code, machine contracts, examples, generated review material, and test assertions. Any stale active version blocks the build and the direct Cloudflare release agent; the release validator has no waiver authority.
Security, incidents, and limitations
Cloudflare provides the public edge and verified WAF controls. Security headers, same-origin enforcement, bounded inputs, secret-pattern rejection, throttling, signed payment webhooks, idempotency, least-privilege credentials, and private order authorization reduce risk. They do not eliminate it. Confirmed material incidents and corrective actions will be added to this report when public disclosure is appropriate and lawful. Security concerns should be reported through the Zinvyl contact route without placing exploit details or sensitive data in public intake.
Current maturity
Zinvyl is a high-complexity controlled-launch marketplace with identity, agent commerce, payments, fulfillment, analytics, policy gates, and direct release automation. It does not claim the marketplace liquidity, reputation history, messaging scale, dispute volume, or global compliance maturity of Upwork or Fiverr. Worldwide intake is broader than current transaction activation, and every unsupported location or service remains review-gated.
Accountability and changes
This report is reviewed when a material release changes payments, taxes, identity, provider access, data handling, legal terms, automated authority, or release controls. Historical legal and operational review records are retained internally; public statements are updated when the live behavior changes. Report a mismatch through the Zinvyl contact form.