Registry Policy

1. Purpose of oneentity.id

oneentity.id is the canonical public read-only resolver for stable Entity-ID records.

The purpose of oneentity.id is to provide stable public resolution for Entity-ID records while those records are active, maintained, compliant with this Registry Policy, and paid where applicable.

oneentity.id is not a social network, identity verification provider, certificate authority, public authority, official government register, credit bureau, background-check service, or general-purpose hosting platform.

Registration, claiming, record management, and billing are handled separately through myentity.id. Public resolution happens on oneentity.id.

2. Operator

oneentity.id is operated by:

eeoom
Wittenbauerstrasse 61
Graz, Austria
Email: contact@oneentity.id

The operator may change over time, including through business transfer, assignment, reorganization, incorporation, merger, sale, or delegation of operation.

3. Definitions

Registry means the oneentity.id identifier namespace, resolver, records, lifecycle rules, and related operational systems.

Record means a public or internal Entity-ID record managed under this Registry Policy.

Record holder means the person, organization, or account responsible for registering, maintaining, paying for, or requesting public resolution of a record.

Entity UID means the stable internal identifier assigned by the registry, such as an identifier used in a stable @id.

Public slug means a human-readable alias or resolver path, such as a name-based URL.

Public resolution means the public serving of a record through oneentity.id, including HTML, JSON-LD, redirects, structured data, sitemap inclusion, or other public output.

Active lifecycle status means that a record is active, maintained, compliant, and paid where applicable.

4. Public resolver only

oneentity.id is a public read-only resolver.

This domain is intended to serve public records, structured data, resolver pages, robots.txt, sitemap files, and related read-only outputs.

oneentity.id does not provide login, billing, claim, edit, admin, or write functions on this domain.

5. Active public resolution

Public resolution is an active maintained service, not an indefinite archive.

Active public resolution of a oneentity.id record requires an active lifecycle status, including payment where applicable.

A record with active lifecycle status may be publicly resolvable and may be eligible for HTML output, JSON-LD output, sitemap inclusion, links, metadata, redirects, and other public resolver functions.

If a record expires, remains unpaid, is abandoned, becomes inactive, is suspended, is disputed, violates this Registry Policy, creates legal or security risk, or otherwise requires registry action, the registry may restrict, suspend, remove, archive, discontinue, or stop public resolution of the record.

6. Stable Entity UIDs

Stable entity UIDs are designed for long-term stability and are not intentionally reassigned to a different entity.

However, non-reassignment of an Entity UID does not create a right to perpetual public resolution, hosting, display, indexing, structured data output, redirects, recovery, or continued publication of record data.

A stable Entity UID may remain internally reserved even if the public record is no longer resolved, displayed, indexed, maintained, or published.

7. Public slugs and aliases

Public slugs are registry-managed aliases used for human-readable public resolver URLs.

Public slugs are not property and do not create ownership rights, trademark rights, name rights, priority rights, exclusivity rights, or other rights in a name, brand, trademark, personal name, organization name, product name, work title, keyword, or identifier.

No person or organization has an automatic right to any specific public slug, even if the slug matches their legal name, business name, brand, trademark, domain name, username, product name, work title, or other identifier.

Slugs may generally be allocated on a first-come, first-served basis, but only subject to registry discretion, eligibility, availability, payment where applicable, reserved names, rights conflicts, abuse prevention, policy compliance, and applicable law.

The registry may refuse, reserve, hold back, assign, change, rename, redirect, suspend, restrict, release, or reassign public slugs at its discretion where necessary or appropriate to protect registry integrity, prevent confusion, prevent impersonation, address rights conflicts, comply with law, reduce abuse, support technical operation, or enforce this Registry Policy.

The registry may maintain reserved slugs, protected slugs, premium slugs, blocked slugs, sensitive slugs, or internally restricted slugs. The registry is not required to make any specific slug available for registration or public use.

A public slug may be changed or removed without changing the stable Entity UID. The stable Entity UID, not the public slug, is the primary persistent identifier principle of the registry.

8. Grace period and recovery period

If a record expires or payment fails, the registry may provide a limited grace period.

During the grace period, the registry may continue public resolution to avoid accidental disruption, but it is not required to provide public resolution indefinitely.

After the grace period, the record may enter a recovery or redemption period. During this period, the previous record holder may be allowed to reactivate the record subject to the current policy, current pricing, payment, account status, and registry discretion.

Unless otherwise stated:

• Grace period: 14 days
• Recovery period: 30 days

The registry may shorten, extend, suspend, or skip these periods in cases of abuse, fraud, impersonation, rights conflict, legal requirement, security risk, chargeback, policy violation, or operational necessity.

9. Final expiry, purge, and reserved UID stub

If a record is not renewed or recovered within the applicable grace and recovery periods, public resolution may be discontinued.

The resolver may return 404 Not Found, 410 Gone, or another appropriate non-resolving status.

After final expiry, discontinuation, or purge:

• the public profile may be removed;
• JSON-LD output may be removed;
• sitemap inclusion may be removed;
• sameAs, links, metadata, redirects, and structured data may be removed;
• public record data may be deleted or minimized;
• the registry may retain only a minimal internal reserved identifier stub to prevent intentional reassignment of the stable Entity UID.

The registry has no obligation to provide indefinite public resolution, hosting, display, indexing, structured data output, redirects, recovery, or continued publication for unpaid, expired, abandoned, inactive, suspended, disputed, unlawful, abusive, or non-compliant records.

10. Data minimization after expiry

Discontinuing public resolution and deleting or minimizing record data after expiry helps prevent abandoned, outdated, unwanted, or no longer authorized personal and entity data from remaining publicly available indefinitely.

Where a record contains personal data, the registry may delete, redact, or minimize record data when the record is no longer active, no longer maintained, no longer paid where applicable, or no longer necessary for the purposes for which it was processed.

The registry may retain limited internal reservation, lifecycle, security, billing, audit, dispute, abuse-prevention, or legal-compliance data where necessary and permitted by applicable law.

11. Record holder responsibilities

Record holders are responsible for ensuring that submitted record data is accurate, lawful, non-misleading, current, and authorized.

Record holders must not submit, maintain, or request publication of records that:

• impersonate another person or organization;
• falsely imply affiliation, authorization, ownership, employment, endorsement, or official status;
• infringe trademarks, name rights, copyrights, privacy rights, personality rights, or other third-party rights;
• contain unlawful, misleading, fraudulent, abusive, defamatory, harassing, unsafe, or harmful content;
• expose personal data without an appropriate legal basis or authorization;
• create safety risks, doxxing risks, harassment risks, or risks to minors or vulnerable persons;
• manipulate search engines, AI systems, crawlers, or knowledge graphs through deceptive or abusive practices.

12. Payment and active lifecycle status

Payment may be required for registration, reservation, lifecycle maintenance, and active public resolution of an entity identifier.

Payment does not verify identity, authority, ownership, affiliation, rights, or factual accuracy.

Payment is a registry access and lifecycle requirement. It may help reduce abuse, abandoned records, unauthorized records, spam, and outdated public data, but it does not constitute endorsement, certification, or verification by the registry.

Refunds are excluded to the maximum extent permitted by applicable law, especially where registry allocation, reservation, activation, lifecycle handling, or technical processing has already occurred. Mandatory statutory rights remain unaffected.

13. No public verification status

oneentity.id does not provide a public “verified” badge or general verification status.

The registry may perform internal eligibility, control, authorization, or abuse checks for operational purposes. Such checks are used to decide whether a record or field may be displayed, exposed, restricted, downgraded, or removed.

Internal checks do not imply that the registry certifies the full truth, accuracy, authority, ownership, affiliation, legality, or current validity of a record.

14. External links and structured identity signals

Record holders may submit external websites, profiles, references, and links.

Some fields and links may create strong identity, ownership, affiliation, authorship, or equivalence signals. This includes sameAs links, official websites, social profiles, organization roles, brand relationships, works, products, and identifiers.

The registry may classify submitted links based on evidence of control, authorization, account connection, reciprocal reference, domain control, documentation, administrative review, or other eligibility signals.

Submitted links may be displayed publicly before they are internally reviewed. Until sufficient eligibility evidence is accepted by the registry, such links may be treated as external references, marked with attributes such as rel="nofollow" or rel="ugc", exposed only through weaker structured data fields such as subjectOf, excluded from structured data, or not displayed at all.

The public display of a submitted link does not mean that the registry has accepted the link as a strong identity signal, identity-equivalence signal, ownership signal, affiliation signal, endorsement, certification, or verification.

Links with sufficient evidence may be exposed as stronger identity signals, including schema.org sameAs or HTML rel="me".

The registry may also accept manual administrative review, contractual authorization, client onboarding evidence, written authorization, prior business relationship, or other evidence deemed sufficient by the registry operator as a basis for exposing a link or field as a stronger structured identity signal.

Administrative acceptance of a link or field is an internal eligibility decision only. It does not create a public verification status, certification, endorsement, warranty, or guarantee of identity, authority, ownership, affiliation, or factual accuracy.

The registry may change link classification requirements over time. Fields or links previously accepted may later be hidden, removed, downgraded, excluded from JSON-LD, marked nofollow, require renewed eligibility checks, or stop being displayed.

The registry may remove, downgrade, relabel, nofollow, exclude, or stop displaying links that are unconfirmed, disputed, misleading, inactive, unavailable, unsafe, unlawful, abusive, or inconsistent with this Registry Policy.

15. Domain and account control signals

For organization records, brand records, product records, service records, event records, and other records connected to a domain or external account, the registry may require proof of control or authorization.

Accepted control methods may include, without limitation:

• DNS TXT records;
• files under /.well-known/;
• HTML meta tags;
• reciprocal links;
• reciprocal structured data references;
• supported account connection methods;
• payment/account evidence;
• documentation;
• other methods accepted by the registry.

The registry may require renewed control checks if a domain changes ownership, a link becomes unavailable, a dispute arises, or the registry changes its eligibility requirements.

16. Suspension, restriction, and removal

Non-payment, expiry, abandonment, inactivity, abuse, fraud, impersonation, rights conflicts, legal requirements, security concerns, safety risks, disputes, or violations of this Registry Policy may result in suspension, restriction, removal from public resolution, archival, purge, or eventual discontinuation of the record.

The registry may take action without prior notice where necessary to protect users, affected persons, third-party rights, registry integrity, infrastructure, security, legal compliance, or public safety.

The registry may refuse, restrict, suspend, remove, or discontinue records involving minors, vulnerable persons, safety risks, harassment, doxxing, impersonation, or other sensitive circumstances.

17. Rights conflicts and disputes

The registry may reserve, suspend, transfer, rename, redirect, restrict, or remove slugs and records in case of trademark, name, identity, impersonation, ownership, authorship, affiliation, rights, or confusion conflicts.

The registry is not required to resolve all disputes between third parties and may require parties to obtain appropriate legal, administrative, contractual, or judicial resolution.

The registry may take interim action while a dispute is pending.

18. No guarantee of accuracy or third-party acceptance

Records may contain user-provided, registry-maintained, partially checked, or unverified information.

The registry does not guarantee that all record data is complete, current, accurate, lawful, suitable for a particular purpose, or accepted by third parties.

The registry does not guarantee that search engines, AI systems, crawlers, browsers, directories, knowledge graphs, platforms, or third-party services will index, display, cite, rank, understand, trust, accept, or continue to access any record.

19. Availability, outages, and third-party infrastructure

The registry is designed for reliable long-term operation, but oneentity.id does not guarantee uninterrupted, error-free, or continuous availability of the registry, resolver, website, APIs, redirects, metadata, JSON-LD output, or any related service.

Public resolution may be temporarily unavailable, delayed, degraded, cached, inconsistent, or interrupted due to maintenance, updates, security measures, abuse mitigation, software defects, operational incidents, DNS issues, network problems, third-party infrastructure failures, hosting provider outages, CDN outages, force majeure events, legal requirements, or other circumstances inside or outside the registry operator’s reasonable control.

The registry operator may perform maintenance, deploy changes, restrict traffic, rate-limit requests, block abusive access, or temporarily disable parts of the service to protect the security, integrity, stability, or lawful operation of the registry.

Temporary unavailability, degraded performance, caching delays, crawler access issues, indexing delays, DNS issues, CDN outages, or failures by third-party systems to access, process, display, cite, or resolve a record do not constitute a breach of the persistence principle.

Identifier persistence and service availability are separate concepts.

20. Abuse prevention and access restrictions

The registry may rate-limit, block, challenge, restrict, or temporarily disable access to protect security, availability, lawful operation, abuse prevention, infrastructure integrity, or registry integrity.

Public resolver access does not create a right to unrestricted scraping, automated extraction, abusive crawling, excessive requests, circumvention of technical controls, or use that harms the registry or affected persons.

21. Registry continuity, transfer, and discontinuation

The registry is designed for long-term operation and stable identifier resolution. However, oneentity.id does not guarantee perpetual operation of the registry, perpetual hosting, or indefinite public resolution of records.

The registry operator may modify, transfer, assign, merge, reorganize, delegate, archive, wind down, or discontinue the registry or parts of its services for business, legal, technical, security, operational, or economic reasons.

Where reasonably practicable, the registry operator may provide advance notice before a material discontinuation of the registry and may provide export, archival, redirect, or transition mechanisms. The availability, scope, and duration of such mechanisms remain at the registry operator’s discretion.

No record holder is entitled to perpetual free hosting, perpetual public resolution, continued operation of any specific resolver, URL, namespace, feature, field, output format, or service.

Persistent identifiers are a design goal and registry principle, not a guarantee of perpetual operation, hosting, indexing, display, citation, error-free availability, or continuous public resolution.

22. Legal requests and compliance

The registry may restrict, suspend, remove, disclose, preserve, or process records and related data where required or reasonably necessary for legal compliance, regulatory requests, court orders, law enforcement requests, rights enforcement, dispute handling, security, fraud prevention, abuse prevention, or protection of affected persons.

23. Changes to this Registry Policy

The registry may update this Registry Policy over time.

Changes may be necessary due to legal requirements, operational experience, abuse patterns, technical changes, business changes, lifecycle changes, pricing changes, or changes in registry design.

Continued use, maintenance, payment, renewal, or public resolution of a record after a policy change may be treated as acceptance of the updated policy, to the extent permitted by applicable law.

24. Governing law and jurisdiction

This Registry Policy is governed by the laws of Austria, excluding conflict-of-law rules and without prejudice to mandatory consumer protection rights where applicable.

Place of jurisdiction, to the extent legally permitted, is Graz, Austria.

25. Relationship to other legal documents

This Registry Policy may be supplemented by additional Terms of Service, Privacy Policy, Legal Notice, payment terms, claim rules, abuse procedures, or lifecycle documentation.

In case of conflict, the more specific document may apply to the relevant subject matter.