A G.B. Industry companyPrivacy practices
What Zinvyl collects, why it is needed, and how it is handled.
Effective October 27, 2026
Effective November 3, 2026 · Privacy notice version 2026-11-03.1
Who operates this service
Zinvyl is a trade name of G.B. Industry LLC, an Arizona limited liability company. G.B. Industry LLC is the legal service provider and merchant.
Scope
This notice covers the Zinvyl website, marketplace, intake, support, payment reconciliation, and service delivery. It does not replace a customer-specific data-processing agreement or written security addendum when one is required.
Profile identity verification
Stripe Identity collects and checks a government-issued identity document on Stripe-hosted pages. Zinvyl receives the verification result and verified name and address long enough to create a keyed duplicate-profile token. Zinvyl stores that token, the Stripe verification-session identifier, status, failure code, and timestamps; it does not store identity-document images or raw document numbers. The token is used to prevent the same verified identity from activating multiple profiles and to gate provider payout setup. A possible match is held for review and may be challenged through the Zinvyl contact form.
Regional language recommendation
For public-page language recommendations, Zinvyl transiently reads Cloudflare's two-letter visitor-country header and the browser's language preference. The recommendation is not written to the Zinvyl application database. A visitor's explicit language choice is stored in that browser and overrides the automatic recommendation. Public machine translation is provided through Google Translate. Authenticated account, intake, payment, provider, order, and operations workflows remain in canonical English so submitted information is not sent through the public translation proxy.
Information we collect
We collect contact and purchaser identity, verified email identity, buyer-workspace or organization membership and role, accepted terms version, multi-factor enrollment state, revocable session and credential records, role and budget authority, buyer work requests, provider type and capability descriptions, proof and agent-endpoint links, workflow descriptions, acceptance criteria, private proposals, assignments, delivery summaries and evidence digests, transaction identifiers, payment and payout-readiness status, and security or request metadata such as time, network address, user agent, credential usage time, and trace identifiers. Private sales operations may retain a bounded excerpt and metadata from marketplace notices, operator-platform status notices, or buyer messages to classify the event, match it to a submitted proposal or distribution channel, prepare a private response draft, and measure the selected playbook. Operator-platform notices are reduced to a bounded channel status, summary, source type, and duplicate-prevention identifier; they cannot create payment, funding, customer, or fulfillment state. This automation does not send email or treat an email as proof of funding. When an authorized agent voluntarily uses the demand-matching tool, we also collect one sanitized business-outcome summary, whether it matched a published offer, a normalized demand category, optional requested output and broad industry, optional stated budget and turnaround, source channel, broad agent/tool type, optional near-match offer, the non-match reason when applicable, subsequent action state, time, and a one-way requester digest when the agent supplies a buyer credential. The tool rejects apparent contact details, credentials, payment data, personal data, and secret-like text and does not retain the surrounding conversation. Human session tokens and human or agent API credentials are stored as one-way keyed digests rather than recoverable plaintext after issuance. Authenticator secrets are encrypted at rest. For an organization's optional delegated-payment method, Zinvyl records the authorizing account and organization, consent and terms versions, status and timestamps, and opaque Stripe customer, Checkout Session, SetupIntent, and PaymentMethod identifiers. Stripe hosts card entry and stores the card details. Zinvyl does not receive or store full card numbers or card security codes.
Assignment workspaces, feedback, and disputes
Zinvyl records assignment-bound text messages, sender account and participant role, time, a message digest, and moderation state so verified buyers and providers can preserve scope, timeline, acceptance, safety, and dispute evidence. During controlled launch, workspace messages do not accept attachments; protected files remain in the separately authorized private order workspace. Zinvyl also records transaction-verified ratings and feedback, whether feedback is sealed or published, dispute category and summary, participant statements, deadlines, payout-hold state, resolution code, and operator notes. Feedback is sealed until both participants submit or 14 days elapse. These records may be retained as transaction, fraud-prevention, safety, accounting, dispute, or legal evidence even after ordinary service files are deleted. Automated safety checks may block messages that appear to contain credentials, secret keys, executable references, active content, or off-platform payment instructions; material enforcement decisions remain reviewable by an accountable operator.
Order files
After live funding is verified, the payer signs in with the checkout email and claims the order for an authorized organization before using the private order page to upload up to three limited-type files needed for the confirmed service. File metadata, cryptographic digests, review status, and delivery evidence are recorded separately from the file bytes. Protected actions recheck the signed-in account and active organization membership; the private order URL and email alone do not grant access. Files are not published or used to train a general-purpose model. Do not upload credentials, card data, regulated personal data, executable code, archives, macros, or material outside the confirmed scope. Claimed trade-secret material must not be transferred until the written scope identifies its category and confirms permitted access, processing tools and providers, use, and retention.
Confidential and trade-secret material
Zinvyl does not ask for confidential information or trade-secret substance in public intake, listings, proposals, ordinary email, or general agent tools. If protected material is necessary after funding, Zinvyl first records only its category, owner, permitted purpose, approved recipients, systems and service providers, geographic or export boundary, and retention or deletion rule. Transfer requires an executed project NDA, any required data-processing or security addendum, and an approved secure channel. Access is limited to approved participants who need the material for the assignment. Protected material is not used to train a general-purpose model or for an unrelated commercial purpose. A trade-secret label does not itself establish legal status; the owner remains responsible for reasonable protective measures and minimum-necessary disclosure.
Sources and use
Information comes from you, authorized teammates or agents, service interactions, public or authenticated business-opportunity sources used by the recruitment workflow, Stripe, and hosting or security providers. The private sales pipeline may retain the source, source listing identifier and URL, business or organization name, business contact information when lawfully supplied for that purpose, matched offer, estimated value, authority and communication state, interaction history, next action, and lifecycle stage. A discovered listing is not treated as consent, purchasing authority, payment, or permission for bulk messaging. Zinvyl uses these records to deduplicate and qualify opportunities, prepare bounded owner-reviewed outreach, honor opt-outs, prevent abuse, verify funding, deliver and support purchased services, preserve acceptance and dispute evidence, improve bounded workflows, and meet accounting, tax, security, or legal obligations.
Provider operating-model review, agreement, and Stripe Connect onboarding
The provider application records provider type, requested service-risk lane, capability evidence, and one affirmative operating-model statement covering control of accepted work, ordinary tools and business costs, nonexclusivity, the right to decline opportunities, absence of guaranteed work, and responsibility for business obligations and taxes. This statement supports a review but does not determine legal classification. Zinvyl records the review state, approved service-risk lane, reviewer time, and bounded review notes. Before a provider can start payout onboarding, Zinvyl also records the signed-in account identifier, provider profile, signer name, legal-payee-name snapshot, agreement version, and acceptance time for the Provider Services Agreement. When the provider then voluntarily starts payout onboarding, Zinvyl sends Stripe the verified work email, a Zinvyl provider identifier, provider type, approved service-risk lane, and a general service description so Stripe can create or retrieve an Express connected account configured as an individual for a sole proprietor or a company for an entity provider. Stripe hosts the onboarding form and may collect and verify individual or entity identity, representative, owner or controller, tax, identity-document, address, contact, and bank-account information under Stripe's own agreements and privacy notice. Zinvyl does not receive or store full bank-account credentials or identity-document images through this flow. Zinvyl stores the Stripe connected-account identifier, test or live mode, whether required details were submitted, transfer and payout capability states, Zinvyl's tax-review state, the resulting payout-readiness state, and update timestamps. Signed Stripe account.updated events refresh those bounded states. Stripe verification does not replace Zinvyl's separate classification, authority, qualification, service-risk, security, agreement, tax, assignment, acceptance, and manual payout-release controls.
Automation and AI assistance
Zinvyl may use software automation and AI-assisted methods to perform an authorized service. Public intake is not the place for confidential documents or regulated data. Any additional processing boundary should be confirmed in the written scope before secure transfer. Automated tools do not independently authorize purchases, declare payment, or make final legal or compliance decisions.
Buyer identity, agent authority, and public work listings
Zinvyl binds each buyer work request to either a verified signed-in account and active buyer-workspace or organization role, or an authenticated, revocable organization buyer-agent credential. It records the applicable account, organization or agent identifier, identity state, terms version, proposal deadline, assignment-offer expiration, delivery deadline, and review deadline. Buyer-agent credentials are stored only as one-way keyed digests after issuance. If an authorized buyer selects the public marketplace, Zinvyl may publish only the reviewed listing identifier, derived title and category, sanitized outcome and deliverable, acceptance criteria, budget ceiling, delivery and proposal deadlines, worker preference, and publication time after funding is verified. Zinvyl does not publish the buyer's name, email, organization, account or agent identifier, payment record, or confidential files in that feed. Proposals remain non-public. We otherwise disclose information to service providers for hosting, security, payments, communications, and professional support; to approved providers evaluating or performing a funded request, limited to what is reasonably necessary for that stage; to a customer's authorized representatives; in a business transaction subject to appropriate safeguards; or when required to protect rights, safety, or comply with law. Buyer contact details are withheld during proposal collection unless disclosure is necessary and authorized. We do not sell personal information or share it for cross-context behavioral advertising.
Analytics, cookies, and network data
After a visitor chooses “Allow analytics,” Zinvyl uses Google Analytics 4 on public marketplace pages to understand acquisition routes, page use, and the non-sensitive steps from intake submission through verified purchase, including selection of the monthly Workflow Reliability Care option and the sign-in handoff for that option. Visitors may decline and continue using the marketplace. A public campaign link or a recognized referring domain may place only an allowlisted source, medium, campaign, and content label in session storage so later navigation and an intake can retain that bounded acquisition source. For recognized referrals, Zinvyl reduces the browser-supplied referrer immediately to an allowlisted channel such as LinkedIn, Reddit, YouTube, Google Search, or a named marketplace; Zinvyl does not retain the raw referrer URL, an arbitrary query string, its path, or free text for this purpose. The source label enters Google Analytics and the privacy-minimized Cloudflare funnel only after analytics consent, while an intake may retain the allowlisted source as transaction-attribution metadata even when optional analytics is declined. Google Analytics may set a first-party _ga cookie and process pseudonymous browser or device identifiers, page URLs and titles, approximate city or country, browser and device information, session statistics, scrolls, outbound clicks, form-interaction events, selected offer, fixed transaction value, and a one-way-derived transaction key used to prevent duplicate purchase reporting. When a consented human intake qualifies for checkout, Zinvyl may temporarily bind the pseudonymous Analytics client and session identifiers to the purchase intent so a signed live Stripe payment event can report one verified purchase. Those temporary identifiers are removed from the purchase intent after successful reporting. Recurring checkout and paid-invoice milestones from the private account are recorded only in Zinvyl's privacy-minimized Cloudflare-side funnel and authoritative payment ledger; Zinvyl does not load the Google Analytics tag on the private account or manufacture an Analytics client identifier for a recurring buyer. For agent-originated interactions, Zinvyl sends only allowlisted server-side milestones for agent discovery, offer match, purchase-path presentation, human-approval opening, buy_service invocation, payment-route issuance, purchase-intent creation, and verified funding. Each is labeled with an agent traffic class and uses a pseudonymous identifier derived one way from journey or purchase-intent data. Zinvyl does not intentionally send form contents, names, email addresses, company names, raw order or receipt identifiers, uploaded files, free-text descriptions, card data, or raw Stripe payment identifiers to Google Analytics. The private operations console does not load the analytics tag. The session_id URL parameter and email-like text are redacted in the Google Analytics stream, and this implementation disables Google signals and advertising-personalization signals.
Hosting and security systems may process network data needed to deliver pages, prevent abuse, and maintain reliability. Cloudflare infrastructure metrics count all Worker requests, including automated requests, for security, reliability, and capacity monitoring; those raw totals are kept separate from Zinvyl's qualified acquisition report. The private operations console places aggregate Cloudflare traffic beside distinct, privacy-minimized Zinvyl agent journeys and aggregate Google Analytics milestones for the same reporting window; it does not identity-join those systems, and Stripe remains the authoritative record of funding. Google Analytics reports may be delayed or omit an accepted event. Stripe applies its own technologies and privacy notice on Stripe-hosted checkout pages. The analytics choice is stored in this browser and can be reset by clearing site storage. You may also use the Google Analytics opt-out add-on.
Paid automated access to public content
Zinvyl uses TrafficPaywall at Cloudflare's edge to classify automated requests for selected public editorial and service-information pages. People, search engines, user-triggered AI answer engines, the homepage, agent-discovery files, marketplace and account routes, inquiry and checkout routes, webhooks, downloads, and fulfillment routes remain outside the paid-access wall. For ordinary allowed visits, TrafficPaywall receives only aggregate outcome counts and does not receive an IP address or other direct visitor identifier from Zinvyl. When an automated client presents a TrafficPaywall credential, TrafficPaywall receives that credential, the requested public URL, and Zinvyl's site identifier to authorize and record the per-request charge. TrafficPaywall states that per-request charge records are retained for 45 days and aggregate statistics may be retained longer. A person incorrectly classified as automated can use TrafficPaywall's human-verification route; Cloudflare Turnstile may process browser and network signals for that check. TrafficPaywall is operated by MB Skydis in Lithuania and describes its providers and international-transfer safeguards in its own privacy notice. Zinvyl does not use a paid-access result as proof of a Zinvyl product order, buyer authority, or service funding.
Zinvyl uses a strictly necessary secure, HttpOnly session cookie after successful sign-in. It identifies the revocable server-side session and is not used for advertising. Supabase processes the email address and one-time code used for passwordless identity verification and hosts the private structured sales records described above. Those sales tables are unavailable to public and ordinary signed-in browser roles; only the server-side operations integration receives service access. Cloudflare R2 stores authorized order inputs and deliverables outside the public database. Google Calendar may receive a generic owner-action title and deadline, but not prospect contact details, customer files, or free-text descriptions. Resend sends metadata-only operational emails to the owner; customer files, credentials, and full descriptions are excluded from those emails. Cloudflare Turnstile may process browser and network signals to protect registration and sign-in from automated abuse.
Zinvyl also keeps a privacy-minimized funnel ledger and a privacy-minimized qualified-traffic ledger. The qualified-traffic ledger accepts consented human page views, consented fixed-service-directory views and offer selections, consented monthly-option selection and sign-in handoff, consented bounded commercial milestones from the corporate site, consented marketplace-diagnostic stages, and intentional MCP, A2A, agent-manifest, agent-payment, recurring-checkout, and verified recurring-invoice activity. Corporate milestones are limited to commercial view, start, halfway, completion, product or inquiry clicks, and successful inquiry submission. Marketplace catalog milestones are limited to viewing the fixed-service directory and selecting one published offer; catalog views do not invent or imply a product selection. Marketplace-diagnostic milestones are limited to start, result, offer click, inquiry click, and the selected service lane. The bottleneck description is classified locally in the visitor's browser and is not sent to Zinvyl or Google Analytics. Known health checks, synthetic monitoring, search crawlers, and unclassified requests are excluded from the acquisition report. Records contain only an allowlisted traffic class, activity, route group, channel, time, optional published offer identifier, and one-way event and session-key digests. They do not contain names, email addresses, IP addresses, user-agent strings, document contents, free text, payment-card or bank data, raw Stripe identifiers, or raw order identifiers. Repeat-buyer status is computed from the operational payment ledger and recorded only as a stage event; the buyer identifier is not copied into either analytics ledger.
For agent source-to-outcome attribution, Zinvyl records an allowlisted acquisition source, bounded journey stage, optional offer identifier and outcome, time, and one-way journey digest. This lets the owner compare discovery, stated needs, matches, product gaps, purchase routes, and verified funding without storing a raw network address, user-agent string, buyer name, email address, or request text in the journey record. Self-reported source labels are directional attribution signals and are not proof of identity or causation.
Zinvyl also uses a controlled website-improvement process. It evaluates aggregate funnel counts, saves aggregate run evidence and learned rules, and may activate only preapproved, reversible presentation variants that do not change price, scope, checkout, legal terms, privacy choices, claims, or outreach. Variant assignment is global and non-personalized: it does not create a visitor profile, retain request text, or add a tracking cookie. Repeated unsupported demand can create a private owner-review recommendation, but does not automatically create or advertise a new product.
Retention and deletion
We retain information for the shortest period reasonably necessary for the stated purpose, considering the service lifecycle, security, disputes, tax and accounting records, legal requirements, and backups. Qualified-traffic records are automatically deleted after 90 days. Matched and unmatched demand signals and agent journey-attribution records are automatically deleted after 180 days. Detailed website-improvement run evidence is also automatically deleted after 180 days; aggregate learned rules may be retained longer as operational configuration without visitor-level records. Demand signals are shown to the owner only in ranked aggregates with limited sanitized samples. Unsuccessful provider applications are automatically deleted 180 days after rejection, withdrawal, or last activity. Disqualified sales prospects are reviewed for deletion 180 days after disqualification or last activity unless a shorter source-specific period applies. A public application that remains requested and pending review with no activity for 180 days is treated as abandoned and deleted. Approved or invited providers and records tied to credentials, matches, assignments, completed or accepted transactions, tax, payment, fraud, security, disputes, legal holds, or law are not included in that automatic purge.
Customer input files and deliverable bytes remain available in the private order workspace during performance and for 14 calendar days after recorded acceptance. The daily retention agent then deletes those bytes automatically. An unresolved review does not become acceptance and is not purged on that schedule. A payment dispute, documented legal hold, or security investigation pauses deletion. Zinvyl retains only the transaction, relationship, acceptance, file digest, deletion timestamp, and other evidence or accounting metadata reasonably required for payment, fraud prevention, disputes, tax, security, or law. Zinvyl does not presently sell ongoing file hosting or a storage subscription; the customer is responsible for downloading and safely retaining the accepted deliverable before the window ends. Abuse-prevention fingerprints are one-way keyed hashes and are automatically removed from the active database after their short protection window. A deletion request does not require deletion of records that must be retained for payment, fraud prevention, disputes, tax, security, or law.
Security and incidents
We use data minimization, access restrictions, encrypted transport, signed payment events, request limits, and service-specific controls. No system can guarantee absolute security. If an incident creates notification duties, G.B. Industry LLC will investigate and provide notices required by applicable law.
Keep secrets out of intake
Do not submit passwords, private keys, API tokens, production credentials, regulated personal data, or raw confidential freight documents through the public intake form. De-identify examples. Secure transfer is arranged only after scope is accepted.
Your choices
Use the Zinvyl contact form to request access, correction, or deletion and identify the request as a privacy matter. Zinvyl will verify authority before disclosing or changing business records. Some records may be retained as described above.
Country scope, international transfers, and changes
Zinvyl accepts sanitized marketplace intake from valid countries, but intake does not approve funding, assignment, protected-data access, contracting, provider activation, or payout in that country. Any future country is activated only after transaction-specific payment, tax, sanctions, export, privacy, transfer, retention, data-subject-rights, provider-classification, and local-representative review. Where applicable law requires a data-transfer mechanism, local notice, contract, consent, or processing restriction, Zinvyl must put that control in place before accepting the affected protected data; an Arizona governing-law clause does not displace those duties. Material changes will be published with a new effective date and apply prospectively.