SubprocessorsList of Subprocessors
Overview of the further processors (subprocessors) that the provider engages for processing customer data pursuant to Art. 28(4) GDPR and § 5 of the Data Processing Agreement.
Version 4 · As of 5 October 2026
This list is Annex 1 to the Data Processing Agreement (DPA). It names the services that process personal data on behalf of customers. Services that the provider uses for this website under its own responsibility are described in the privacy policy.
1. Supabase
| Company | Supabase Pte. Ltd. |
|---|
| Address | 65 Chulia Street #38-02/03, OCBC Centre, Singapore 049513, Singapore |
|---|
| Privacy contact | privacy@supabase.io |
|---|
| Purpose | Database, sign-in and accounts, file storage, real-time sync, and server-side functions (Edge Functions) of the platform. |
|---|
| Data categories | The customer data stored in the platform, including account and sign-in data of users, inspection content (master data, areas, findings, actions, notes, comments), photos with metadata, audio files and transcripts, signatures, contact details of third parties, checklists, generated reports and report templates, profile pictures and company logos, import documents, details of sent emails with delivery status, and feedback, posts, and signatures of external persons via the link pages. |
|---|
| Processing location | Frankfurt am Main (Germany) |
|---|
| Third-country relation and safeguard | Yes. The contracting party is established in Singapore; there is no adequacy decision for Singapore. Access by Supabase and its sub-subprocessors from third countries is possible. Safeguard: EU Standard Contractual Clauses (Module 3) in Supabase’s data processing agreement. |
|---|
| Contracts | |
|---|
2. PowerSync
| Company | Journey Mobile, Inc. |
|---|
| Address | 3700 Quebec St, Ste 100 PMB 132, Denver, CO 80207, USA |
|---|
| Privacy contact | dpo@powersync.com |
|---|
| Purpose | Synchronization of inspection data between the platform and the mobile app. |
|---|
| Data categories | Copy of the tenant’s synchronized inspection data: customers and contacts with contact details (name, function, email, phone, address), projects, inspections with attendees, areas, findings, actions with responsible person and deadline, checklists, notes, comments, and transcripts, and the details of photos, audio files, and signatures (not the files themselves); ID of the signed-in user. |
|---|
| Processing location | Dublin (Ireland) |
|---|
| Third-country relation and safeguard | Yes. The contracting party is established in the USA. It engages Amazon Web Services and MongoDB, among others, as sub-subprocessors; the full list is linked below. Safeguard: EU Standard Contractual Clauses (Module 3) in PowerSync’s data processing agreement. |
|---|
| Contracts | |
|---|
3. Google Cloud Run
| Company | Google Cloud EMEA Limited |
|---|
| Address | 70 Sir John Rogerson’s Quay, Dublin 2, Ireland |
|---|
| Privacy contact | Contact form of the Cloud Data Protection Team |
|---|
| Purpose | Operation of the web app servers including the link pages for external persons, conversion of reports from Word to PDF, conversion of audio recordings, and creation of data exports (ZIP archive). |
|---|
| Data categories | Content of requests to the web app while in transit; report content during conversion to PDF; audio recordings during their conversion; content of the data exports. |
|---|
| Processing location | St. Ghislain (Belgium) |
|---|
| Third-country relation and safeguard | Contracting party in the EU (Ireland). A transfer to Google LLC and other group companies in the USA or other third countries is possible. Safeguard: EU-US Data Privacy Framework (Google LLC is certified) and EU Standard Contractual Clauses in the Cloud Data Processing Addendum. |
|---|
| Contracts | |
|---|
4. Google Vertex AI (Gemini)
| Company | Google Cloud EMEA Limited |
|---|
| Address | 70 Sir John Rogerson’s Quay, Dublin 2, Ireland |
|---|
| Privacy contact | Contact form of the Cloud Data Protection Team |
|---|
| Purpose | AI functions of the platform: checklist import, report import, comment suggestion, action suggestion, and audio transcription. |
|---|
| Data categories | Uploaded import documents including the photos they contain; for action suggestions the texts, photos, notes, actions, and transcripts of the finding together with its area and inspection point; for comment suggestions the same details for the finding, for the inspection point, or as a summary of all findings of the inspection, each with the user’s draft text; for transcription the audio file. |
|---|
| Processing location | Frankfurt am Main (Germany) |
|---|
| Third-country relation and safeguard | Contracting party in the EU (Ireland). A transfer to Google LLC and other group companies in the USA or other third countries is possible. Safeguard: EU-US Data Privacy Framework (Google LLC is certified) and EU Standard Contractual Clauses in the Cloud Data Processing Addendum. |
|---|
| Contracts | |
|---|
5. Google Cloud Storage
| Company | Google Cloud EMEA Limited |
|---|
| Address | 70 Sir John Rogerson’s Quay, Dublin 2, Ireland |
|---|
| Privacy contact | Contact form of the Cloud Data Protection Team |
|---|
| Purpose | Daily backup of the platform’s files. |
|---|
| Data categories | The files kept in the platform’s file storage: photos with metadata, audio files, signatures, generated reports, report templates, profile pictures and company logos, and proof photos from external persons via the link pages. Draft reports, uploaded import documents, data exports (ZIP archive), and the archives of the data return are not backed up. |
|---|
| Processing location | Frankfurt am Main (Germany) |
|---|
| Third-country relation and safeguard | Contracting party in the EU (Ireland). A transfer to Google LLC and other group companies in the USA or other third countries is possible. Safeguard: EU-US Data Privacy Framework (Google LLC is certified) and EU Standard Contractual Clauses in the Cloud Data Processing Addendum. |
|---|
| Contracts | |
|---|
6. Sentry
| Company | Functional Software, Inc. |
|---|
| Address | 45 Fremont Street, 8th Floor, San Francisco, CA 94105, USA |
|---|
| Privacy contact | compliance@sentry.io |
|---|
| Purpose | Error diagnostics for the web app and the mobile app: error events, session replay, and error reports by users, as well as server errors of the web app. |
|---|
| Data categories | Error messages and stack traces with user and tenant ID, application version, route accessed, and browser or device details; in the session replay the displayed texts in plain form, including names of customers and contacts as well as property addresses; in the error report an image of the visible area, the console buffer, the reporter’s email address, and the description and category of the report. |
|---|
| Processing location | Frankfurt am Main (Germany). Only Begehung.pro’s account and organization data at Sentry (user accounts, settings) is located in the USA, no events, replays, or attachments. |
|---|
| Third-country relation and safeguard | Yes. The contracting party is established in the USA. Safeguard: EU-US Data Privacy Framework (Functional Software, Inc. is certified) and EU Standard Contractual Clauses in Sentry’s data processing agreement. |
|---|
| Contracts | |
|---|
7. Amazon Web Services (Amazon SES, Amazon SNS, Amazon EventBridge)
| Company | Amazon Web Services EMEA SARL |
|---|
| Address | 38 Avenue John F. Kennedy, L-1855 Luxembourg, Luxembourg |
|---|
| Privacy contact | aws-EU-privacy@amazon.com |
|---|
| Purpose | Sending all emails of the platform: to third parties (protocols and reports with attachment, task emails, emails for coordinating a draft) and to the platform’s own users (sign-in, confirmation, password, and notification emails); return of delivery, bounce, and complaint events; verification of a customer’s sender domain. |
|---|
| Data categories | Name and email address of recipients, subject, content, and attachment of the emails, sender address and sender domain, delivery events. |
|---|
| Processing location | Frankfurt am Main (Germany) |
|---|
| Third-country relation and safeguard | Contracting party in the EU (Luxembourg). A transfer to Amazon.com, Inc. and other group companies in the USA or other third countries is possible. Safeguard: EU Standard Contractual Clauses (Modules 2 and 3) in the AWS Data Processing Addendum; Amazon.com, Inc. is also certified under the EU-US Data Privacy Framework. |
|---|
| Contracts | |
|---|
8. Google Firebase Cloud Messaging
| Company | Google LLC |
|---|
| Address | 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA |
|---|
| Privacy contact | Contact form of the Firebase Data Protection Team |
|---|
| Purpose | Delivery of push notifications to the app on Android devices, iPhones, and iPads; to iPhones and iPads via the Apple Push Notification service. |
|---|
| Data categories | Device identifier of the app (registration token) and content of the notification: visible part (title and text) and data part (type, identifiers, in-app target path, placeholder values). Depending on the type, the content includes names of persons (whoever reports an action as completed, author of a post, signatory), recipients of an undeliverable or unsent email, customer name, property name, action text, an excerpt of a post (up to 200 characters), report details (format, sealing date, version number), error codes, and the email service’s diagnostic text. No file names, photos, or files. |
|---|
| Processing location | Google’s global infrastructure, including in the USA |
|---|
| Third-country relation and safeguard | Contracting party in the USA. Safeguard: EU-US Data Privacy Framework (Google LLC is certified) and EU Standard Contractual Clauses in the Firebase Data Processing and Security Terms. |
|---|
| Contracts | |
|---|
9. Apple Push Notification service
| Company | Apple Inc. |
|---|
| Address | One Apple Park Way, Cupertino, CA 95014, USA |
|---|
| Privacy contact | Apple’s privacy contact form |
|---|
| Purpose | Delivery of push notifications to iPhones and iPads. |
|---|
| Data categories | Device identifier at Apple’s push service and content of the notification: visible part (title and text) and data part (type, identifiers, in-app target path, placeholder values). Depending on the type, the content includes names of persons (whoever reports an action as completed, author of a post, signatory), recipients of an undeliverable or unsent email, customer name, property name, action text, an excerpt of a post (up to 200 characters), report details (format, sealing date, version number), error codes, and the email service’s diagnostic text. No file names, photos, or files. |
|---|
| Processing location | Apple’s servers, including in the USA |
|---|
| Third-country relation and safeguard | Contracting party in the USA. Apple Inc. is not certified under the EU-US Data Privacy Framework. Apple does not offer a separate data processing agreement for the Apple Push Notification service; the terms of the Apple Developer Program License Agreement (Attachment 1) apply. According to its privacy policy, Apple bases transfers from the European Economic Area on EU Standard Contractual Clauses; a copy is available via Apple’s privacy contact form. |
|---|
| Contracts | |
|---|
Notice and objection
The provider announces an intended change to this list by email to the address of the customer account, at least four weeks before the new or changed subprocessor is engaged. If an existing subprocessor engages a further sub-subprocessor, the provider informs the customer without undue delay after becoming aware of it. The customer may object to the change in accordance with § 5 of the DPA.
Change log
| Date | Change |
|---|
| 5 Oct 2026 | Version 4. Google Firebase Cloud Messaging and Apple Push Notification service: delivery of push notifications to the app. |
| 28 Sep 2026 | Version 3. Google Cloud Storage: backup of the files. |
| 25 Sep 2026 | Version 2. Amazon Web Services added (engaged since 3 Sep 2026). Third-country information corrected: version 1 stated no third-country relation for any entry; Supabase (Singapore), Journey Mobile, and Functional Software (USA) are established in a third country, and Google and Amazon may transfer data to their US parent companies. Added for each entry: full address, privacy contact, data categories, processing location with city, safeguard, and the providers’ contracts and subprocessor lists. Google Cloud Run: purposes extended by the conversion from Word to PDF, the conversion of audio recordings, and the data exports; the provider is itself responsible for operating this website (see privacy policy). Google Vertex AI completed with comment suggestion, action suggestion, and audio transcription. Sentry: mobile app and server errors of the web app added. Supabase no longer sends sign-in and password emails; they are sent via Amazon Web Services. Processing location of PowerSync: Dublin (Ireland). |
| 3 Sep 2026 | Amazon Web Services (Amazon SES, Amazon SNS, Amazon EventBridge) engaged for the platform’s email delivery; added to this list with version 2 on 25 Sep 2026. |
| 20 Aug 2026 | Version 1. List published with Supabase, PowerSync, Google Cloud Run, Google Vertex AI, and Sentry. |
The provider makes a copy of the agreement with a subprocessor available on request (§ 5(5) DPA); for the Apple Push Notification service, the linked Apple terms apply. Questions about this list are answered by the provider’s privacy contact: datenschutz@begehung.pro.