Misrepresentation Policy (Use of “Verified” Claims)

Effective date: [2025-12-20] Applies to: All users of Epistemic Vault services (Scale and ORG), Recorder apps, APIs/SDKs/CLI, and federation features Purpose: Prevent deceptive or inaccurate claims about what Epistemic Vault verification proves

1) Core principle

Epistemic Vault verification is a statement about cryptographic integrity and provenance consistency. It is not a statement about:

• factual truth,
• legality,
• ethics,
• intent, or
• court admissibility.

Any representation of Epistemic Vault outputs must preserve this boundary.

2) Prohibited claims (not allowed)

You may not state or imply that Epistemic Vault verification:

1. Proves the event happened as depicted
2. Confirms a story is true or “fact-checked”
3. Guarantees legality or consent
4. Guarantees court admissibility or provides “legal certification”
5. Guarantees the uploader/recorder is trustworthy
6. Proves there was no staging, coercion, or deception
7. Guarantees metadata accuracy beyond device-reported capture values
8. Represents endorsement by MiulusTek of content, persons, or organizations

This applies to:

• marketing materials,
• product UI/UX,
• media publications,
• social posts,
• legal filings and evidence submissions,
• partner integrations and API consumers.

3) Required framing (allowed claims)

When you reference verification publicly or in a user-facing interface, use claims that are:

• specific,
• cryptographic,
• non-interpretive.

Approved language examples:

• “Verified for cryptographic integrity and provenance consistency.”
• “This file passed Epistemic Vault integrity checks (hash/signature verification).”
• “Epistemic Vault verified that the file has not been altered relative to its cryptographic provenance.”

Short-form label (UI-safe):

• “Integrity verified (cryptographic).”

If space allows, include:

• “Verification is not a claim of truth.”

4) Proof bundles and receipts

You may describe Proof Bundles and Receipts as:

• “independently verifiable cryptographic artifacts,” and
• “offline-verifiable in many workflows,”

but you may not describe them as “court-certified” or “legal certification.”

5) Enforcement

MiulusTek may take enforcement actions if it determines, in its reasonable discretion, that a user or partner is misrepresenting verification results, including:

• requiring corrections or retractions,
• disabling misleading UI labels or marketing copy,
• suspending access to APIs or accounts,
• terminating accounts for repeated or severe violations,
• refusing federation interactions where misrepresentation creates ecosystem risk.

For ORG Edition deployments, organizations are encouraged to adopt an internal equivalent of this policy to protect downstream trust.

6) Reporting suspected misrepresentation

If you believe a party is misrepresenting Epistemic Vault verification, report it to:

• _abuse@epistemicvault.com
• Include links/screenshots and (if available) relevant asset IDs or receipt identifiers.

7) Relationship to Terms

This policy supplements the Terms & Conditions and does not limit other remedies. Violations may constitute a breach of the applicable Terms, EULA, Order Form, or enterprise agreement.