Security and data flow

Know where the data goes. Before you connect it.

This is the forwardable version for an IT approver: what Alice reads, what it stores, what leaves your environment, and what gets created in Power BI.

The production data path
  1. Read an authorized source or privately stored upload.
  2. Run an approved, read-only transformation in an isolated processing session.
  3. Write serving data to your storage or a workspace-specific managed container.
  4. Create and refresh Power BI artifacts in the Microsoft workspace you authorize.

What happens at each boundary

1

Source

Direct connectors read the tables or objects you select. Uploaded files are stored in private application storage so scheduled runs can process them.

2

Transform and serve

Alice processes the selected data, previews capped result samples for you, and writes open-format serving files or tables to the configured destination.

3

Power BI

Using the Microsoft authorization you provide, Alice creates or refreshes the dataset in the Power BI workspace you chose.

Controls implemented today

Encrypted credentials

Connector secrets and Microsoft tokens are encrypted at the application layer. Production encryption keys are supplied separately from the database.

HTTPS and private uploads

Production forces HTTPS and secure cookies. File uploads use private object storage rather than public URLs.

Scoped managed storage

When Alice provides serving storage, each workspace gets its own managed container and a container-scoped credential.

Workspace roles

Application access is scoped to workspaces with Admin, Data Engineer, Analyst, and Viewer roles for different capabilities.

A bounded AI request

Ask Alice sends Anthropic your request plus table and column names and types. Source rows stay in Alice's processing session; the generated SQL is previewed before you apply it.

Stripe-hosted card entry

Stripe processes checkout. Alice does not receive or store your full card number.

Storage and retention policy

Your storage

Serving data written to storage you own remains under your account and your retention controls.

Managed storage

Managed serving files sit in a per-workspace Azure container. The current export, termination, and deletion commitments are maintained in the Terms and Privacy Policy.

Operational records

Alice keeps the configuration, run history, metrics, and capped previews needed to operate and support the service, subject to the Privacy Policy.

Subprocessors, personal-data rights, RB2B's marketing-site role, and the complete retention policy are listed in the Privacy Policy.

Have a security questionnaire or a source we should check?

Send the security requirement