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) | Registration | PostgreSQL | Until account deletion |
| Meeting recordings (audio + video) | Recorder | Storage Box | Until user deletes or account deletion |
| Meeting transcriptions (text + speaker labels) | Recorder provider (Reemove.ai / Recall.ai) | PostgreSQL | Until user deletes |
| Chat messages | Users | PostgreSQL | Until user deletes |
| File uploads | Users | Active Storage | Until user deletes |
| Activity logs | System | PostgreSQL | Indefinite |
| Session data (IP, user agent) | Authentication | PostgreSQL | Until session expires |
| Vector embeddings | Derived from content | PostgreSQL (pgvector) | Linked to source data lifecycle |
Data processors (sub-processors)
| Processor | Role | Location | DPA required | Data transferred |
|---|---|---|---|---|
| Hetzner | Server hosting, database, file storage | Germany | Yes | All data |
| Nebius | LLM inference, embeddings, image interpretation (default) | Finland | Yes | Text prompts (may contain personal data) |
| Berget.ai | LLM inference (emergency failover) | Sweden | Yes | Text prompts (may contain personal data) |
| Reemove.ai | Meeting + voice transcription (KB-Whisper) | Sweden | Yes | Audio, meeting metadata |
| Cloudflare | Network proxy in front of the transcription service | USA (global) | Yes | Audio in transit |
| Recall.ai | Meeting recording + transcription (opt-in per project) | EU region | Yes | Audio/video streams, meeting metadata |
| Mailgun | Outgoing + incoming email | EU (Germany) | Yes | Names, email addresses, email content |
| Stripe | Payments + billing | Ireland (EU) | Yes | Billing data |
| Idura (Criipto) | BankID identification + e-signing | Denmark (EU) | Yes | Document text, signer identity |
| Twilio | SMS (codes, signing invitations) | USA | Yes | Phone numbers, SMS text |
| Expo | Push notifications | USA | Yes | Device tokens, notification text |
| Brave Search | Web search for prospect research (fallback) | USA | Yes | Search queries with person/company names |
| OpenAI | Real-time voice chat, Shout image generation (opt-in) | USA | Yes | Voice audio, prompt text |
| Composio | OAuth & API access for connected Outlook/Gmail mailboxes | USA | Yes | OAuth tokens, email metadata and content returned by searches |
| Igdrasil | Bank connection (opt-in) | Sweden | Yes | Company identifiers, bank transactions |
| Google Ads | Search campaigns for Bygger Ads (opt-in) | Ireland (EU) / USA | To verify | Advertiser name + org. number, ad text, keywords, landing page, budget |
| Google Fonts, jsDelivr, jspm | Fonts + front-end libraries loaded by the browser | Global CDN | No | IP address, user agent |
| Let's Encrypt | SSL certificates | USA | No (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 management | Contractual necessity (6.1.b) | Required to provide the service |
| Meeting recording | Consent (6.1.a) or Legitimate interest (6.1.f) | Depends on context |
| Transcription | Same as recording | Same legal basis applies |
| AI summaries | Same as recording | Derived processing |
| Analytics / activity logs | Legitimate 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:
- That the meeting is being recorded
- Purpose of the recording (e.g., note-taking, quality assurance)
- That AI transcription will be performed
- How long the recording is retained (30 days)
- How to request deletion (right to erasure)
- 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 |
|---|---|---|
| Hetzner | Signed | Done |
| Berget.ai | Signed | Done |
| Nebius | Signed | Done |
| Recall.ai | Signed | Done |
| Reemove.ai | To verify | Sign DPA |
| Composio | Signed | Done |
| Stripe | Signed | Done |
| Expo | Standard ToS | Review |
| Cloudflare | To verify | Accept/download provider DPA |
| Mailgun | To verify | Accept/download provider DPA |
| Idura (Criipto) | To verify | Accept/download provider DPA |
| Twilio | To verify | Accept/download provider DPA |
| Brave Search | To verify | Accept/download provider DPA |
| OpenAI | To verify | Accept/download provider DPA |
| Igdrasil | To verify | Accept/download provider DPA |
| Google Ads | To verify | Accept 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 |
|---|---|---|---|
| Database | Hetzner, Germany | Yes | Low |
| Recordings | Hetzner Storage Box, Germany | Yes | Low |
| LLM prompts | Nebius (Finland) / Berget.ai failover (Sweden) | Yes | Low |
| Meeting recording + transcription (Reemove.ai) | Reemove.ai, Sweden | Yes | Low |
| Meeting recording + transcription (Recall.ai) | Recall.ai, EU | Yes | Low |
| Real-time voice + Shout images (opt-in) | OpenAI, USA | No | Medium (SCC/DPF) |
| Connected Outlook/Gmail mailboxes (opt-in) | Composio, USA | No | Medium (SCC/DPF) |
| Ad campaigns (Bygger Ads, opt-in) | Google Ads, Ireland / USA | Partly | Low (company data, SCC/DPF) |
| SMS + push notifications | Twilio / Expo, USA | No | Medium (SCC/DPF) |
| Transcription traffic proxy | Cloudflare, USA | No | Medium (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 account | Delete user record | Done — selective GDPR delete in superadmin |
| Solo projects | Cascade delete entire project (no other members) | Done — only when sole member |
| Shared projects | Reassign ownership, remove membership | Done — project data preserved for team |
| Interviews / Vaults | Nullify user reference (dependent: :nullify) | Done — project retains data |
| Sessions, support, push tokens | Direct delete (personal data only) | Done |
| Recordings, transcriptions, AI | Cascade with solo project / preserved in shared | Done |
| Backups | Data "beyond use" until backup rotates out | Acceptable 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 hours | Notify supervisory authority (IMY in Sweden) after becoming aware of breach |
| Without undue delay | Notify affected individuals if high risk |
| 24-48 hours | Processors must notify us (include in DPA) |
Breach response plan:
- Detect — monitoring, logging, alerts
- Contain — isolate affected systems
- Assess — determine scope, data affected, risk level
- Notify IMY — within 72 hours if risk to individuals
- Notify users — if high risk (identity theft, financial harm)
- Document — maintain breach register regardless of notification decision
3. Current Application Security Posture
What's good
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
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
- Sign DPAs — Done: Hetzner, Berget.ai, Nebius (March 2026)
- Implement 2FA — Done: email OTP with trusted device cookie (March 2026)
- Increase minimum password length — Done: 12 characters minimum
- Add login rate limiting — Done: 10/3min login, 3/5min OTP resend
- Build data deletion pipeline — Done: GDPR deletion in superadmin with data summary and cascade delete (March 2026)
- Conduct DPIA — Done: Draft documented in docs/dpia.md (March 2026)
- Encrypt backups — Done: Restic with AES-256 encryption to Hetzner Storage Box
- Document participant notification process — Done: Recorder bot announces presence when joining meetings
6. Compliance Checklist
Before launching on Hetzner
Application changes needed
Documentation needed
Server hardening
7. Decision Log
| Decision | Rationale |
|---|---|
| EU-only data processors preferred | Eliminates cross-border transfer complexity |
| Berget.ai for LLM inference | Swedish company, data stays in Sweden — EU-based inference provider |
| Nebius for LLM inference | EU datacenter (Finland), no cross-border transfer issues |
| EU-only LLM processing | Chat, 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 active | Users derive ongoing value from historical recordings. Legal basis: contractual necessity (Art. 6.1.b). Deleted on account deletion. |
| Storage Box for backups | Same jurisdiction (Germany) as server, no additional transfer |
| Email OTP over TOTP app | Lower 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 hosting | German company, data stays in Germany (EU). Dedicated server (AX102-U) with full disk encryption. DPA signed. No data leaves EU jurisdiction. |
| Project-dependent model router | Allows per-project LLM provider selection (Berget.ai, Nebius, Reemove.ai) — flexibility without leaving EU |
| Reemove.ai for meeting recording + transcription | Swedish company, hosted in Sweden — default recording and transcription provider. Data stays in Sweden. DPA signed. |
| Recall.ai as alternative recording + transcription provider | Cloud recording service with EU servers — offered as opt-in alternative. Per-project configurable. Data stays in EU. DPA signed. |
| Per-project recorder provider selection | MeetingRecorderProvider abstraction allows each project to choose between Reemove.ai (default) and Recall.ai — both EU-based, giving flexibility in recording capabilities. |
| Qdrant for vector database | Hosted in Germany (EU), purpose-built vector DB for semantic search and RAG |