Privacy policy
At Omxus, our mission is to deliver secure, distributed public ledger frameworks and sovereign validation protocols that respect individual user privacy while preserving systemic trust. Whether you are interacting with our public coordination APIs, running a consensus verification node, or accessing the Omxus Client Workspace, we are deeply committed to safeguarding the data we collect or manage on your behalf.
This Privacy Policy applies to personal information gathered through our public websites, distributed interfaces, protocol APIs, and foundational applications (collectively, our "Services"). This policy does not apply to zero-knowledge state logs or raw transactional payload distributions verified directly on-chain by external third-party node networks.
1. Personal Data We Collect
We collect information that identifies or relates to you ("Personal Data") based on how you actively interact with our network layers:
Personal Data You Provide:
- Account Registration & Credential Matrix: When creating an account for the Omxus Workspace, we collect your profile name, verification contacts, email addresses, and cryptographic keys generated during system onboarding.
- Telemetry Inputs & User Configurations: We log preference metadata, specific network filters, and interface properties when you configure your public consensus dashboards or run state-tracking tools.
Personal Data We Collect Automatically:
- Node Metrics & Device Diagnostics: System status configurations, operating architecture parameters, validation speeds, processing constraints, and generalized geographic parameters derived from connection nodes.
- Cookie Registries & Local State Storage: We leverage lightweight, functional browser variables to preserve access tokens across active developer sessions securely.
2. How We Use Personal Data
We process gathered data points strictly to achieve predictable, stable application behaviors across our client ecosystems:
- To maintain, scale, and insulate the Omxus network infrastructure against active validation risks or structural data poisoning attacks.
- To verify cross-node synchronization rules and generate real-time public telemetry datasets regarding network stability.
- To respond cleanly to custom developer support inquiries or process system protocol updates seamlessly.
3. Disclosure of Personal Data
Omxus does not broker or commercialize your personal information. Data distributions are isolated entirely to infrastructure partners, legal enforcement mandates, or designated structural affiliates when processing validation routines.
4. Retention
We preserve underlying operational system indicators for as long as necessary to provide stable infrastructure service access. Temporary cache states are flushed automatically within 30 days unless legal safety or compliance constraints demand persistent state preservation.
5. Data Controls
You maintain direct authority over your data parameters. The Omxus Workspace includes dedicated utilities allowing clients to export historical interface telemetry records, purge historical identity vectors, or adjust specific synchronization defaults in real time.
6. Your Rights
Depending on regional laws, you have rights to access, amend, erase, or port your Personal Data. To submit an administrative privacy inquiry or invoke regional rights, contact our legal support desk at privacy@omxus.org.
7. Children
Our coordination services and infrastructure components are designed exclusively for mature operators. We do not intentionally harvest or verify details linked to children under the age of 13.
8. Security
We implement strict technical safeguards, multi-layered encryption, and isolating firewalls to neutralize structural access vulnerabilities. However, please be aware that no public internet channel or ledger broadcast ever guarantees absolute, uncompromised structural insulation.
9. Additional U.S. State Disclosures
State legal definitions require exact alignment detailing data management categories. The disclosure matrix below reviews how information is handled under our strict network rules:
| Category of Personal Data | Purpose of Use | Disclosure of Personal Data |
|---|---|---|
| Identifiers Account keys, system names, device IP registries, network contact points. |
To provision interface access, isolate malicious nodes, and verify structural system performance. | Core cloud host platforms, diagnostic frameworks, security operations networks. |
| Telemetry Records Node configuration paths, execution velocities, browser metadata metrics. |
To improve processing efficiencies and track systemic network consensus issues. | Infrastructure stability analysts, optimization tools. |
| Geolocation Indicators Coarse regional connection ranges derived via network handshakes. |
To route public ledger loads effectively and detect fraudulent data distribution spikes. | Localized structural verification clusters. |
10. Changes to the Privacy Policy
We will periodically update this policy document to match structural adjustments made to the Omxus protocol. Any structural changes will be announced clearly on this canvas alongside an updated reference timestamp.
11. Data Controller
For individuals located within sovereign administrative regions, the formal data processing entity remains the Omxus Foundation, headquartered at 1456 Third Street, San Francisco, California, United States.
12. How to Contact Us
If you have any specific concerns regarding data management choices, please submit a detailed inquiry to our data protection officer directly at dpo@omxus.org.