Trust Graph Publication
Trust Graph Publication Policy
Effective date: July 2, 2026. This policy explains how Monocrat handles public Trust Graph claims, provenance, consent, correction, takedown, revocation, and account-deletion disposition.
1. Scope
The Monocrat Trust Graph is the public or agent-facing projection of verified business facts when the applicable source, provenance, freshness, consent, privacy, safety, and legal checks allow publication. This policy applies to Trust Graph pages, JSON-LD, MCP or agent-facing responses, public claim manifests, and Trust Graph publication support workflows.
This policy supplements the Terms of Service, Privacy Policy, Acceptable Use Policy, and Account & Data Controls.
2. Publication Standard
Trust Graph publication is for source-backed buyer-relevant business evidence, not marketing copy, paid placement, unsupported ranking, or cosmetic omission of gaps. A public claim must have an evidence basis, source refs safe to disclose or summarize, verification status, freshness status, scope, caveats, coverage metadata, and a publication decision that allows the public projection.
Monocrat does not convert missing, stale, contradictory, unfavorable, withheld, policy-blocked, consent-blocked, or not-attempted evidence into positive claims. Those states may be redacted or aggregated when public details would reveal private information, but they are not treated as favorable evidence.
3. Source Tiers And Consent
| Tier | What It Means | Publication Boundary |
|---|---|---|
| Public or source-policy-approved data | Information already public, official, licensed, customer-authorized for public use, or otherwise permitted by a source-policy review. | May publish only when the source policy, provenance, freshness, correction/takedown, privacy, safety, and legal checks pass. |
| Owner-approved business data | Your own business records, metrics, policies, or operational facts that do not reveal another party's private information. | Requires authenticated owner app/web review, source refs, freshness, caveats, publication preview, and audit evidence before publication. |
| Counterparty or customer data | Named customer, supplier, investor, partner, contractor, testimonial, relationship, or outcome claims involving another party. | Requires the needed owner authority and counterparty, customer, or source-owner consent for the exact claim and granularity. |
4. Publication Gates
Public Trust Graph publication, testimonial publication, consent outreach, revocation, private graph access-token changes, and other external-access decisions are high-stakes actions. Email, push, Inbox, app links, or previews may notify or deep-link, but they do not publish, revoke, request consent, expose private graph access, or complete external communication by themselves.
Monocrat may block or defer publication when source refs are missing, evidence is stale, a source policy does not permit the use, required consent is missing or revoked, the claim is unsafe or legally sensitive, the graph is too sparse, or a privacy/safety review requires a narrower public surface.
5. Public And Private Boundaries
Public Trust Graph surfaces do not expose raw private business records, raw support messages, order IDs, buyer PII, private payment details, private source refs, raw provider payloads, low-volume sensitive anecdotes, internal abuse/manipulation flags, legal or safety review details, private relationship triggers, or account deletion reasons.
When a public surface can safely show only aggregate or redacted coverage, Monocrat may publish a public-safe label, caveat, or count instead of the exact private source or reason. If the safe public projection cannot be made, the evidence remains internal or unpublished.
6. Counterparty Graphs And Network Signals
Monocrat may use customer operational context to identify counterparties for same-tenant internal enrichment. Public counterparty graphs or network signals can publish only from independently public, source-policy-approved, consented, or aggregate-safe evidence. Public outputs must not reveal which tenant, source record, relationship type, deletion event, or private operational trigger caused graph creation, refresh, or suppression.
Confidential, NDA, stealth, legal, competitive, personal-safety, or other sensitive relationships default to internal-only handling unless a public-source basis or consent record allows the exact projection. Aggregate network signals require tenant-policy permission, privacy and safety thresholds, and enough volume to avoid exposing individual relationships.
7. Corrections, Disputes, And Takedowns
If you believe a Trust Graph claim is inaccurate, stale, unsupported, overbroad, non-consented, source-policy-blocked, unsafe, or otherwise inappropriate for publication, contact privacy@monocrat.ai or legal@monocrat.ai. Include the graph URL or claim, the issue, your relationship to the business or claim, and any supporting evidence.
Monocrat may correct, caveat, narrow, unpublish, revoke, suppress, retain under review, or decline a request depending on the source evidence, consent state, public-source basis, legal duties, safety posture, and audit record. Disputed claims may be marked under dispute or removed from favorable public use while review is pending.
8. Revocation And Private Graph Access
A claimed graph owner may be able to revoke a public graph slug, change private graph access, or request that eligible claims be unpublished through authenticated product or support workflows. Revocation does not assign the old slug to another business. Private graph access tokens, if enabled, apply to all consumers, including agent consumers.
9. Account Deletion Disposition
Account deletion handles Trust Graph claims by provenance class. Public or independently source-derived claims may persist independently of the Monocrat account only when source policy, provenance, freshness, correction/takedown, safety, privacy, and legal review still support publication. Tenant-private-source-derived, Monocrat-generated, tenant-action-derived, tenant-consent-derived, and tenant-bound counterparty-consent-derived claims are deleted, unpublished, revoked, or recomputed with disposition evidence.
Public graph output does not reveal that an account deletion, tenant opt-out, consent change, private relationship, or support/legal event is the reason a claim is missing or suppressed. Account deletion and data access/export handling are described in Account & Data Controls.
10. Limits
Trust Graph publication may be disabled, limited, manually reviewed, or unavailable during private beta. A Trust Graph claim is not legal, tax, accounting, financial, credit, procurement, employment, medical, or other professional advice, and it is not a guarantee that an agent, buyer, vendor, partner, or regulator will reach any particular decision.
11. Changes
Monocrat may update this policy by posting an updated version or notifying affected users through another reasonable channel. The effective date identifies the latest version.