This Privacy Notice describes how Registry//9 handles information submitted through this public website and through early access communications.

Registry//9 is a public-facing intelligence interface for property incident signals, entity traces, manager resolution and operator-specific routing. This notice covers the public site, access request flow and related business communications.

When you request access, contact us or communicate with Registry//9, you may provide business contact information such as your name, company, work email, website, operator category, territory, signal interests and workflow notes.

The current access request interface prepares an email packet. If you choose to send that email, the submitted information is transmitted through your email client and received by Registry//9 for review.

We use submitted information to review operator fit, understand territory and signal-class requirements, configure early access, respond to inquiries and improve the public-facing interface.

Access is reviewed by operator type, territory, signal class and commercial action path. This helps preserve signal quality, constrain buyer overlap and keep each operator aligned with records they can actually use.

Registry//9 may reference public records, municipal datasets, property metadata, enforcement activity, ownership records and other publicly available or commercially available information surfaces.

Derived outputs may include signal classes, asset context, entity traces, manager candidates, contact surfaces, confidence indicators and operator-specific routes. These derived outputs are intended to support commercial review workflows, not to replace professional judgment.

Where Registry//9 presents manager, owner or contact information, confidence should be understood as an operational indicator. A contact surface may be verified, probable or candidate depending on the underlying basis.

The presence of a signal, contact or route does not guarantee buyer intent, claim eligibility, legal liability, repair scope, code status or any particular commercial outcome.

We may use infrastructure, hosting, analytics, email and operational service providers to run the public site and respond to access requests.

These providers are used for normal business operations. We do not design the public site around selling submitted access request data as a standalone list.

We retain access request information and business communications for as long as needed to evaluate access, operate the service, maintain records and improve the Terminal experience.

If an access request is not relevant to Registry//9, we may delete, archive or ignore the submitted packet at our discretion.

For privacy-related questions about the public site or access request process, contact Registry//9 using the access request channel or the business contact method provided during direct communication.