Terms and Conditions

Terms and Conditions

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 Terms and Conditions govern access to and use of PGI Hub — Procurement Global Intelligence — by website visitors, closed-beta users, buyer organizations, vendor organizations, invited suppliers, procurement users, administrators, and any person acting through an account or workspace. They establish the contractual operating boundary for PGI as a procurement intelligence and RFQ workflow platform, not as a seller-of-record, buyer-of-record, broker, payment intermediary, escrow provider, customs broker, freight forwarder, insurer, tax advisor, legal advisor, product-quality guarantor, or supplier-performance guarantor.

PGI is currently operated as a controlled closed-beta founder draft environment. These Terms do not approve public production launch, paid subscriptions, GST invoicing, live payments, vendor payouts, escrow, automated supplier award, guaranteed supplier verification, guaranteed pricing, guaranteed stock, guaranteed delivery, guaranteed quality, or guaranteed tax treatment.

2. Operator, Acceptance, and Version Control

By accessing PGI, creating an account, joining a workspace, uploading procurement data, claiming a vendor profile, responding to an RFQ, submitting rates/offers, requesting supplier contact access, or continuing to use the platform after a posted update, the user accepts the applicable PGI terms, policies, notices, and workflow disclaimers.

3. Operational Definitions

• PGI means PGI Hub — Procurement Global Intelligence.
• Closed Beta means invite-only, controlled, no-payment platform access for evaluation, data-validation, workflow testing, and operational readiness.
• Buyer means a person or organization using PGI to upload procurement requirements, manage sourcing workflows, discover potential suppliers, compare quotes, or manage procurement projects.
• Vendor means a business, supplier, distributor, manufacturer, service provider, contractor, or authorized representative using PGI to claim a profile, submit capability information, respond to RFQs, or manage supplier-side information.
• Potential Supplier means a supplier profile, source, or entity presented for evaluation and not necessarily claimed, verified, available, suitable, or approved by PGI.
• PGI Researched means PGI has assembled or normalized information from public, third-party, user-provided, vendor-provided, or internal research sources; it does not mean legal, tax, quality, commercial, or supplier verification has been completed.
• Not Yet Claimed means the vendor has not completed the vendor claim workflow.
• Not PGI Verified means PGI has not completed a defined verification process supported by retained evidence.
• Contact Hidden means supplier contact information is not exposed to buyers except through governed workflows and approved access controls.
• RFQ Workflow Record means a structured procurement request, quote request, buyer requirement, vendor response, quote comparison, clarification, communication, or status update recorded in PGI.
• Total Landed Cost Estimate means a decision-support calculation or comparison using assumptions about unit price, GST/tax basis, freight, duty, brokerage, currency, MOQ, lead time, incoterms, and other cost inputs.
• Platform Informational Inferences has the meaning below.

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.

4. Closed Beta Status

PGI is not approved for public production use under this pack. Closed beta access is limited to invited participants, controlled testing, limited procurement workflow validation, and product/legal/operations review.

PGI may alter, restrict, suspend, disable, or remove beta functionality, workflows, records, labels, supplier outputs, vendor profiles, RFQ capabilities, quote comparison tools, and AI-assisted outputs where required for safety, legal review, quality control, data correction, misuse prevention, security, or product readiness.

5. Eligibility, Organization Authority, and Account Security

Users represent that they have authority to act for the individual, company, procurement team, vendor, supplier, or organization they register, invite, manage, or represent. A user must not claim a vendor profile, upload confidential procurement data, submit an RFQ, respond to a buyer, publish supplier information, or manage organization settings unless authorized.

Each account owner is responsible for credential security, workspace membership, access roles, SSO/email control, and prompt reporting of suspected unauthorized access. PGI may restrict access, force session revocation, require re-authentication, suspend roles, or preserve audit records when account misuse or unauthorized activity is suspected.

6. Buyer Use Terms

Buyers may use PGI to upload BOMs, requirements, drawings, specifications, part data, MPNs, aliases, quantities, target geographies, sourcing notes, quote requests, supplier shortlists, and procurement project information. The buyer remains responsible for confirming that the upload is authorized, accurate, non-infringing, not unlawfully disclosed, and suitable for processing in a closed-beta procurement workflow.

Buyers must independently validate supplier identity, technical suitability, certifications, availability, pricing, tax basis, quality capability, logistics feasibility, contract terms, and final purchasing decisions. PGI does not approve, award, guarantee, or execute supplier selection.

7. Vendor Use Terms

Vendors may use PGI to claim profiles, submit business information, manage capabilities, product categories, part aliases, rates/offers, stock, lead times, certifications, team roles, and RFQ responses. Vendors are responsible for the accuracy, authority, legality, timeliness, and commercial meaning of any vendor-submitted data.

A vendor claim does not automatically make the vendor PGI Verified. A claimed profile can still be limited, under review, hidden, corrected, suspended, or removed where profile data is unsupported, stale, misleading, disputed, abusive, or inconsistent with PGI's closed-beta controls.

8. Admin and Operator Rights

PGI may operate administrative, moderation, review, audit, security, data-quality, support, and legal controls. PGI may correct labels, restrict visibility, hide contacts, disable RFQ sending, suppress supplier discovery outputs, place records in review queues, suspend accounts, remove content, and preserve evidence where required by operational risk, legal review, security, abuse prevention, or data integrity.

Admin rights must be exercised under internal SOPs, role-based access, audit logging, and least-privilege controls. Internal SOPs are not public user-facing promises and must not be published as footer legal pages.

9. Supplier Discovery, Vendor Claim, Marketplace Labels, and Contact Hidden

Supplier discovery outputs are decision-support records. Labels such as Potential Supplier, PGI Researched, Not Yet Claimed, Not PGI Verified, Claimed, PGI Reviewed, and PGI Verified must be displayed only according to retained evidence and platform rules.

PGI may keep supplier contacts hidden to protect privacy, prevent scraping, reduce misuse, preserve workflow integrity, and ensure governed buyer-vendor communication. Contact access, where enabled, remains subject to eligibility, acceptance, review, audit logging, and platform controls.

10. BOM, RFQ, Quote Comparison, TLC, and Procurement Workflow

PGI can normalize messy BOMs, identify MPN aliases, classify categories, map materials/processes/UOM, match potential suppliers, structure RFQs, compare quotes, and estimate total landed cost assumptions. These functions depend on buyer input, vendor input, public-source data, third-party data, provider/API data, historical records, rules, and AI-assisted analysis.

A quote excluding GST and freight must not be treated as directly equivalent to a quote including taxes, freight, packaging, delivery, and warranty terms. A distributor with lower unit price but international shipment, import duty, brokerage, currency conversion, MOQ, and long delivery risk must not be presented as commercially superior without visible TLC assumptions and data-quality warnings.

11. AI and Procurement Intelligence

AI-assisted outputs, classifications, summaries, risk flags, supplier suggestions, normalization results, ranking explanations, missing-spec detections, and procurement reports are Platform Informational Inferences. PGI must not represent AI outputs as final technical, legal, tax, customs, logistics, insurance, quality, or procurement advice.

Low-confidence outputs should be review-bound. Users must not automate supplier awards, final procurement commitments, contact disclosure, payment actions, legal conclusions, tax decisions, customs classifications, or safety-critical sourcing decisions solely from AI outputs.

12. Orders, Purchase Orders, Communication, and Delivery Status

PGI may support PO/order workflow records, vendor communications, production/delivery status updates, and procurement project tracking. PGI does not become a party to buyer-vendor contracts unless a separate reviewed and signed agreement expressly says otherwise.

Buyers and vendors remain responsible for commercial terms, specifications, acceptance criteria, delivery commitments, quality inspection, taxes, logistics, disputes, warranties, returns, and enforcement. PGI does not guarantee order completion, delivery, quality, pricing, stock, lead time, tax treatment, or supplier performance.

13. Data Rights, Confidentiality, and Usage Restrictions

Users retain responsibility for data they upload or submit. PGI receives the limited rights necessary to operate the platform, structure procurement workflows, generate Platform Informational Inferences, maintain audit logs, provide support, improve data quality, enforce policies, and prepare professional review materials.

Buyer BOM/RFQ/project data must be treated as confidential procurement data except where the buyer authorizes controlled sharing through an RFQ or workflow. Vendor profile data can be visible according to claim status, publication settings, contact-hidden rules, and PGI labels. Users must not scrape, resell, reverse engineer, bulk export, misuse, or exploit PGI data, supplier records, ranking logic, taxonomy, or proprietary procurement intelligence.

14. Intellectual Property and PGI Proprietary Systems

PGI owns or controls its platform design, workflows, taxonomies, scoring methods, ranking explanations, software, UI, databases, data-quality rules, normalization logic, AI orchestration, audit structures, legal pack architecture, and proprietary procurement intelligence, except for third-party rights and user-owned data. No user receives ownership of PGI systems by using the platform or receiving an output.

15. Acceptable Use, Security, and Confidentiality

Users must not submit illegal, infringing, misleading, abusive, malicious, deceptive, fake, unauthorized, export-controlled, privacy-invasive, credential-harvesting, scraping, spam, malware, or security-testing activity unless expressly permitted under the Security Disclosure process. Users must not misrepresent supplier identity, buyer authority, quote commitments, certification status, stock, tax basis, lead time, pricing, contact rights, or product/service suitability.

16. Privacy, Cookies, and Data Requests

PGI's processing of personal data, contact data, account data, vendor profile data, buyer procurement data, cookies, deletion requests, correction requests, and support/grievance requests is governed by the Privacy Policy, Cookie Policy, Data Usage Policy, Data License Policy, Data Deletion Policy, Data Correction Policy, and Grievance/Support Policy.

17. Suspension, Termination, Takedown, and Correction

PGI may suspend, restrict, remove, correct, hide, review, or preserve any account, workspace, vendor profile, supplier label, contact field, RFQ record, quote, output, or workflow where required by suspected misuse, inaccurate data, unsupported claims, legal risk, security risk, privacy risk, vendor dispute, buyer dispute, operational risk, or closed-beta control. Relevant actions should be audit logged and escalated under internal SOPs where applicable.

18. Future Paid Subscription Placeholder and Inactive Payment Terms

The current closed-beta pack does not approve paid subscriptions, live payment collection, GST invoicing, vendor payouts, escrow, commission collection, paid ranking placement, refunds, chargebacks, or payment-provider processing. Payment-related documents are draft/inactive review materials only.

No payment workflow may be enabled until founder approval, lawyer review, CA/tax/GST review, payment-provider approval, operational approval, implementation review, and launch sign-off are complete.

19. Warranty Disclaimer

PGI is provided in closed beta on an evaluation and workflow-support basis. PGI disclaims warranties to the maximum extent permitted after professional review, including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, availability, uninterrupted operation, supplier suitability, vendor performance, price accuracy, stock accuracy, lead-time accuracy, tax correctness, logistics feasibility, quality, and compliance.

20. Limitation of Liability

Subject to final lawyer review and applicable law, PGI's liability should be limited for indirect, incidental, special, consequential, exemplary, punitive, lost profit, lost revenue, lost savings, procurement loss, production delay, lost opportunity, data loss, supplier failure, quote error, delivery failure, tax error, customs error, or reliance on Platform Informational Inferences. Any monetary cap, exclusion, jurisdiction-specific limitation, and enforceability treatment must be reviewed by counsel before paid/public production.

21. Indemnity

Subject to professional review, users should indemnify PGI for claims, losses, liabilities, costs, and expenses arising from unauthorized use, inaccurate submissions, misleading vendor data, unlawful buyer uploads, RFQ misuse, contact misuse, breach of confidentiality, IP infringement, privacy violations, security abuse, or violation of these Terms.

22. Governing Law and Dispute Resolution Placeholder

Governing law, venue, arbitration, court jurisdiction, consumer/business treatment, interim relief, and dispute escalation remain placeholders pending lawyer review and incorporation details. No production dispute-resolution clause is approved by this founder draft.

23. Notices, Support, and Grievance Route

Operational notices may be delivered through platform UI, account email, support channel, admin dashboard, or legal page updates. Support and grievance handling should route through the Grievance/Support Policy and internal grievance SOP.

24. Changes to Terms

PGI may update these Terms during closed beta. Material changes to required documents should trigger versioning, content hashing, route-map updates, notice matrix updates, acceptance logging, and re-acceptance where required.

Related Documents

• privacy-policy
• closed-beta-terms
• 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.