The words we use, defined once.

Terms

AI agent (in Rhea Data)

An assistant that works inside Rhea Data from chat on a person’s authority, within granted permissions. The documented interface supports metadata, folders and version review under organization-level read scopes.

API

An interface applications use to make requests. Rhea Data offers one API across connected providers, within available operations and granted permissions.

Approval

An explicit, cryptographically confirmed decision by a person to allow a specific action.

Authentication

Checking who is signing in. Rhea Key provides a cryptographic proof that the participating site verifies before creating a session.

Authorization

Deciding what a person, application or assistant is allowed to do. Signing in does not grant unrestricted access.

Configured connection

A relationship to a customer-chosen system. Configuration or request signing does not itself move content or prove that an operation is enabled in production.

Connected provider

Customer-owned storage connected to Rhea Data. The storage-signing reference describes implemented request paths; enablement and available operations are confirmed separately.

Content-transfer path

Where content actually travels during a selected operation. An authorized-client direct path and a ciphertext relay/copy fallback have different handling and credential boundaries.

Control layer

An independent layer that coordinates identity, permissions and supported work across connected systems. A control relationship does not mean all underlying content travels through Rhea servers.

Encryption before storage

Protected file content is encrypted on the authorized client before storage. Your provider stores ciphertext; operational metadata is handled separately.

First factor

The primary method a website uses to authenticate a sign-in. Rhea Key can replace a password rather than adding a step after it. It is not proof of civil identity.

Future vision

Planned capabilities rather than operating services, including the next compute and data center chapter and the long-term silicon direction.

Grant / scope

The defined authority given to a person, application or assistant: what work is allowed and which resources it covers. Each request is checked against that scope; the available granularity depends on the interface.

In-app audit history

How far back you can view activity inside Rhea Data. This visibility window is not a schedule for deleting records.

Metadata

Information describing data or activity, such as a name, version, update date, requester or outcome. It is distinct from protected content and may still be personal data.

Neutral Global Data Layer

Rhea’s independent infrastructure direction: customer-controlled data work across connected systems through Rhea Data, and passwordless sign-in on participating websites through Rhea Key.

Next strategic chapter

Rhea’s decided move into physical infrastructure — compute and data centers — after the digital foundation. A committed direction, not current operations.

Nonce

A one-time request value used to bind a proof to the request that asked for it.

Processed data

Content handled or transferred during the month. It is not purchased storage capacity or the size of all your stored data.

Provider

A service that stores customer data. Rhea Data connects available integrations while the provider continues to hold and bill for storage.

Provider-neutral

Not tied to, or favouring, any single storage, cloud or platform provider.

Recorded activity

Attributable Rhea Data activity that identifies the actor, requested work and recorded outcome. It does not mean every event in every external system is observed.

Relay

An end-to-end encrypted fallback transit path used when a firewall, proxy or CORS policy blocks direct bucket communication. Relayed transfers count 5× from the first byte; direct transfers count 1×.

RK-1

Rhea Key’s site-bound cryptographic sign-in protocol. A relying backend issues a single-use browser-bound challenge, verifies the signed response and creates its own session.

Signed storage request

A provider request with a cryptographic signature or access signature. It follows authorization; it does not itself prove every connector operation is enabled.

Unlimited Data entities

Unlimited seats, storage connections, machine identities, AI agents, documents and folders. These counts are not consumption: the monthly data allowance still applies.

Unlimited Key saved connections

Saved quick-access relationships between a cryptographic address and a participating website. Unlimited saved connections apply only to the selected, verified paid address; other addresses on the account do not inherit it. This is not a charge per sign-in.

Zero-custody (design goal)

The aim that Rhea never holds the private keys that would let it act as a user.