Aller au contenu

This page is available in English and German only. Showing the English version.

Version du 14 November 2026English · DeutschCe qui a changé
Somme de contrôle de cette version (SHA-256)

4be9313bc0c2e9b201ce53dd1854cb874b7d13a63530d90664d988507020f995

Version antérieure, remplacée par la version du 16 novembre 2026. Vers la version actuelle

PackMate — Data Processing Agreement (Art. 28 GDPR)

This agreement is provided in German and English; the German version prevails.

Version of 14 November 2026

Preamble

This agreement governs the processing of personal data by the processor on behalf of the controller in the context of the use of the Shopify application PackMate.

The controller is the operator of the Shopify shop (“merchant”) who installs PackMate.

The processor is:

Valerian Huber, Einzelunternehmen (sole proprietorship)

(address as stated in the legal notice (Impressum) at packmate.shop)

support@packmate.shop

Conclusion of the agreement

This agreement is concluded when the merchant agrees to it in the app. Before that, PackMate does not process any personal data of the merchant's customers. There is no individual negotiation — the application is provided on a standardised basis via the Shopify App Store. Anyone who requires different terms contacts support@packmate.shop before acceptance.

This agreement is available at packmate.shop/dpa (as promised in the privacy policy). It takes precedence over the terms of use insofar as it concerns the processing of personal data.

Demarcation: what PackMate is itself responsible for

This agreement concerns only the data that PackMate processes on behalf of the merchant — above all data of its end customers. For the merchant's own data (shop domain, contact email, settings, billing) and for visitors to the website packmate.shop, PackMate is a controller in its own right; the privacy policy applies to these (packmate.shop/privacy).

The merchant's platform. Shopify (Shopify International Limited, Ireland) processes the shop data under the merchant's own agreement with Shopify. PackMate only reads and writes there on the merchant's instructions. Shopify is not a sub-processor of PackMate.

Recipient on the merchant's instructions. DHL Paket GmbH (Germany) is a controller in its own right for the carriage. If the controller creates a label, PackMate transmits the recipient's name and address for this purpose via the controller's own DHL business customer access. DHL is not a sub-processor of PackMate.

§ 1 Subject matter, nature and purpose of the processing

The subject matter is the provision of a packaging and shipping tool within the controller's Shopify shop.

The purpose of the processing is exclusively the provision of this service:

  • Calculation of the suitable packaging for orders (pack calculation, 3D view)
  • Creation of DHL shipping labels in the name of the controller via the controller's own DHL business customer access
  • Reporting shipment data back to the shop (fulfilment, shipment number)
  • Generation of packing slips
  • Provision of the administration interface and assistance with data subject requests
  • Support at the request of the controller

Excluded is any use of the data for the processor's own purposes, in particular for profiling, for disclosure to third parties for advertising purposes or for training AI models. PackMate does not operate its own AI inference.

Duration: The processing takes place for the duration of the installation. It ends with the uninstallation of the application; the consequences are governed by § 9.

§ 2 Type of data and categories of data subjects

Categories of data subjects

  • End customers of the controller (recipients of shipments)
  • Staff of the controller who operate the application

Categories of personal data that PackMate stores

CategoryFields
Recipient data for the shipping labelName, address (street, postcode, city, country)
Shipping label as a fileDHL label (PDF) on which name and address are printed
Shipment referenceOrder number, DHL shipment number, shipment number for tracking, carton dimensions, weight, status
Data subject requestsEmail address and Shopify customer ID of the requesting person, affected orders
Login data of staffShopify session (access token, first name and last name, email of the logged-in user)

Processed only transiently, not stored: The delivery address of an order for the packing slip is read from Shopify at the time of generation.

Not processed:

  • Email address and telephone number of end customers are not transmitted to DHL and not stored in shipping_labels — for the recipient, the DHL order contains only name and address. The only exception is the email from a data subject request (row “Data subject requests” above).
  • Payment data: Billing runs via Shopify (Managed Pricing); PackMate receives no card or account data.
  • Special categories under Art. 9 GDPR.

Access rights in Shopify: PackMate requests only the rights named in the app configuration — these do not include a right to customer records (read_customers).

§ 3 Binding nature of instructions

The processor processes personal data solely on documented instructions from the controller. This agreement as well as the configuration and operation of the application by the controller (for example: create label, cancel label) are deemed instructions.

A transfer to a third country takes place only on documented instructions from the controller and subject to the conditions of Arts 44 et seq. GDPR. Transfers to the sub-processors in Annex 1 are deemed instructed.

Individual instructions are to be addressed in text form (e.g. email) to support@packmate.shop.

If the processor considers an instruction to be unlawful, it informs the controller thereof without undue delay and may suspend its execution until the controller confirms or amends it.

Processing on the basis of a legal obligation under Union or Member State law remains permissible; the processor informs the controller beforehand, unless the law prohibits this.

§ 4 Confidentiality

The processor uses for the processing only persons who have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. The obligation continues beyond the end of their activity.

Transparency note: The processor is a sole proprietorship. Only the owner has access to production data. No other persons are used; should this change, sentence 1 applies.

§ 5 Technical and organisational measures (Art. 32)

The processor takes the measures described in Annex 2 (TOM) and maintains them for the term of the agreement.

The measures may be developed further as long as the level of protection is not reduced. Material changes are documented.

The annex also expressly names open items. The controller can thereby carry out its risk assessment on a complete basis.

§ 6 Sub-processors (Art. 28(2) and (4))

The controller grants general written authorisation for the engagement of the sub-processors named in Annex 1.

Before adding or replacing a sub-processor, the processor informs the controller in text form (e.g. email) with a notice period of 30 days. The controller may object to a change within 30 days of being informed. If the parties do not reach agreement, the controller may terminate the contract with effect from the time of the change.

Where the processor engages a sub-processor, it imposes on it by contract the same data protection obligations as apply to the processor under this agreement, in particular sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing meets the requirements of the GDPR. Where a sub-processor fails to fulfil its data protection obligations, the processor remains fully liable to the controller for the performance of the sub-processor's obligations.

§ 7 Data subject rights

The processor assists the controller by appropriate measures in fulfilling requests of data subjects (Arts 15–22 GDPR).

If a data subject contacts the processor directly, the processor forwards the request without undue delay to the controller and does not answer it itself.

The request channels that Shopify provides for apps are implemented:

RequestWhat PackMate does
Access (customers/data_request)The request is stored and displayed to the controller in the interface, together with the label data stored for the orders named. The controller answers the request.
Erasure (customers/redact)For the orders named, name and address in shipping_labels are replaced by the placeholder [redacted] and the label PDF (label_url) is deleted. Email and customer ID in gdpr_requests are cleared.

After an erasure, the shipment reference, dimensions and weight are retained. They no longer carry a name and no longer an address and serve the controller as proof of its shipments and for its packaging quantity reports.

If an erasure or access step fails technically, the application reports an error to Shopify and Shopify delivers the request again — a request is thus not silently lost.

If a concern cannot be handled through these channels (for example a rectification), the processor assists on request.

§ 8 Notification obligations and assistance (Arts 32–36)

The processor notifies the controller without undue delay, and at the latest within 24 hours of becoming aware of it, of any personal data breach.

The short period is chosen deliberately: the controller's notification deadline vis-à-vis the supervisory authority (72 hours, Art. 33(1)) begins with this notification.

The notification contains, as far as known: nature of the incident, data categories concerned and approximate number of data subjects concerned, time of occurrence and of discovery, likely consequences as well as measures taken and planned. An incomplete first notification is permissible and will be supplemented. The notification is sent to the shop's email address or, if provided, to the address voluntarily given at acceptance.

The processor does not itself notify the supervisory authority — that is a matter for the controller.

On request, the processor assists with data protection impact assessments (Art. 35) and prior consultations (Art. 36), insofar as the necessary information originates from its sphere.

§ 9 Erasure and return

9.1 During the term: automatic anonymisation after 90 days

The recipient's name and address as well as the label PDF are automatically removed 90 days after creation of the label: name and address are replaced by [redacted], label_url is deleted.

The run is triggered daily — by a cron call (03:15 UTC). Between the expiry of the 90 days and the removal there is thus, as a rule, at most one day.

9.2 After the end of the agreement (uninstallation)

Point in timeProcess
Upon uninstallationThe shop is marked as uninstalled, all API keys of the shop are revoked, the Shopify sessions are deleted
With the shop/redact call from Shopify (per Shopify's specification approximately 48 hours after uninstallation)Final deletion of all shop-related records, except for the proof of acceptance of this agreement (§ 9.2): first the tables without cascading deletion, then the shop record with all tables attached to it, then the sessions
Up to 14 days beyond thatRetention in backups on the server, which are deleted thereafter
Up to 35 days beyond thatRetention in the encrypted off-site backup (Hetzner, Falkenstein), which is deleted thereafter

Exempt from deletion is the proof of acceptance of this agreement (shop, Shopify user ID of the accepting person, time, version, checksum of the text; name and email address only if provided voluntarily). We retain it until the end of the third calendar year after the contract ends in order to be able to prove the conclusion of the contract (Art. 17(3)(e) GDPR), and delete it thereafter.

Apart from the acceptance record of this agreement (without end customer data), no shop-related table survives the shop/redact run. An automated test enforces this.

The controller may request an export of its data before uninstallation or, after uninstallation, immediate deletion (support@packmate.shop). The export is provided in a common, machine-readable format.

9.3 Statutory retention obligations

Statutory retention obligations of the processor remain unaffected. Such data are blocked and not processed further.

The legal basis for this is Art. 17(3)(b) GDPR: the obligation to erase does not apply to the extent that the processing is necessary for compliance with a legal obligation. The exception extends exactly as far as the obligation and not one record further.

That the remaining data are blocked and not processed further follows from Art. 5(1)(b) and (c) GDPR (purpose limitation, data minimisation). The blocking takes place automatically and does not depend on a request by the data subject (not applicable is Art. 18 GDPR, which presupposes one of four exhaustively listed situations).

For the end customer data in shipping_labels, the processor has no retention obligation of its own; the retention of shipping records is a matter for the controller.

§ 10 Evidence and audits

On request, the processor makes available to the controller the information that is necessary to demonstrate compliance with Art. 28 — in particular this agreement together with its annexes as well as the current version of the TOM.

Audits are carried out primarily by presenting this evidence. An inspection on site is possible with reasonable advance notice, during normal business hours and without unreasonable disruption of operations; it may be carried out by an auditor bound to confidentiality. The data centres are located at Hostinger; an inspection there is governed by the terms of this provider.

The processor points out that it holds no certification (such as ISO 27001) and does not claim any.

§ 11 Place of processing and third-country transfers

The processing takes place in the European Union, unless stated otherwise in Annex 1.

For the sub-processors named there that are established outside the EU, the transfer basis under Chapter V GDPR is documented per provider in Annex 1. Where it has not yet been reviewed, it says “to be confirmed” there instead of an assumption.

§ 12 Amendments

We inform the controller of amendments to this agreement at least 30 days before they take effect, in text form (e.g. email), in the app and by email, together with the amended passages. The controller may object within this period; in that case the previous version continues to apply until the end of the contract, and either party may terminate the contract with effect from the time of the amendment. If the controller does not object or accepts the new version in the app, it applies from the stated date. Amendments that are necessary because of a legal obligation apply from the time of that obligation.

Notices under this agreement are sent to the shop's email address or, if provided, to the address voluntarily given at acceptance.

§ 13 Liability and final provisions

Art. 82 GDPR applies. Otherwise, liability is governed by the terms of use; a limitation does not apply to intent and gross negligence, nor to claims of data subjects.

The law of the Federal Republic of Germany applies.

Amendments to this agreement are governed by § 12; declarations in this respect require text form (e.g. email). If a provision is invalid, the agreement otherwise remains valid; the invalid provision is replaced by the statutory provision.

In the event of conflicts between this agreement and the terms of use, this agreement takes precedence insofar as the processing of personal data is concerned.

Annexes

No.Annex
1Approved sub-processors
2Technical and organisational measures

The annexes form an integral part of this agreement.

Annex: Transfer to DHL on the merchant's instructions

See Preamble, “Recipient on the merchant's instructions”.

PackMate is registered with DHL as a software provider and calls the DHL shipping interface (Parcel DE Shipping) with its own app key — on behalf of the respective merchant and with the merchant's own business customer access credentials and billing number. The merchant remains DHL's contractual partner for its shipments; PackMate is not a contractual partner of the individual shipment. The merchant's access credentials are stored in encrypted form (Annex 2, §1.4).

Change history

  • 14 November 2026: Acceptance in the app with record; amendment clause § 12; the merchant's platform; period for the proof

PackMate — Annex 1: Approved sub-processors (Art. 28(4) GDPR)

The language clause of the agreement applies to this annex.

Annex to the DPA between the merchant (controller) and

PackMate — Einzelunternehmen Valerian Huber (processor). Version of 14 November 2026.

Allocation of roles: The merchant is the controller for the data of its end customers, PackMate

its processor. The services listed here are thus sub-processors within the

meaning of Art. 28(4) — the merchant authorises them and may object to them (DPA § 6).

1. Active sub-processors

Sub-processorPurposeData categoriesRegistered office / place of processingThird country / basis
Hostinger (legal entity: Hostinger International Ltd., Larnaca, Cyprus)Operation of the server alpin-prod-vps (since 30 September 2026, previously shopforge-prod-vps): application, database, backups of the last 14 days, uploaded logosall data stored by PackMate (at rest)Data centre Frankfurt am Main, Germanyno (EU)
Hetzner Online GmbH (Germany)Storage for the daily off-site backup (database and uploaded files), 35 days retentionall data stored by PackMate — gpg-encrypted (AES256) before transfer, the key is not held by HetznerObject Storage Falkenstein, Germany (bucket packmate-backups-fsn1)no (EU)
Resend (legal entity: Plus Five Five, Inc., USA), addressed via the operator's sending proxyTransactional emails to the merchant (welcome, quota warnings, deadline reminders)Email address of the merchant, message content — no end customer dataProvider established in the USA, sending according to its own statement via AWS SES in an EU regionyes — DPF, SCC Module 2 as fallback

2. Not listed as external sub-processor (with reasons)

ServiceReason
Sending proxy `internal.alpin-code.de` (alpin-code-cockpit)Own infrastructure of the same operator (sole proprietorship V. Huber). The proxy passes the email on to Resend (listed above); no further recipient.
GlitchTip (sentry.alpin-code.de)Self-operated on own infrastructure — no external recipient. Error reports contain the error message, stack trace and request context; whether personal data can end up in them is to be confirmed (§4).
Vercel Inc.Only serves the website packmate.shop. There, PackMate is a controller in its own right (privacy policy, packmate.shop/privacy); end customer data of the merchant do not reach Vercel.
alpin-code-cockpit (monitoring)Operator's own monitoring. Receives operating metrics (counts, status), no end customer data.

2a. Shopify

Shopify is not a sub-processor (see DPA, ‘The merchant's platform’).

3. Third-country transfers (Arts 44 et seq. GDPR)

ProviderLegal entity / registered officeBasis
ResendPlus Five Five, Inc., USADPF + SCC Module 2

Hostinger (data centre Germany) processes in the EU.

4. To be confirmed / open

  1. GlitchTip: check error reports for personal data (stack traces and request URLs can carry payload data), so that the classification “self-operated, no recipient” holds.

5. Obligation to amend and inform

A new or changed sub-processor requires prior information of the merchants including the right to object (DPA § 6, Art. 28(2)).

PackMate — Annex 2: Technical and organisational measures (Art. 32 GDPR)

The language clause of the agreement applies to this annex.

Annex to the DPA between the merchant (controller) and

PackMate — Einzelunternehmen Valerian Huber (processor). Version of 14 November 2026.

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

1.1 Physical access control (physical)

No hardware of our own. The processing runs on a rented server at Hostinger (alpin-prod-vps since 30 September 2026, previously shopforge-prod-vps; data centre Frankfurt am Main). Physical security is the responsibility of the provider (Annex 1). Certifications of our own are not claimed.

1.2 System access control (system)

  • Network separation: Only the application container is reachable from outside, via the reverse proxy Traefik (api.packmate.shop, plus /mcp). The database (packmate-postgres) and packing service (packmate-packing) are attached exclusively to the internal network packmate_backend and have no published ports.
  • Login to the app: via Shopify session token (JWT, short lifetime), verified by the official Shopify library. The shop is determined server-side from the token, not from information supplied by the browser.
  • Machine interface: API keys per shop, stored only as SHA-256 hash, the plaintext is displayed once; each key carries a list of permissions (BP-008) — at most ten active keys per shop. Keys of uninstalled shops are rejected and revoked upon uninstallation.
  • Cron endpoints can only be called with a bearer key.

1.3 Data access control (data) — tenant separation

  • Each shop is a separate tenant. The separation takes place in the application: every query on shop-related tables filters on shop_id.
  • Stated honestly: The database does not additionally enforce this separation — there is no row-level security. A forgotten filter in a new query would not be caught by the database. See §7.

1.4 Encryption of access credentials at rest

  • The merchant's DHL access credentials (password, where applicable API key) are stored encrypted with AES-256-GCM.
  • The key comes from the environment variable ENCRYPTION_KEY, not from the source code. In production, the application refuses encryption and decryption if the key is missing or is shorter than 32 characters — a built-in fallback key exists only outside production.

1.5 Data minimisation

  • End customer data are stored only to the extent that the shipping label requires them: name and address, no email and no telephone number.
  • PackMate does not request a read right to customer records.
  • When emails are sent, the recipient address is not logged; webhook logs contain only counts.

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

2.1 Transfer control

  • TLS for all externally reachable routes: Traefik with Let's Encrypt certificates, entry point websecure.
  • Outgoing connections to DHL (https://api-eu.dhl.com/parcel/de/shipping/v2/), to the sending proxy (https://internal.alpin-code.de) and to error tracking run over HTTPS.
  • The connection between the application and the database or packing service does not leave the internal container network.
  • Webhooks from Shopify are verified by HMAC signature before they are processed.

2.2 Input control

  • Schema changes are made via versioned, sequentially numbered migrations.
  • Changes to the application are made via version control with complete history; the build checks types and tests.

2.3 Abuse prevention

  • Rate limiting on the machine interface per plan, response 429 when exceeded.

3. Availability and resilience (Art. 32(1)(b), (c))

  • Daily backup of the database and uploaded files at 03:47 UTC. On the server 14 days, older backups are deleted. This results in a maximum data loss of approximately 24 hours (RPO).
  • Off-site copy: the same backup, encrypted with gpg (AES256) before transfer, in Hetzner Object Storage Falkenstein (bucket packmate-backups-fsn1, deletion lock 30 days). Versions older than 35 days are deleted.
  • Restore test weekly (Mondays 05:17 UTC): restores the off-site state into a disposable database.
  • Health check: The database and packing service have container health checks on which the start of the application depends; every deploy waits for healthy containers and then queries the health endpoint.
  • Error tracking via a self-operated GlitchTip instance (sentry.alpin-code.de) — no external recipient.
  • Dead man's switch for the scheduled tasks: The cron wrapper reports every run to the operator hub; a missing run is noticed there instead of passing in silence.

4. Erasure and anonymisation (Art. 32(1)(a), Art. 5(1)(e))

  • 90 days after label creation, recipient name and address are replaced by [redacted] and the label PDF is deleted. Triggered daily by cron (03:15 UTC).
  • Erasure request from an end customer (customers/redact): the same anonymisation immediately for the orders named, plus clearing of the email in gdpr_requests.
  • Uninstallation (shop/redact): Deletion of all shop-related records. Only the DPA acceptance record is excepted (version, checksum of the text, time, Shopify user ID of the accepting person; name and email only if provided voluntarily). It is kept until the end of the third calendar year after the contract ends and is then deleted by the nightly run. The database prevents changes and premature deletion (trigger).
  • If an erasure webhook fails, the application responds with 500, and Shopify delivers again — an erasure is not silently lost.

5. Process for regular review (Art. 32(1)(d))

  • Independent review body: The application is reviewed by the operator hub against a catalogue of release criteria; security findings are handled as issues with evidence.
  • Regression tests for the erasure and security paths are in the repo and run in the build (see §4).

6. Job control

  • Sub-processors are named exhaustively in Annex 1.

7. Notes (as of 14 November 2026)

These points are not fulfilled or cannot be substantiated from the repo and are deliberately disclosed:

  1. No row-level security. The tenant separation depends solely on the shop_id filter in every query (§1.3).
  2. No external penetration test and no certification (ISO 27001 or similar) — neither in place nor claimed.
  3. No access log at record level. The earlier draft statement “every access is logged” is not implemented in the code and is dropped.