Data protection – information for customers
Data protection – information for customers
Information for customers and business contacts of Stackable GmbH
Version 1.1 · 2026-11-13
Download as PDF1. Responsible party
2. Our role
For the contact data of your staff (name, business email address, phone number, ticket content) we act as an independent controller under the GDPR. We use it to deliver and administer subscriptions and support for the Stackable Data Platform (SDP). We do not process personal data on your behalf.
A data processing agreement under Art. 28 GDPR is therefore not required for the support relationship. Should a specific engagement require us to access systems or data containing personal data, we agree a data processing agreement before it starts.
3. What we process and why
Data
Purpose
Legal basis
Retention
Data
Contract, account and invoice contacts (name, business email address, phone number, role, invoice address)
Purpose
Administering the contract, invoicing, service notices
Legal basis
Art. 6(1)(b) GDPR; Art. 6(1)(f) GDPR for individual contact persons
Retention
6 years after the end of the year in which the contract ended; invoices 8 years under commercial and tax law
Data
Support tickets (contact data, ticket content, attachments)
Purpose
Providing support
Legal basis
Art. 6(1)(b) GDPR; Art. 6(1)(f) GDPR for individual contact persons
Retention
12 months after the contract ends; attachments are deleted together with the ticket
Data
Customer portal: account data (name, business email address, login data, role) and the content you enter or we provide to you there
Purpose
Providing the customer portal as the central place for our business relationship: managing subscriptions and support contacts, communicating with us, submitting requests and feedback, and accessing documents such as invoices and security information
Legal basis
Art. 6(1)(b) GDPR; Art. 6(1)(f) GDPR for individual contact persons
Retention
12 months after the account is closed; content follows the retention of the respective record, for example support tickets or invoices
Data
Shared Slack channels (name, email address, messages and files you post)
Purpose
Communication with customers who accept our invitation to a shared channel
Legal basis
Art. 6(1)(b) GDPR; Art. 6(1)(f) GDPR for individual contact persons
Retention
For the duration of the shared channel; the channel and its content are deleted 12 months after the contract ends
Data
Marketing contacts (name, business email address, company)
Purpose
Newsletter, event invitations
Legal basis
Art. 6(1)(a) GDPR (consent)
Retention
Until consent is withdrawn
From resolved tickets we keep generic technical findings for internal use: what occurred, which behaviour caused it, which settings resolved it, and anonymised log excerpts. We ensure that these records contain no customer data and cannot be linked to a customer.
4. Where your data is processed
Provider
Used for
Location
Data processing agreement
Security documentation
Transfer mechanism
Provider
Atlassian (Jira Service Management)
Used for
Support portal and tickets
Location
EU
Data processing agreement
Atlassian data processing agreement
Security documentation
Transfer mechanism
EU-U.S. Data Privacy Framework (Atlassian certified); standard contractual clauses in the DPA as fallback
Provider
Google (Google Workspace)
Used for
Email and calendar
Location
Global (no data region set)
Data processing agreement
Google Workspace data processing agreement
Security documentation
Google Workspace security whitepaper
Transfer mechanism
EU-U.S. Data Privacy Framework (Google LLC certified); standard contractual clauses in the DPA as fallback
Provider
HubSpot
Used for
CRM: contact, contract and marketing data
Location
EU
Data processing agreement
HubSpot data processing agreement
Security documentation
Transfer mechanism
EU-U.S. Data Privacy Framework (HubSpot, Inc. certified); standard contractual clauses as fallback
Provider
DigitalOcean (hosting of our customer portal and its database)
Used for
Customer portal: accounts and the content held in the portal
Location
EU (Frankfurt)
Data processing agreement
DigitalOcean data processing agreement
Security documentation
Transfer mechanism
EU-U.S. Data Privacy Framework (DigitalOcean, LLC certified); standard contractual clauses in the DPA as fallback
Provider
easybill (easybill GmbH)
Used for
Invoicing: name and address of the invoice addressee
Location
Germany (processing in the EU/EEA only)
Data processing agreement
Data processing agreement concluded
Security documentation
Technical and organisational measures available on request
Transfer mechanism
None required (no transfer outside the EU/EEA)
Provider
Slack (Salesforce)
Used for
Shared channels with customers
Location
United States
Data processing agreement
Slack data processing addendum
Security documentation
Slack GDPR and security information
Transfer mechanism
EU-U.S. Data Privacy Framework (Slack Technologies, LLC, via Salesforce); standard contractual clauses in the DPA as fallback
Provider
Lettermint (Lettermint B.V.)
Used for
Transactional email: notifications from the customer portal and other system emails to customer contacts (name, email address, message content)
Location
EU/EEA (Netherlands and Germany)
Data processing agreement
Lettermint data processing agreement
Security documentation
Transfer mechanism
None required (no transfer outside the EU/EEA)
These providers process data on our behalf under the linked agreements. Where a provider accesses data from outside the EU/EEA, the listed transfer mechanism applies. Invoice data is also passed to our tax advisor, who processes it as an independent controller bound by professional secrecy. Beyond that, we disclose personal data to no other recipients unless required by law.
5. Security
- A written information security policy binds all employees; it is approved by management and reviewed at least once a year. Information security is the responsibility of a designated Chief Information Security Officer.
- All employees are bound to confidentiality and are instructed in data protection and confidentiality obligations when they join; these obligations continue after employment ends.
- Every user authenticates with an individual identity through a central identity provider; shared accounts exist only where an application cannot support individual accounts. Multi-factor authentication is enforced for all users on the identity provider and the core systems connected to it, and required for all other business accounts. Passwords have a minimum length of 12 characters, accounts lock after repeated failed logins, initial passwords must be changed at first login, and credentials are shared only through encrypted one-time links.
- Access rights follow the need-to-know and need-to-use principles and are granted per application by a named responsible person, individually or by role. All systems holding non-public data require authentication and authorisation. Accounts and access rights are reviewed at least once a year.
- Accounts are deactivated when an employee or external user leaves: central accounts by the management team, application accounts by the responsible person for that application. Devices are returned and shared credentials rotated.
- Logins and account changes on the central identity systems are logged.
- Work devices are fully encrypted, lock automatically, run without administrative rights for daily work and receive security updates at least weekly. Private computers are not used for work. Personal or customer data is never stored unencrypted on removable media, and data on decommissioned devices and media is securely deleted.
- Rules for remote work and travel: no third-party access to devices or documents, clean desk, and screen privacy when working with personal data.
- Every cloud service passes a selection process assessed by the Chief Information Security Officer before use, covering security, data protection and the return and deletion of data when the service is terminated; services in use are recorded in an asset inventory. Company and customer data is stored only with the contracted providers listed above; using other services, including free online and AI tools, for confidential or personal data is prohibited. Where a service allows it, we export regular backups so that copies exist outside the provider.
- Encryption in transit and at rest is provided by the processors listed above.
- An emergency plan defines continuity measures for our critical systems; major outages are handled by an emergency task force of management, the Chief Information Security Officer and the infrastructure team.
- Security incidents follow a defined process of reporting, assessment and classification, containment, evidence preservation, recovery and lessons learned, under the responsibility of the Chief Information Security Officer. Employees report through an internal emergency plan; external parties can report to security@stackable.tech.
- Customer portal: runs on DigitalOcean App Platform in Frankfurt with a managed PostgreSQL database. The platform provides HTTPS with managed certificates, DDoS mitigation and automatic operating-system patching; the application itself is deployed and updated from our source repository. The database is reachable only over a private network, encrypted at rest and in transit, and backed up daily with point-in-time recovery for the previous seven days; backups are kept by DigitalOcean separately from the database, so deleted data disappears from backups after at most seven days. Administrative access is limited to named engineers who sign in through our central identity provider with multi-factor authentication, one token-based service account used for deployments, and one emergency account protected by multi-factor authentication. Customer accounts sign in with username and password; multi-factor authentication for customer accounts is not currently offered.
Certifications: none. Our security policies follow the control structure of ISO/IEC 27001:2022. A detailed description of our technical and organisational measures is available on request.
6. Incidents
If a personal data breach affects your data, we notify you without undue delay after becoming aware of it, and the competent supervisory authority within 72 hours where Art. 33 GDPR requires it. Incidents are handled in the process described in section 5; if your data is affected, your business contact at Stackable informs you about the nature and scope of the incident, and our management decides on notifications under Art. 33 and 34 GDPR. Communication with you is coordinated between that contact, the Chief Information Security Officer and management, and limited to verified facts.
7. Your rights
8. Version
Current version: 1.1, 2026-11-13.
Version
Date
Changes
Version
1.1
Date
2026-11-13
Changes
Lettermint added to section 4 as the provider for transactional email.
Version
1.0
Date
2026-11-11
Changes
Initial version.