Data License Policy
- Version
- v0.4
- Status
- founder_draft
- Effective date
- TBD
- Last updated
- 2026-06-20
Full legal content
Data License Policy
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
This Data License Policy governs the rights PGI needs to operate buyer workflows, vendor workflows, supplier discovery, data quality controls, RFQ records, quote comparison, AI-assisted analysis, audit logs, and procurement intelligence during closed beta. It does not transfer ownership of buyer procurement data or vendor-submitted business data to PGI, and it does not authorize unrestricted resale, public disclosure, or public model training.
2. Operational Definitions
- Data Control Matrix means the allocation of ownership/control, platform operating rights, display rights, confidentiality limits, correction/deletion limits, and review obligations by data class.
- Buyer BOM/RFQ/Project Data means buyer-uploaded or buyer-created procurement records.
- Vendor Profile Data means supplier identity, categories, capabilities, public business facts, claim status, labels, and profile content.
- Vendor Offers/Rates/Stock/Lead-Time Data means dynamic commercial data submitted by vendors or gathered through governed sources.
- PGI-Researched Facts means supplier facts assembled from public sources, third parties, provider/API records, or internal research.
- AI Outputs and Review Flags means Platform Informational Inferences, confidence scores, low-confidence flags, uncertainty warnings, explanations, and human review results.
- PGI Taxonomy/Ranking Logic means PGI-owned category systems, capability maps, normalization rules, scoring logic, ranking explanations, data-quality models, and evaluation records.
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. Data Ownership and Control Matrix
| Data class | Primary owner/control | PGI operating license | Display rights | Correction/deletion limits |
|---|---|---|---|---|
| Buyer BOM/RFQ/project data | Buyer/authorized organization | Process, store, normalize, analyze, share through buyer-authorized RFQ, support, audit | Not public; RFQ-scoped only | Subject to project, audit, legal, dispute, security limits |
| Vendor profile data | Vendor/public-source mix depending on field | Store, normalize, display per label/visibility, route claims/corrections | Profile-visible per publication/contact-hidden rules | Correction/suppression route; public-source constraints apply |
| Vendor offers/rates/stock/lead time | Vendor/provider/source submitting data | Compare, display, warn, freshness-score, use for TLC assumptions | Workflow-visible with basis warnings | Can be expired, corrected, hidden, retained in audit |
| Public-source facts | Source-dependent | Index, normalize, label as researched/unclaimed/unverified | Limited profile display with labels | Source provenance retained; correction/takedown route |
| PGI-researched facts | PGI compiled from permitted sources | Use for discovery and data-quality workflows | Display only with PGI Researched/Not Verified labels | Review and correction route |
| Quote data | Buyer/vendor workflow parties | Store, compare, audit, support dispute workflow | Parties/admin-limited | Retention needed for commercial evidence |
| AI outputs/review flags | PGI-generated from inputs | Use for decision-support, quality control, review queues | Workflow-visible depending on context | Underlying data correction can trigger regeneration |
| PGI taxonomy/ranking logic | PGI | Proprietary operation and improvement | Explanations only, not full logic disclosure | Not user-owned; audit access internal |
| External provider data | Provider/source terms | Use according to provider policy and API agreement | Subject to provider/source restrictions | Must respect provider data terms |
| User feedback | Submitting user/org with PGI operational license | Improve product, data quality, notices, support | Internal/product review | Deletion subject to audit/security limits |
4. Rights Granted to PGI
Users grant PGI a limited, non-exclusive, revocable where feasible, worldwide operating license to host, store, parse, normalize, classify, structure, compare, summarize, display, route, transmit, audit, secure, support, and generate Platform Informational Inferences from submitted data solely for PGI platform operation, closed-beta review, data-quality improvement, support, security, legal-readiness, and professional review preparation.
This license does not authorize PGI to sell buyer confidential BOM/RFQ data as standalone data, publicly disclose buyer sourcing strategy, expose hidden vendor contacts outside governed workflows, or use confidential closed-beta procurement data for general-purpose public model training without reviewed approval.
5. Confidentiality Limits
Buyer confidential procurement data remains confidential to the buyer workspace and buyer-authorized RFQ recipients. Vendor profile data can be displayed based on publication rules, claim status, contact-hidden settings, and marketplace labels. Quote and RFQ records are visible only to workflow parties and authorized PGI personnel under role-based access and audit rules.
6. External Provider and Public Source Data
Provider/API and public-source data must carry source provenance, freshness, field trust, and usage restrictions where known. PGI must not strip source restrictions, fabricate verification status, or convert external provider data into guaranteed stock, price, lead-time, tax, or delivery claims.
7. Non-Training / Training Position
Closed-beta buyer confidential data, vendor contact data, RFQ/quote records, and support/grievance data should not be used for public or general-purpose model training without separate reviewed consent/notice architecture. PGI may use data to operate AI-assisted extraction, normalization, safety evaluation, quality control, and human review queues under the Responsible AI Policy.
8. Export, Correction, Deletion, and Retention
Data export, correction, deletion, suppression, retention, and audit handling are governed by the Data Export, Data Correction, Data Deletion, Data Retention, Vendor Correction, Privacy, and Audit Log policies. Deletion can be limited by legal evidence, security, RFQ/quote integrity, dispute handling, provider/source obligations, and audit requirements.
Related Documents
privacy-policydata-usage-policydata-retention-policydata-classification-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.