Skip to content
Home / Privacy Policy

Privacy Policy

Binding version, adopted unchanged from our body of legal texts. Questions about it are answered at datenschutz@zepdesk.de.

Version 1.11.0 Valid from 2026-11-23 Provider: ZeptronIT UG (haftungsbeschränkt), Harmsdorf

As of: 2026-11-20

This English text is a convenience translation. The legally binding version is the German original.

1. Controller

The controller responsible for data processing on this website and the ZepDesk platform is:
ZeptronIT UG (haftungsbeschränkt)
Leon Marzoll
Möhlbarg 12, 23911 Harmsdorf
Email: datenschutz@zepdesk.de

2. Collection and Processing of Personal Data

2.1 When Visiting the Website

When this website is accessed, information is automatically sent by the browser of your device to the server of our website and temporarily stored in a log file: IP address, date and time of access, time-zone difference from GMT, content of the request (the specific page), access status/HTTP status code, amount of data transferred, referrer URL, browser, operating system and its interface, language and version of the browser software. The server of this website is located in a data center of Hetzner Online GmbH in Helsinki, Finland (EU), and is separate from the ZepDesk platform (section 4).

Legal basis: Art. 6 Abs. 1 lit. f DSGVO (GDPR) (legitimate interest in secure, stable operation).
Storage period: The IP address is not anonymized. No fixed deletion period is currently set for these log files; once it is set, we will state it here.

2.2 When Registering and Using ZepDesk

We process the following personal data:

  • Contact data: first and last name, email address, company, billing address
  • Login data: hashed password hash (never in plain text), session cookies; when signing in with Google, Microsoft or Apple, the connection to your account there (section 2.10)
  • Payment data: processed exclusively by our payment provider Mollie (see section 5) or, for subscriptions via the App Store, by Apple (see section 5c). They never reach us in plain text
  • Usage data: login times, API access logs, subdomain usage for troubleshooting and abuse detection
  • Support data: the contents of your support requests

Legal basis: Art. 6 Abs. 1 lit. b DSGVO (performance of a contract); for billing purposes also Art. 6 Abs. 1 lit. c DSGVO (statutory retention obligation, §§ 147 AO (German Fiscal Code), 257 HGB (German Commercial Code)).

2.3 Protection of the Login (Cloudflare Turnstile)

We protect the pages for login, registration and password reset on app.zepdesk.de against automated access with Cloudflare Turnstile. For this, your browser loads a program from Cloudflare and transmits technical information to Cloudflare such as IP address, browser and device characteristics and information about the interaction with the page. Cloudflare then confirms whether the request comes from a human; our platform checks this result. Your login credentials and content from ZepDesk are not sent to Cloudflare. If the protection is set up for your instance, the same applies to the emergency access through which administrators log in directly to your ZepDesk instance.

Recipient: Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. Processing in the USA takes place; it is based on the adequacy decision of the EU Commission on the EU-US Data Privacy Framework, under which Cloudflare is certified.
Legal basis: Art. 6 Abs. 1 lit. f DSGVO (protecting your account and the platform against automated login attempts). Access to information on your device is strictly necessary under § 25 Abs. 2 Nr. 2 TDDDG in order to provide the secured login you requested.

2.4 Address Completion (OpenPLZ API and Photon)

So that addresses arrive complete and correctly spelled, ZepDesk and the registration on app.zepdesk.de suggest matching entries while you type. For this, our server queries two public directories, not your browser. The services therefore see the IP address of our server, not that of your device.

  • Postal code and municipality (OpenPLZ API): In the setup wizard and for the assessment rate of trade tax and property tax, that is for your registered office, your business premises and your properties, we send the postal code and receive the associated localities and municipalities with the official municipality key. If a postal code covers several municipalities, we additionally send the longest word of the street name, without the house number. Recipient: STÜBER SYSTEMS GmbH, Grabbeallee 31, 13156 Berlin, Germany.
  • Address (Photon): In address fields, for example for customers, suppliers, business partners, leads, shareholders, members and properties, in the company and billing details, in the setup wizard, during registration and in the partner application, we send the street name without the house number once it has three characters, and receive suggestions from OpenStreetMap data. Recipient: komoot GmbH, Kienberger Allee 4, 12529 Schönefeld, Germany.

Only the postal code and the street name are transmitted, no house number. Names, e-mail addresses, customer numbers and other content from ZepDesk do not go to the services. A postal code and a street name without a house number do not relate to an identifiable person. We cache the answers on our server so that the same question does not go out again: localities for a postal code for up to 30 days, address suggestions for one hour.

Legal basis: insofar as personal data is involved at all, Art. 6(1)(f) GDPR (legitimate interest in complete, correctly spelled addresses and in the correct municipality for the assessment rate).

2.5 Checking VAT Identification Numbers (VIES)

Whether a VAT identification number is valid is checked by our server with the VAT Information Exchange System VIES of the European Commission. Only the country code and the number are transmitted. VIES forwards the request to the tax administration of the state that issued the number and reports back whether it is valid, depending on the state also with the holder's name and address. We cache the answer for one day.

  • Your own number: when you enter or change it in your account on app.zepdesk.de, and in the partner application. Whether we charge you VAT depends on it. In the developer application we check it to confirm your company details (section 2.9).
  • In ZepDesk: the numbers of your business partners in the recapitulative statement and the number of a lead when you enter it, then once a month again.

Recipients: European Commission (VIES) and the tax administration of the member state that issued the number.
Legal basis: for your own number Art. 6(1)(c) GDPR (VAT obligations when we invoice you) and Art. 6(1)(f) GDPR; we check the numbers of your business partners and leads on your behalf (section 7).

2.6 Time Stamps for the Change Log

If anchoring is switched on for your instance, our server sends a hash value of the latest entry in your change log to a time-stamping service once a day, by default freeTSA.org, and receives a signed time stamp in return. This makes it possible to show later that the log has not been changed since. A hash value allows no conclusion about the content or about persons; no personal data leaves our server. By default, anchoring is switched off.

2.7 Referral Programme

ZepDesk customers can recommend us and receive a commission for it. The terms of participation at /teilnahmebedingungen-empfehlungsprogramm apply. Participation and settlements are handled in the partner portal partner.zepdesk.de. We process the following data:

  • If you arrive via a referral link: the referral code. It is part of the page address, is carried along in the address until registration and appears there in the field “Referral or discount code”. We store nothing on your device for this, neither a cookie nor an entry in your browser’s local storage. Because the code is part of the address, it may appear in the server log files (section 2.1).
  • If you were referred: that you came to us via the code of a particular customer, by which route (link, entry in the form, added later by our support), your discount and when it ends, and your payments to us as the basis of the commission. In the partner portal, the referrer sees your customer number, the date of the assignment, your status (for example active or cancelled), whether you pay and, for each payment, the date, the amount and the commission on it. The referrer does not see your company, names of persons, your contact details or content from your ZepDesk. We inform you of this before you submit your registration. You can object to this disclosure (Art. 21 GDPR). The referrer then only sees your data as a summary line without customer number and without individual payments; the assignment and the referrer’s commission remain.
  • If you refer others yourself: your participation with the version of the terms of participation and its checksum, the time, the person who agreed and the IP address of their browser (see below), your VAT status, tax number or VAT identification number (checked via VIES, section 2.5), your bank details for payouts, your choice between payout and offsetting, your credit balance, your credit notes with itemised statement and your declaration on professional rules (§ 15 of the terms of participation). We notify you of new credit notes by e-mail. At your request we take over details from your billing profile when you join.
  • Your sign-in to the partner portal: You sign in via the central ZepDesk login on app.zepdesk.de, with the login details of your customer account and, if set up, your second factor; there is no separate password for the partner portal. To hand the sign-in over to the partner portal we generate a one-time code. We store it only as a check value together with your e-mail address and whether you signed in with a second factor, for at most two minutes, and it can be redeemed only once. You can also switch to the partner portal directly from your signed-in ZepDesk via “Refer”. ZepDesk then confirms to the partner portal, server to server, who is signed in; no password is transmitted. For this we process your user identifier (e-mail address), the billing profile you come from and the time. The one-time code is then bound to that billing profile and is likewise stored only as a check value, for at most two minutes, and can be redeemed only once. Here too the sole purpose is your sign-in to the partner portal; as for the other sign-in, the legal basis is Art. 6(1)(b) GDPR. If you have not joined yet, the approval for joining is valid for at most 30 minutes. With every access we check that you are still the holder of the billing profile. After sign-in the partner portal stores a session token in your browser’s local storage, as described in section 2.8.
  • To prevent abuse, for every assignment we compare persons, e-mail addresses, postal addresses, VAT identification numbers and payment methods with the referrer’s account so that nobody refers themselves.

We do not send invitations to third parties, and we do not accept recipients’ addresses. We do not count clicks on referral links.

Proof of your consent: When you agree to the terms of participation in the partner portal, our administration receives the IP address of your browser with this declaration. We store it together with the version and checksum of the text, the time and the person who agreed. This lets us prove that and when participation and settlement by credit note were agreed; a credit note requires a prior agreement (§ 14(2) sentence 5 UStG, German VAT Act). Nobody but our administration sees the IP address, and we use it for nothing else.

Purposes: assignment and discount, calculation of the commission, settlement by credit note, payout or offsetting against your own fees, proof of consent to the terms of participation, prevention of abuse and aggregated figures for managing the programme (registrations, paying customers, commission).

Legal bases: Art. 6(1)(b) GDPR for the participation contract with the referrer including the sign-in to the partner portal and for your customer contract with discount; Art. 6(1)(c) GDPR in conjunction with § 147 AO, § 257 HGB and § 14b UStG for retaining credit notes and accounting records; Art. 6(1)(f) GDPR for the data the referrer sees about you (our legitimate interest in settling the commission in a verifiable way), for preventing abuse and for the IP address on joining (our legitimate interest in being able to prove the conclusion of participation, including the credit note agreement, towards you and the tax authorities and to defend against claims).

Recipients: the referrer to the extent described above, our tax adviser and the bank through which we pay out commissions.

Retention: data on the assignment and participation for as long as commission can arise, then until the limitation period expires; credit notes, itemised statements and accounting records for 8 years (section 8). We delete the IP address from your consent three years after the end of the year of your last credit note, once no further commission can arise from your participation. If there was never a settlement, we delete it three years after the end of the year in which your participation ended (regular limitation period, §§ 195, 199 BGB). We keep the version, checksum, time and person of the consent together with the credit notes because they prove the agreement on the credit note procedure.

Objection: Where we process on the basis of Art. 6(1)(f) GDPR, you can object under Art. 21 GDPR (section 9).

2.8 Sales Partner Programme

Businesses can refer ZepDesk as sales partners. The partner agreement at /partnervertrag applies. Application, login and settlements run through the partner portal partner.zepdesk.de. In doing so we process:

  • Your application: company and legal form, contact person and authorised representative, address, e-mail address and telephone number, register entry, date of the trade registration and the proof of it that you upload, tax number or VAT identification number with the result of the VIES check (section 2.5), whether you are a small business, your bank details (IBAN, BIC, account holder) and your remarks. Address completion helps you enter the address (section 2.4).
  • Your acceptance of the partner agreement: version, time, the person who accepted and the IP address of the browser through which the application was made. This is how we prove that and when the partner agreement, including settlement by self-billing credit note, was agreed (section 14 (2) sentence 5 UStG).
  • Your access to the partner portal: e-mail address, password only as a hash, confirmation of the e-mail address, time and IP address of your last login, and failed attempts after which access is temporarily blocked. Each login also records a line with the IP address in our server's log. Where protection is set up, Cloudflare Turnstile checks application and login as described in section 2.3. After login, the partner portal stores a session token in your browser's local storage; it is technically necessary for the login, is valid for at most twelve hours and is deleted when you log out.
  • Your referrals and settlements: the customers attributed to you, your terms, the monthly settlements with itemised statement, the credit notes, objections to them and the payouts.
  • If you come to us through a sales partner: The partner sees in its portal your company name, your customer number, the date of attribution, your status, your discount rate and, for each payment, date and amount with the commission on it. It does not see contact details, contact persons or content from your ZepDesk. We point this out to you before you submit your registration. If you were already a ZepDesk customer before, you still receive the discount; the partner then receives no commission and does not see you.

Purposes: checking the application, concluding and performing the partner agreement, access to the partner portal, attribution of customers, settlement of commission by self-billing credit note and payout, proof of acceptance of the partner agreement, protection of access against misuse.

Legal bases: Art. 6(1)(b) GDPR for application, partner agreement, access, settlement and payout; Art. 6(1)(c) GDPR in conjunction with § 147 AO, § 257 HGB and § 14b UStG for retaining credit notes and bookings; for the information the partner receives about its customers, Art. 6(1)(c) GDPR in conjunction with § 87c HGB (settlement and statement of account towards the sales partner), alternatively Art. 6(1)(f) GDPR (our legitimate interest in settling with the partner in a verifiable way); Art. 6(1)(f) GDPR for the IP address on application (proof of conclusion of the contract towards you and the tax authorities) and for the login data and failed attempts (protection of your access).

Recipients: We create the credit notes in our own ZepDesk instance, which is operated like ZepDesk (section 4). In addition: our tax adviser, the bank through which we pay out commissions, the European Commission for the VIES check (section 2.5) and Cloudflare for protecting the forms (section 2.3). Mollie receives no data from the partner programme; we pay commissions by bank transfer. We send e-mails to you as described in section 6.

Storage period: credit notes and itemised statements as accounting vouchers for eight years, the bookings in our accounts for ten years, in each case from the end of the calendar year (§ 147 (1) no. 1 and 4, (3) AO, § 257 (4) HGB, § 14b UStG). We delete the IP address from your application three years after the end of the year of your last credit note, once the partner agreement has ended and no further commission can arise. If there was never a settlement, we delete it three years after the end of the year in which the agreement ended or your application was rejected (regular limitation period, §§ 195, 199 BGB). The IP address of your last login is overwritten with each login and deleted after the end of the partner agreement with the same period as the IP address from your application. No deletion period is currently set for the lines in the server log. We keep the other information from a rejected application until a deletion rule is set up; we will then state the period here.

Objection: Insofar as we process on the basis of Art. 6(1)(f) GDPR, you can object under Art. 21 GDPR (section 9).

2.9 ZepDesk Developers

Businesses whose software complements ZepDesk can apply for ZepDesk Developers in the partner portal at partner.zepdesk.de/developers and build applications that access a customer's ZepDesk with that customer's consent (developer apps). If you are the owner or an administrator of a customer with a running contract, you do not need to apply: you log in with your ZepDesk account and set up the access yourself. If you accept the Terms for ZepDesk Developers in the application or when setting up, they apply to your participation. Insofar as you use the respective function, we process:

  • Your application: company name and legal form, authorised representative, address, contact person with e-mail address and telephone number, tax number or VAT identification number with the result of the VIES check (section 2.5), register entry, name, website and category of your product, the purpose of the connection, one contact person each for technical matters and for data protection with e-mail address, the addresses of your privacy policy and your legal notice, and your confirmation that your product is not an accounting or financial accounting program. Without the mandatory information the form does not accept the application. We do not ask for bank details or a password. Where protection is set up, Cloudflare Turnstile checks the form as described in section 2.3. So that the form is not submitted in bulk, our server counts applications per IP address; the counter expires after one hour. We do not store your IP address with the application.
  • Setting up without an application: If you log in to the Developer Portal with your ZepDesk account and do not yet have access there, we use your confirmed e-mail address to check for which customers you are the owner or an administrator and whether their contract is running. For this we read your role at the company, the status of the customer account and of the subscription, a termination date and whether a payment method is stored. If this applies to at least one customer, we show you a step for setting up; for this step we keep for at most 15 minutes which e-mail address it applies to, which customer accounts can be chosen, which version of the Terms applies and whether you logged in with a second factor. If you set up the access, we copy company name, legal form, address and VAT identification number from the customer account you choose into your developer account; we do not check the VAT identification number again in the process. If none is stored in the customer account, we ask for your tax number. We store which customer account the information comes from, and your confirmation that your product is not an accounting or financial accounting program. A link to confirm your e-mail address and a manual review do not apply; the central login has confirmed your address (section 2.2). So that the step is not called in bulk, our server counts the attempts per IP address and per e-mail address. Once a day and at every login we check whether you are still the owner or an administrator of a customer with a running contract. If that is no longer the case, your access is suspended until we have reviewed your participation; we note this with the date in your developer account and in the internal log of our administration and inform you by e-mail.
  • Your acceptance of the Terms: If you accept them in the application, we store with your developer account the version of the Terms, the checksum of their wording and the time. This is how we prove that and when the contract was concluded and with which wording. If you accept them in the application, we do not record your IP address or the name of the person who accepted. If you set up the access without an application, there is no manual approval; we therefore record who accepted: in the internal log of our administration your e-mail address, the customer account chosen, the version and checksum of the Terms and your confirmation about the product, and in the login log (section 2.2) one line each with time and IP address when we offer you the step and when you set up the access; your e-mail address is held there only as a check value.
  • Confirmation of your e-mail address: Only for an application. We send you a confirmation link that is valid for 24 hours. For this we create an access record with your e-mail address for your application, which nobody can currently use to log in: its password is a random value that nobody knows and is held only as a hash. We store the link only as a check value; once you confirm, we delete it and mark the address as confirmed.
  • Matching and review: Only for an application. Using e-mail address, VAT identification number, and company name together with postcode or e-mail domain we check whether you are already a ZepDesk customer, and using the e-mail address whether you are already a sales partner. If the e-mail address is already registered with a sales partner or an access to the partner portal, we do not create a new application; we then only receive an internal notification (below) so that we can get in touch with you. We review your information manually. To do so we consult public sources such as the commercial register, the legal notice and the website of your product, and send a test message to the contact persons for technical matters and data protection. We record how and when we decided and who decided, for an approval also the points checked, as well as our notes on the review. Each decision is also recorded in the internal log of our administration, with the reason and the message we sent you about it. If your e-mail address is already registered with a sales partner or an access to the partner portal, you cannot set up the access without an application; we then receive an internal notification with your e-mail address and the company name of the customer accounts you would be entitled for, so that we can get in touch with you, and the login log holds a line about it with time and IP address.
  • Your access to the Developer Portal: for each person with access: e-mail address, role (owner or member), who invited them and when, confirmation of the address, password only as a hash, time of the last password change, time and IP address of the last login, and failed attempts after which access is temporarily blocked. We store links for setting or resetting a password only as a check value; they can be used once and are valid for 24 or two hours. If you log in with your ZepDesk account, the central login at app.zepdesk.de confirms your e-mail address (section 2.2); this creates a one-time code valid for at most two minutes. After login, the Developer Portal stores a session token in your browser's local storage; it is technically necessary for the login, is valid for at most twelve hours and is deleted when you log out. For the same period our server keeps the IP address of the login with the session. Login, blocking after failed attempts, setting a password and resetting the demo company each also write a line to our server's log, with the identifiers of the access or the developer account, for a reset with the person's e-mail address, without IP address. Faults when fetching the log of calls or when passing a block on to an instance are recorded there in the same way, with the identifiers of the developer account or app and the name of the instance. Where protection is set up, Cloudflare Turnstile checks the login and the password forms as described in section 2.3.
  • Your developer apps: name, category, descriptions and price information, the support contact channels (e-mail address, website, telephone number), the addresses of your privacy policy, your legal notice, your data processing agreement and your statement on professional secrecy, your role under data protection law, the place of processing, the addresses for setup and redirect, the requested permissions and the app's secrets, these only as a check value with date and the person who created them. For each review of an app we record who approved which version and when, with the points checked and notes, as well as our queries to you and the reasons for a pause or block.
  • Your demo company: If we set up a demo company for you after approval or after setting up without an application, it is a separate ZepDesk instance with the sample data of a fictitious company. Login is through the central ZepDesk login, with the e-mail address and the name of the contact person from your application (section 2.2). If you set up the access without an application, we use your e-mail address and, as the name, “Developer” with your company name. The demo company sends no e-mails and no letters, connects no bank and submits nothing binding to the tax office or social insurance; only test submissions in test mode are possible there. Please do not enter any real personal data there. To tell whether you still use the demo company, we read the last access: setup or reset, login, calls by your apps and work in the open browser window.
  • Log of calls: If a developer app calls a ZepDesk instance, that instance records each call: time, method, path and area called, result, duration and error code, without the content transferred. The customer sees this log for the connection; you see it in the Developer Portal for your demo company.
  • If you as a customer connect a developer app: We store your consent with the person who consented, the time, the text and the permissions granted in your instance; there we process it on your behalf (section 7). Your instance reports to our administration only your company name and the identifier of your company record when you connect an app, revoke its access or we block it. In their portal the developer sees your company name, since when the app has been connected and whether the connection still exists. Which data the app reads you determine with your consent; whether the developer processes it as your processor or as a controller in their own right is stated in the catalogue and at consent. If we enable your company for the beta of an app, we also record your company name, the day and the person who enabled it, and that you are not subject to professional secrecy.
  • E-mails and internal notifications: You receive the confirmation link from us and, after the review, a message about approval or rejection; we send a rejection only to a confirmed address. If you set up the access without an application, you instead receive a confirmation by e-mail with your company name, the version of the Terms and the time of your acceptance. If you are not yourself the owner of the customer account, we also inform the owner by e-mail: with the company name, your e-mail address, the time and the version of the Terms, and with a note on how to object. We record in the internal log of our administration that we informed the owner. If you use the Developer Portal, e-mails about your accesses (invitation, setting and resetting the password) and about your demo company are added. We notify ourselves internally by e-mail of every new application: once with company name, legal form, address, VAT identification number and product name, and once to our sales team with company name, legal form, name and e-mail address of the contact person, VAT identification number with the result of the VIES check, product name, website, category, purpose of the connection and whether your e-mail address has already been confirmed. We notify our sales team by e-mail of every access that is set up without an application, with company name, legal form, identifier of the customer account, your e-mail address and VAT identification number. If an application matches an existing customer account or the e-mail address is already registered, the notification states e-mail address, company name and VAT identification number, for a customer account also its identifier and the reason for the match.

If you name contact persons to us or invite people to your team, please inform them about this section. We answer questions about ZepDesk Developers at developers@zepdesk.de.

Purposes: review of the application or of your entitlement as owner or administrator of a customer, conclusion and performance of the contract for ZepDesk Developers, contact with you and the named contact persons, attribution to an existing customer or partner relationship, access to the Developer Portal, review, approval, pause and block of developer apps, provision and deletion of the demo company, display of the apps to customers, log of calls to protect the platform and to inform the customer, proof of the conclusion of the contract and of our decisions, protection of accesses and forms against misuse.

Legal bases: Art. 6(1)(b) GDPR for application, contract, access, review, demo company and the display of your apps in the catalogue, insofar as you yourself, as a business, are or want to become the contracting party; for persons a business names to us or invites to its team, and their contact details, Art. 6(1)(f) GDPR (our legitimate interest in reviewing that business's application, performing the contract with it and reaching the named persons). For setting up without an application likewise Art. 6(1)(b) GDPR, insofar as you yourself become the contracting party; if you act for a business, Art. 6(1)(f) GDPR (our legitimate interest in concluding and performing the contract with that business). Art. 6(1)(f) GDPR also for the matching with our customers and sales partners (our legitimate interest in correctly attributing an application to an existing customer or partner relationship), for the internal notifications (our legitimate interest in processing applications promptly), for the counters per IP address, the IP addresses of the session and of the last login, the failed attempts, the lines in the server log and the log of calls (our legitimate interest in protecting the platform, accesses and customers against misuse and in investigating faults) and for the proof of your acceptance of the Terms, our notes and the log of decisions (our legitimate interest in being able to prove the conclusion of the contract and our decisions); for checking whether you are the owner or an administrator of a customer with a running contract, and its daily repetition (our legitimate interest in giving access without an application only to persons who may act for a customer); for recording your e-mail address and IP address when setting up (our legitimate interest in being able to prove the conclusion of the contract, because nobody approves manually, and in investigating misuse); for informing the owner of the customer account (our legitimate interest and that of the business in its learning of a contract that someone concludes on its behalf); for the counters per e-mail address. For customers who connect a developer app: Art. 6(1)(b) GDPR (your contract with us; you initiate the connection) and, for the information the developer sees about you, alternatively Art. 6(1)(f) GDPR (our legitimate interest and that of the developer in knowing and supporting the connected companies). Section 2.5 applies to the check of the VAT identification number.

Recipients: ZepDesk customers who may see your app (at the beta stage only the enabled companies, at the demo stage only your demo company) receive the company name, town and country of your business, name and description of the app, the price information, the support contact channels, the addresses mentioned, your role under data protection law, the place of processing and the requested permissions. If you as a customer connect a developer app, its developer receives the information about your company mentioned above. In addition: Cloudflare for protecting the forms (section 2.3) and the European Commission for the VIES check (section 2.5). We operate the application, the Developer Portal and the demo companies like ZepDesk (section 4). We send e-mails as described in section 6. Payment service providers and banks receive no data from the programme.

Storage period: the session token and the IP address of the session for at most twelve hours, the counters per IP address for at most one hour, the check value of the confirmation link until confirmation or until the application is deleted. The time and IP address of the last login are overwritten with each login. If the owner removes a person from the team, we delete their access immediately. If you do not use your demo company for 90 days, we remind you by e-mail; if it then remains unused for a further 30 days, we delete the instance with all data in it. We delete entries in the log of calls after 30 days. We delete the information from a rejected or never confirmed application six months after the decision or after the confirmation link expired, together with the access record, the internal notifications and our notes on it, also in the internal log of our administration; a notification about an e-mail address already registered six months after it was received. When the contract ends, we delete your accesses, your demo company and your developer account after 30 days (section 12 (9) of the Terms), except for the information we keep as evidence: we keep the information from the application, your developer apps, the proof of your acceptance and our notes on reviews and decisions, also in the internal log of our administration, after the end of the contract until the regular limitation period has expired, i.e. three years from the end of the year in which the contract ended (§§ 195, 199 BGB). There is no fixed deletion period for the lines in the server log: the server writes them to log files that it rotates at 100 KB; it keeps 20 older files and deletes the oldest each time. How long a line remains therefore depends on how much the server logs. We keep the step for setting up for at most 15 minutes. The counters per e-mail address expire after one hour, the counters per IP address when setting up after five minutes. We keep the information from setting up without an application and the proof of your acceptance like the information from an application, i.e. until three years after the end of the year in which the contract ended. For the entry in the login log, section 2.2 applies. Section 8 applies to backups already made.

Objection: Insofar as we process on the basis of Art. 6(1)(f) GDPR, you can object under Art. 21 GDPR (section 9).

2.10 Signing in with Google, Microsoft or Apple

Instead of your email address and password, you can also sign in at the central login on app.zepdesk.de with your account at Google, Microsoft or Apple, insofar as we offer the respective option. This also applies if you come to the central login from the partner portal or the Developer Portal. Signing in through a provider is voluntary; you can still sign in with your email address and password at any time. No new ZepDesk account is created in the process: this option is only open to an existing account that you have connected once to your account with the provider.

The provider buttons are part of our page; as long as you do not click one of them, the provider receives nothing from our page. If you click one, your browser takes you to the provider's sign-in page. As with any visit to its pages, the provider receives your IP address and technical information about your browser and device, together with the information that you want to sign in to ZepDesk. This happens every time you sign in through the provider, so the provider learns when you sign in to ZepDesk. At the provider, you sign in if you are not already signed in there and confirm the sign-in to ZepDesk. We never learn your password with the provider. The provider then sends you back to us with a one-time code. Our server redeems this code with the provider for a confirmation of your sign-in signed by the provider (ID token) and verifies it. Beyond that, we send the provider no information about you, in particular no content from ZepDesk.

Connecting once: The first time, you connect your account with the provider to your ZepDesk account. To do so, you confirm with the email address and password of your ZepDesk account and, if set up, your second factor that this account belongs to you. After that, signing in through the provider is enough; a second factor you have set up still applies. After connecting and after every renewed confirmation, we send an email to the address of your ZepDesk account, stating the name of the provider and, if known, the email address of your account there. This lets you notice if someone else creates a connection. If you change or reset your ZepDesk password, all connections of your account are suspended until you confirm them again with the new password.

In doing so, we process:

  • From the provider's confirmation: the permanent identifier of your account with the provider; for Google and Microsoft, the email address of that account (for Microsoft, failing that, the sign-in name if it is an email address) and whether the provider marks it as verified; for Microsoft, also the identifiers of your account and of its directory, which for a work or school account is that of your organisation. From Google we only request the identifier and the email address, from Apple neither your name nor your email address. Microsoft also sends your name; we do not take it over. We do not store your name, a profile picture, the provider's tokens or, for Apple, an email address. Whether you can sign in is decided by the identifier alone, never by the email address.
  • The connection: the provider, the identifier of your account there and check values derived from it, for Microsoft the identifiers of account and directory, the email address of your account with the provider and whether it is verified (only for display and for the email on connecting), your ZepDesk account with its email address and a check value of it, when and how you confirmed the connection (password, if set up together with a code by email or from an authenticator app), a check value derived from the stored hash of your password so that the connection is suspended after a password change (neither the password nor the hash itself), the time of your last sign-in through the provider and, if the connection is removed, when and by whom.
  • Temporarily on our server, encrypted and for no more than ten minutes: the sign-in you started (provider, time, random values to secure the return and where you return to afterwards), after the return the information from the provider's confirmation until you are signed in or have created the connection, and, when connecting, your ZepDesk account, the type of your second factor, the number of attempts and the key with which we check its code (for an authenticator app, its secret key).
  • The cookie zd_sso_tx: So that the return from the provider only succeeds in the browser in which you started the sign-in, app.zepdesk.de sets this cookie when you click a provider. It contains only a random value, is valid for no more than ten minutes, cannot be read by scripts on the page and is only transmitted over encrypted connections. We delete it as soon as the sign-in through the provider has been accepted or the connection has been created, and also if you cancel at the provider or the sign-in fails; otherwise it expires after ten minutes at the latest.
  • Login log and protection against misuse: As with every login (section 2.2), our server records every sign-in through a provider, every connecting and removing of a connection and every rejected attempt in one line: time, IP address, provider, result and, where the ZepDesk account is known, a check value of its email address, not the address itself. To prevent mass sign-in attempts, we limit attempts per IP address and count failed attempts.

Recipient: the provider you choose. It processes the sign-in on its side under its own responsibility and in accordance with its privacy policy:

  • Google: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. According to Google, it operates data centres around the world; processing in the USA is possible. Google LLC in the USA is certified under the EU-US Data Privacy Framework, for which an adequacy decision of the EU Commission exists. Privacy policy: policies.google.com/privacy
  • Microsoft: Microsoft Ireland Operations Limited, One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland, and, according to Microsoft, also Microsoft Corporation, One Microsoft Way, Redmond, WA 98052, USA. According to Microsoft, it stores and processes data in your region, in the USA and in other countries; Microsoft Corporation is certified under the EU-US Data Privacy Framework, and Microsoft also uses standard contractual clauses of the EU Commission. If you sign in with a work or school account, your organisation manages that account; according to Microsoft, it can access your data and can see in its logs when you signed in to ZepDesk. Privacy statement: microsoft.com/en-us/privacy/privacystatement
  • Apple: Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland. According to Apple, personal data is generally stored by Apple Inc. in the USA; Apple governs this transfer with standard contractual clauses of the EU Commission. If you use an Apple Account managed by your organisation, your organisation can, according to Apple, manage the apps with which you use Sign in with Apple. Privacy policy: apple.com/legal/privacy

We send the email on connecting as described in section 6. We process everything else on our administration platform at Hetzner in Germany (section 4).

Legal basis: Art. 6(1)(b) GDPR for signing in through the provider and for the connection, insofar as you yourself are a contracting party of ZepDesk; for persons who use ZepDesk as users of a customer without being a contracting party themselves, Art. 6(1)(f) GDPR (our legitimate interest and that of the customer in giving you access in the way you choose yourself). Art. 6(1)(f) GDPR also for the confirmation with password and second factor, the check value of the password, the email on connecting, the limiting and counting of attempts and the login log (our legitimate interest in protecting your account against being taken over through someone else's account with the provider, and in detecting and investigating misuse); for the login log, section 2.2 also applies as for every login. Setting and reading the cookie zd_sso_tx is strictly necessary under § 25 Abs. 2 Nr. 2 TDDDG in order to provide the sign-in through the provider that you requested securely; no consent is required for this.

Storage period: the cookie and the temporary information for no more than ten minutes; the counters for limiting attempts expire after one minute, the counters of failed attempts 15 minutes after the last failed attempt. We store the connection until it is removed and delete it at the latest together with your ZepDesk account (section 8). We keep a removed connection as evidence of who connected which account with the provider to your ZepDesk account and removed it again, and when, and delete it twelve months after it was removed. No fixed deletion period has been set up for the login log yet; as soon as it is set, we will state it here. Section 8 applies to the daily backups.

Removing a connection: You cannot yet remove a connection yourself in ZepDesk. Until that is possible, we remove it in our administration at your request; please write to support@zepdesk.de. Changing or resetting your ZepDesk password also takes effect immediately: all connections of your account are then suspended until you confirm them again with the new password. You can also withdraw ZepDesk's sign-in at the provider: at Google in your Google Account (myaccount.google.com/linkedapps), at Apple under Sign in with Apple in the settings of your Apple Account (account.apple.com), at Microsoft in the settings of your Microsoft account, and for a work or school account at myapplications.microsoft.com or through your organisation. This does not remove the connection stored with us: if you agree again at the provider later, it can lead to your ZepDesk account again. If you want to remove the connection completely, please write to us in that case too.

Objection: Insofar as we process on the basis of Art. 6(1)(f) GDPR, you can object under Art. 21 GDPR (section 9). The easiest way to do so for the future is to sign in with your email address and password again and have the connection removed.

Applicability: This section applies from the day on which we offer sign-in via one of these providers, even if that day is before the date stated above.

3. Cookies

Our website uses only technically necessary cookies (a session cookie to maintain your login, CSRF protection). For signing in with Google, Microsoft or Apple, app.zepdesk.de also sets the cookie zd_sso_tx when you click a provider; it is valid for no more than ten minutes (section 2.10). No marketing, analytics, or tracking cookies without your explicit consent. We set no cookie for the referral programme (section 2.7).

Legal basis: § 25 Abs. 2 TDDDG (German Telecommunications Digital Services Data Protection Act) Nr. 2 (strictly necessary to provide the service you requested).

3a. Web analytics (Umami)

For anonymous web analytics we use Umami, a self-hosted analytics tool on our own server (analytics.zeptronit.com) in a data center of Hetzner Online GmbH in Helsinki, Finland (EU). Umami works without cookies and without cross-device tracking. Only aggregated, anonymous usage data is collected, such as the page viewed, the referrer, the approximate country of origin, and the browser and device type, as well as clicks on the links to sign-up and pricing and, on the home page, how far visitors scroll. No full IP addresses are stored and no data is shared with third parties. If you arrive via a referral link, we remove the referral code from the address before it is sent to Umami. Umami therefore does not record the code.

Legal basis: Art. 6 Abs. 1 lit. f DSGVO (legitimate interest in the needs-based design and statistical analysis of our website). As no cookies are set and no personal data is processed, no consent under § 25 TDDDG is required.

4. Hosting and Infrastructure

We operate the ZepDesk platform in data centers of
Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen,
at the Falkenstein (Vogtland) site in Germany. The application, the databases, files and receipts, the daily backups, our management platform app.zepdesk.de with the central login, the sign-in service for connections connect.zepdesk.de (section 5b.1) and the knowledge service of the AI assistant are located there. Hetzner acts for us as a processor pursuant to Art. 28 DSGVO.

Outside Germany, but within the EU, the following process data:

  • Receipt recognition and dictation: Scaleway SAS in a data center in Paris, France (section 7b).
  • Website and web analytics: servers of Hetzner Online GmbH in Helsinki, Finland (sections 2.1 and 3a). They contain no data from ZepDesk.

Further recipients are named in sections 2.3 (protection of the login), 2.4 (address completion), 2.5 (VAT ID), 2.10 (signing in with Google, Microsoft or Apple), 5 (payments), 5a (bank connection), 5b (connections to third-party providers), 6 (email delivery), 7b (AI assistant) and 7c (app).

5. Payment Processing (Mollie)

For payment processing (SEPA direct debit, credit card, PayPal) we use the EU payment provider:
Mollie B.V., Keizersgracht 126, 1015 CW Amsterdam, Niederlande

During payment, the following data is transmitted to Mollie: name, email address, invoice amount, IBAN or card details. The payment data is entered encrypted directly with Mollie and does not reach us in plain text (PCI-DSS compliant). Mollie's privacy policy: mollie.com/privacy.

Legal basis: Art. 6 Abs. 1 lit. b DSGVO (performance of a contract).
Role: Mollie processes this data as a payment service provider.

5a. Bank Connectivity (finAPI and Qonto)

When you link a bank account in ZepDesk to import your transactions automatically, we use the following account information service under PSD2:
finAPI GmbH, Adams-Lehmann-Straße 44, 80797 München, Germany

The connection to your bank is authorized solely by you via your bank's secured procedure. The account and transaction data you release is transmitted (including IBAN, balance, booking texts, amounts, payment references). finAPI is a payment service provider licensed and supervised by BaFin. finAPI's privacy notice: finapi.io/datenschutz.

Legal basis: Art. 6 Abs. 1 lit. b DSGVO (performance of a contract) and your consent under Art. 6 Abs. 1 lit. a DSGVO for the account access.
Server location: Germany (EU).
Role: finAPI acts for us as an account information service.

Qonto: If your business account is with Qonto, you can connect it directly instead of via finAPI. For this, you store an API key from your Qonto account in ZepDesk, and ZepDesk uses it to fetch your transactions from Qonto (Qonto SA, 6 Impasse Bonne Nouvelle, 75010 Paris, France). Only the request and your key go to Qonto; ZepDesk stores the key encrypted. Qonto is your bank, not our service provider; we process the transactions on your behalf (section 7).

5b. Connections to Third-Party Providers (Integrations)

ZepDesk can connect to services where you have your own account. Data only flows once your company's administration switches on a connection and stores your access to the provider for it or signs in there. ZepDesk then uses this access to fetch data from your account with the provider, such as payments, payouts and fees, orders, invoices, files or booked appointments, and stores it in your instance. ZepDesk writes nothing into your account with the provider; only the request and your access go to the provider. ZepDesk stores the access encrypted. If you switch a connection off, ZepDesk fetches nothing more. If you disconnect it, ZepDesk deletes the access and also revokes a sign-in with the provider where the provider allows this for a single connection. You can also withdraw the access at any time in your account with the provider.

  • Payment services and point of sale: Mollie (your own Mollie account, independent of section 5), PayPal, PayPal Point of Sale (formerly Zettle), Stripe, SumUp
  • Online shops and marketplaces: Ecwid and Billbee; Shopify, WooCommerce (the request only goes to your own store) and Amazon Seller Central as soon as they are available in ZepDesk
  • Purchasing: Amazon Business as soon as it is available in ZepDesk
  • Receipt sources: Google Drive, OneDrive and Dropbox as soon as they are available in ZepDesk
  • Industry software: Das Programm
  • Appointments: meetergo
  • Webhooks to Make, Zapier or your own system: exactly the events you select go, with their fields, to the address you specify.

How signing in with the provider works is described in 5b.1. What individual connections read and to whom the request goes is described in 5b.2 to 5b.5, the legal basis and storage period for all connections in 5b.6. You connect your bank via section 5a, the AI assistant via section 7b.

5b.1 Signing in with the provider and our sign-in service (connect.zepdesk.de)

For connections with a "Connect with …" button, you sign in directly with the provider and agree there which data ZepDesk may read. We do not receive your password for the provider. The way there and back runs through our sign-in service at connect.zepdesk.de: it exchanges your consent with the provider for an access token, stores it encrypted, passes it on to your instance and renews it for as long as the connection exists. For this we use the open source software Nango, which we operate ourselves on our servers at Hetzner Online GmbH in Falkenstein (section 4). The maker of the software receives no data.

The data processed are the access and refresh tokens, the identifier of your account with the provider (such as your SumUp merchant code), which instance the connection belongs to, when it was established and when it was disconnected, and, for technical reasons, the IP address and details of your browser when connect.zepdesk.de is called. Our management platform app.zepdesk.de also records which account is connected to which instance. If you connect Shopify through our own Shopify app, the sign-in runs through this management platform; it only records which store is connected to which instance and passes the access token to your instance alone.

Storage period: If you disconnect a connection, we delete the access token in your instance and in the sign-in service. It is finally removed from the service's database after one day at the latest and from its encrypted backups after 30 days. The record on the management platform remains after disconnecting so that an interrupted disconnection can be completed, and is deleted like your account data (section 8). Section 8 (server logs) applies to logs containing connection data.
Legal basis: Art. 6 Abs. 1 lit. b DSGVO (providing the connection you switch on); for the IP address and browser details Art. 6 Abs. 1 lit. f DSGVO (legitimate interest in secure, stable operation).

5b.2 Payment services and point of sale: Mollie, SumUp, PayPal Point of Sale

  • Mollie: settlements and payouts, payments, refunds as well as balances and movements of your Mollie account, for each payment with amount, date, description and, depending on the payment method, the payer's name, the cardholder's name or an email address. Recipient of the request: Mollie B.V., Keizersgracht 126, 1015 CW Amsterdam, Netherlands. Mollie names recipients outside the EEA for individual cases and then relies, for example, on standard contractual clauses of the EU Commission.
  • SumUp: your payouts with the card payments and fees they contain as well as your merchant data with merchant code; if you use the cash book and switch on daily sales, also your sales and refunds with tax rate. Recipient: the SumUp company you have your contract with; for the European business, according to SumUp, one of these companies: SumUp Limited (Dublin, Ireland), SumUp EU Payments, UAB (Vilnius, Lithuania) or SumUp Payments Limited (London, United Kingdom). According to SumUp, it stores the data of its European business in the European Economic Area. According to SumUp, data may, however, also go to group companies, payment participants and service providers outside the EEA or in the United Kingdom; SumUp states that it secures this by contract.
  • PayPal Point of Sale (formerly Zettle): payments, fees and payouts as well as your point of sale receipts with items, amounts and the reference of the card payment. Recipient: PayPal (Europe) S.à r.l. et Cie, S.C.A., 22-24 Boulevard Royal, L-2449 Luxembourg; according to PayPal's terms, the point of sale service is provided by iZettle Merchant Services AB, Stockholm, Sweden.

5b.3 Online shops: Shopify and Billbee

  • Shopify: your orders with items, taxes and refunds as well as the name, email address and billing address of the customers who ordered, plus, once ZepDesk fetches them, the payouts of Shopify Payments with fees. Invoices, customers and items are created from this in your instance. Recipient: Shopify International Ltd., 2nd Floor, 1-2 Victoria Buildings, Haddington Road, Dublin 4, D04 XN32, Ireland. According to Shopify, it also processes data in Canada, where the company has its headquarters, and in the USA, within the group on the basis of Binding Corporate Rules.
  • Privacy requests via Shopify: If a customer requests access via Shopify, ZepDesk creates a task for your company's administration. If they request deletion of their data, ZepDesk clears the stored raw data of the affected completed orders, including their name there, and creates a task. If you remove our app from your store, ZepDesk disconnects and clears the raw data of all completed orders of the store. Booked invoices remain unchanged because retention obligations apply to them.
  • Billbee: your invoices per sales channel with items and taxes as well as the name, company, email address, delivery country and, where applicable, VAT identification number of the buyers. Invoices, customers and items are created from this in your instance. Recipient: Billbee GmbH, Arolser Str. 10, 34477 Twistetal, Germany.

5b.4 Amazon Seller Central and Amazon Business

Both connections are in preparation and apply as soon as they are available in ZepDesk. They only read financial and invoice data and serve your accounting alone; signing in runs through "Login with Amazon" and our sign-in service (5b.1). More on our page about the Amazon connection.

  • Amazon Seller Central: your settlements and financial events, that is sales per order, refunds, Amazon fees and commissions and the payouts to your bank account, each with order number and SKU. ZepDesk only requests the "Finance and Accounting" role from Amazon; ZepDesk does not read the names, addresses or contact details of your buyers.
  • Amazon Business: your payment transactions on Amazon Business (charges and refunds) with order number, invoice number, date, amount and seller, plus the invoices and credit notes as PDF, which ZepDesk places in the receipt inbox as receipts. They carry the details an invoice must carry, including the name and address of the invoice recipient and, where Amazon lists it, the delivery address. Amazon's payment data also contains the name and email address of the orderer and the payer, the last four digits of the payment instrument, company and department names and fields of your order form; ZepDesk receives them along with it but does not store them. ZepDesk only requests the "Business Purchase Reconciliation" role.

Recipient: the Amazon company with which you have concluded your contract for Seller Central or Amazon Business.
Deletion: If you disconnect an Amazon connection, ZepDesk deletes the access token (5b.1). After disconnecting, and likewise if you withdraw ZepDesk's access at Amazon, ZepDesk deletes from your instance within 30 days all data from your Amazon account that has not been taken over into your accounting, that is, neither as a receipt in the receipt inbox nor in a booking. Of records that were taken over, only the identifier, date, amount, description and counterparty remain as proof of origin. ZepDesk does not delete receipts with their PDF or bookings in the process, not even an invoice that has not yet been booked; they remain for as long as statutory retention obligations require. Section 8 applies to the daily backups. In Seller Central you withdraw access via "Apps and Services" and "Manage Your Apps".

5b.5 Receipt sources: Google Drive, OneDrive, Dropbox

Every new file in the folder you choose becomes a receipt in the receipt inbox. ZepDesk downloads the file and recognizes it like an uploaded receipt (section 7b). Only the files of this folder are read, with name, size and time of change, and their content.

  • Google Drive: ZepDesk only sees the folders and files you select in Google's picker ("drive.file" permission), plus the display name of your Google account, with which ZepDesk checks the connection. For the selection, ZepDesk opens a separate page that loads Google's picker (Google Picker); Google receives technical details such as your IP address from your browser in the process. Recipient: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. According to Google, it operates servers worldwide; Google LLC in the USA is certified under the EU-US Data Privacy Framework, for which an adequacy decision of the EU Commission exists.
  • OneDrive: the "Files.Read" permission allows reading your files; ZepDesk only reads the folder you name. Recipient: Microsoft Ireland Operations Limited, One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland. According to Microsoft, it usually stores data in your region or in the USA; Microsoft Corporation is certified under the EU-US Data Privacy Framework, and Microsoft also uses standard contractual clauses of the EU Commission.
  • Dropbox: ZepDesk only reads the folder "Apps/ZepDesk" in your Dropbox, plus the name and email address of your Dropbox account, which Dropbox gives to every app. Recipient: Dropbox International Unlimited Company, Dublin, Ireland. According to Dropbox, it processes data in the USA and worldwide; Dropbox, Inc. is certified under the EU-US Data Privacy Framework, and Dropbox also uses standard contractual clauses.

Data from Google APIs: ZepDesk only uses it to create receipts in your instance from it. ZepDesk does not use it for advertising, does not sell it and only passes it on to the processors named in this policy for hosting (section 4) and receipt recognition (section 7b), unless you pass it on yourself, for example to the AI assistant. ZepDesk's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

5b.6 Legal basis, roles and storage period

You are the controller for the data from your accounts with the providers, and we process it on your behalf (section 7). You usually base the processing on the performance of your contracts and your statutory obligations to keep books and retain records (Art. 6 Abs. 1 lit. b and c DSGVO). Insofar as we process data ourselves to provide the connection you switched on (access, sign-in, identifier of your account), the legal basis is Art. 6 Abs. 1 lit. b DSGVO; loading Google's picker is strictly necessary under § 25 Abs. 2 Nr. 2 TDDDG to provide the selection you requested. You have your own contract with the provider; its terms and privacy notices apply, including on where it processes data. The providers are not our processors.

  • Access: until you disconnect the connection (5b.1).
  • Raw data in the connection's inbox: ZepDesk clears the provider's full response to a completed record after 90 days by default, and for records from which ZepDesk cannot take anything over, 90 days after the last fetch. Your company's administration can set the period between one day and ten years. Afterwards, the identifier, date, amount, counterparty and the reference to what was created from it remain. Daily sales of a point of sale system are an exception: ZepDesk does not clear the individual transactions behind the daily total because they document the booked daily total; the next item applies to them.
  • Invoices, receipts, customers, items and bank entries created from a connection are part of your accounting; your statutory retention obligations and section 8 apply to them.
  • Amazon: additionally the deletion within 30 days under 5b.4.

5c. Subscriptions via the App Store (Apple In-App Purchase)

If you purchase a subscription via in-app purchase in the ZepDesk app for iOS, the seller is Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland. For the purchase, Apple processes the data of your Apple ID, your payment method and your receipt under its own responsibility. We are neither a controller instructing Apple nor a processor for Apple. Apple's privacy policy applies: apple.com/legal/privacy.

What we receive from Apple: For your subscription, we receive signed purchase information from Apple: the identifiers of the transaction and of the original transaction, the purchased product (plan and term), purchase and expiry date, whether the subscription renews automatically and into which product, the end of a grace period, the time of a refund or revocation, price and currency, the App Store country and whether it is a test or a real purchase. So that we can assign the purchase to your ZepDesk account, our platform issues a random assignment identifier before the purchase, which Apple returns with the purchase. We do not receive card data, bank details, or the name and email address of your Apple ID.

How we receive the data: After the purchase, the app passes the signed purchase information to our platform (app.zepdesk.de), which verifies Apple's signature. If your subscription changes, for example through renewal, cancellation, a change, expiry or a refund, Apple notifies our platform directly (App Store Server Notifications). In addition, we reconcile the status of your subscription daily via Apple's interface.

Purpose: We use the data to provide your instance, renew the subscription, carry out changes, restrict access in the event of payment problems, expiry or a refund, avoid duplicate subscriptions and reconcile our accounts with Apple.

Legal basis: Art. 6 Abs. 1 lit. b DSGVO (GDPR) (performance of a contract), for retention under tax and commercial law Art. 6 Abs. 1 lit. c DSGVO (GDPR) (§ 147 AO, § 257 HGB).
Recipients and third countries: Apple Distribution International Ltd. (address above). According to Apple, personal data is generally stored by Apple Inc. in the USA; Apple governs the transfer there with standard contractual clauses of the European Commission.
Storage period: We retain the purchase information on your subscription for 8 years, counted from the end of the calendar year of the respective purchase or renewal (§ 147 Abs. 3 AO, § 257 Abs. 4 HGB). We delete the log of Apple's notifications 12 months after receipt.

Cancellation, refund, account deletion: Cancellation and refunds are handled exclusively by Apple, for example in the subscription settings of your Apple ID or at reportaproblem.apple.com. You can request the deletion of your ZepDesk account in the app; a running subscription at Apple does not end as a result and must be cancelled separately at Apple.

6. Email Delivery

We send emails of the platform (such as confirmation codes, password resets, invoices, system notifications) via the mail server of
ALL-INKL.COM, Neue Medien Münnich, owner René Münnich, Hauptstraße 68, 02742 Friedersdorf,
with data centers in Dresden, Germany. The emails you send from ZepDesk to your customers and business partners also go through this mail server, as long as you have not set up your own mailbox for sending in ZepDesk. The contents of your emails are not analyzed for advertising purposes.

7. Data Processing (AVV)

Insofar as you, as the customer, process personal data of your end customers or employees in ZepDesk, you are the controller within the meaning of the DSGVO and we are your processor pursuant to Art. 28 DSGVO. The data processing agreement (AVV) required for this is part of our AGB (general terms and conditions) and is concluded online upon conclusion of the contract. You can find the text at /avv.

7a. Platform-as-a-Service: Technical Access to Your Instance

ZepDesk is not only a standard SaaS solution but also a Platform-as-a-Service (PaaS): your instance runs in its own, separated area (namespace) of our Kubernetes cluster at Hetzner in Falkenstein, with its own database schema and its own area in the object storage. We operate and maintain it and customize it individually on request. This entails certain technical access options, which we transparently disclose here:

7a.1 Passive Monitoring (automatic, without Ops interaction)

To ensure operation, we continuously collect and store technical metrics:

  • Telemetry of the cluster nodes and the containers of your instance: utilization of processor, memory and storage
  • Site metrics (daily): database size in MB, file size in MB, number of users, number of companies, number of invoices, as numeric values, not contents
  • HTTP availability checks: every 5 minutes, response status code and response time
  • Status reports of the containers of your instance (status, version, uptime)
  • Server log files: access and error logs of the web server of your instance, with IP address. They are kept in the container logs of the cluster, are not anonymized and disappear when the cluster rotates them by size or the container is replaced; no separate deletion period is set

Contents from your database (customer, invoice, and article data) are not read during passive monitoring. Legal basis: Art. 6 Abs. 1 lit. b DSGVO (performance of a contract) and lit. f (legitimate interest in stable operation).

7a.2 Active Ops Access (only in case of a malfunction or upon your instruction)

For maintenance and customization purposes, our technicians have the technical ability to connect to your instance. Specifically, we can:

  • Administrative access to the cluster nodes and into the containers of your instance (running commands, reading logs)
  • Database access: database administrator access for troubleshooting, backup restoration, data repair
  • Execute platform maintenance commands: Migration, module install commands)
  • Impersonation: switch into your customer platform as a logged-in user in order to reproduce a specific support issue
  • Deploy custom code: install our own extension modules or scripts, provided that you have commissioned customization services

7a.3 When do we actively access?

Exclusively in one of the following cases:

  1. Upon your express instruction / your support ticket request (e.g. "please install Addon X", "my import got stuck"). Legal basis: Art. 6 Abs. 1 lit. b DSGVO (performance of a contract) and, if you have concluded a Platform Service Agreement (see /platform-service), also this contractual basis.
  2. In the event of a serious malfunction that endangers the operation of your instance (e.g. disk full, DB corruption). Legal basis: Art. 6 Abs. 1 lit. f DSGVO (legitimate interest in service availability).
  3. In the event of security incidents (e.g. suspected malware, brute-force attacks). Legal basis: Art. 6 Abs. 1 lit. f DSGVO.
  4. In the event of a legal obligation (e.g. official requests for information). Legal basis: Art. 6 Abs. 1 lit. c DSGVO.

7a.4 Information about Access

There is currently no log of this access that you can view yourself in the customer portal. We answer questions about individual access to your instance at datenschutz@zepdesk.de; your right of access under Art. 15 DSGVO (section 9) remains unaffected.

7a.5 Independence from the Standard SaaS Usage Agreement

Active Ops customization services (point 7a.2, item 5 above) require a separate Platform Service Agreement (PSV). Without such a PSV, our active interventions are limited to maintenance and emergency measures (7a.3 nos. 2 to 4). Details on the PSV can be found at /platform-service.

7b. AI Assistant (optional feature)

ZepDesk includes an optional AI assistant that supports you in operating it (answering questions, creating drafts and booking suggestions, performing operating steps). The feature is opt-in and not required for the operation of the core functions.

Which data is transmitted: only if you actively use the AI assistant are your input and a portion of the currently visible page content (limited, not your entire database) transmitted to the configured language model in order to generate the response. Without active use, no transmission takes place.

Provider (Bring Your Own Key): the language model is provided by a provider that you configure yourself and for which you store your own access key (BYOK). The key is stored encrypted and is not logged. For this third-party service chosen by you, you are the contracting party of the respective provider; its terms and privacy notices apply additionally in this respect. If you do not use your own access but an access to a provider that we provide, we transmit your input and the page excerpt to this provider on your behalf; for a provider based in the USA, the following paragraph then applies as well.

Transfer to a third country: if you choose a provider outside the EU (e.g. Anthropic, based in the USA), a transfer to a third country takes place in this respect. Alternatively, you can integrate an EU provider via a compatible endpoint. Our platform's own AI functions, by contrast, run exclusively on servers in the EU, and they are two distinct things:

  • Receipt recognition: An uploaded receipt is transmitted to Scaleway SAS, 8 rue de la Ville-l’Évêque, 75008 Paris, France, so that a language model can read out supplier, date, amounts, tax rates and a suggested account assignment. What is transmitted is the receipt as an image or, if the file contains text, that text. Scaleway acts for us as a processor pursuant to Art. 28 GDPR; processing takes place in a data center in Paris, no transfer to a third country occurs. According to Scaleway, it does not store the content and does not use it for training; only if a request causes a technical error there may Scaleway keep it for up to two weeks for troubleshooting. The result is a suggestion and creates no booking; only your approval does.
  • Speech-to-text (“dictation”): your recording goes via our management platform in Falkenstein to Scaleway (address as above), where a language model in a data center in Paris turns it into text; storage and troubleshooting are handled as for receipt recognition. We do not store the recording; the recognized text appears in your input field. If we switch off the outsourced recognition, a speech recognition on our management platform in Falkenstein produces the text, and the recording does not leave Germany.

No advice: outputs of the AI assistant are non-binding recommendations and information, not tax or legal advice; details are governed by the AGB.
Legal basis: Art. 6 Abs. 1 lit. b DSGVO (use of the feature you have activated); with respect to the provider relationship you have chosen, your own legal basis as the controller.

7c. ZepDesk App for Android and iOS

The ZepDesk app gives you access to your ZepDesk instance from your phone. For the business data you view, enter and send in the app (such as receipts, invoices, customers and files in the document storage), sections 2.2, 4, 7 and 7b apply as in the web interface. This section describes what the app processes beyond that. The app shows no advertising, does not track you across other apps or websites, does not read an advertising ID, sets no cookies and receives no push notifications. It includes no third-party analytics or crash reporting services; which technical data Google receives from the document scanner on Android is described in 7c.3. Subscriptions that you purchase in the app for iOS via the App Store are described in section 5c.

7c.1 Sign-in and connections

On iOS, you can create a new ZepDesk account directly in the app. For this, the app asks for your first and last name, your email address, a password (at least 10 characters), the name and legal form of your company, the desired address of your instance and your postal address, together with your consent to the terms and conditions, the privacy policy and the data processing agreement and your confirmation that you act as an entrepreneur. You confirm your email address with a six-digit code that we send you by email and that is valid for 15 minutes. We store this information as for registration on the website (section 2.2), together with the version and time of your consents. If you do not confirm your email address, we delete the registration after 24 hours or as soon as you register again with the same email address. If you do not purchase a subscription after confirming, we delete the account after 30 days, unless a purchase at Apple is still being processed.

You sign in to our platform app.zepdesk.de with your email address and password, and where required with a confirmation code. The app then receives an access token and a refresh token and keeps both in the protected storage of the device (Keychain on iOS, Keystore on Android). They cannot be transferred to another device; on Android they are excluded from the device backup. For your company the app additionally obtains short-lived access credentials that are held in memory only.

The app connects exclusively to app.zepdesk.de and to the address of your ZepDesk instance. Where applicable it loads your company logo through a time-limited link from our storage at Hetzner (section 4). All connections are encrypted (HTTPS); the published app does not allow unencrypted connections.

Legal basis: Art. 6 Abs. 1 lit. b DSGVO (performance of the contract).
Storage period: the refresh token is valid for at most 30 days. When you sign out, the app signs you out with us and deletes both tokens from the device. For sign-in records on our platform, section 2.2 applies.

7c.2 Device check against abusive access

So that only the genuine app on an unmodified device obtains access, the app identifies itself when you register, when you sign in, when you reset your password, when you request account deletion and when it requests access credentials: on Android via Google's Play Integrity API, on iOS via Apple's App Attest. For this the app passes only a one-time random number from our platform to the service (on iOS its hash) and forwards the service's response to us. No content from ZepDesk is sent to Google or Apple. According to Google, Google additionally processes information about the app (package name, version, signing certificate), its licensing status and information about the device, such as an attestation by Google Play services. On Android we have Google decrypt the result and verify it ourselves; on iOS we store the public part of the App Attest key in order to verify later checks. We log the result of each check without any information about your person.

Legal basis: Art. 6 Abs. 1 lit. f DSGVO (protecting your account and the platform against automated and abusive access). Access to your device is strictly necessary under § 25 Abs. 2 Nr. 2 TDDDG to provide the secured access you have requested.
Recipients: on Android Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland; on iOS Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland. Processing in the USA cannot be ruled out; for Google it is based on the European Commission's adequacy decision for the EU-US Data Privacy Framework, under which Google LLC is certified, and for Apple, according to Apple, on standard contractual clauses of the European Commission.
Storage period: the random number is valid for a single check and expires after five minutes. The public App Attest key is not assigned to any person and remains stored as long as the installation can use it. According to Google, Google deletes its data after a fixed retention period.

7c.3 Camera, scanner, photos and files

You capture receipts and documents with the operating system's document scanner: on iOS with Apple's VisionKit, on Android with the Google ML Kit document scanner from Google Play services. Edge detection and cropping take place on the device. If the scanner is not available, the app takes the photo directly. The app asks for camera permission before it uses the camera for the first time; it uses the camera only when you start a capture or the reading of a QR code. The app reads the QR code on a till receipt on the device and sends only the decoded text to your ZepDesk instance. You choose photos and files for the document storage in the system picker; the app receives only what you select there and does not ask for access to your photo library or your storage. Captures and files are sent to your ZepDesk instance only when you store them or send them as a receipt; sections 7 and 7b apply there.

Google ML Kit (Android only): the document scanner and the QR reader on Android are based on ML Kit. According to Google, the scanner processes the images on the device. ML Kit does, however, transmit technical usage data to Google, such as the device manufacturer, model and operating system, the app's package name and version, a per-installation identifier, performance metrics, and event and error codes. According to Google, it uses this data for diagnostics and usage analytics of ML Kit and does not pass it on to third parties. The recipient is Google (address as in 7c.2).

Legal basis: Art. 6 Abs. 1 lit. b DSGVO for capture, selection and transfer; access to the device's camera and storage is strictly necessary under § 25 Abs. 2 Nr. 2 TDDDG to carry out the capture you have started. For the use of ML Kit, Art. 6 Abs. 1 lit. f DSGVO (a reliable system scanner instead of the app accessing the camera itself).
Storage period: captures remain in the app's outbox until they are sent or discarded by you (7c.6). The app clears the caches of the scanner and of the picker as soon as it has taken over the capture or stored the file.

7c.4 Error reports

If an unexpected error occurs in the app, it sends an error report to our platform (app.zepdesk.de). The same applies to crashes recorded by the operating system (on Android the list of terminated processes, on iOS MetricKit); the app reads these at a later start. A report contains: the first line of the error message (at most 300 characters), a shortened extract of the affected program locations, the type of error, the app version, the operating system and its version, and the address of the ZepDesk instance currently open. It contains neither your name nor your email address nor an identifier of your account. Before sending, the app replaces email addresses, IBANs, long character strings and numbers with six or more digits with placeholders; for crashes recorded by the operating system only email addresses and IBANs, because long character strings there are program addresses. The app sends at most 20 reports per start. Reports it could not send are kept until the next start, at most 30 reports.

Legal basis: Art. 6 Abs. 1 lit. f DSGVO (error-free and secure operation of the app). Crashes recorded by the operating system are read under § 25 Abs. 2 Nr. 2 TDDDG, as this is strictly necessary to keep the app you use working.
Recipients: only us; the platform runs at Hetzner (section 4).
Storage period: 14 days in our platform's error log, then automatic deletion. On the device until the next successful transmission.

7c.5 Device key and biometrics

When you approve a tax return or tax filing to the tax office from the app, you confirm this with your device's biometrics, such as Face ID or your fingerprint. For this the app creates, once per company and user, a key in the security area of the device (Secure Enclave on iOS, Keystore on Android). The private part never leaves the device. The following are sent to your ZepDesk instance: the public key, on Android the Keystore attestation (certificate chain), the device name (on Android manufacturer and model, on iOS the device type such as "iPhone"), a random identifier of this installation and a signature for each approval. Your instance checks whether an Android key has been revoked using Google's public revocation list; no information about you is sent to Google in the process.

Your biometric characteristics are processed exclusively by the operating system. The app only receives the result, confirmed or not. The same applies to the app lock with Face ID or fingerprint, which you can switch on under "Mehr" (More).

Legal basis: Art. 6 Abs. 1 lit. b DSGVO (carrying out your approval) and Art. 6 Abs. 1 lit. f DSGVO (proof that the approval came from your device).
Storage period: device keys are not deleted but only revoked, so that approvals can be verified later. The proof of an approval (signature, key identifier, time, IP address and client identifier) is stored together with the transmission record and kept as long as that record.

7c.6 Data on the device, signing out and uninstalling

The protected storage of the device holds the tokens, your app lock choice, the identifiers of the device keys and the identifier of this installation. The app's directory holds: the outbox with receipts not yet sent (photos and details), unfinished invoices and quotes, the most recently loaded overview, your company's logo and colours, the areas you visited last, your settings (such as language and appearance) and error reports waiting to be sent. Other apps cannot access this data.

When you sign out, the app deletes the tokens, the cached overview, logo and colours, the areas visited last, unfinished invoices and quotes, and your app lock choice. Receipts in the outbox remain on the device until they are sent after your next sign-in or you discard them in the outbox; the device keys and your settings remain as well.

Device backup: if you have switched on the backup of your device (Google on Android, iCloud on iOS), it may contain content from the app's directory, such as receipts in the outbox. Your sign-in is excluded: on Android the backup does not include the protected storage, on iOS the tokens can only be used on this device.

Uninstalling: when you delete the app, the operating system removes the app's directory, and on Android also the keys in the Keystore. iOS may keep Keychain entries beyond an uninstallation. Please therefore sign out before deleting the app.

Legal basis: Art. 6 Abs. 1 lit. b DSGVO; storage on the device is strictly necessary under § 25 Abs. 2 Nr. 2 TDDDG to provide the functions you use.

7c.7 Sharing, links and obtaining the app

If you share a PDF or a file or choose "In anderer App öffnen" (open in another app), the app briefly places the file in a temporary directory, hands it to the system share sheet and then deletes it. You decide where the file goes. The app opens the legal texts, help and, on Android, the account deletion page in your browser; sections 2.1 and 3a apply there. On iOS, you request the deletion of your account directly in the app under "Mehr" (More); we send you a confirmation by email.

You obtain the app through Google Play or the App Store. Google and Apple respectively process data under their own responsibility, such as your store account and the time of the download. Their privacy notices apply. Section 5c applies to subscriptions that you purchase in the app via the App Store.

8. Storage Period

  • Account data: for the duration of the contract plus a 30-day grace period. Thereafter, complete deletion or anonymization, insofar as no statutory retention obligations preclude this.
  • Invoice data: 8 years pursuant to § 147 (3) AO, § 257 (4) HGB, § 14b UStG, from the end of the calendar year.
  • Server logs: without anonymization and without a fixed deletion period, see sections 2.1 and 7a.1.
  • Backups: daily, in the object storage in Falkenstein. They are kept until a deletion rule is set up; we will then state the period here.
  • Connections to third-party providers: see section 5b.6, for Amazon additionally 5b.4.
  • ZepDesk app: see section 7c.
  • App Store subscriptions: see section 5c.
  • Referral programme: see section 2.7.
  • Sales partner programme: see section 2.8.
  • ZepDesk Developers: see section 2.9.
  • Signing in with Google, Microsoft or Apple: see section 2.10.

9. Your Rights

You have the right, in relation to us:

  • to information (Art. 15 DSGVO) about the data stored concerning you
  • to rectification (Art. 16 DSGVO) of inaccurate or incomplete data
  • to erasure (Art. 17 DSGVO / "right to be forgotten")
  • to restriction of processing (Art. 18 DSGVO)
  • to data portability (Art. 20 DSGVO) in a common machine-readable format
  • to object to the processing (Art. 21 DSGVO)
  • to withdraw your consent (Art. 7 Abs. 3 DSGVO)

You can lodge complaints with the competent supervisory authority: Unabhängiges Landeszentrum für Datenschutz Schleswig-Holstein (ULD), Holstenstraße 98, 24103 Kiel.

To exercise your rights, contact us at datenschutz@zepdesk.de. You can export your data yourself at any time with the complete export under Administration → Company → Complete export; if you cancel, we also provide you with an export.

10. SSL/TLS Encryption

For security reasons, this page and the entire ZepDesk platform use end-to-end SSL/TLS encryption (Let's Encrypt, protocol TLS 1.2 / 1.3). You can recognize this by the "https://" and the padlock symbol in your browser bar.

11. Changes to This Privacy Policy

We reserve the right to adapt this statement so that it always complies with current legal requirements or in order to implement changes to our services in the privacy policy. The new privacy policy then applies to your renewed visit. The current version is always available online at /datenschutz.

The path of your data, documented.

Legal texts are not an end in themselves: every version is versioned, dated, and traceable. The process behind it in four steps.

STEP 1
Collection
STEP 2
Purpose limitation
STEP 3
Processing in the EU
STEP 4
Deletion after the retention period
PROCEDURE ................

The binding version is the one specified above with its effective date.