Data Usage Policy
- Version
- v0.4
- Status
- founder_draft
- Effective date
- TBD
- Last updated
- 2026-06-20
Full legal content
Data Usage 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 Usage Policy governs how PGI uses buyer, vendor, public-source, provider/API, workflow, audit, and AI-derived data for closed-beta procurement intelligence. It establishes operational limits for data processing, visibility, supplier discovery, BOM normalization, RFQ workflows, quote comparison, TLC assumptions, reports, quality review, and legal-readiness records.
2. Operational Definitions
- Permitted Platform Use means processing necessary for account operation, procurement workflow, supplier discovery, RFQ routing, quote comparison, TLC estimation, AI-assisted extraction, support, security, audit, and legal-readiness.
- Restricted Data Use means use that would publicly expose confidential buyer procurement data, bypass contact-hidden controls, treat unverified supplier data as guaranteed, or train broad public models without reviewed approval.
- Data Quality Warning means a visible notice identifying stale, incomplete, conflicting, low-confidence, inferred, or unsupported data.
- Field Trust means a trust level attached to a data field based on source type, evidence, freshness, vendor confirmation, verification status, and conflict history.
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. Permitted Data Uses
PGI may use data to create accounts, manage workspaces, process BOMs, normalize MPN aliases, classify categories, map materials/processes/UOM, produce RFQ workflow records, display potential supplier profiles, apply contact-hidden controls, compare quotes, estimate total landed cost assumptions, generate procurement reports, maintain audit logs, respond to support/grievance requests, improve data quality, and prepare professional review materials.
4. Restricted Data Uses
PGI must not use closed-beta buyer confidential procurement data to publicly reveal a buyer's sourcing needs. PGI must not publish hidden supplier contact data except through governed workflows. PGI must not use data to claim guaranteed supplier verification, guaranteed price, guaranteed stock, guaranteed lead time, guaranteed delivery, guaranteed quality, or guaranteed GST/tax treatment.
PGI must not use commission, paid plan, billing status, credits, sponsored status, or commercial relationship to influence organic supplier ranking unless a separate professionally reviewed sponsored placement policy exists and the placement is clearly disclosed.
5. Visibility and Notice Architecture
| Data/output | Required control |
|---|---|
| Buyer BOM/RFQ data | Confidential workspace and RFQ-scoped visibility |
| Vendor profile data | Label and publication controls |
| Vendor contact data | Contact Hidden by default unless governed access applies |
| Quote data | Party-specific visibility and audit record |
| TLC estimates | Assumption table and data-quality warnings |
| AI outputs | Decision-support warning, confidence, human review where needed |
| Public-source facts | Source/provenance, freshness, and Not PGI Verified labels |
| Admin/security logs | Internal-only least-privilege access |
6. PGI-Specific Examples
| Scenario | Required data-use treatment |
|---|---|
| Buyer uploads ambiguous “MS plate 5mm” | Normalize with low-confidence material/process flags; require buyer validation before RFQ. |
| Vendor stock data is 14 days old | Mark stale; downgrade trust; avoid presenting as guaranteed available stock. |
| Quote excludes GST and freight | Display basis warning before quote comparison or TLC estimate. |
| Supplier profile is PGI Researched and Not Yet Claimed | Display labels and avoid verification or endorsement language. |
| Mouser unit price is lower than a local supplier | Compare only with FX, freight, duty, GST, brokerage, MOQ, delivery, and source confidence assumptions. |
7. Breach, Misuse, and Operational Response
Misuse includes unauthorized upload, scraping, contact harvesting, false profile claims, unsupported certifications, misleading rates/stock, RFQ spam, reverse engineering, data exfiltration, and using AI outputs as final professional advice. PGI may suspend accounts, restrict workflows, hide data, correct fields, queue records for review, preserve logs, and escalate under internal SOPs.
Related Documents
privacy-policydata-license-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.