Skip to content
All technical docs Bricks technical documentation

Data flows

How Bricks controls where a tenant's data can go: every third-party connection is declared and signed, enforced in the browser and on the server, and listed for the people concerned.

Data flows

Bricks Technical Documentation

How Bricks controls where a tenant's data can go: every third-party connection is declared and signed, enforced in the browser and on the server, and listed for the people concerned.


1. Every third-party connection is declared and signed by a person

A data flow is a record of data going to a named third party. It states:

  • Who — the vendor, the hosts the data goes to, and the vendor's jurisdiction.
  • Why — a purpose and a category (map tiles, video embed, social share link, analytics, and so on).
  • On what basis — the GDPR lawful basis, whether opt-in consent is required, the categories of personal data, and how long the vendor keeps them.
  • Who signed, and when — an organisation admin. Revoking a flow closes access and keeps the record.

Studio AI prepares, a person signs. Before Studio AI writes a third-party address into your app, it checks that a signed flow covers it. If none does, it prepares an unsigned declaration and asks you to sign it. Flows declared in a tenant-spec manifest are never signed by applying it, and changing the terms of a signed flow removes the signature until someone signs again.

Studio AI does not declare a payment processor: apps take payments through the platform's payment links.

2. In the browser, an app reaches only what is declared

A published app's Content-Security-Policy is built from its signed frontend flows. By default an app may reach only itself, the Bricks platform and the platform's storage. A signed flow adds its vendor's hosts for every kind of browser request — scripts, stylesheets, fonts, images, media, requests and frames — and the browser blocks any address no signed flow names. A flow's category (map tiles, video embed, analytics, and so on) describes it in the lists and the register; it does not decide what is allowed.

Flows already running were signed by the platform. When blocking began, the browser flows already in use by published apps were signed by the platform so that those apps kept working. Every screen and export shows them as signed by the platform, never by a person. An organisation admin can sign one in their own name or revoke it.

Browsers report what is blocked. For each app, Bricks counts every refused address and the kind of request, with the first and last time it was seen. It keeps no page address, IP address or user agent.

3. On the server, workflows reach only declared hosts

A backend egress flow lets a tenant workflow send data to a vendor from the server. It never changes the browser policy, and usually belongs to the whole organisation rather than to one app. Every workflow node that can call an external address goes through the same check:

mermaid diagram

Vendor credentials (your own API keys) are stored encrypted under Integrations → API credentials and attached only for the host they belong to. A hand-edited workflow is checked the same way.

A signature opens a host, not a table. The check matches a call on its target host alone: the declared host, or any of its subdomains. One signed flow therefore lets every call to that host through, whatever data it carries and for whatever purpose. The table, columns, purpose and lawful basis a flow states are kept for the register; they are not compared with the call. Several flows naming the same host are, for the check, one permission: signing any of them lets through the calls all of them describe, and the host closes only when its last signature is revoked. This holds across the organisation: a flow declared for an app and one declared for the organisation open the same host.

Current limits

  • Declaring which table and columns a flow exports documents the disclosure; it does not stop other columns, or other data, from being sent to a host that is open.
  • Some outgoing traffic is not yet covered by data flows, for example bring-your-own email sending.

4. The people concerned can read the declarations

  • Organisation admins and builders — each app has a Data flows page (Apps → the app → Data flows): flows grouped by the host they name, since the host is what the check enforces, each showing the table and columns it says leave, its category, lawful basis, jurisdiction and status; revoked history; Sign and Revoke buttons and the Article 30 register for that app as a PDF in your language, both for organisation admins. Flows that belong to the whole organisation are under Integrations → Data flows, shown the same way. Before a backend egress flow is signed, the page states the host the signature opens, every other flow it also covers, and any signature that already opens that host. The organisation's GDPR Article 30 register — controller, recipients, transfers outside the EEA, retention, automated processing — is under Settings → Data protection, as a PDF and a CSV per section.
  • Members of the organisation — BricksID shows each member, per organisation, the recipients, transfers, retention and automated processing that concern them.

Current limits

  • Visitors of your app are not shown the declared flows. Bricks generates no privacy notice, cookie banner or consent prompt in a published app. If your visitors must be informed or asked for consent, your app has to do it in its own pages; Studio AI can build them with you.

This page describes behavior in production. Data flows are declared through Studio AI tools and enforced by the workflow engine described in The RPC API & workflows.