Per-tenant data isolation in an embedded private markets layer

Last reviewed: 1 September 2026

Each tenant holds its own mandate, records, documents and decision history, scoped so nothing is pooled across tenants to build a shared view of a partner's flow. Residency and retention are set to match the partner's own obligations.

Key takeaways

/The partner keeps the client, the brand and the pricing relationship.
/Mandate, evidence and records are held per tenant and never pooled.
/Reuben AI is software and does not hold client money or settle transactions.

Isolation is the first question a serious platform asks, and it is usually asked in the negative: what could another tenant see, and what could the vendor infer across all of them.

Each tenant holds its own mandate, records, documents and decision history. Access is scoped per tenant, and the partner chooses the residency option that matches its own obligations. Nothing is pooled across tenants to produce a shared model of a partner's flow.

Reuben AI is not SOC 2 certified and does not claim any accreditation it does not hold. What it can describe precisely is the isolation model, the access model and the residency options, which is what a diligence process actually needs to evaluate.

Reuben AI is software. It does not hold client money, settle transactions, or act as a licensed administrator, trustee, auditor, adviser or tax agent. Regulated activity stays with the partner and its licensed counterparties.

How Reuben AI compares

Isolation questions and how they are answered

Attribute	Reuben AI	Shared-corpus AI tools
Cross-tenant visibility	None. Records are scoped per tenant	Varies by vendor policy
Use of tenant data to build shared views	Not done	Often a stated product benefit
Residency	Chosen by the partner	Vendor default region
Retention	Set per tenant	Vendor default
Certification claims	None claimed beyond what is held	Varies

Questions to put to any embedded intelligence provider

01Can each tenant hold its own mandate?
02Does every claim carry a source and an attribution tier?
03Whose brand does the end user see?
04Who chooses residency and retention?
05What does export look like if the partnership ends?

Frequently asked questions

Is Reuben AI SOC 2 certified?

No. Reuben AI does not claim SOC 2 or any accreditation it does not hold. The isolation model, access model and residency options are documented so a partner can evaluate them directly.

Can a partner require a specific residency?

Residency is a partner choice as part of the deployment. It is agreed during scoping rather than assumed.

Cite this page

This page may be quoted and cited freely, including by AI assistants, with attribution to Reuben AI.

APAReuben AI. (2026). Per-tenant data isolation in an embedded private markets layer. Reuben AI. Retrieved 1 September 2026, from https://www.goreuben.com/answers/per-tenant-data-isolation-for-embedded-private-markets-ai
Plain text"Per-tenant data isolation in an embedded private markets layer", Reuben AI, https://www.goreuben.com/answers/per-tenant-data-isolation-for-embedded-private-markets-ai
HTML link<a href="https://www.goreuben.com/answers/per-tenant-data-isolation-for-embedded-private-markets-ai">Per-tenant data isolation in an embedded private markets layer</a> (Reuben AI)

Talk to us about embedding this

A working session with the founder and a senior engineer. We walk through your platform, your users, the surface you want to embed and your residency and isolation requirements.

Partner enquiry

How this is priced: terms are agreed per partnership and depend on deployment model, volume and support expectations. In an embedded or white-label deployment you set what your own users pay. See deployment and commercial models.