Skip to content
All technical docs Bricks technical documentation

GDPR

What Bricks provides for an organisation's GDPR obligations: protection by design, a generated record of processing, declared processors and transfers, security of processing, retention and erasure, and what the people concerned can see.

GDPR

Bricks Technical Documentation

What Bricks provides for an organisation's GDPR obligations: protection by design, a generated record of processing, declared processors and transfers, security of processing, retention and erasure, and what the people concerned can see.


An organisation on Bricks is the controller of its data; Bricks processes it on the organisation's behalf, under the Data Processing Agreement. This page says what the platform does for the controller's obligations and what evidence it gives. The other regulations are covered in Compliance evidence for auditors.

Art. 25 — Data protection by design and by default

  • Nothing runs undeclared. An organisation's tables, roles, permissions, apps, workflows, third parties and retention rules are declared before they exist, and the platform builds the system from those declarations.
  • Access follows from declarations. Who can read or write each table derives from the roles and permissions declared, enforced row by row by the database. Each role is read as a mandate given by someone with the authority to give it.
  • Third parties are closed by default. An app or workflow reaches a third party only once an administrator has signed a declaration for it (art. 28 and 44 below).

Art. 30 — Record of processing activities

Each organisation has one record of processing, generated from what the platform knows. It can be read for the whole organisation or for one app, in the reader's language, as a PDF and as CSV per section.

Section Source
Controller The organisation's details
Categories of data The organisation's tables and columns
Recipients Its declared data flows, revoked ones included
Transfers outside the EEA The flows' jurisdictions, including where the operator's law differs from the declared one
Retention The flows and the organisation's retention rules
Staff access Every access by Bricks staff (art. 32 below)
Automated processing The organisation's workflows
AI processing Each AI assistant's declared purpose, data, recipient, jurisdiction and safeguards

Current limits. Purposes, data subjects and security measures are not yet recorded by the platform; those sections are shown empty with the reason, for the organisation to complete.

Art. 28 and 44 — Processors and transfers

Every connection to a third party is a declared data flow: vendor, jurisdiction, purpose, lawful basis, whether consent is required, categories of personal data, the vendor's retention, signed by an administrator. Unsigned or revoked flows are blocked in the browser and on the server. Flows to vendors outside the EEA, or whose operator falls under another law, appear as transfers in the record of processing. Enforcement is described in Data flows.

Art. 32 — Security of processing

  • Encryption: in transit everywhere; at rest by the hosting providers, Scaleway (France) and Infomaniak (Switzerland); secrets for third-party services encrypted by the application; values an organisation chooses encrypted with a key that belongs to it alone; passwords and keys stored only as hashes.
  • Trails: every write to enrolled tables, whatever the channel, without a second copy of the data; every role given or removed; every run of a workflow.
  • Staff access: Bricks staff act on an organisation's data only at its request, with a reason and the support request behind it. Each access is recorded before it runs, kept twelve months and shown to the organisation's administrators.

Current limits. There is no end-to-end encryption: the platform can read the data organisations and people store. Secrets held for third parties share one platform key, with no rotation procedure yet.

Art. 5(1)(e) and 17 — Storage limitation and erasure

  • An organisation declares how long its data is kept: per table, a period, what happens at expiry and a notice period. A new rule first runs in observation mode and acts only once switched on. Rows can be held with a reason; each daily run is recorded.
  • Workflow traces are kept 90 days by default; a longer period needs an administrator's signature.
  • Audit trails survive the deletion of a person without keeping a copy of their data.
  • Closing a BricksID account removes the person's identity and keeps only records of what Bricks granted or what was bought. The person is told before and after.
  • Database snapshots are kept seven days, which bounds how long deleted data can be restored.

Art. 13 to 20 — What the people concerned see

  • In their BricksID, members of an organisation see what it does with their data: the controller, recipients, transfers, retention, automated and AI processing.
  • Their identity, documents and signatures are kept in their BricksID, not only in the organisation's systems.

Current limits. Visitors of an organisation's published apps are not yet shown the record of processing.