Orbeva Finance security & data handling
Last updated July 2026
Before you connect anything, you should know exactly what Orbeva can access, what it cannot do, and how your data is handled. This page describes the current posture in plain language for buyers, users, procurement, and legal review.
Can Orbeva move money?
No. Plaid connections are read-scoped; Orbeva cannot initiate payments, transfers, or trades.
Does Orbeva see my bank password?
No. Plaid brokers the connection, and Orbeva stores only a revocable read-scoped token.
Is my data mixed with other clients?
No. Your workspace is scoped by tenant identifiers and protected by application and database boundaries.
How are provider claims handled?
We publish a provider or retention statement only while its supporting contract or executable evidence is current.
Read-only by design
Account connections are established through Plaid and are read-only. Orbeva can see balances, transactions, and holdings to produce your insights — it cannot move money, initiate payments, or place trades. We never see or store your banking password; Plaid brokers the connection and we hold only a revocable, read-scoped token.
Per-client isolation
Product records and access paths are scoped to a tenant identifier. Tenant isolation is covered by application, schema, and integration contracts so one workspace cannot intentionally read another workspace's data.
Model and data-use claims
Financial data is processed to produce product outputs for your workspace. Provider, retention, and training-use statements are published only when the supporting contract or executable evidence is current. See the company privacy and subprocessor disclosures for the maintained public record.
Encryption
Data is encrypted in transit (TLS) and at rest. Per-client secrets, such as connection tokens, are stored encrypted and are only ever decrypted within the boundary that needs them, scoped to your tenant.
Retention & deletion
Product workflows provide export and deletion controls. Specific retention and deletion commitments are described in the current privacy notice and applicable service terms rather than inferred from marketing copy.
Subprocessors
We use a small, named set of infrastructure and model providers. See the live subprocessors list. The company claim ledger keeps public control statements tied to evidence and expiry dates.
Assurance status
Orbeva publishes assurance milestones when they are independently supportable. For a current control, contract, or procurement question, contact the security team rather than relying on a roadmap claim.
Found something, or have a security question? Email security@orbeva.ai.