BYGGER

Security & GDPR Analysis

Last updated: March 17, 2026

This document covers security posture, GDPR compliance, and data protection for the Bygger platform — including the meeting recorder service that captures, transcribes, and processes personal data.

1. Data Flow & Personal Data Inventory

What personal data we process

Data type Source Storage Retention
User accounts (name, email, password hash)RegistrationPostgreSQLUntil account deletion
Meeting recordings (audio + video)RecorderStorage BoxUntil user deletes or account deletion
Meeting transcriptions (text + speaker labels)Recorder provider (Reemove.ai / Recall.ai)PostgreSQLUntil user deletes
Chat messagesUsersPostgreSQLUntil user deletes
File uploadsUsersActive StorageUntil user deletes
Activity logsSystemPostgreSQLIndefinite
Session data (IP, user agent)AuthenticationPostgreSQLUntil session expires
Vector embeddingsDerived from contentPostgreSQL (pgvector)Linked to source data lifecycle

Data processors (sub-processors)

Processor Role Location DPA required Data transferred
HetznerServer hosting, database, file storageGermanyYesAll data
NebiusLLM inference, embeddings, image interpretation (default)FinlandYesText prompts (may contain personal data)
Berget.aiLLM inference (emergency failover)SwedenYesText prompts (may contain personal data)
Reemove.aiMeeting + voice transcription (KB-Whisper)SwedenYesAudio, meeting metadata
CloudflareNetwork proxy in front of the transcription serviceUSA (global)YesAudio in transit
Recall.aiMeeting recording + transcription (opt-in per project)EU regionYesAudio/video streams, meeting metadata
MailgunOutgoing + incoming emailEU (Germany)YesNames, email addresses, email content
StripePayments + billingIreland (EU)YesBilling data
Idura (Criipto)BankID identification + e-signingDenmark (EU)YesDocument text, signer identity
TwilioSMS (codes, signing invitations)USAYesPhone numbers, SMS text
ExpoPush notificationsUSAYesDevice tokens, notification text
Brave SearchWeb search for prospect research (fallback)USAYesSearch queries with person/company names
OpenAIReal-time voice chat, Shout image generation (opt-in)USAYesVoice audio, prompt text
ComposioOAuth & API access for connected Outlook/Gmail mailboxesUSAYesOAuth tokens, email metadata and content returned by searches
IgdrasilBank connection (opt-in)SwedenYesCompany identifiers, bank transactions
Google AdsSearch campaigns for Bygger Ads (opt-in)Ireland (EU) / USATo verifyAdvertiser name + org. number, ad text, keywords, landing page, budget
Google Fonts, jsDelivr, jspmFonts + front-end libraries loaded by the browserGlobal CDNNoIP address, user agent
Let's EncryptSSL certificatesUSANo (no personal data)Domain names only

Data flow diagram

Meeting participants (Teams/Zoom/Meet)
         |
         v (audio + video stream)
+--------------------------------------------------+
|  Meeting Recorder Provider                        |
|  (project-configurable)                           |
|                                                   |
|  Option A: Reemove.ai (Sweden)                    |
|    Recording + transcription                      |
|    Hosted in Sweden, data stays in EU              |
|                                                   |
|  Option B: Recall.ai (EU servers)                 |
|    Recording + transcription                      |
|    Cloud service, bot joins meeting               |
+--------+-----------------------------------------+
         |
         v (transcript + recording)
+------------------------------------------+
|  Hetzner AX102-U (Germany)               |
|                                          |
|  Recording stored --->  Storage Box      |
|         |              (Germany)          |
|         |              Audio + video      |
|         v                                |
|  Transcript stored in PostgreSQL         |
|         |                                |
|         v                                |
|  +-----------------------------+         |
|  |  LLM Inference Router      |         |
|  |  (project-dependent config) |         |
|  +--+-------------+-----------+         |
|     |             |                     |
|     v             v                     |
|  Nebius        Berget.ai                |
|  (Finland)     (Sweden)                 |
|  default LLM   emergency failover       |
|     |             |                     |
|     +-------------+                     |
|           |                             |
|           v                             |
|  AI summaries stored in PostgreSQL      |
|           |                             |
|           v                             |
|  Embeddings sent to Qdrant ----------->  Qdrant (Germany)
|           |                             |  Vector database
|           v                             |  Semantic search & RAG
|  Vector search available                |
+------------------------------------------+

2. GDPR Compliance

2.1 Legal basis for processing

Processing activity Legal basis (Art. 6) Notes
User account managementContractual necessity (6.1.b)Required to provide the service
Meeting recordingConsent (6.1.a) or Legitimate interest (6.1.f)Depends on context
TranscriptionSame as recordingSame legal basis applies
AI summariesSame as recordingDerived processing
Analytics / activity logsLegitimate interest (6.1.f)Document LIA

Meeting recording — consent vs legitimate interest:

  • External participants (clients, partners): Use consent. Notify before recording starts, allow opt-out.
  • Internal meetings (employees): Consent is problematic due to power imbalance. Use legitimate interest with documented LIA instead.
  • Important: Some EU member states (notably Germany) require all-party consent for recording regardless of GDPR legal basis.

2.2 Participant notification requirements

Before any recording starts, all participants must be informed of:

  1. That the meeting is being recorded
  2. Purpose of the recording (e.g., note-taking, quality assurance)
  3. That AI transcription will be performed
  4. How long the recording is retained (30 days)
  5. How to request deletion (right to erasure)
  6. Who has access to the recording/transcript

Action required: Ensure the recorder bot announces itself when joining a meeting, or that the meeting organizer informs participants.

2.3 Data Processing Agreements (DPA)

Processor DPA status Action needed
HetznerSignedDone
Berget.aiSignedDone
NebiusSignedDone
Recall.aiSignedDone
Reemove.aiTo verifySign DPA
ComposioSignedDone
StripeSignedDone
ExpoStandard ToSReview
CloudflareTo verifyAccept/download provider DPA
MailgunTo verifyAccept/download provider DPA
Idura (Criipto)To verifyAccept/download provider DPA
TwilioTo verifyAccept/download provider DPA
Brave SearchTo verifyAccept/download provider DPA
OpenAITo verifyAccept/download provider DPA
IgdrasilTo verifyAccept/download provider DPA
Google AdsTo verifyAccept Google Ads Data Processing Terms in the manager account

Every DPA must include:

  • Purpose and duration of processing
  • Type of personal data processed
  • Obligations of the processor
  • Breach notification timeline (push for 24-48 hours)
  • Sub-processor list and change notification mechanism
  • Prohibition on using data for model training
  • Data deletion obligations after contract ends

2.4 Data residency

Data Location EU/EEA? Risk
DatabaseHetzner, GermanyYesLow
RecordingsHetzner Storage Box, GermanyYesLow
LLM promptsNebius (Finland) / Berget.ai failover (Sweden)YesLow
Meeting recording + transcription (Reemove.ai)Reemove.ai, SwedenYesLow
Meeting recording + transcription (Recall.ai)Recall.ai, EUYesLow
Real-time voice + Shout images (opt-in)OpenAI, USANoMedium (SCC/DPF)
Connected Outlook/Gmail mailboxes (opt-in)Composio, USANoMedium (SCC/DPF)
Ad campaigns (Bygger Ads, opt-in)Google Ads, Ireland / USAPartlyLow (company data, SCC/DPF)
SMS + push notificationsTwilio / Expo, USANoMedium (SCC/DPF)
Transcription traffic proxyCloudflare, USANoMedium (SCC/DPF)

2.5 Right to erasure (Art. 17)

Users/participants can request deletion of their personal data. The system must be able to:

Data type Deletion method Status
User accountDelete user recordDone — selective GDPR delete in superadmin
Solo projectsCascade delete entire project (no other members)Done — only when sole member
Shared projectsReassign ownership, remove membershipDone — project data preserved for team
Interviews / VaultsNullify user reference (dependent: :nullify)Done — project retains data
Sessions, support, push tokensDirect delete (personal data only)Done
Recordings, transcriptions, AICascade with solo project / preserved in sharedDone
BackupsData "beyond use" until backup rotates outAcceptable under GDPR

Selective GDPR deletion: solo projects cascade-deleted, shared projects reassigned to remaining team. User references nullified on shared data (interviews, vaults). Personal data (sessions, tickets, tokens) permanently deleted.

2.6 Data Protection Impact Assessment (DPIA)

A DPIA (Art. 35) is likely required because:

  • Processing voice recordings at scale
  • Using AI/automated decision-making on personal data
  • Systematic monitoring of individuals (meeting recording)

DPIA conducted and documented in docs/dpia.md (March 2026).

2.7 Data breach notification

Deadline Obligation
72 hoursNotify supervisory authority (IMY in Sweden) after becoming aware of breach
Without undue delayNotify affected individuals if high risk
24-48 hoursProcessors must notify us (include in DPA)

Breach response plan:

  1. Detect — monitoring, logging, alerts
  2. Contain — isolate affected systems
  3. Assess — determine scope, data affected, risk level
  4. Notify IMY — within 72 hours if risk to individuals
  5. Notify users — if high risk (identity theft, financial harm)
  6. Document — maintain breach register regardless of notification decision

3. Current Application Security Posture

What's good

Good
Authentication bcrypt password hashing, secure HTTPOnly cookies, 12-character minimum passwords
Good
Two-factor authentication Email OTP (6-digit code), 10-minute expiry, 5-attempt lockout, trusted device cookie (30 days)
Excellent
Multi-tenancy isolation Strict accessible_projects scoping throughout
Good
API security SHA256-hashed API keys, bearer token auth
Good
Rate limiting API: 100 req/min per company. Web: login 10/3min, OTP resend 3/5min, registration 5/3min
Good
Session management 8-hour session expiry, HTTPOnly signed cookies, secure flag in production
Good
Encryption at rest Active Record Encryption on email, phone, Stripe customer ID, OTP codes (deterministic)
Good
Secrets management Rails encrypted credentials, no plaintext secrets
Good
CSRF protection Rails default CSRF tokens on all forms
Good
CSP headers Content Security Policy with nonces, violation reporting via report_uri
Good
Parameter filtering Sensitive fields filtered from logs
Good
Audit logging Public Activity gem, project-scoped
Good
SQL injection protection Parameterized queries, sanitized SQL
Good
File upload validation MIME type whitelist, 10 MB size limit
Good
SSL/TLS force_ssl = true, HSTS enabled
Good
Webhook security IP-restricted to internal networks
Good
Internal API Restricted to localhost/private networks
Good
Dependency scanning Brakeman (Rails static analysis), bundler-audit (gem CVEs), importmap audit (JS CVEs) — all in CI

Previously identified improvements

All previously identified security improvements have been addressed. See the compliance checklist below for details.

4. Infrastructure Security (Hetzner AX102-U)

Server hardening checklist

SSH key-only auth Disable password SSH login
UFW firewall Allow only 22 (SSH), 80, 443
unattended-upgrades Automatic security patches
Fail2ban Block brute-force SSH/HTTP attempts
Non-root user Run services as unprivileged user
Docker rootless Consider rootless Docker for recorder containers
Log monitoring Ship logs to external service or monitor locally
Disk encryption LUKS if required by policy (performance trade-off)

Network security

Internet
    |
    v
+----------+
| UFW      |  Port 22: SSH (key-only, Fail2ban)
| Firewall |  Port 80: HTTP -> redirect to HTTPS
|          |  Port 443: HTTPS (Rails via Kamal)
|          |  All other ports: BLOCKED
+----------+
    |
    v
+----------------------------------+
|  Internal services (localhost)   |
|  PostgreSQL :5432                |
|  Redis :6379                     |
|  RabbitMQ :5672                  |
|  Recorder API :8001              |
+----------------------------------+

No internal services exposed to the internet. All inter-service communication on localhost.

5. Risk Assessment

Threat matrix

Threat Likelihood Impact Mitigation
Brute-force login Low High Rate limiting (10/3min) + OTP lockout (5 attempts) + Fail2ban + 2FA
SQL injection Low Critical Parameterized queries (already implemented)
XSS Low Medium CSP headers + Rails escaping (already implemented)
Data breach via stolen credentials Low Critical Email OTP 2FA + 8h session timeout + 12-char password minimum
Server compromise Low Critical Unattended-upgrades + UFW + SSH keys + monitoring
Sub-processor breach Low-Medium High DPAs with breach notification clauses
Accidental data exposure Medium High Multi-tenancy isolation (already strong)
Insider threat Low High Audit logging + principle of least privilege
Backup data theft Low Low Mitigated — Restic AES-256 encrypted backups
Recording of unconsenting participants Medium High (legal) Participant notification before recording

Highest priority actions

  1. Sign DPAs — Done: Hetzner, Berget.ai, Nebius (March 2026)
  2. Implement 2FA — Done: email OTP with trusted device cookie (March 2026)
  3. Increase minimum password length — Done: 12 characters minimum
  4. Add login rate limiting — Done: 10/3min login, 3/5min OTP resend
  5. Build data deletion pipeline — Done: GDPR deletion in superadmin with data summary and cascade delete (March 2026)
  6. Conduct DPIA — Done: Draft documented in docs/dpia.md (March 2026)
  7. Encrypt backups — Done: Restic with AES-256 encryption to Hetzner Storage Box
  8. Document participant notification process — Done: Recorder bot announces presence when joining meetings

6. Compliance Checklist

Before launching on Hetzner

✅ Sign DPA with Hetzner (March 2026)
✅ Sign DPA with Berget.ai (March 2026)
✅ Sign DPA with Nebius (March 2026)
✅ Verify sub-processor lists from all vendors (March 2026)
✅ Verify no vendor uses data for model training (March 2026)
✅ Sign DPA with Recall.ai (March 2026)

Application changes needed

✅ Implement 2FA — Email OTP with trusted device cookie (March 2026)
✅ Increase minimum password to 12 characters
✅ Add session inactivity timeout — 8-hour session expiry
✅ Add login attempt rate limiting — 10/3min login, 3/5min OTP resend
✅ Add Active Record Encryption — email, phone, Stripe ID, OTP codes
✅ Build right-to-erasure deletion pipeline — GDPR delete in superadmin (March 2026)
✅ Encrypt backups — Restic AES-256 to Hetzner Storage Box
✅ Add bundler-audit to CI — brakeman + bundler-audit + importmap audit (March 2026)

Documentation needed

✅ Privacy policy updated to reflect AI transcription — docs/privacy-policy.md (March 2026)
✅ Data Processing Agreement template for customers — docs/dpa-template.md (March 2026)
✅ Legitimate Interest Assessment for meeting recording — docs/legitimate-interest-assessment.md (March 2026)
✅ Data Protection Impact Assessment — Draft in docs/dpia.md (March 2026)
✅ Breach response procedure document — docs/breach-response-procedure.md (March 2026)
✅ Data retention policy document — docs/data-retention-policy.md (March 2026)
✅ Record of Processing Activities (Art. 30) — docs/record-of-processing-activities.md (March 2026)

Server hardening

✅ SSH key-only authentication
✅ UFW configured (22, 80, 443 only)
✅ Fail2ban installed and configured
✅ unattended-upgrades enabled
✅ Services running as non-root user
✅ Log monitoring configured

7. Decision Log

Decision Rationale
EU-only data processors preferredEliminates cross-border transfer complexity
Berget.ai for LLM inferenceSwedish company, data stays in Sweden — EU-based inference provider
Nebius for LLM inferenceEU datacenter (Finland), no cross-border transfer issues
EU-only LLM processingChat, summaries, analysis and embeddings use EU providers only, with no US-based fallback. OpenAI (USA) is used only for opt-in real-time voice and Shout image generation.
Recordings retained while user activeUsers derive ongoing value from historical recordings. Legal basis: contractual necessity (Art. 6.1.b). Deleted on account deletion.
Storage Box for backupsSame jurisdiction (Germany) as server, no additional transfer
Email OTP over TOTP appLower friction for users — no authenticator app needed. Acceptable security for current threat model. Can upgrade to TOTP later.
Trusted device cookie (30 days)Balances security with usability — users only verify OTP once per device per month
Hetzner for hostingGerman company, data stays in Germany (EU). Dedicated server (AX102-U) with full disk encryption. DPA signed. No data leaves EU jurisdiction.
Project-dependent model routerAllows per-project LLM provider selection (Berget.ai, Nebius, Reemove.ai) — flexibility without leaving EU
Reemove.ai for meeting recording + transcriptionSwedish company, hosted in Sweden — default recording and transcription provider. Data stays in Sweden. DPA signed.
Recall.ai as alternative recording + transcription providerCloud recording service with EU servers — offered as opt-in alternative. Per-project configurable. Data stays in EU. DPA signed.
Per-project recorder provider selectionMeetingRecorderProvider abstraction allows each project to choose between Reemove.ai (default) and Recall.ai — both EU-based, giving flexibility in recording capabilities.
Qdrant for vector databaseHosted in Germany (EU), purpose-built vector DB for semantic search and RAG