TECHNICAL TRANSPARENCY

Minimize identity. Preserve utility.

This page describes application-level data handling for security and infrastructure review. It is deliberately factual and is not presented as a substitute for a formal legal privacy notice.

IDENTITY

Pseudonymous by design.

Transport IP hint + user-agent + optional x-seenrelay-client are privacy-salted and hashed for frictionless lease continuity.

Transport materialRaw IP and user-agent are not used as database identity; the application derives privacy-salted operational fingerprints.

Observer provenanceSelf-asserted IDs and Ed25519 public keys are salted before persistence. Cryptographic proof still means key possession, not real-world identity.

Submission boundaryDo not submit credentials, private keys or unnecessary sensitive personal data. Credential-bearing source URLs are rejected and SeenRelay does not semantically inspect payloads with an LLM.

Environment integrityPreview/CI uses an isolated database. Production metrics are reserved for actual Production activity.

RETENTION

Keep evidence only as long as it serves a purpose.

Observation rows

configured evidence horizon

Observer/fact state

aligned pseudonymous state

Hive leases

30d

operational retention

Reuse events

90d

network utility evidence

Fact summaries remain available for STALE/latest-observed semantics until an explicit deletion policy removes them. Aggregate operational metrics are separate from raw observation evidence.

MACHINE REVIEW

Prefer structured disclosure?

Data practices JSON Service descriptor