Frequently asked questions.

No. Your connected storage provider holds the stored data. Rhea Data is the environment for protected documents, permissions, sharing, collection, supported movement and recorded activity. Rhea's broader direction is a reusable authority and operations layer across supported systems.

Rhea Data connects to storage your organization already owns: AWS S3, Microsoft Azure Blob Storage, Google Cloud Storage, Cloudflare R2, Oracle Cloud Object Storage and MinIO. Current document workflows include protection, organization, sharing, file requests, movement between connected locations and recorded activity. The Platform page lists every capability.

Rhea Data-protected file content is stored as ciphertext in connected customer-owned storage. Rhea processes operational metadata and wrapped key material, and current connection modes can use provider credentials processed by its backend. Authorized devices handle readable content. The metadata and credentials page explains these boundaries.

Only encrypted protected-file content and the object metadata needed to store it, such as object keys, sizes and access times. The storage provider does not receive plaintext or encryption keys.

Rhea Data and Rhea may process the operational metadata required to provide authorization, organization administration, metering, security and audit functions — for example organization structure, roles, sessions, document identifiers, storage references, usage records, and audit events. This operational metadata is distinct from protected file content and does not include the plaintext of anything stored.

Bring Your Own Storage (BYOS) means encrypted objects are written to a storage bucket the organization owns and controls rather than to a Rhea-hosted store. Rhea Data encrypts each object client-side with AES-256-GCM, then uploads the ciphertext. Six storage families are supported: AWS S3, Microsoft Azure Blob Storage, Google Cloud Storage, Cloudflare R2, Oracle Cloud Object Storage and MinIO. Private and on-premises infrastructure is supported through the customer-controlled connector.

Bring Your Own Database follows the same rule as storage: the database stays where the organization runs it, and Rhea governs who may perform which scoped operation. Connectivity begins with PostgreSQL. Operations are enforced in the customer's environment; Rhea does not offer arbitrary querying over encrypted data.

Rhea Key authenticates the user and signs approvals in supported Rhea workflows. Rhea Data's organizational and resource permissions still determine what is allowed. Possessing or connecting a key does not grant universal access to an organization's data.

Because private authentication material stays on the user's device and Rhea does not operate a key-recovery service, losing the device without a working recovery path can make data whose access depended only on that device's key unrecoverable through it. A lost or compromised device should be reset from another trusted device or reported so its authority can be invalidated for future authorizations.

Rhea ID returns signed Yes / No / Unknown answers to identity questions, without transferring identity documents. Those answers can inform authorization decisions. It is separate from Rhea Key's cryptographic authentication. It is not a prerequisite for Rhea Data's current supported workflows.

No. Organizations operating under GDPR, NIS2, DORA, EHDS or sector-specific requirements may evaluate Rhea Data as one technical and organizational control within a broader compliance programme. Rhea Data does not by itself make an organization compliant, and legal obligations depend on the organization's deployment, policies, processes, contracts and applicable law.

No. Rhea Data uses a Bring Your Own Storage (BYOS) model. Your organization connects Rhea Data to storage under its own control. Rhea does not provide, host, or operate customer storage.