The dembrane mark, drawn as a field of dotsCompliance & trust

Deliberation technology needs trust at the core

Safety in dialogue is non-negotiable. That’s why dembrane is built for trust from the ground up.

ISO 27001 certified · GDPR compliant · EU hosted · Code on GitHub

How dembrane processes your data

Step 1

Participants record the audio of their conversations. No personal data need to be collected before recording to start.

Step 2

The audio recording is transcribed into text. We use a double model approach to ensure transcription accuracy.

Step 3

Conversation hosts can perform analysis on the audio and the transcripts using the dembrane dashboard.

Two people talking at a table beside a phone showing their conversation being captured

Audio recording

Language models*

Data Pipelines

Processed Insights

A group at round tables in front of a screen showing clustered insights

Audio data is deleted 30 days after the project finishes. Data can be deleted immediately upon request. Only what participants share voluntarily during the conversation is recorded. The host is the data controller.

*Our Language Model Providers & sub-processor is Google Cloud Vertex AI. We have strict data protection agreements with all subprocessors. All data processing happens on Northwest EU servers.

All data is stored and encrypted at rest on Northwest European servers. Our current data storage provider is DigitalOcean.

Built for trust, by design

Security, privacy, and transparency are foundational to how we build.

Anonymous by default

Built on Chatham House rules: what's said matters, not who said it.

Code on GitHub

Our codebase is fully source available. We are proud and open about our secure system designs.

EU hosted

All data processed and stored on Northwest European servers. No exceptions.

GDPR compliant

Minimal data collected. All data stays within the EU. Your legal basis, supported.

ISO27001 Compliant

Full ISMS implementation meeting the industry standard for information security.

Tech-independent

No vendor lock-in. Switch to different providers whenever you need to.

No training by default

We wont use client data for training our models unless you opt in.

We'll be there for you

Email, call, in-person: Real human support.

What kinds of data are used for what and why?

dembrane is built with data minimization in mind. Only four categories of data are processed to deliver value, and you stay in full control.

What kinds of data are used for what and why?
CategoryDescriptionPurposeRetentionLegal Basis (Controller’s choice)*
🎙️ Audio recordingSensitive personal dataAll audio recorded with dembrane (voluntarily shared).To transcribe contributions. Kept for retranscription and fact-checking.Project duration + 30 days. Can be deleted anytime by admin.Your chosen legal basis (Art. 6(1) GDPR)
📝 Transcription textPersonal data (content-dependent)Transcribed conversations from recorded audio.To perform analysis and provide evidence for the analysis.Project duration + 30 days. Can be deleted anytime by admin.Your chosen legal basis (Art. 6(1) GDPR)
🔍 Analysis dataPersonal data (content-dependent)Generated by dembrane and users from transcription data via chat and other features.To understand diverse stakeholder perspectives shared during sessions.Project duration + 30 days. Can be deleted upon request.Your chosen legal basis (Art. 6(1) GDPR)
👤 Account dataPersonal dataUser email and encrypted password to create and identify user accounts.To maintain accounts for dashboard access and deliver services.As long as account exists. Can be deleted upon request.Contract; Art. 6(1)(b) GDPR

*dembrane acts as the processor (Art. 28 GDPR). The applicable legal basis is determined by you as controller.

You’re not alone

We’re trusted by leading organisations across public and private sectors

Still here? Let's work together

Sameer Pashikanti | [email protected]