Contact Hidden Policy

Contact Hidden 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 Contact Hidden Policy governs how PGI protects supplier, vendor, and business contact details from broad disclosure, scraping, unauthorized outreach, and premature buyer-vendor communication. It binds buyers, vendors, administrators, support operators, and any workflow that displays or requests supplier contact access.

PGI supplier discovery does not automatically grant the right to view, export, scrape, message, call, resell, or bypass hidden contact information. Contact access is a governed workflow, not a marketplace entitlement.

2. Operational Definitions

• Contact Hidden means vendor or supplier contact information is not generally visible to buyers and is shielded by platform controls.
• Contact Request means a buyer-initiated request to access, invite, route, or communicate with a supplier under PGI workflow rules.
• Governed Access means access controlled by eligibility, acceptance, workflow context, rate limits, review, and audit logs.
• Hidden Contact Misuse means scraping, inference, manual harvesting, off-platform bypass, unsolicited outreach, or attempted circumvention of PGI contact controls.
• Supplier Discovery Output means any supplier list, profile, label, ranking, or suggestion shown to a buyer.

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. Contact Governance Architecture

PGI may keep contact details hidden for Potential Supplier, PGI Researched, Not Yet Claimed, Not PGI Verified, and other supplier profiles. Contact hiding supports privacy, data minimisation, source integrity, anti-scraping controls, vendor trust, and closed-beta operational governance.

Where contact access is enabled, PGI should record the user, organization, supplier profile, workflow context, accepted document version/hash, timestamp, source, and relevant approval status. Contact access can be rate-limited, denied, revoked, or escalated for review.

4. Buyer Rules

Buyers must not scrape, infer, harvest, purchase, resell, publish, or bypass hidden contact data. Buyers must not pressure PGI or vendors to expose contact details outside governed workflows. Buyers must not use supplier discovery labels as proof that a supplier wants outreach, is verified, is available, or accepts RFQs.

5. Vendor Rules

Vendors may submit contact details and contact-governance preferences subject to platform controls. Vendors are responsible for ensuring submitted contact data is accurate, authorized, and not personal data submitted without permission. PGI may hide or suppress contact data where needed for privacy, abuse prevention, source restrictions, or data-quality concerns.

6. PGI Operational Examples

7. Breach and Operational Response

PGI may suspend accounts, block contact requests, hide supplier profiles, revoke access, disable exports, rate-limit sessions, preserve logs, and escalate incidents when contact misuse is suspected. Severe misuse can trigger account termination, vendor/buyer notice, legal review, or security investigation.

8. Product UI and Acceptance Mapping

Related Documents

• vendor-terms
• vendor-data-policy
• vendor-verification-policy
• marketplace-labels-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.