4,125 words, 113 clausesupdated November 11, 2025read 13/10/2026source
·Last Updated: November 11, 2025 (Version 1.0.10) Sign the Data Processing Agreement here Pitch Software GmbH
| 1 | Purpose and extent of Data Processing | Provision of the Pitch software as a web application, desktop application, or mobile application, and which functions as a platform for creating, collaborating, and distributing of presentations; the collection, storage, analysis and reporting to the Customer of data and metrics of reader engagement with presentations; fulfilment of the Processor's obligations under the Contract. Tools based on large language models such as generative pre-trained transformer models ("GPT") may be used for presentation generation, automatically annotating slide data, convert images used across the web application into a vector representation. |
|---|---|---|
| 2 | Types of personal data | Contact data; usage data; any data filled in by the Customer in the Software, such as prompts; Employee Data; Customer Data; Supplier Data; User-generated Data; User data; Profile data; Usernames; password; email; logfiles; data relating reader interaction with presentations; |
| 3 | Categories of data subjects | Users of the Pitch software; readers of presentations; possibly other data subjects mentioned or included in data filled in by the Customer in the Software. |
·According to Art. 32 GDPR controller and processor of personal data must take technical and organizational measures (TOM) to ensure that the security and protection requirements of data protection are met. Technical measures are to be understood as all protection attempts that are physically implementable in the broadest sense, such as securing doors and windows or measures implemented in software and hardware, such as setting up a user account and password requirement. Organizational measures are to be understood as protection attempts that are implemented through instructions, procedures and procedures.
| No. | Category of Measures | Description of Category | Technical Measures | Organisational Measures |
| 1 | Encryption (Art. 32 (1) a) GDPR) | Cryptographic measures to ensure that information is hashed when transferred internally or externally and can only become readable again by using the correct encryption key. | Encryption of the company website ("data in motion") |
| Encryption of data carriers on laptops/notebooks and mobile data carriers ("data at rest") |
| 2 | Confidentiality - physical access control (Art. 32 (1) b) GDPR) | Measures to prevent unauthorised persons from gaining access to data Processing systems with which personal data is processed or used. | Security of the buildings, windows and doors with an alarm system | Digital keys management system |
| Automated access control system and manual locking system with safety locks Light barriers/motion detectors Video surveillance of entrances |
| 3 | Confidentiality - data access control (Art. 32 (1) b) GDPR) | Measures to prevent data Processing systems from being used without authorisation. | Authentication with username /password, and/or biometric methods | Allocate user rights, defining user profiles, assignment passwords, and assign user profiles to IT-systems |
| Use of Intrusion-Detection-Systems | Immediate blocking of authorization when employees leave the company Locked housings / security locks |
| Password protected screensavers and automated screen locking in case of inactivity, and two-factor user authentication |
| Implementation of virtual networks for the separation of data streams |
| 4 | Confidentiality - data usage control (Art. 32 (1) b) GDPR) | Measures to ensure that persons entitled to use a data Processing system have access only to the data to which they have a right of access, and that personal data cannot be read, copied, altered or removed without authorisation in the course of Processing or use and after storage. | Use of document shredders or appropriate service providers and physical deletion of data mediums before reuse | Development of an authorization concept (Differentiated authorisations for read, edit or delete data) and password procedures (incl. special characters, minimum length, change of password) |
| Assignment of rights by system administrator |
| 5 | Confidentiality - transmission control (Art. 32 (1) b) GDPR) | Measures to ensure that personal data cannot be read, copied, altered or removed during electronic transmission or transport or storage onto data carriers, and that it is possible to check and establish to which bodies the transfer of personal data by means of data transmission facilities is envisaged. | Documentation of all interfaces | Documentation of recipients of data and the time periods of planned surrender or agreed erasure time limits |
| 6 | Confidentiality - separation control (Art. 32 (1) b) GDPR) | Measures to ensure that data collected for different purposes can be processed separately. | Segregation of functions (production/testing) | Development of an authorization concept |
| Separated databases and separate tables within database | Logical client separation |
| 7 | Integrity - input control (Art. 32 (1) b) GDPR) | Full documentation of data management and maintenance must be maintained - to ensure the ongoing integrity of data. Measures for subsequent checking whether data has been entered, changed or removed (deleted), and by whom. | No local admin privileges | Assignment of authorisations for input |
| Alteration and erasure of data on the basis of an authorisation concept |
| 8 | Availability - availability control (Art. 32 (1) b) GDPR) | Measures to ensure that personal data is protected from accidental destruction or loss. | Air conditioning in server rooms | Alarm during unauthorized entry into server room |
| Fire extinguishers in server rooms, installation of fire and smoke detection systems, uninterruptible power supply (UPS) | Remote data backup in secure outsourced locations |
| Monitoring of temperature and humidity and power outlet strip with surge protection in server rooms | Development of an emergency plan and a disaster recovery plan, in flood areas: server rooms above waterline |
| Server room not under sanitary facilities |
| 9 | Availability - job control (Art. 32 (1) b) GDPR) | Measures to ensure that, in the case of commissioned Processing of personal data, the data is processed only in accordance with the instructions of the Controller. | Selection of the Processor giving consideration to diligence aspects (in particular with respect to data security) Contractual penalties for breaches |
| Written instructions to the Processor (e.g. Data Processing Agreement) as defined in Art. 28 (2) GDPR |
| Processor has appointed a Data Protection Officer |
| Efficient rights of control agreed with the Processor |
| Putting the Processor's employees under an obligation of data confidentiality (Art. 28 Abs. 3 lit. b GDPR) |
| Assurance of deletion of the data at the end of the provision of services, continuous control of the Processor and its activities |
| Use of Subcontractors requires the Controller's consent and prior verification and documentation of the security measures taken by the Processor |
| 10 | Resilience (Art. 32 (1) b) GDPR) | Measures to ensure the resilience of the systems and services that guarantee that the systems and services are designed in such a way that even high peak loads and high continuous loads of Processing can be handled. | Testing of storage, access and line capacities |
| 11 | Restoration of availability (Art. 32 (1) c) GDPR) | Measures to ensure that availability of and access to the data can be restored in a timely manner in the event of a physical or technical incident. | Redundant design of the infrastructure (of hard disks, e.g. RAID) | Backup concept |
| Cloud Service | Testing of data restoration |
| 12 | Data protection management (Art. 32 (1) d) GDPR) | Measures to ensure a process for regularly testing, assessing and evaluating the effectiveness of the technical and organisational measures for ensuring the security of the Processing. | Checking of the DSB and the IT revision |
| No. | Name of the further processor | Description of processing via this further processor |
|---|---|---|
| 1 | Auth0, Inc., 10800 NE 8th Street Suite 600, Bellevue, WA 98004, USA | Authentication software |
| 2 | Amazon Web Services Inc. 410 Terry Avenue North, Seattle, WA 98109-5210, USA. | Secure cloud service platform for database storage |
| 3 | Zebrafish Labs (Imgix), 423 Tehama Street Floor 1 San Francisco, CA 94103, USA | Image optimization software |
| 4 | Longtail Ad Solutions, Inc. (JWPlayer), 2 Park Ave FL 10, New York, NY, 10016-5675, USA | Live collaboration enabling software |
| 5 | Pusher Ltd 28 Scrutton Street London, EC2A 4RP, United Kingdom | API service for adding real-time bi-directional |
| 6 | WorkOS Inc. 775 14th Street, San Francisco, CA, 94114, USA | Enterprise SSO software |
| 7 | MagicBell, Inc. 340S Lemon Ave #9214, Walnut, CA, 91789, USA | In-app notification software |
| 8 | Mux, Inc. 34-37 Liverpool Street,Unit 4.06, 4th Floor, London, EC2M 7PP, United Kingdom | Video transmission software |
| 9 | Sendgrid Twilio Germany GmbH Rosenheimer Str. 143C, 8167, Munich, Germany | Authentication software |
| 10 | Algolia, Inc. 301 Howard St, 3rd floor, San Francisco, CA 94105, USA | Search API |
| 11 | OpenAI OpCo, LLC 3180 18th St., San Francisco, CA 94110, USA | API platform for accessing Large Language Models GPT-4 and GPT 3.5 |
| 12 | Anthropic PBC, 548 Market St, PMB 90375, San Francisco, CA 94104, USA | API platform for accessing Large Language Model Claude |
| 13 | fal - Features & Labels Inc., 2261 Market St. Suite 10467, CA 94114, USA | API platform for generative media models Sign the Data Processing Agreement here |
·Please contact us on privacy@pitch.com, should you have any questions. Version 1.0.10 (November 11, 2025)