Platform
Platform OverviewAI Adoption & Multi-ModelSelf-Updating AI CRMSales & Industry CRMSales CRM Use CasesRecruiting CRM Use CasesB2B Contact IntelligenceMultichannel OutboundProjects & TasksTeam MessengerSocial Media StudioFunnels & NewslettersMeetings & Scheduling
Consulting, Pricing & Resources
AI & Cloud TransformationManaged GTM ServicesAlexander Weltzsch · Executive AdvisoryDennis Hilger · B2B Growth AdvisoryPricing & SaaS Savings CalculatorAboutEnterprise AI InsightsAI & B2B GlossaryB2B Landing Page PlaybookTrust Center & LegalContact & Live Demo
← Back to Trust Center
Trust Center · Art. 32 GDPR

Technical & Organizational Measures (TOMs)

English translations are provided for convenience. Under German law, the original German versions govern.
NOTE: Convenience Translation: This English translation of our Technical and Organisational Measures is provided for informational and convenience purposes only. In case of any discrepancies or legal disputes, the original German version (Technische und organisatorische Maßnahmen) remains legally and contractually binding.

Technical and Organisational Measures (TOMs) of Dealcode GmbH

pursuant to Art. 32 GDPR for the marketing website dealcode.ai, the CRM platform app.dealcode.ai, the mobile event lead scanner scanner.dealcode.ai, and the booking platform meetings.dealcode.ai

As of: September 2026 | Version 2.0 (Binding Annex to the Data Processing Agreement)



Preamble & Introduction

Taking into account the state of the art, the costs of implementation, and the nature, scope, context, and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Dealcode GmbH, c/o SPACE Hamburg, Am Sandtorkai 27, 20457 Hamburg, Germany (hereinafter "Processor" or "dealcode"), implements the following technical and organisational measures pursuant to Art. 32 GDPR to ensure a level of security appropriate to the risk for the Controller's data.



1. Confidentiality (Art. 32(1)(b) GDPR)

1.1 Physical Access Control

Measures to prevent unauthorized persons from gaining physical access to data processing systems used to process personal data.
  • Physical Security of Cloud Data Centers (Google Cloud Platform):
  • dealcode does not operate proprietary physical server rooms or on-premise data centers. All server, application, container, and database systems are hosted 100% in certified data centers of the Google Cloud Platform in Frankfurt am Main, Germany (europe-west3). Google Cloud data centers maintain internationally recognized security certifications in accordance with ISO/IEC 27001, ISO/IEC 27017, ISO/IEC 27018, SOC 1/2/3, and BSI C5. Physical security of the data centers includes: Multi-layered security perimeters with biometric access control, turnstiles, and laser intrusion detection; Continuous 24/7 surveillance by trained security personnel and high-resolution CCTV; Strict visitor management protocols requiring ID verification, advance authorization, and continuous escort; Automated alarm systems for unauthorized access attempts and comprehensive access logging.
  • Physical Security at Corporate Headquarters (Am Sandtorkai 27, 20457 Hamburg):
  • No servers containing customer data are operated at company headquarters. Office premises access is secured via electronic badge access systems. Keycards are assigned personally and can be deactivated centrally and immediately upon loss. Visitors are logged and escorted by staff while on office premises. Lockable security cabinets are utilized for confidential personnel and corporate records.

    1.2 System Access Control

    Measures to prevent unauthorized persons from using data processing and IT systems.
  • Authentication on Customer and User Systems (app.dealcode.ai / scanner.dealcode.ai):
  • User login is tenant-specific via corporate email addresses and complex passwords. Passwords are never stored in plaintext, but processed using state-of-the-art, cryptographically resilient hashing algorithms (bcrypt with an appropriate salt work factor). Two-Factor Authentication (2FA): The platform enforces two-factor verification for administrative logins and sensitive actions via time-limited, cryptographic one-time tokens (AuthToken) delivered through verified channels. Brute-Force Protection & Rate Limiting: Automated account lockouts and exponential throttling (rate limiting) are applied after consecutive unsuccessful authentication attempts. OAuth 2.0 Identity Providers: Users can alternatively authenticate via official enterprise identity providers (Google Workspace, Microsoft 365 Entra ID) using Single Sign-On (SSO).
  • Authentication on Internal Administration Systems:
  • Access to internal management dashboards (admin.dealcode.ai) is strictly restricted to individually named and authorized system administrators. 2FA is technically enforced without exception for all administrative accounts. Administrative support access to customer workspaces occurs exclusively following explicit authorization by the customer or within the scope of contracted customer support.
  • Cloud Infrastructure and Database Access:
  • No Direct SSH Access over the Internet: Cloud Run container instances are isolated and do not expose static, publicly accessible SSH ports. Cloud SQL Auth Proxy: Production MySQL database access occurs strictly via IAM-authenticated, encrypted proxy tunnels without public IP exposure. Principle of Least Privilege in Cloud IAM: Google Cloud Console permissions follow the least privilege model. Production environment access requires personal accounts secured with hardware security keys (FIDO2/WebAuthn).
  • Employee Endpoint Security:
  • Full-disk encryption (FileVault / BitLocker with AES-256) is mandatory on all employee workstations. Automated screen lock is enforced after a maximum of 5 minutes of inactivity. Centrally managed endpoint detection and antivirus software are deployed across all devices.

    1.3 Data Access Control

    Measures to ensure that persons authorized to use a data processing system have access only to the data to which they have access rights.
  • Role-Based Access Control (RBAC):
  • The platform implements a granular role and permission model with 6 distinct system roles: WORKSPACE_OWNER: Full ownership, billing data, workspace deletion; ADMINISTRATOR: User management, system configuration, integrations; MANAGER: Campaign and data approvals, lead assignments; CAMPAIGN_MANAGER: Creation and management of campaigns and sequences; VIEWER: Read-only access to designated CRM records; AGENCY: Cross-tenant management for authorized partner agencies. All API routes perform server-side permission checks (requireTenantAuth, rbac.ts) before executing data operations.
  • Logical Multi-Tenancy Isolation:
  • Data belonging to different customers is strictly separated within the central relational database. Every record (contacts, companies, campaigns, deals, notes, activities, tasks) is strictly partitioned and bound to a unique tenant identifier (tenantId / tenantDomain). Prisma middleware and server-side database layers enforce tenant filtering on every query. Automated integration tests ensure no database queries can execute without valid tenant binding.
  • Customer Support Authorization:
  • dealcode employees have no visibility into customer CRM contact records or email contents during standard platform operations. Temporary support access may only be granted upon explicit request and instruction by the customer for troubleshooting purposes.

    1.4 Separation Control

    Measures to ensure that data collected for different purposes can be processed separately.
  • Separation of Development, Staging, and Production Environments:
  • Strict separation is maintained between production systems (app.dealcode.ai), staging environments, and local developer workstations. Development and test systems utilize exclusively synthetic test data or anonymized mocks. No real personal customer data is ever processed in staging or development environments.
  • Functional Data Separation:
  • CRM business data, billing records (Credit Ledger), and security audit logs are maintained in distinct database tables. File attachments, voice memos, and business card images are stored separately from relational databases in secured Google Cloud Storage buckets utilizing tenant-specific path partitions and time-limited signed URLs.

    1.5 Pseudonymisation (Art. 32(1)(a) GDPR)

  • Statistical Telemetry & System Metrics: Performance monitoring and error tracking telemetry are aggregated without personal identifiers.
  • SalesViewer Visitor Data: Company visitor identification on the marketing website operates via statistical corporate IP resolution. Private residential IP addresses are discarded immediately and never persisted.

  • 2. Integrity (Art. 32(1)(b) GDPR)

    2.1 Transfer Control & Transit Encryption

    Measures to ensure that personal data cannot be read, copied, modified, or deleted without authorization during electronic transmission.
  • Encryption in Transit:
  • All web connections to dealcode.ai, app.dealcode.ai, scanner.dealcode.ai, and meetings.dealcode.ai are encrypted via HTTPS with Transport Layer Security (TLS 1.3 / minimum TLS 1.2) using Perfect Forward Secrecy (PFS) and modern cipher suites. Unencrypted HTTP requests are automatically redirected to HTTPS via HTTP Strict Transport Security (HSTS). Internal communication between Google Cloud Run services, Cloud SQL Auth Proxies, and Cloud KMS occurs over encrypted Google private backend networks.
  • Cryptographic Protection of External APIs:
  • Communication with external APIs (Google Workspace, Microsoft Graph, Unipile, FullEnrich, SalesViewer) is conducted exclusively over TLS-encrypted HTTPS endpoints.
  • Email Transport Encryption:
  • Campaign and transactional system emails are dispatched with opportunistic to enforced TLS encryption as supported by receiving mail transfer agents.

    2.2 Storage Control & Encryption at Rest

    Measures to ensure that stored data is protected against unauthorized access and tampering.
  • Encryption at Rest:
  • All database instances (Google Cloud SQL MySQL 8.0) are encrypted at the filesystem and storage block level using AES-256. All Google Cloud Storage buckets (documents, images, audio recordings) are encrypted by default using AES-256.
  • Key Management via Google Cloud KMS:
  • Sensitive secrets such as OAuth refresh tokens (Gmail, Microsoft 365, Social Media) and external API keys are never stored in plaintext. They are protected via Envelope Encryption utilizing master encryption keys managed in Google Cloud Key Management Service (Cloud KMS). Master keys reside in Hardware Security Modules (HSMs) in the Frankfurt am Main cloud region (europe-west3) and are never exposed in application source code or log files.

    2.3 Input Control & Tamper-Proof Audit Logging

    Measures to verify whether and by whom personal data has been entered, modified, or removed in data processing systems.
  • Centralized Audit Logging:
  • Key security- and administration-relevant events are logged in a tamper-resistant format: TenantLogin: Timestamp, user ID, IP address, user-agent string, authentication outcome; TenantActivity: Functional interaction logging and module views; AdminAuditLog: Administrative modifications (e.g. role updates, subscription plan changes); CreditLedgerTransaction: Comprehensive ledger recording every credit debit/credit with tenant ID, user email, timestamp, action key, and resulting balance.
  • Log File Integrity:
  • System and application logs are collected in Google Cloud Logging (Stackdriver). Log integrity is protected against retrospective tampering by users or third parties.

    3. Availability and Resilience (Art. 32(1)(b) GDPR)

    3.1 Availability Control & Fault Tolerance

    Measures to ensure that personal data is protected against accidental destruction or loss and systems remain available.
  • High-Availability Container Architecture:
  • Web applications and APIs run on Google Cloud Run. Cloud Run horizontally scales microservices across multiple physical availability zones within the Frankfurt am Main region (europe-west3).
  • Database High Availability:
  • The Cloud SQL MySQL database is deployed with automated cross-zone replication. In case of hardware failure in one zone, automatic failover to the standby instance occurs without data loss.
  • DDoS Protection & Web Application Firewall:
  • Google Cloud Armor and Google's global edge infrastructure protect platform services against Distributed Denial of Service (DDoS Layer 3, 4, and 7) attacks.
  • Monitoring & Alerting:
  • 24/7 service availability, latency, and error rate monitoring via Google Cloud Monitoring and external uptime checkers. Automated escalation paging to the on-call engineering team upon breach of defined operational thresholds.

    3.2 Recoverability (Art. 32(1)(c) GDPR)

    Measures to ensure that systems and data can be restored rapidly in the event of an incident.
  • Automated Backup Strategy:
  • Daily automated full database backups of the production Cloud SQL instances. Point-in-Time Recovery (PITR): Continuous binary logging enables point-in-time state recovery to any second within a minimum retention window of 7 days.
  • Backup Storage & Verification:
  • Backups are encrypted (AES-256) and stored redundantly across Google Cloud Storage. Automated restoration tests verify that database backups can be restored without errors.
  • Disaster Recovery Plan (DRP):
  • A documented Disaster Recovery Plan defines recovery targets: RTO (Recovery Time Objective): < 4 hours for core services, < 24 hours for full system restoration; RPO (Recovery Point Objective): < 15 minutes via continuous transaction logs.

    4. Regular Testing, Assessing and Evaluating (Art. 32(1)(d) GDPR)

    4.1 Data Protection Management & Incident Response

  • Appointment of a Data Protection Officer:
  • External DPO: Martin Bastius, heyData GmbH, Kantstraße 99, 10627 Berlin, Germany (datenschutz@heydata.eu).
  • Security Incident Response Process:
  • Documented incident management protocols for detecting, evaluating, and reporting data breaches. In the event of a reportable personal data breach (Art. 33/34 GDPR), affected Controllers are notified without undue delay within at most 48 hours of confirmation to allow Controllers to meet their statutory 72-hour supervisory reporting window.
  • Employee Confidentiality & Training:
  • All personnel are contractually committed in writing to data secrecy and confidentiality under § 53 BDSG and Art. 28(3)(b) GDPR prior to commencing duties. Regular data protection and information security training for all staff.

    4.2 Technical Vulnerability Management & Code Security

  • Automated Vulnerability Scanning (CI/CD Pipeline):
  • Automated dependency audits on every code commit (npm audit, GitHub Dependabot, static code analysis). Strict deployment policies prohibiting dependencies with known critical vulnerabilities.
  • Code Reviews & Four-Eyes Principle:
  • All code updates undergo mandatory peer review prior to merging into production branches. Automated unit and integration test coverage for authentication, RBAC, and multi-tenancy boundaries.

    5. Specific Security Measures for Modern Platform Modules

    5.1 Artificial Intelligence & LLM Processing (Google Vertex AI)

  • Strict Purpose Limitation & Exclusion of Model Training:
  • Natural language processing for emails, transcripts, notes, and drafts utilizes enterprise APIs from Google Cloud Vertex AI (Frankfurt am Main). Google contractually commits never to use data from enterprise workspaces to train, retrain, or refine general foundation models.
  • Prompt Sanitization & Preflight Verification:
  • Before dispatching campaign messages, an automated routine (aiPreflight.ts / verifyAndPolishMessage) validates drafts for unpopulated placeholders, syntax errors, and unintended disclosures.
  • Protection of Google User Data:
  • Strict adherence to the Google API Services User Data Policy* (Limited Use Requirements): Google Workspace API data is never utilized for advertising purposes.

    5.2 Mobile Lead Scanner App (scanner.dealcode.ai)

  • Browser Sandbox & OS Permissions:
  • The mobile scanner web application runs within the sandbox environment of modern mobile browsers (iOS Safari / Android Chrome). Camera and microphone access require explicit, native user authorization via the mobile operating system for each session.
  • Secure Media Transmission:
  • Captured business card photos and voice memos are not cached unencrypted on the mobile device, but streamed directly via TLS-secured APIs to Google Cloud Storage. Client-side QR decoding (jsQR) minimizes unnecessary transmission of raw image data to backend servers.

    5.3 Appointment Scheduling & Mailbox Dispatch (meetings.dealcode.ai)

  • Proxy Routing & PWA Cache Isolation:
  • The subdomain meetings.dealcode.ai is served via a dedicated edge proxy (proxy.ts). Service worker caches and client storage are strictly isolated to prevent client-side cache poisoning.
  • Host Mailbox Authorization:
  • Calendar invites and confirmation emails are dispatched directly through the customer's authenticated mailbox (Gmail API or Microsoft Graph). dealcode acts purely as a coordinating API interface.

    6. Subcontractor Management & BYOK Distinction

  • Subcontractor Due Diligence & Contractual Coverage:
  • All sub-processors undergo technical and organizational vetting prior to engagement. Data Processing Agreements pursuant to Art. 28 GDPR including EU Standard Contractual Clauses are executed with all vendors.
  • Core Sub-processors of dealcode:
  • Service Provider / SubcontractorCorporate Seat / Data ResidencyFunction / Services ProvidedCertifications & Safeguards
    Google Cloud EMEA Ltd.Dublin, Ireland / Frankfurt am Main (europe-west3)Primary hosting, Cloud Run, Cloud SQL (MySQL), Cloud KMS, Cloud Storage, Vertex AI EnterpriseISO 27001, ISO 27017, ISO 27018, SOC 1/2/3, BSI C5
    Unipile SASParis, France (EU)Provision of a hosted interface session (Hosted Session / Auth on Behalf) for the optional secure connection of the user's social media profileGDPR-compliant DPA, EU data residency
    SalesViewer GmbHBochum, Germany (EU)Corporate visitor identification (Buyer Intent) with 72h bufferGDPR-compliant DPA, German data center
    Stripe Technology Company Ltd.Dublin, Ireland (EU)Payment processing for subscriptions and credit bundlesPCI-DSS Level 1, SOC 1/2 Type II
    FullEnrich SAS / Corp.Paris, France (EU) / USAOptional B2B contact data enrichment (active credit usage only)EU entity, EU Standard Contractual Clauses
    Aircall SASParis, France (EU)Planned telephony and voice communication interfaceISO 27001, GDPR-compliant DPA, EU seat
    1. Distinction from Customer-Connected Third-Party Systems (OAuth & BYOK):
    Services connected directly by the customer via OAuth or personal API keys (such as Google Workspace, Microsoft 365, Dropcontact, BetterContact, or personal LLM API keys) are not sub-processors of Dealcode. For these services, a direct contractual and data processing relationship exists between the customer and the respective provider. Dealcode acts solely as an authorized technical client acting strictly upon customer instruction.

    These Technical and Organisational Measures (TOMs) form Annex 2 and are an integral, binding component of Dealcode's comprehensive legal and compliance framework:

    Data Processing Agreement (DPA / Art. 28 GDPR): https://www.dealcode.ai/legal/data-processing-agreement
    List of Sub-processors (Art. 28(2) GDPR): https://www.dealcode.ai/legal/list-of-sub-processors
    General Terms and Conditions (T&Cs): https://www.dealcode.ai/legal/terms
    Privacy Policy (Website & Platform): https://www.dealcode.ai/legal/privacy-policy
    Profile Visibility & Opt-Out (Art. 21 GDPR): https://www.dealcode.ai/opt-out
    Dealcode Trust Center: https://www.dealcode.ai/trust-center