Closed Beta Terms

Closed Beta Terms

Closed-beta legal boundary: Founder-prepared draft for closed-beta readiness. Lawyer/CA review required before paid/public production. PGI Hub has no approved live payments, GST invoicing, vendor payouts, escrow, public marketplace launch, automated supplier award, or production legal approval under this pack.

1. Master Overview and Boundary

These Closed Beta Terms govern PGI invite-only evaluation access, controlled workflow testing, founder/legal/operations review, and no-payment beta participation. They bind closed-beta buyers, vendors, invited suppliers, organization administrators, and internal operators, and they do not approve public production launch, paid plans, live payment collection, GST invoicing, vendor payouts, escrow, automated supplier award, or verified marketplace claims.

2. Operational Definitions

• Closed Beta means limited, invite-only access for evaluation, workflow validation, and readiness testing.
• Beta Participant means any buyer, vendor, supplier, admin, reviewer, or user admitted into the beta.
• Beta Data means account records, uploaded BOMs, RFQs, quotes, vendor profiles, rate/stock data, logs, feedback, support records, and Platform Informational Inferences created during beta.
• Launch Blocker means a missing legal, CA/tax/GST, payment-provider, operational, privacy, security, or founder approval required before paid/public use.
• No-Payment State means PGI must not charge users, collect subscription fees, invoice GST, settle vendor payouts, hold escrow, or process marketplace payments.

Platform Informational Inferences means outputs generated, derived, normalized, classified, ranked, estimated, compared, summarized, or otherwise presented by PGI using platform logic, user-provided data, vendor-provided data, public-source data, third-party data, provider/API data, AI-assisted analysis, rule-based logic, or internal procurement intelligence methods.

Platform Informational Inferences are not professional, engineering, legal, tax, logistics, insurance, customs, financial, or procurement advice. They are decision-support outputs only. The buyer, vendor, or contracting party remains exclusively responsible for independent validation before relying on such outputs for commercial, technical, legal, tax, logistics, compliance, or contractual decisions.

3. Closed-Beta Rules

4. Participant Obligations

Participants must use PGI only for lawful closed-beta evaluation and authorized procurement workflow testing. Participants must not treat PGI outputs as final supplier approvals, final tax guidance, final engineering validation, final price confirmation, final stock confirmation, or final delivery commitments.

Buyers must upload only data they are authorized to process. Vendors must submit only accurate business and commercial data. Both sides must preserve confidentiality and avoid scraping, contact harvesting, fake profiles, unsupported certifications, misleading quotes, or unauthorized RFQ activity.

5. Data, Confidentiality, and Feedback

Beta data may be incomplete, experimental, stale, or subject to correction. PGI may use participant feedback, bug reports, workflow observations, and data-quality findings to improve product design, legal notices, operational SOPs, and Codex implementation requirements. Confidential buyer procurement data and hidden supplier contact data remain subject to PGI's data and privacy controls.

6. Platform Changes and Suspension

PGI may change, disable, remove, rate-limit, audit, or place beta features into review without advance notice where required for safety, security, legal review, data correction, product maturity, or operational readiness. PGI may suspend users or workflows for misuse, unauthorized uploads, misleading supplier claims, RFQ abuse, contact-hidden violations, or security risk.

7. Product UI and Acceptance Mapping

8. Paid/Public Launch Prohibition

Paid subscriptions, live payments, GST invoicing, vendor payouts, escrow, provider charging, commission workflows, public marketplace launch, and production legal claims remain blocked until founder, lawyer, CA/tax/GST, payment-provider, privacy/security, and operational approvals are complete.

Related Documents

• terms-and-conditions
• privacy-policy
• acceptable-use-policy

Review Status

Founder-prepared draft. Lawyer/CA review required before paid/public production.

Paid/public production readiness: Not approved. Lawyer/CA/payment-provider/founder review required.