LEGAL AND POLICY DISCLOSURE

GENTIF™ Certification and Directory Policy

Certification, proof page, badge, Trust Registry Record, domain ownership, supersession, lifecycle status, and non-endorsement policy.

Last updated: 2026-06-11 · Beta release policy set: v1.9.5j

Non-endorsement rule: GENTIF™ classifies and certifies conformance to structured declarations. GENTIF™ does not endorse, recommend, rank, guarantee, audit, or warrant listed websites or their content.

1. What GENTIF™ certification means

A GENTIF™ certification or proof page means that a Digital Entity, domain, site, or organization has completed specified GENTIF™ workflow steps for a Trust Declaration, Trust Assertion set, Trust Credential, registry record, or certification record. Certification may include domain control verification, declaration structure, credential status, timestamps, and registry conformance checks.

2. What GENTIF™ does not certify

Unless explicitly stated in a separate written agreement, GENTIF™ does not certify the truth, legality, safety, quality, security, financial condition, ownership chain, licensing, professional status, regulatory compliance, editorial accuracy, or business practices of a site or organization.

3. Self-declared classifications

Categories, maturity tiers, content classifications, industry labels, and directory descriptions are generally self-declared or customer-submitted unless marked otherwise. GENTIF™ may require edits, restrict categories, exclude sensitive categories, or require manual review.

4. Directory policy

The directory is a neutral Trust Registry discovery surface for published registry records and conformance status. It is not a ranking system, recommendation engine, marketplace endorsement, or quality score. GENTIF™ may order listings neutrally, hide beta or unapproved entries, remove expired or revoked entries, exclude high-risk categories, and display disclaimers.

5. Proof pages and badges

Badges and proof pages display Trust Credential, Trust Declaration, registry, certification, or lifecycle status. They must not be used to imply endorsement, guarantee, safety approval, legal compliance, or superiority. Users must not alter badge code, misrepresent status, hide revocation, or display a badge for an unverified or unrelated domain.

6. Verification methods

GENTIF™ may support root-file, DNS TXT, meta tag, hosted proof, badge, sitemap, and other methods. Strong methods may be required for ownership control, supersession, certification, and sensitive changes. Hosted proof or badge proof may assist setup but may not be enough to supersede a verified owner.

7. Supersession and archive

When current domain control is proven, GENTIF™ may allow a verified owner to supersede stale, agency, contractor, or manager-held control. Prior manager work product may be preserved as a read-only archive for dispute history but does not preserve control rights.

8. Revocation and review

GENTIF™ may suspend, revoke, expire, delist, or require manual review of credentials, declarations, badges, proof pages, directory entries, and ownership claims where records are disputed, stale, inaccurate, harmful, unauthorized, risky, abusive, or inconsistent with policy.

9. Abuse reports

Public abuse reports and internal reviews support reactive enforcement. GENTIF™ may review reports, request information, restrict content, suspend accounts, or revoke credentials. GENTIF™ does not undertake to proactively police every website or all third-party content.