Data Processing Agreement (DPA) under Art. 28 GDPR

Radom UG (haftungsbeschränkt) · As of November 17, 2026 (version 2026-11-17)

Convenience translation; the German version prevails.

Preamble

The customer uses an online service of Radom UG (haftungsbeschränkt) under the general terms and conditions of that service (hereinafter the “Main Contract”). In doing so, Radom UG processes personal data on behalf of the customer. This agreement governs the rights and obligations of the parties under Art. 28 GDPR.

Parties

  • Controller (hereinafter the “Customer”): the business that uses the service with a customer account or through a Single Order under § 12 of the terms.
  • Processor (hereinafter the “Provider”): Radom UG (haftungsbeschränkt), Telemannstr. 2, 60323 Frankfurt am Main, Local Court (Amtsgericht) of Frankfurt am Main, HRB 141671, represented by its managing director Arber Lamce.

§ 1 Subject matter, duration and details of the processing

  1. The subject matter is the processing of personal data that the Customer enters or uploads when using the service. The subject matter, nature and purpose of the processing, the types of personal data, the categories of data subjects and the storage period are set out in Annex 1 of the respective service.
  2. This agreement applies for the term of the Main Contract. The obligations regarding deletion (§ 9) and confidentiality (§ 4) continue beyond that for as long as the Provider processes the Customer's data.
  3. Data that the Provider processes as a controller in its own right is not covered by this agreement. This includes in particular the Customer's account data, billing, server log files and abuse prevention. The privacy policy of the service applies to such data.

§ 2 Instructions

  1. The Provider processes the data only on documented instructions from the Customer, including with regard to transfers to a third country. This does not apply to processing that the Provider is required to carry out under Union or Member State law. In that case, the Provider informs the Customer of that legal requirement before the processing, unless that law prohibits this (Art. 28(3)(a) GDPR).
  2. The instructions result from the Main Contract, this agreement and the Customer's use of the functions of the service. The Customer gives further instructions in text form (e.g. by email). Instructions that go beyond the contractually agreed scope of services are treated as a request to change the services.
  3. If the Provider considers that an instruction infringes data protection provisions, it informs the Customer without undue delay (Art. 28(3), sentence 3 GDPR). It may suspend carrying out the instruction until the Customer confirms or changes it.

§ 3 Obligations of the Customer

  1. The Customer is responsible for the lawfulness of the processing, in particular for the permissibility of transmitting the data to the Provider and for safeguarding the rights of the data subjects.
  2. The Customer informs the Provider without undue delay if, when checking the results, it finds errors or irregularities with regard to data protection provisions.

§ 4 Confidentiality

The Provider ensures that the persons authorised to process the data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality (Art. 28(3)(b) GDPR). This obligation continues after their activity has ended.

§ 5 Security of processing

  1. The Provider implements the technical and organisational measures under Art. 32 GDPR that are described in Annex 2.
  2. The measures are subject to technical progress. The Provider may replace them with equivalent or better measures as long as the level of protection is not reduced. It documents significant changes.

§ 6 Sub-processors

  1. The Customer grants the Provider general authorisation to engage other processors (sub-processors) (Art. 28(2) GDPR). The sub-processors engaged at the time of conclusion are listed in Annex 3 and are deemed approved.
  2. The Provider informs the Customer in text form at least 30 days in advance if it intends to add or replace a sub-processor. The information is sent by email to the address stored in the customer account. The Customer may object to the change in text form within 14 days of receipt for an important reason relating to data protection. If the parties do not reach an agreement, either party may terminate the Main Contract extraordinarily with effect from the time of the change.
  3. The Provider contractually imposes on each sub-processor the same data protection obligations as are set out in this agreement (Art. 28(4) GDPR).
  4. A transfer to a third country takes place only if the requirements of Art. 44 et seq. GDPR are met, e.g. by an adequacy decision or standard contractual clauses.

§ 7 Assistance with the rights of data subjects

  1. The Provider assists the Customer with appropriate technical and organisational measures in fulfilling the rights of data subjects under Chapter III GDPR (Art. 28(3)(e) GDPR).
  2. If a data subject contacts the Provider directly, the Provider forwards the request to the Customer without undue delay. It does not answer it itself, except on the Customer's instruction.

§ 8 Assistance with further obligations, notification of breaches

  1. The Provider assists the Customer in complying with the obligations under Art. 32 to 36 GDPR, insofar as the nature of the processing and the information available to it permit (Art. 28(3)(f) GDPR). This includes the security of processing, the notification and communication of breaches and the data protection impact assessment.
  2. The Provider notifies the Customer of a personal data breach without undue delay after becoming aware of it (Art. 33(2) GDPR). The notification contains, as far as available, the information under Art. 33(3) GDPR. Information that is not yet available is provided subsequently.

§ 9 Deletion and return

  1. The Provider deletes the Customer's data automatically after the storage period stated in Annex 1 has expired. On the Customer's instruction, it deletes them earlier.
  2. After the end of the Main Contract, the Provider deletes all of the Customer's data still stored at the latest when this storage period expires (Art. 28(3)(g) GDPR). This does not apply to data that the Provider is required to store under Union or Member State law.
  3. The service makes the results of the processing available to the Customer for download directly. The Provider owes no return beyond that. The source data remain with the Customer.

§ 10 Evidence and audits

  1. On request, the Provider makes available to the Customer all information necessary to demonstrate compliance with the obligations under Art. 28 GDPR (Art. 28(3)(h) GDPR). This may include certificates or evidence from the sub-processors.
  2. The Customer, or an auditor appointed by the Customer who is bound to confidentiality, may conduct audits, including inspections. The Customer announces an inspection in text form at least 30 days in advance, except where there is a justified suspicion of a breach. It takes place during normal business hours, without disrupting operations, and as a rule no more than once per calendar year. Data centres of sub-processors are audited by means of their evidence.
  3. The Customer bears the costs of an inspection unless it reveals a material breach of this agreement by the Provider.

§ 11 Liability

Liability towards data subjects is governed by Art. 82 GDPR. Otherwise, the liability provisions of the Main Contract apply between the parties.

§ 12 Conclusion of the agreement and final provisions

  1. This agreement is concluded in electronic form (Art. 28(9) GDPR). For Single Orders it forms part of the general terms and conditions of the service (§ 12 (12) there); it is concluded by the declaration the Customer's AI agent makes for the Customer at the first upload, at the latest when the terms are accepted at payment. For customer accounts it is concluded as soon as the Customer accepts it; the Customer declares acceptance in text form by e-mail to support@konverter-pro.de. It applies to all personal data that the Customer processes in the service from that time.
  2. On request, the Provider also makes this agreement available to the Customer as a signed document (PDF).
  3. In the event of contradictions, this agreement takes precedence over the Main Contract insofar as the protection of personal data is concerned.
  4. Amendments and additions require text form. This also applies to any waiver of this form requirement.
  5. Should a provision be invalid, the validity of the remaining provisions remains unaffected.
  6. The law of the Federal Republic of Germany applies. The place of jurisdiction is Frankfurt am Main, insofar as permitted by law.

Annexes for the Konverter Pro service (konverter-pro.de)

Annex 1: Details of the processing

Subject matter and purposeReading, converting and pre-assigning accounts for bank statements, statements of payment service providers and marketplaces, trial balances (SuSa), KZV statements and electronic invoices, and producing booking files for DATEV and other accounting software (Lexware, sevDesk, BuchhaltungsButler, Excel/CSV). This covers files the Customer uploads or sends through an AI agent and data the Customer retrieves through an interface the Customer has connected.
Formats processedBank statements as PDF (including scans), CSV, TSV (.tsv), Excel (.xlsx, .xls), MT940 (.sta, .mt940, .940, .mt9), camt.053 (XML) and as photos (JPG, PNG, HEIC). Exports from PayPal (CSV), Shopify (orders export CSV), SumUp (sales and payout reports), Amazon Seller (settlement), Adyen (settlement), Etsy (statement), Revolut Business (CSV), Amazon Business invoices (PDF) and other providers. Trial balances (PDF), KZV statements (PDF). Electronic invoices: ZUGFeRD/Factur-X (PDF with embedded XML) and XRechnung (UBL and CII).
Data sources on the Customer's instructionUploaded files. Files the Customer's AI agent sends through the MCP interface or names by a publicly reachable https address, from which the Provider fetches them. A Stripe account connected by the Customer through Stripe Connect: balance transactions, payouts, fees, descriptions, invoice numbers, and the country and VAT ID of end customers. A Shopify store connected by the Customer: orders and payouts; end-customer names are not retrieved. Stripe and Shopify are the Customer's data sources, not sub-processors.
Nature of the processingReceiving (upload, retrieval through connected interfaces, fetching addresses named by the Customer's AI agent), reading (text extraction, text recognition on the Provider's own server, AI-assisted reading under Annex 3 No. 2), converting, reconciling (balance and completeness checks), proposing accounts (the Customer's rules, the Customer's earlier confirmations, keywords, AI proposals), storing, providing for review and download, returning questions, previews and results to the Customer's AI agent, deleting.
Types of personal dataNames of account holders, payers and payees. IBAN, BIC and account numbers. Booking and value dates, amounts, currencies. Payment references and booking texts. References (e.g. invoice, order, mandate and payout references). Tax attributes (VAT IDs, tax rates, countries). Data from electronic invoices (issuer, recipient, line items, amounts, bank details). Accounts and balances from trial balances. The Customer's DATEV details (adviser and client number, fiscal year, chart of accounts, accounts). The Customer's booking rules (e.g. counterparty patterns). File names of uploaded files. Any other data contained in the files transmitted.
Categories of data subjectsBusiness partners of the Customer whose payments appear in the data: customers, suppliers, service providers, landlords, employees (e.g. salary payments), shareholders. End customers of online shops and payment service providers. Issuers and recipients of electronic invoices and their contact persons. Account holders, where they are natural persons. For tax advisers, also their clients and their clients' business partners.
Place of processingServers of Hetzner Online GmbH in the Nuremberg data centre (Hetzner Cloud), Germany. Exceptions: AI-assisted processing by Microsoft Azure OpenAI (Annex 3 No. 2), support e-mail through Google Workspace (Annex 3 No. 3) and operational alerts to the Provider through the messenger Telegram (Annex 2), which contain only counts, technical codes and details of the Provider's servers. What the service returns to the Customer's AI agent goes to the tool the Customer chose; its provider is not a sub-processor of the Provider.

Retention

DataRetention and deletion
Uploaded files, generated output files, conversions and the bookings read from themDeleted automatically 90 days after upload or retrieval, whatever their status (daily run at 03:00). This also applies to orders with an API key, whose order entry is deleted 30 days after it was created. For Single Orders, the next row applies.
Single OrdersA Single Order expires 7 days after it was created; payment does not extend this period. The Provider deletes expired orders automatically, together with the technical account and all files, bookings, answers, assignment rules and DATEV details (hourly run, usually within one more day). If an agent wallet payment is still running at expiry, it waits until Stripe has decided on it. Payment records and receipts are not covered by this agreement (§ 1 (3)); the privacy policy applies to them.
Conversions the Customer deletes earlierFiles are deleted at once; the records, including the bookings, 30 days later (daily run at 04:00), and no later than after 90 days.
Learning records from the Customer's confirmations and corrections (booking text, counterparty, IBAN, amount, proposed and chosen account)Kept for the lifetime of the customer account, so later proposals for the same Customer improve. They are not deleted after 90 days but together with the customer account, for Single Orders with the technical account. On the Customer's instruction the Provider deletes them earlier.
Booking rules, accounting profiles (with DATEV details) and saved CSV mappingsUntil the Customer deletes them, and at the latest with the customer account.
Generated export files in the cache1 hour (plus a 5-minute transition). For resilience, the cache is also written to the disk of the same server, where remnants may stay until the next automatic clean-up of that file.
Processing status in the cache; column mappings for CSV files (without content)24 hours.
Deletion of the customer accountImmediately: conversions, bookings, files, learning records, rules, profiles, mappings, settings and sessions. Afterwards only the fact and time of the deletion are recorded, under the account's identifier, without name or e-mail address.
BackupsThe database (with conversions, bookings, learning records, rules and profiles) is backed up daily. Deleted data may remain in these backups for up to 16 days; they are then deleted automatically. Before each software release the database is also backed up in encrypted form. These backups are currently not deleted automatically. Uploaded files are not contained in any backup. Working files we create before corrections to individual accounts, in support cases or when testing our service are currently not deleted automatically; they may also contain content from uploaded files.
Uploads without a customer account (guest access)Not covered by this agreement, because guests do not accept the terms. Guest uploads are deleted after 7 days (see the privacy policy). If a guest registers or signs in from the preview, the file uploaded in the preview is moved into their customer account and the guest copy is deleted. If the file was read with AI in the preview, that result is taken over without sending the file to the AI service again.

Single Orders (§ 12 of the terms)

For Single Orders, the following also applies:

  • Duration: Before payment there is no Main Contract yet (§ 12 (2) of the terms). This agreement nevertheless applies from its conclusion until the order is deleted, even if no payment follows.
  • Instructions: Instructions also include what the Customer's AI agent sends through the interface, including the release of AI processing. The Customer instructs the Provider to return questions, previews and results to the AI agent the Customer chose.
  • AI processing: Without a release by the Customer's AI agent, no content goes to Microsoft Azure OpenAI (Annex 3 No. 2). Format detection for CSV files does not run for Single Orders.
  • Notices: A Single Order has no customer account. The Provider therefore announces a change of sub-processors (§ 6 (2)) by publishing it on this page. It reports requests from data subjects (§ 7 (2)) and breaches (§ 8 (2)) to the e-mail address given at payment. For an unpaid Single Order the Provider has no contact details of the Customer; a notice is then not possible.

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

1. Confidentiality

  • Physical access control: The servers are in the data centre of Hetzner Online GmbH in Nuremberg. Hetzner controls physical access. The Provider runs no server rooms of its own.
  • System access control:
    • Administrative access only by SSH with a cryptographic key; password login is disabled.
    • A firewall rejects incoming connections by default and allows only released services, in particular HTTP and HTTPS.
    • The database, the cache and the internal application interface are reachable only locally on the server. The cache requires a login with its own user and password.
  • Data access control:
    • Customer accounts are protected by a password stored only as a bcrypt hash, or by Google sign-in.
    • Failed logins are limited: after 10 failures within 15 minutes, login for the affected address is blocked for 15 minutes. Requests per client are rate-limited as well.
    • Changing or resetting the password and linking Google invalidate every earlier login token. A password change ends the other sessions.
    • Requests for conversions, bookings, files and exports check that the data belongs to the signed-in customer account.
    • A Single Order can be accessed by whoever knows its randomly generated order identifier (job token). The service stores only a hash (SHA-256) of the token and of API keys, and for API keys also the first 12 characters for recognition. Download links are signed and valid for 1 hour.
    • Only the management and persons it has expressly authorised, who are bound to confidentiality, have access to the servers.
  • Separation control: Stored files are kept per customer account in separate directories; records are assigned to the customer account. For each Single Order the service creates a separate technical account. The services run in separate containers without administrator rights.
  • Pseudonymisation:
    • Application logs carry identifiers instead of file names and booking texts; e-mail addresses, IBANs, BICs and amounts are masked in logs.
    • Operational alerts to the Provider run through the messenger Telegram. They contain only counts, technical codes and details of the Provider's servers (routes, containers, processes, server paths), no identifiers or names of the Customer's files and no content.
    • Guest uploads are stored under a pseudonymous reference instead of the IP address. Orders through the MCP interface likewise carry a pseudonymous reference instead of the IP address in the database.

2. Integrity

  • Transfer control:
    • All connections to the service are encrypted with TLS (HTTPS); unencrypted requests are redirected to HTTPS.
    • Text recognition for scanned documents runs on the Provider's own server.
    • Before any text is sent to the AI service (Annex 3 No. 2), e-mail addresses, IBANs and labelled BICs and account numbers are masked, and source text is limited to the relevant lines. Images are sent in full. Transmission is encrypted.
    • Backups taken before each software release are stored encrypted.
  • Input control: Server and application logs. Server log files are rotated daily and deleted after at most 15 days. Application logs are size-limited per service (at most 30 MB) and discarded at each software release.

3. Availability and resilience

  • Backup:
    • The database is backed up daily. Deleted data may remain in these backups for up to 16 days; they are then deleted automatically.
    • Before each software release an additional encrypted backup is made and test-restored in an isolated environment without a network. These backups are currently not deleted automatically.
    • Uploaded files are not backed up.
  • Operations:
    • The services run in separate containers with automatic restart and continuous health checks.
    • They are monitored automatically every 15 minutes (availability, containers, failed conversions), and incidents are reported.
    • The scheduled deletion and maintenance jobs record each run, and their status can be queried.

4. Procedures for regular testing, assessment and evaluation

  • Every software change goes through a review (code review), automated tests and checks in an isolated test environment before release.
  • After release it is checked automatically with a synthetic test account, including in the browser. If that check fails, the previous version is restored automatically.
  • Deletion concept, implemented automatically:
    • files, conversions and bookings after 90 days;
    • conversions the Customer deletes: files at once, records after 30 days;
    • Single Orders with their data after they expire, 7 days after creation, usually within one more day;
    • cached export files after 1 hour;
    • server logs after at most 15 days;
    • daily backups after at most 16 days;
    • learning records, rules and profiles with the customer account.
  • Deletion of the customer account: Deleting the account removes, in one step, all conversions, bookings, files, learning records, rules, profiles, mappings, settings and sessions. An active Stripe subscription is cancelled and a Stripe Connect link is disconnected.
  • Privacy-friendly defaults:
    • Analytics services load only after consent. File names, e-mail addresses and booking content are not sent to them.
    • In the customer account, the Customer can switch AI processing off separately for each of the three purposes (default: on).
    • For Single Orders, AI processing is off until the Customer's AI agent releases it.
    • Without a customer account, the service reads with AI in guest access only files it cannot read without AI (at most 2 pages); the upload screen points this out.

Annex 3: Sub-processors

No.Sub-processorServicePlace of processing
1Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, GermanyHosting, storage and backupNuremberg data centre, Germany
2Microsoft Ireland Operations Ltd., One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, IrelandAzure OpenAI Service for three purposes. In the customer account, the Customer can switch off each purpose separately (default: on); for Single Orders the service runs only after a release by the Customer's AI agent. (a) AI reading: photos and image files, pages of PDF files without a usable text layer, and trial balances and KZV statements are sent as images. PDF bank statements for which no bank template fits or whose reading looks incomplete, electronic invoices with missing mandatory data, and files from which no booking can otherwise be read are sent as selected text. (b) Completing missing data: if a booking lacks the counterparty or payment reference, the related source lines are sent. (c) Account proposals: per booking, the direction, amount, currency, counterparty (up to 80 characters), payment reference (up to 120 characters) and available attributes such as type, category, country, tax rate and fee. In text, e-mail addresses and IBANs as well as labelled BICs and account numbers are masked before transmission; images are sent in full. For mapping CSV columns only structural data, without content, is sent.EU: images in the Azure region Sweden Central, text in the EU data zone of Microsoft Azure
3Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, IrelandGoogle Workspace: the service's e-mail (support mailbox and sending of system messages). Customer content only if the Customer sends files or data to support by e-mail or uses the bug-report form (message and file name).EU; a transfer to Google LLC (USA) cannot be excluded and is based on the EU-US Data Privacy Framework or standard contractual clauses