Your organization
Choose providers and define the resource, action and scope a person, application or assistant may use.
Honesty · Neutrality · Security
Customer authority. Clear architectural safeguards.
Rhea brings defined permissions, protected-content handling and attributable activity together. Customer control starts with a clear view of who can act, where work happens and how each party handles data.
Who holds what
A deliberate division of responsibility.
Customer authority guides the work. Rhea coordinates supported requests. Your chosen providers continue operating.
Rhea Data
Check authorized work, process necessary operational metadata and preserve attributable Rhea activity.
Your infrastructure
Keep your provider accounts, storage and billing. Content paths and credential handling follow the selected connection mode.
For independent sign-in, the Rhea Key device approves and the participating website verifies the signed response before creating its own session. Data access remains a separate permission decision.
Architectural detail
Content, keys, metadata and authority are not the same thing.
- 01
Protected content
Protected file content is encrypted on the authorized client before storage where that protection model applies. Your provider stores ciphertext; operational metadata is handled separately.
- 02
Keys and sign-in
Rhea Key uses device-held cryptographic keys for passwordless sign-in. Its zero-custody design goal keeps private sign-in keys under the person’s control. Device setup and recovery depend on the supported product flow.
- 03
Two sign-in verification paths
Direct RK-1 verifies the device-signed proof against the stored site challenge. OIDC verifies an issuer-signed identity token against the issuer’s published keys. Your website creates its session only after the checks required by its chosen flow. Device-reported assurance is not hardware attestation or certification.
- 04
Server-side responsibilities
Authorization, rate limits, billing and audit metadata run server-side. Data also includes a ciphertext relay/copy fallback and server-generated audit PDFs. Client-side content handling does not mean all computation happens on your device.
- 05
Granted access
Supported routine work can continue within an authorized session or connection. Sensitive operations can require a separate explicit approval. Review activity and disconnect when needed. Applications and assistants remain limited to their granted permissions and enabled interface operations. Sensitive work may require separate explicit approval.
- 06
Revocation
Disconnecting stops further access. It cannot undo completed actions or data already disclosed. Review activity separately from deciding whether a connection should continue.
Inspect content, key and credential responsibilities
| What it is | Where it is handled | Responsibility | Important boundary |
|---|---|---|---|
| Protected file content | Encrypted and opened on the authorized client in the applicable protection mode; stored with the provider. | Customer controls access and content-key handling. | This does not make operational metadata invisible or make every transfer mode identical. |
| Operational metadata | Rhea services process information needed for permissions, activity, usage and billing. This can include personal data. | Rhea and the customer have responsibilities defined by the product mode and applicable agreement. | Content encryption does not mean no server-side data processing. |
| Rhea Key sign-in private key | Held by the Rhea Key device; the device signs the site-bound request. | The person approves; the participating website verifies the proof. | The sign-in key is not a storage-provider credential or proof of legal identity. |
| Customer-held provider credentials | Used in the authorized browser in that custody mode. | The customer supplies credentials; Rhea still checks authorized object and operation. | Browser signing does not remove server authorization or prove all operations are enabled. |
| Server-managed provider credentials | Handled by the server-managed connection path. | That mode has different credential-custody and server responsibilities. | Do not apply the customer-held mode's credential boundary to every connection. |
| Authorization, audit and usage records | Processed by Rhea services to enforce access and account for work. | Rhea enforces supported checks; customers review recorded activity and scope. | Audit visibility is not data deletion. Revocation stops future access, not earlier disclosures. |
Evaluate the integration
Trace the workflow you intend to use.
Match the requested operation to its interface, granted scope and execution mode. For sign-in, follow the site-issued request through device approval to backend verification and session creation.
Neutrality
Neutral means working alongside everyone — and staying accountable.
Neutrality means customer choice, portability and constructive cooperation across competing ecosystems. Transparent rules and customer-controlled access support that direction. These principles guide how Rhea works with providers; they do not depend on exclusive partnerships.
- 01
Provider choice
No preferred cloud or platform. Customers choose supported connections; Rhea works alongside their providers, which keep operating and billing.
- 02
Transparent rules
How access and approval decisions are made should be documented and inspectable, not hidden.
- 03
Customer control
Customers hold the authority over their data, keys and disclosures. Rhea is designed to serve that authority, not replace it.
- 04
Interoperability
Consistent interfaces let customers work across supported provider connections without treating them as one provider.
- 05
Portability
Moving between providers should be a choice, not a captivity. Rhea aims to make leaving as easy as joining.
- 06
Clear governance
Clear, inspectable rules and accountability are part of Rhea’s neutrality principles. Customers should be able to understand who controls access and how decisions are made.
Integration references
Technical guides
Use the Data storage-signing and Key sign-in guides to understand integration responsibilities. No independent audit or certification reports are claimed.
Data · Key guidesSecurity and privacy
Clear routes to report and request.
Report a vulnerability privately, request security documentation or ask about data-protection responsibilities through the appropriate Rhea contact.
Continue
See the architecture behind your requirements.
Follow Data’s supported interfaces and request signing, or Key’s independent authentication and backend verification.