Rhea ID
A planned verified-identity layer — coming soon.
Rhea ID is coming soon. It is not currently generally available, and everything on this page describes intended future behavior.
01 — The problem
Repeated identity checks, unnecessary exposure.
Users are repeatedly asked to upload documents, complete verification checks, and share more personal information than a given decision actually requires. Organizations then become responsible for collecting and protecting that sensitive data again and again.
This creates friction for users and unnecessary handling of personal information across services.
02 — What it's intended to establish
Verified identity or a specific attribute, confirmed on demand.
Rhea ID is planned to establish verified identity or specific identity attributes for services that choose to require them, while reducing repeated exposure of unnecessary personal information.
Rhea ID is intended to let a service confirm a required identity fact or attribute without requiring the user to repeatedly distribute more personal information than the decision requires.
03 — Planned examples
Illustrative, planned attribute confirmations.
None of the following exist today. They describe the intended future direction only.
- Status: Coming soon
Confirm a person satisfies an age requirement.
- Status: Coming soon
Confirm a verified organizational role or representative status.
- Status: Coming soon
Confirm a required identity or residency attribute.
- Status: Coming soon
Connect a verified attribute to an authorization decision when a participating service chooses to require it.
04 — How it fits
RED · Rhea Key · Rhea ID.
RED protects and governs sensitive file content today. Rhea Key provides cryptographic authentication, signing and approval today. Rhea ID is planned to add verified identity or attribute confirmation as a separate, optional layer that a participating service could choose to require.
05 — What it will not do
Rhea ID is not required for current RED protected-file operations. Services will choose whether a verified identity or attribute is required.
Rhea ID does not carry RED protected-file contents.
Rhea ID is coming soon.
These interfaces are not currently generally available. Public technical documentation will be published only when the corresponding integration surfaces are ready.