Inkmateinkmate

Last updated: 14 November 2026

Data processing agreement

Data processing agreement (DPA / AVV) under Art. 28 GDPR between the operator of a Shopify shop that installs Inkmate and Inkmate.

This English version is provided for convenience only. The German version (Vereinbarung zur Auftragsverarbeitung) is legally binding and prevails in the event of any discrepancy.

Preamble

The controller is the operator of the Shopify shop ("merchant") that installs Inkmate.

The processor is:

Valerian Huber, sole proprietorship
Address as stated in the imprint (in German)
support@inkmate.shop · valerian@luvex.tech

Not covered by this agreement are the data that Inkmate processes as a controller in its own right: the contract and billing data of the merchant itself and the operating logs for the security of the service.

Conclusion: upon installation of the app in the Shopify shop; there is no individual negotiation. This agreement takes precedence over the terms of use (in German) insofar as it concerns personal data.

Language: The German version is authoritative; an English version is provided for information only.

Section 1 Subject matter and purpose

Provision of a tool for print templates (flyers, inserts, QR codes, landing pages) in the merchant's shop, including the evaluation of QR scans and the creation of invoices for orders, insofar as the merchant uses these functions. Any use for the processor's own purposes is excluded, in particular profiling, advertising and the training of AI models. Inkmate itself does not use any AI services (for services connected by the merchant, see Section 6).

Duration: for the term of the installation; the consequences of its end are governed by Section 9.

Section 2 Data and data subjects

Data subjectsDataWhen
The merchant's end customersName, address, VAT ID, email address, Leitweg-ID or buyer reference (for the XRechnung e-invoice), order and customer ID in invoicesif the merchant creates invoices via Inkmate
End customersNames in mail merge templatesif the merchant creates mail merge letters
End customersOrder and customer events from Shopify (webhooks)continuously, insofar as automations are used
Persons who scan a QR codeShortened IP hash, device, browser, referrerat the time of the scan
The merchant's staffName, email, rolewhen they work in the app

Images uploaded by the merchant (e.g. logos) may show persons. The processor treats them as personal data. Uploaded images are publicly accessible via their address because they appear in printed and digital templates (Annex 2).

Payment data of end customers is not processed.

Section 3 Instructions

The processor processes personal data only on documented instructions from the controller, unless required to do so by Union or Member State law to which the processor is subject. In such a case, the processor informs the controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest. This agreement and the controller's operation of the app constitute instructions.

Individual instructions must be sent in text form to the address stated in the preamble.

If the processor considers an instruction to be unlawful, the processor informs the controller without undue delay.

Section 4 Confidentiality

The processor is a sole proprietorship. Only the owner of the sole proprietorship has access to production data.

The processor ensures that all persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality (Art. 28(3)(b) GDPR).

Section 5 Technical and organisational measures

The processor implements the measures described in Annex 2, including the gaps openly identified there.

Section 6 Sub-processors

The processor engages further processors only with the prior authorisation of the controller in text form. The controller grants general authorisation for the services listed in Annex 1. The processor informs the controller in text form of any intended change (addition or replacement) 30 days in advance. The controller may object for good cause; if the change is maintained, the controller has the right to terminate.

The processor imposes on each sub-processor, by contract, the same data protection obligations as set out in 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 (Art. 28(4) GDPR). Where a sub-processor fails to fulfil its data protection obligations, the processor remains liable to the controller for the performance of those obligations.

The merchant's own AI services. If the merchant uses their API key to connect their own AI service via the interface or the MCP access, including the hosted one at api.inkmate.shop/mcp, Inkmate transmits the requested data to this service on the merchant's instructions. This may include data of end customers and contacts, such as email addresses, customer names on invoices and recipient names from mail merges. The choice of service, the legal basis, any contract required with the service and the basis for any transfer to third countries are the responsibility of the merchant. The service is not a sub-processor of Inkmate.

Section 7 Data subject rights

The processor assists with requests under Arts. 15–22 GDPR. Erasure requests from end customers received via Shopify (customers/redact) are implemented automatically: contacts, events and stamps are deleted, mail merge templates and metrics are anonymised, rendered files are removed. Invoices are retained because the merchant is required to keep them (Section 9).

Access requests (customers/data_request) are recorded and answered via support; there is no self-service export yet.

Section 8 Notification obligations

The processor notifies the merchant of any personal data breach without undue delay, and no later than 24 hours after becoming aware of it. The notification contains, as far as known: the nature of the incident, the categories of data concerned and the approximate number of data subjects concerned, the time of occurrence and discovery, the likely consequences and the measures taken and planned.

The processor does not itself notify the supervisory authority. The processor assists with data protection impact assessments (Art. 35 GDPR) and prior consultations (Art. 36 GDPR).

Section 9 Uninstallation, return and deletion

TimeAction
UninstallationThe app's access ends; interface keys are revoked; data is retained for the time being
48 hours later (Shopify shop/redact)Permanent deletion of all data of the shop, including all files and including the invoices
Backup copiesRetained until overwritten in the regular cycle (35 days)
Important for merchants who create invoices via Inkmate: The statutory retention obligation (Section 147 AO, Section 14b UStG, up to ten years) lies with the merchant. Shopify's platform rules require an app to delete all shop data after uninstallation. Therefore export invoices before uninstalling. Inkmate cannot restore them after deletion.

Where a statutory retention obligation prevents deletion during ongoing use, the data is restricted instead of deleted (Art. 17(3)(b) GDPR; Art. 5(1)(b) and (c) GDPR).

Sections 10–12 Evidence, third countries, liability

Evidence: by this agreement including its annexes; an on-site inspection is possible with prior notice. The processor holds no certification.

Third countries: Processing takes place in the EU unless Annex 1 states otherwise. The transfer basis for each provider is stated there.

Liability: in accordance with Art. 82 GDPR. German law applies. Amendments must be made in text form.

Annex 1: Sub-processors

Art. 28(4) GDPR

1. Sub-processors

Sub-processorPurposeDataLocationBasis under Chapter V
Hostinger International Ltd., Larnaca (Cyprus)Servers: app, database, local backup copies (14 days)all dataData centre FrankfurtSCC (onward transfer to Hostinger's US/CA subcontractors)
Hetzner Online GmbH, Gunzenhausen (Germany)File storage (object storage): generated PDFs, logos, preview images; encrypted off-site backup copies (AES-256, 35 days with a deletion lock)App files; in PDFs also order and address data; in the backup copies all data (encrypted)Data centre Falkenstein (Germany)not required, processing in the EU
Resend (Plus Five Five, Inc., USA), via the operator's sending proxyDaily summary email to the merchantMerchant's email; names of templates (for mail merge, possibly customer names), order IDs, linksAWS SES EU region; provider in the USADPF + SCC Module 2
Vercel Inc., USADelivery of the website inkmate.shopConnection data of visitorsglobalDPF (certification active, checked 26 September 2026)

2. Engaged by the merchant directly

ServiceWhenDataClassification
Shopify (Shopify International Ltd., Ireland)always, platform of the appShop identity, order and customer eventsPlatform with its own contract with the merchant, not a sub-processor of Inkmate. Transfer basis: BCR within the group + SCC to third parties, no DPF.

3. Not listed as sub-processors

ServiceReason
GlitchTip (error reports)self-operated, same operator
Umami (audience measurement)self-operated, only in the admin interface
Operator's central operations servicesame operator; sending proxy (see Resend) and operating metrics

Not in use: Anthropic and OpenAI.

Annex 2: Technical and organisational measures

Art. 32 GDPR

1. Confidentiality

  • Physical: application, database and local backup copies (14 days) at Hostinger in Frankfurt; file storage and encrypted off-site backup copies (35 days) at Hetzner, data centre Falkenstein (Germany).
  • Sign-in: exclusively via Shopify; session token with verified signature, expiry and audience.
  • Server access: only with an SSH key, password login disabled. Only the owner has access to production data.
  • Encryption of individual fields (AES-256-GCM): name, address and VAT ID on invoices, contact emails, stored order events, Shopify access tokens, interface keys for third-party services, invoice PDF and e-invoice XML in file storage.
  • Rendered packing slips are stored unencrypted in file storage and can only be retrieved with a session of the shop they belong to (No. 6).
  • The merchants' interface keys are revoked upon uninstallation.
  • Tenant separation via shop_id in the application (No. 6).
  • Database bound locally only, not reachable from outside.
  • Data minimisation: IP addresses only as an HMAC hash; Inkmate itself does not use any AI services; no payment data.

2. Integrity

  • Transport only encrypted (TLS, Let's Encrypt; HTTP redirects to HTTPS).
  • Webhooks with constant-time HMAC verification.
  • Invoices with sequential numbering per shop.
  • Access log: viewing, downloading and exporting invoices, contacts, the order list and API exports are logged per shop, retention 12 months.

3. Availability

MeasureStatus
Daily backup of database and file storagerunning, locally on the app server at Hostinger, kept for 14 days; encrypted with gpg AES-256 before leaving the server
Copy outside the serverdaily to a write-protected bucket at Hetzner, data centre Falkenstein (Germany), kept for 35 days with a deletion lock
Restore testweekly and automatic from the off-site copy, last successful on 9 November 2026
Monitoringevery backup and every restore test is reported to the operations hub

4. Review

Continuous monitoring by the hub (availability, certificates, backup reports, dependencies, containers); annual review of this annex.

5. Control of processing

Sub-processors only in accordance with Annex 1; master register in the hub (external_services).

6. Openly identified gaps (as of 10 November 2026)

GapWhy it mattersWhat closes it
Server disk not encryptedFields and files are encrypted, not the storage mediumDisk encryption, measure in preparation
Rendered packing slips unencryptedcontain name and addressEncrypt storage as for invoices
Log incompletePacking slip downloads and the operator's database access are not recordedExtend the log to file retrievals and operator sessions
Development not fully separated from productionDevelopment tools have access to the production serverRule and separate access, measure in preparation
Tenant separation only in the applicationan error in a query is not caughtRow-level security policies as a second line

Change history

26 September 2026: first version.

9 November 2026: Section 1 and Section 6: the merchant's own connected AI services.

10 November 2026: Annex 2: measures brought up to the state of the measurement of 10 November 2026; Section 9: backup copies 35 days.

14 November 2026: Preamble: German version authoritative; Sections 3, 4 and 6: mandatory content under Art. 28 GDPR added; Sections 1, 2, 6 and Annex 1: capture of contacts via landing pages and Klaviyo removed; Section 2: no city/region for scans; Annexes 1 and 2: locations of backup copies aligned.