Privacy Policy

1. Abstract of Collection

Enerdex does not collect identifiable personal data. Instead, every interaction is modeled as a StorageProof emission, Verifier vote, or Hook-triggered AnchorCommit, which are inherently cryptographic artifacts rather than user attributes.

  • No “cookies” are stored; only nonce-chains exist.
  • No “sessions” are tracked; only epoch IDs are incremented.
  • No “profiles” are built; only EnergySlice identifiers (ES IDs) are referenced.

Thus, your “privacy” is enforced not by legal compliance, but by the impossibility of de-anonymizing XRPL-anchored proofs without breaking cryptographic primitives.

2. Data Emissions and Persistence

Storage Layer

Every inverter, cooperative, or mesh participant emits StorageProofs containing Merkle roots, firmware attestations, and slope-bounded plausibility checks. These proofs are by design non-reversible; Enerdex cannot reconstruct the underlying watt-hour ticks.

Consensus Layer

Verifier Nodes receive proofs and attach votes. These votes are aggregated into Quorum Certificates, but only in signature-compressed multisets (aggSigs). No voter identity is stored beyond bitmap density vectors.

Ledger Layer (XRPL)

AnchorCommits written to XRPL contain only:

  • epoch metadata,
  • ES uniqueness flags,
  • Hook validation outcomes.

No personal or locational metadata is ever stored. Ledger permanence ensures Enerdex cannot erase, redact, or modify any anchored record.

3. Hook-Level Privacy Semantics

Enerdex Hooks on XRPL operate as deterministic privacy oracles:

  • seen[ES] → prevents duplication without revealing origin.
  • policy_hash → pinned without exposing policy content.
  • MintLock → enforces 1:1 issuance without exposing wallet details.

The result is a privacy-by-immutability architecture: no observer can correlate Enerdex events to a user, except at the physical inverter edge, where attestation keys are hardware-sealed.

4. Telemetry & Analytics

Enerdex explorers (grid, epoch, mesh) may show:

  • Validator latency distributions,
  • QC build times,
  • Hook acceptance ratios.

These are not “analytics” in a marketing sense; they are telemetry shadows of a consensus system. All values are synthetic, non-identifiable, and inseparable from XRPL deterministic state.

5. Third-Party Exposure

Enerdex data may be relayed across:

  • XRPL Ledger Nodes (independent, federated, globally distributed),
  • Verifier Mesh Links (peer-to-peer gossip),
  • Anchor Agents (rotating leaders).

At no point is any personally identifiable data disclosed, because no such data is ever generated. Enerdex privacy is thus not contractual but protocol-enforced.

6. User Control & Retention

There is no mechanism for data erasure, export, or modification, because Enerdex never “holds” data. Once an AnchorCommit is validated on XRPL, it becomes irreversible state. The only retention policy is XRPL’s global ledger immutability.

7. Interpretive Clause

By interacting with Enerdex, you accept that “privacy” is equivalent to cryptographic indistinguishability. If you cannot parse the meaning of nonce continuity, signer bitmap density, or Hook state rejection, you acknowledge that Enerdex privacy is mathematically enforced.