Security and data flow
How Bracecast handles your Dataverse data, from the moment a document is requested to the moment it’s delivered.
Where your data is read
Customer data is read only inside Dataverse, by Bracecast plug-ins running as the user who asked for the document. Dataverse security roles, business units and field-level security all apply, so a person can only render data they can already see.
No Bracecast service holds Dataverse credentials. The one exception is the connector gateway for Power Automate and Power Apps: it exchanges the signed-in user’s token on behalf of that user for a single request, relays the call and stores nothing.
How rendering works
The plug-in sends the renderer only what one template needs: the template body, the data for this document and the locale settings. The renderer typesets the document in memory and returns it to Dataverse.
The renderer is stateless. It never stores, logs or forwards template bodies, data payloads or rendered output. Telemetry records timing, sizes and IDs only.
Where it runs
Bracecast runs on Microsoft Azure. Canada (Canada Central, with Canada East for failover) is the primary region and the United States is the second. Each Dataverse environment is connected to one region during setup, and its documents are rendered only there. Failover for Canada stays inside Canada. Plans that include a choice of region can pick the United States.
Keys and secrets
Secrets live in Azure Key Vault and are reached through managed identities. API keys are stored only as SHA-256 hashes. No secret is kept in the solution, in readable Dataverse columns or in browser code.
Templates and versions
Published template versions never change. Every edit creates a new draft, and the Typst and component library versions are recorded with each published version, so a document renders the same way next year as it does today.
Subprocessors
| Subprocessor | Purpose | Region |
|---|---|---|
| Microsoft (Azure) | Hosting, rendering, storage of account and usage records | Canada, United States |
| Stripe | Subscription billing | United States |
| Anthropic | AI composer requests, only when a customer uses it | United States |
Questions security teams ask
Can we run Bracecast entirely inside our own tenant?
Yes, with an Enterprise licence. Enterprise will let you run the whole flow in your company’s own Microsoft tenant and Azure subscription, with the renderer and its supporting services deployed there alongside your Dataverse environment. Templates, data and rendered documents then never leave your company. You choose the region, and the optional AI composer can be turned off. Write to sales@bracecast.io to plan an Enterprise deployment.
Can people see data they aren’t allowed to see?
No. Bracecast plug-ins read data as the user who asked for the document, so Dataverse security roles, business units and field-level security all apply. A person can only put data in a document that they can already see in Dynamics 365.
How do you keep documents accurate and consistent?
Published template versions never change. Every edit creates a new draft that someone has to publish. Each version records its Typst and component library versions, so the same data renders the same document next year as it does today. Where your plan includes the Render Log, every render is recorded in a table in your own Dataverse environment, with the template, version, record, user and status, and you set how long it’s kept.
Does the AI composer see our data?
Not by default. The AI composer works from your template’s structure and synthetic sample data. Real record data is sent only if an admin allows it, and only for the roles they choose. The AI provider is listed with our other subprocessors on the security page.
How are connections and keys protected?
Every call between Dataverse and the renderer uses HTTPS and an API key. We store API keys only as SHA-256 hashes, keep secrets in Azure Key Vault, and never put secrets in the solution, in readable Dataverse columns or in browser code.
Is Bracecast certified for compliance?
Not yet. Because the renderer stores no customer data and your records stay in Dataverse under your existing controls, Bracecast adds little to your compliance scope. Our data flow and subprocessors are published on the security page, and we answer security questionnaires on request at info@bracecast.io.
Questions from your security team are welcome. Write to us from the contact page.