Enterprise
Procurement and trust surface.
A single consolidated view of the procurement subjects a buyer evaluates, with the published state of each. Nothing here is stated without evidence; where a subject is not yet published, that is stated directly.
Built for institutions
Banks. Governments. Defense.
- Runs on your existing cloud or private infrastructure
- Multi-person approval for critical operations
- Audit evidence ready for regulators
| Procurement subject | Details |
|---|---|
| Data Processing Agreement (DPA) | A DPA is provided during enterprise procurement on request. It is not published as a self-serve document. |
| Subprocessor list | A current subprocessor list is provided on request. |
| Data residency | Content stays in the customer-owned storage you connect. Rhea Data does not host customer content, so residency follows your own storage configuration. |
| Service-level agreement | Service-level terms are agreed in writing during enterprise procurement. |
| Support policy | Support tiers and response commitments are provided on request. |
| Incident notification | Notification timelines and channels are defined contractually in the DPA. |
| Customer exit | You can stop using Rhea Data at any time. Protected objects remain in your own storage account under your control; nothing has to be extracted from Rhea. |
| Business continuity procedure | A written continuity procedure exists for enterprise engagements and is shared during procurement. It is not published on the public site. |
| Recovery responsibilities | Rhea Data organizational-data recovery is guardian-based and available where configured. Rhea Key authentication keys are not recoverable by Rhea. See details |
| Performance and file-size limits | Current performance characteristics and file-size limits are provided on request. |
| Pricing | Plans and the operations meter are published in full. See details |
Who owns this decision
Typical procurement participants.
- Executive sponsor — CISO, CIO, CTO, data-protection leader or senior operational owner
- Owns the decision that readable-data authority should sit with the organization rather than with infrastructure administration.
- Technical owner — Security, platform, cloud or data-infrastructure team
- Connects customer-owned storage, configures organizational policy, roles and approvals, and reviews recorded activity.
- Daily users — Legal, finance, investment, research, engineering and operations teams
- Protect, organize, share, request and retrieve important organizational files inside Rhea Data.
- External participants — Clients, partners, experts and contractors
- Submit or receive controlled information through Secure File Requests and shared access, without a loose link or an unmanaged copy.
These are representative deployment roles, not mandatory titles or a claim that every organization buys Rhea Data in the same way.
Architectural position
What is structurally difficult to replicate.
- Content is protected on the device before connected storage receives it, so infrastructure administration does not imply readable-data access.
- Authority, sharing, collection and evidence sit above customer-owned storage rather than inside a provider boundary.
- Rhea never becomes the storage provider, so exit does not require extracting data from a vendor.