Privacy Policy
1. Privacy at a Glance
General Information
The following information provides a simple overview of what happens to your personal data when you visit our website. Personal data is any data that can be used to personally identify you. Detailed information on data protection can be found in our privacy policy below.
Data Collection
Who is responsible? Data processing is carried out by the website operator. Contact details can be found in the Legal Notice.
How do we collect your data? Partly through information you provide (e.g. via email or phone), partly automatically by our IT systems (technical data such as browser, operating system, time of access).
Your Rights
You have the right at any time to free information about the origin, recipient, and purpose of your data, as well as the right to rectification, deletion, or restriction of processing. You also have the right to lodge a complaint with the competent supervisory authority.
What do we use your data for?
The data is collected to ensure error-free provision of the website. No analysis of your user behavior takes place.
Analytics Tools and Third-Party Tools
This website does not use any analytics tools, tracking cookies, or third-party scripts. No statistical evaluation of your browsing behavior takes place.
2. General Information and Mandatory Disclosures
Data Protection
The operators of these pages take the protection of your personal data very seriously. We treat your personal data confidentially and in accordance with statutory data protection regulations and this privacy policy.
When you use this website, various personal data is collected. This privacy policy explains what data we collect and what we use it for. It also explains how and for what purpose this is done.
We would like to point out that data transmission over the Internet (e.g. when communicating by email) may have security gaps. Complete protection of data against access by third parties is not possible.
Responsible Party
ALTENBRAND Datentechnik GmbH
represented by Managing Director Frank Altenbrand
Am Gelicht 5, D-35279 Neustadt, Germany
+49 (0) 6692 202290
The responsible party is the natural or legal person who alone or jointly with others decides on the purposes and means of processing personal data (e.g. names, email addresses, etc.).
Revocation of Your Consent to Data Processing
Many data processing operations are only possible with your express consent. You can revoke consent you have already given at any time. An informal notification by email to us is sufficient. The legality of the data processing carried out until the revocation remains unaffected by the revocation.
Right to Object to Data Collection (Art. 21 GDPR)
Right to Object
If data processing is based on Art. 6(1)(e) or (f) GDPR, you have the right to object to the processing of your personal data at any time on grounds relating to your particular situation; this also applies to profiling based on these provisions.
If you object, we will no longer process your affected personal data unless we can demonstrate compelling legitimate grounds for the processing that override your interests, rights, and freedoms, or the processing serves to assert, exercise, or defend legal claims (objection pursuant to Art. 21(1) GDPR).
If your personal data is processed for the purpose of direct marketing, you have the right to object at any time to the processing of personal data concerning you for the purpose of such marketing; this also applies to profiling insofar as it is related to such direct marketing (objection pursuant to Art. 21(2) GDPR).
Right to Lodge a Complaint with the Supervisory Authority
In the event of violations of the GDPR, data subjects have the right to lodge a complaint with a supervisory authority, in particular in the Member State of their habitual residence, their place of work, or the place of the alleged infringement. The right to lodge a complaint is without prejudice to any other administrative or judicial remedy.
Right to Data Portability
You have the right to have data that we process automatically on the basis of your consent or in fulfillment of a contract handed over to you or to a third party in a common, machine-readable format. If you request the direct transfer of data to another controller, this will only be done to the extent technically feasible.
Information, Deletion, and Rectification
Within the framework of the applicable legal provisions, you have the right at any time to free information about your stored personal data, its origin and recipients, and the purpose of data processing, and, if applicable, a right to rectification or deletion of this data. For this purpose, as well as for further questions on the subject of personal data, you can contact us at any time at the address given in the Legal Notice.
Right to Restriction of Processing
You have the right to request the restriction of the processing of your personal data. The right exists in the following cases:
- If you dispute the accuracy of your data stored by us, we need time to verify. For the duration of the verification, you can request restriction.
- If the processing of your data was/is unlawful, you can request restriction of processing instead of deletion.
- If we no longer need your data, but you need it to exercise, defend, or assert legal claims, you can request restriction instead of deletion.
- If you have lodged an objection pursuant to Art. 21(1) GDPR, a balance must be struck between your interests and ours. As long as it has not yet been determined whose interests prevail, you can request restriction.
If you have restricted processing, these data may only be processed – apart from being stored – with your consent or for the assertion, exercise, or defense of legal claims or for the protection of the rights of another natural or legal person or for reasons of important public interest.
Objection to Advertising Emails
The use of contact data published as part of the legal notice obligation for the purpose of sending unsolicited advertising and information materials is hereby objected to. The operators of the pages expressly reserve the right to take legal action in the event of the unsolicited sending of advertising information, such as spam emails.
3. Data Collection on Our Website
Cookies and Local Storage
This website does not set any of its own HTTP cookies. In particular, no tracking cookies, analytics cookies, or marketing cookies are used.
To store your design preference (e.g. light or dark color scheme), the website uses your browser's localStorage. This is not an HTTP cookie but a client-side storage mechanism that remains exclusively on your device and is not transmitted to our servers. You can delete this data at any time via your browser settings.
It is possible that the hosting provider (Microsoft Azure Static Web Apps) may set technically necessary cookies as part of the technical infrastructure (e.g. for load balancing or security features). These cookies serve exclusively technical infrastructure purposes and do not contain personal data. The legal basis for this is Art. 6(1)(f) GDPR (legitimate interest in the technically error-free provision of the website).
A cookie consent banner is not required, as neither tracking nor marketing cookies are used.
Hosting
This website is hosted on Microsoft Azure Static Web Apps in the West Europe region (Netherlands). Microsoft acts as a data processor pursuant to Art. 28 GDPR. A corresponding data processing agreement is automatically included in our Azure contract via the Microsoft Product Terms.
If you open merchantcentral.de without "www", Cloudflare redirects you to this website. In doing so, Cloudflare processes your IP address and the request data, based on Art. 6(1)(f) GDPR (legitimate interest in a reachable and protected domain). For Cloudflare as a processor and the transfer to the USA, see section 5 d).
Server Log Files
The hosting provider (Microsoft Azure) automatically collects and stores information in so-called server log files, which your browser automatically transmits to us. These are:
- Browser type and browser version
- Operating system used
- Referrer URL
- Hostname of the accessing computer
- Time of the server request
- IP address
This data is not merged with other data sources.
The collection of this data is based on Art. 6(1)(f) GDPR. The website operator has a legitimate interest in the technically error-free presentation and optimization of its website – for this purpose, the server log files must be collected.
Storage duration: Server log files are automatically deleted by Microsoft Azure after 30 days.
Inquiry by Email, Phone, or Fax
If you contact us by email, phone, or fax, your inquiry including all resulting personal data (name, inquiry) will be stored and processed by us for the purpose of handling your request. We will not pass on this data without your consent.
The processing of this data is based on Art. 6(1)(b) GDPR, if your inquiry is related to the fulfillment of a contract or is necessary for the implementation of pre-contractual measures. In all other cases, the processing is based on your consent (Art. 6(1)(a) GDPR) and/or on our legitimate interests (Art. 6(1)(f) GDPR).
The data sent to us by you via contact inquiries will remain with us until you request deletion, revoke your consent to storage, or the purpose for data storage ceases to apply (e.g. after completion of your request). Mandatory statutory provisions – in particular statutory retention periods – remain unaffected.
4. Analytics Tools and Advertising
This website does not use any analytics tools, tracking cookies, or advertising services. No third-party scripts are embedded and no evaluation of your user behavior takes place.
Automated Decision-Making
No automated decision-making including profiling pursuant to Art. 22 GDPR takes place.
5. Data Processing in the merchantCENTRAL Software
The following information relates to the processing of personal data in connection with the use of our software merchantCENTRAL — an extension (app) for Microsoft Dynamics 365 Business Central. This data processing occurs independently of your visit to our website.
Responsible Party
The party responsible for the data processing described below is ALTENBRAND Datentechnik GmbH (see Section 2 of this privacy policy).
a) License Validation
Scope of Data Processing
When using merchantCENTRAL, an automatic license check is performed at regular intervals. The following data is transmitted to our license server:
- License key (transmitted in encrypted form)
- Microsoft Entra Tenant ID of your Business Central environment
- Name of the Business Central environment
- Environment type (Production or Sandbox)
Purpose of Processing
License validation serves to verify the authorization to use the software and to activate the licensed modules.
Legal Basis
Processing is carried out on the basis of Art. 6(1)(b) GDPR (performance of a contract). The license check is technically necessary to provide the contractually agreed software functions.
b) Heartbeat (Usage Signal)
Scope of Data Processing
merchantCENTRAL sends an automatic usage signal ("heartbeat") to our license server once per day. The following data is transmitted:
- License key (transmitted in encrypted form)
- Microsoft Entra Tenant ID
- Name of the Business Central environment
- Environment type (Production or Sandbox)
- Timestamp of the transmission
Purpose of Processing
The heartbeat serves to detect active installations, prevent license misuse, and provide usage statistics for license management.
Legal Basis
Processing is carried out on the basis of Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(f) GDPR (legitimate interest in ensuring proper license usage).
c) Demo Registration
Scope of Data Processing
When you register for the free demo mode of merchantCENTRAL, the following data is collected via a registration wizard within the software and transmitted to our license server:
- Company name
- Contact person name
- Email address
- Country
- Phone number (optional)
- Street, city, and postal code
- VAT registration number (optional)
- Website (optional)
- Microsoft Entra Tenant ID
- Name and type of the Business Central environment
- List of installed merchantCENTRAL modules
- Your GDPR consent (consent timestamp)
Purpose of Processing
The data is used to set up your demo access, to contact you regarding the demo usage, and to convert to a production license.
Legal Basis
Processing is carried out on the basis of Art. 6(1)(a) GDPR (consent). You actively grant your consent in the registration wizard. You may revoke your consent at any time with effect for the future by contacting us at info@altenbrand.de.
d) Data Recipients and Storage Location
All data collected in connection with licensing is stored on Microsoft Azure servers in the Germany West Central region (Frankfurt, Germany). Microsoft acts as a data processor pursuant to Art. 28 GDPR. A corresponding data processing agreement (DPA) is automatically included in our Azure contract via the Microsoft Product Terms.
The data is stored in Azure Table Storage and processed via a secured API (Azure Functions with API key authentication). All transmissions are exclusively via encrypted HTTPS connections.
The license server sits behind Cloudflare (Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA). Cloudflare receives every request, decrypts it for inspection (TLS termination) and forwards it encrypted to Azure. This detects and blocks attacks and misuse (web application firewall, rate limiting). In doing so, Cloudflare processes IP addresses and the content of the requests – for the demo registration, this includes the company and contact data submitted. The same applies to the payment notifications that PayPal and Stripe send to the license server (sections h) and i)). The legal basis is Art. 6(1)(f) GDPR (legitimate interest in operating our services securely).
Cloudflare processes this data as a processor pursuant to Art. 28 GDPR; the data processing agreement (Cloudflare Customer DPA) forms part of our contract with Cloudflare. The transfer to the USA is based on the European Commission's adequacy decision for the EU-US Data Privacy Framework (Art. 45 GDPR), under which Cloudflare is certified. Should it cease to apply, the European Commission's Standard Contractual Clauses (Art. 46(2)(c) GDPR), already agreed in the data processing agreement, apply.
Cloudflare additionally uses data about attacks and threats on its network – such as scores for suspicious IP addresses – for its own purposes, to operate and improve its security services. Cloudflare is itself the controller for this processing. Further information: https://www.cloudflare.com/privacypolicy/
For payment processing via Stripe and for automated email sending, additional service providers are used; details can be found in sections i) and j).
e) Storage Duration
| Data Category | Storage Duration |
|---|---|
| License validation data | For the duration of the license agreement, up to 12 months after contract termination |
| Heartbeat data | 12 months, then automatically deleted |
| Demo registration data | 6 months after expiration of the demo period, unless a production license is acquired |
| Activity log (BC-internal) | 180 days, then automatically deleted |
| Contact and payment data in BC | Up to 12 months after contract termination; anonymization available on request at any time |
| Telemetry of the apps (section n)) | 90 days, then automatic deletion |
After the storage period expires, data is automatically deleted unless statutory retention obligations apply.
f) Your Rights
You are entitled to the rights described in Section 2 of this privacy policy (information, rectification, deletion, restriction of processing, data portability, objection). Please contact info@altenbrand.de for this purpose.
To exercise your right to erasure (Art. 17 GDPR) regarding contact data stored in our license management system (name, email address, phone, address), an informal request by email is sufficient. The anonymization of personal fields is carried out technically in our license management software; license history and billing records are retained for statutory reasons.
g) Necessity of Data Provision
The provision of the data described in a) and b) is technically required for the use of merchantCENTRAL. Without license validation, the software functions cannot be activated.
The provision of the data described in c) is voluntary. However, without demo registration, you cannot use the free demo mode.
h) Payment Processing via PayPal
Scope of Data Processing
If you choose the PayPal subscription payment method, the following data is processed as part of payment processing:
- Email address of your PayPal account
- PayPal subscription ID
- PayPal transaction IDs (per payment)
- Payment amount and currency
- Payment status and date
- Next billing date
Data Recipient
Payment processing is carried out by:
PayPal (Europe) S.à r.l. et Cie, S.C.A. 22-24 Boulevard Royal, L-2449 Luxembourg
PayPal processes your payment data as an independent controller in accordance with its own PayPal Privacy Statement.
Purpose of Processing
The processing serves to execute recurring subscription payments for your licensed merchantCENTRAL modules.
Legal Basis
Processing is carried out on the basis of Art. 6(1)(b) GDPR (performance of a contract). Payment processing is an integral part of the license agreement.
Storage Duration
Payment data is retained for the duration of the subscription and 10 years after contract termination (§ 147 AO, § 257 HGB — statutory retention obligations under German tax law).
Voluntariness
The use of PayPal is voluntary. As an alternative, payment by SEPA direct debit or Stripe is available. The choice of payment method has no effect on the price or the functionality of the software.
i) Payment Processing via Stripe
Scope of Data Processing
If you choose the Stripe subscription payment method, the following data is processed as part of payment processing:
- Stripe subscription ID
- Stripe transaction IDs (per payment)
- Payment amount and currency
- Payment status and date
- Next billing date
Data Recipient
Payment processing is carried out by:
Stripe Payments Europe Ltd. 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland
Stripe processes your payment data as an independent controller in accordance with its own Stripe Privacy Policy.
Purpose of Processing
The processing serves to execute recurring subscription payments for your licensed merchantCENTRAL modules.
Legal Basis
Processing is carried out on the basis of Art. 6(1)(b) GDPR (performance of a contract).
Storage Duration
Payment data is retained for the duration of the subscription and 10 years after contract termination (§ 147 AO, § 257 HGB — statutory retention obligations under German tax law).
Voluntariness
The use of Stripe is voluntary. As an alternative, payment by SEPA direct debit or PayPal is available.
j) Automated Email Notifications
Scope of Data Processing
merchantCENTRAL automatically sends email notifications in the following situations:
- Demo expiry warning: An email is sent approximately 7 days before a demo access expires to the email address provided during demo registration.
- Payment reminder: In the event of outstanding payments, a reminder is sent to the stored email address.
The following data is processed: contact person name, email address, Tenant ID (pseudonymized), and affected module information.
Sending Infrastructure
Emails are sent via Microsoft Azure Communication Services (ACS) in the Germany West Central region (Frankfurt, Germany). Microsoft acts as a data processor pursuant to Art. 28 GDPR. A corresponding data processing agreement is automatically included in our Azure contract via the Microsoft Product Terms.
Purpose of Processing
The notifications serve to timely inform about expiring demo accesses and to provide reminders of outstanding payments.
Legal Basis
Processing is carried out on the basis of Art. 6(1)(b) GDPR (performance of a contract) for demo expiry warnings, and Art. 6(1)(f) GDPR (legitimate interest) for payment reminders.
k) Activity Log (Internal BC Log)
Scope of Data Processing
merchantCENTRAL maintains an internal activity log within your Business Central database. The following data is stored therein:
- Microsoft Entra Tenant ID (pseudonymized)
- Customer name (company name)
- Module code and type of activity (e.g. demo start, license activation, suspension)
- Timestamp and executing user
Purpose of Processing
The log serves the internal traceability of license actions and the operational security of license management.
Legal Basis
Processing is carried out on the basis of Art. 6(1)(f) GDPR (legitimate interest in the traceability of license operations and troubleshooting).
Storage Duration
Activity log entries are automatically deleted after 180 days.
l) Token Service for the Amazon Connector
Scope of Data Processing
The merchantCENTRAL Amazon connector signs in to the Amazon Selling Partner API through the ALTENBRAND application. For this we operate a token service (mca-token.merchantcentral.de). It holds the credentials of this application and the refresh token you grant when connecting your Amazon seller account, and issues short-lived access tokens from it to your Business Central environment. The following data is processed:
- Refresh token of your Amazon seller account
- Microsoft Entra Tenant ID of your Business Central environment
- Account code of the Amazon account in merchantCENTRAL and your Amazon seller ID
- Status and times of the connection (setup, consent at Amazon, last issue of an access token)
- An access log per call: time, operation, outcome and IP address of the caller
When connecting, you sign in with your Microsoft account. The token service takes only the tenant ID from this sign-in; name and email address are not stored.
The token service does not process Amazon business data such as orders, items, buyer or shipping data. Such data is exchanged exclusively and directly between your Business Central environment and Amazon. The service keeps access tokens only briefly in memory; token and key values appear in no log.
Purpose of Processing
The token service connects your Amazon seller account to Business Central without handing the ALTENBRAND application credentials to customers. The access log protects the service against misuse and serves as evidence towards Amazon, whose data protection requirements for providers of Selling Partner applications call for such a log.
Legal Basis
Processing is based on Art. 6(1)(b) GDPR (performance of contract – provision of the Amazon connector). The access log is based on Art. 6(1)(f) GDPR (legitimate interest in the security of the service and in providing evidence towards Amazon).
Data Recipients and Storage Location
The token service runs on Microsoft Azure in the Germany West Central region (Frankfurt, Germany). The refresh token and the application credentials are stored encrypted in Azure Key Vault, connection data and the access log in Azure Table Storage, operational data in Azure Application Insights. Microsoft acts as a processor pursuant to Art. 28 GDPR (see section d)).
To issue an access token, the service sends the refresh token to Login with Amazon, Amazon's sign-in service. Transmission takes place exclusively via encrypted HTTPS connections.
The token service also sits behind Cloudflare. Cloudflare processes IP addresses and the content of requests and responses in order to block attacks and misuse. For Cloudflare's role, the legal basis and the transfer to the USA, see section d).
Storage Period
| Data category | Storage period |
|---|---|
| Refresh token | Until you disconnect in merchantCENTRAL. It is then deleted permanently at once and cannot be recovered. |
| Connection data (tenant ID, account code, seller ID, times) | For the duration of use. After disconnecting, the connection remains recorded as suspended so that a new connection can be matched; we delete it on request. |
| IP address in the access log | 30 days, then automatically anonymized |
| Access log and operational data | 12 months, then automatically deleted |
You can also revoke the authorization you granted the application at Amazon at any time in Amazon Seller Central.
m) Connectors and the Data of Your Business Transactions
Who Is Responsible
The merchantCENTRAL connectors connect your Business Central company with marketplaces (for example Amazon, eBay, Otto, Kaufland, Conrad, bol.com or Cdiscount), shop systems (for example Shopware or Shopify), carriers (for example DHL, DPD or Hermes) and suppliers. They call the interface of the respective provider directly from your Business Central environment and store the retrieved data only there (exception: Ariba connector, section o)).
For the buyer, customer and recipient data that reaches your company this way or is transmitted from it, you as the merchant are the controller within the meaning of Art. 4(7) GDPR. Unlike stated at the beginning of this section 5, ALTENBRAND Datentechnik GmbH is not the controller for this processing: we make the software, operate no server of our own for these data flows – except the Ariba gateway for the Ariba connector (section o)) – and have no access to your company or the data stored in it. Your Business Central environment is operated by Microsoft under your own contract with Microsoft.
If we are given access to your environment at your request, for example in a support case, we process this data only on your instructions as a processor pursuant to Art. 28 GDPR; we conclude a separate agreement with you for this.
Our own services – the license server (sections a) to c)) and the token service for the Amazon connector (section l)) – do not process buyer, customer or recipient data. Nor does the telemetry (section n)) contain it. The Ariba gateway processes such data on your behalf; see section o) for details.
Which Data Is Processed
Which data a connector reads or transmits is determined by the provider's interface. Typical are:
- Marketplace and shop connectors: from orders, name and, where applicable, company, shipping and billing address, email address, phone number and buyer ID at the provider, the items bought, prices and the status of each line; depending on the marketplace also returns with reason and status, messages to and from the marketplace's customer service, and shipping labels
- Shipping connectors: name and address of the recipient and, where the carrier uses them for delivery notifications, email address and phone number; the tracking number and label come back
- Supplier connectors: for drop shipments, your customer's shipping address, which goes to the supplier
- Technical logs of interface calls, if you switch them on: the content of requests and responses, which can contain such data
From the order data, merchantCENTRAL creates sales orders, with a collective customer or one customer per buyer, depending on your setting.
Purpose of Processing
The data serves to handle the contracts with your customers: shipping, invoicing, cancellation, refund, return, customer service and ordering from the supplier.
Legal Basis
The legal basis is determined by you as the controller; as a rule, Art. 6(1)(b) GDPR (performance of the contract with your customer) and, for posted documents, Art. 6(1)(c) GDPR (statutory retention obligations) apply.
Storage Period and Automatic Anonymization
merchantCENTRAL runs a data protection task every night. It anonymizes the buyer data of marketplace and shop orders after the periods you set in the hub's data protection settings (each 1 to 3,650 days):
| Data | Period counted from | Default |
|---|---|---|
| Buyer data of finished orders (shipped, invoiced or cancelled) | Order date | 30 days |
| Buyer data of unfinished orders | Order date | 90 days |
| Kaufland: buyer data of returns and tickets | Last change at Kaufland | as for orders |
| Recipient data on shipping labels | Delivery | 30 days |
| Kaufland: technical log of interface calls | Call | 30 days at most, earlier if the order period is shorter; then deleted |
Name, addresses, email address, phone number, buyer ID, message texts, label PDFs and error texts that can echo interface content are anonymized. Numbers, dates, amounts, statuses, reasons and country codes, which you need as business data, are kept.
The anonymization does not change posted documents in Business Central, such as invoices and credit memos; they are subject to the statutory retention periods. If merchantCENTRAL creates one customer per buyer, you anonymize that customer's master data yourself in the hub's data protection area; the period set there (default 30 days after the last order) shows when this becomes possible.
Your Obligations as Controller
You inform your customers about the processing in your own privacy policy, answer requests from data subjects and check whether the default periods fit your obligations and the requirements of the respective provider.
n) Telemetry of the Business Central Apps
Scope of Data Processing
The merchantCENTRAL hub and most of its modules are set up so that Business Central sends technical operating data about these apps to an Azure Application Insights resource of ALTENBRAND Datentechnik GmbH (setting applicationInsightsConnectionString in the app manifest). Microsoft provides this feature for all Business Central apps; the data is collected by Business Central itself. The following is transmitted:
- Platform telemetry that Business Central generates for operations in our apps: errors and permission errors shown, with the program object concerned and the call stack; start, end and failure of scheduled tasks; outgoing interface calls with target address (base address only, without path and parameters), method, status code and duration; long-running operations; and installation and update of the apps
- Own events of individual apps, for example on license validation or on the protection of stored credentials. We send them exclusively with the data classification "system metadata"; Business Central technically does not forward events with any other classification to Application Insights.
Each event carries the Microsoft Entra tenant ID, name and type of the Business Central environment, the name of the company, name and version of the app and a pseudonymous telemetry ID of the user, which can only be matched to a user within your environment. Business Central transmits the text of an error message only if it is marked as system metadata. Buyer, customer and recipient data, item and document data and credentials are not part of the telemetry.
Independently of this, you can set up an Application Insights resource of your own for your environment in the Business Central admin center. Only you receive that telemetry.
Purpose of Processing
The telemetry serves to detect and fix errors, outages and performance problems in our apps before they affect operations, to detect misuse of stored credentials, and to follow up on support requests.
Legal Basis
Processing is based on Art. 6(1)(f) GDPR (legitimate interest in stable, secure and error-free operation of the software).
Data Recipients and Storage Location
The Application Insights resource runs on Microsoft Azure in the Germany West Central region (Frankfurt, Germany). Microsoft acts as a processor pursuant to Art. 28 GDPR (see section d)).
Storage Period
Telemetry data is automatically deleted after 90 days.
o) Ariba Gateway for the Ariba Connector
Who Is Responsible
SAP Business Network exchanges documents with suppliers via cXML and calls an internet address of the supplier for this. The Ariba connector provides this address through the Ariba gateway, which we operate (ariba.merchantcentral.de). Unlike the other connectors (section m)), the documents of your business transactions with SAP Business Network therefore pass through a service of ALTENBRAND Datentechnik GmbH.
For the personal data in these documents, you as the supplier remain the controller; unlike stated at the beginning of this section 5, ALTENBRAND Datentechnik GmbH is not the controller for it. We process it exclusively on your behalf and on your instructions as a processor pursuant to Art. 28 GDPR. This is based on the data processing agreement for the Ariba gateway, which we conclude with you before the first registration at the Ariba gateway. For the registration and operational data we need to run the gateway securely, we are the controller ourselves.
Which Data Is Processed
On your behalf:
- Purchase orders from your buyers (OrderRequest): shipping and billing address, names of recipients and contact persons, email addresses and phone numbers, the ordered items, quantities and prices, as well as comments and additional fields that may contain the name and email address of the requester
- Status updates from your buyers on invoices and credit memos (status, comment, where applicable the amount paid and due date) as well as the review status of your catalogs
- Documents that Business Central sends to your buyers: order confirmations, ship notices with carrier and tracking numbers, invoices and credit memos, optionally with the e-invoice file, and catalogs, where applicable with the email address for status notifications. The gateway forwards them to SAP Business Network and does not store their content.
As a controller in our own right:
- Registration: Microsoft Entra tenant ID of your Business Central environment, the ID (ANID) of your supplier account on SAP Business Network, test or production account, status (active or suspended) and times (registration, last change of the shared secret); on acceptance of the data processing agreement in the setup wizard, the current data protection notification email and the time of its last change; the shared secret of your supplier account; of the service key Business Central signs in with, only a hash value
- Onboarding code: of the code itself only a hash value, plus tenant ID, time of issue, expiry and use, and an internal note by ALTENBRAND on issuing the code
- Test registration without an onboarding code (for demos, 30 days, at most 100 documents per day): expiry date and daily limit
- Proof of acceptance of the data processing agreement (only for the test registration without an onboarding code): for each acceptance, including a renewal, the version and time, the company name from your Business Central company, tenant ID, identifier (ANID), the user name of the person who accepted and the data protection notification email stated
- Operational logs: time, operation and outcome of each call with document numbers and technical identifiers; for access to storage and Key Vault, also caller, IP address and object name. The logs contain no document data such as addresses or names, and no secrets.
Purpose of Processing
The gateway receives the cXML documents from SAP Business Network, holds them for retrieval by your Business Central environment and sends the documents from Business Central to SAP Business Network. Registration and operational logs serve to assign requests to your company, to protect against misuse and to troubleshoot. The proof of acceptance documents that, and with whom, the data processing agreement was concluded. We send the notifications under the data processing agreement (§ 7 and § 9) to the data protection notification email.
Legal Basis
For the document data, you as the controller determine the legal basis; typically this is Art. 6(1)(b) GDPR (performance of the contract with your buyer). We process it only within the scope of the data processing agreement. We process the registration data on the basis of Art. 6(1)(b) GDPR (performance of contract – provision of the Ariba connector) and the operational logs on the basis of Art. 6(1)(f) GDPR (legitimate interest in secure and error-free operation). We process the proof of acceptance on the basis of Art. 6(1)(f) GDPR (legitimate interest in proving that the data processing agreement was concluded and in establishing, exercising or defending legal claims).
Data Recipients and Storage Location
The gateway runs on Microsoft Azure in the Germany West Central region (Frankfurt, Germany). Shared secrets are stored in Azure Key Vault, documents and registrations in Azure Storage, operational logs in Azure Application Insights. Microsoft acts as our sub-processor for the document data and as our processor for the other data (see section d)). All transfers are encrypted via HTTPS. For the gateway's address we use Cloudflare for name resolution (DNS) only; request content does not pass through Cloudflare.
The recipient of the documents from Business Central is SAP Business Network, which you use under your own contract with SAP. The gateway sends the shared secret only to SAP Ariba addresses.
Storage Period
| Data category | Storage period |
|---|---|
| Content of purchase orders and status updates | 7 days after your Business Central environment has retrieved it; if not retrieved, 180 days at the latest; when the contract ends, within 30 days |
| Receipt record without personal data (identifier, times, document number) | 90 days after receipt; for documents never retrieved, 180 days after receipt; when the contract ends, within 30 days |
| Documents from Business Central | not stored |
| Registration, onboarding code and shared secret | for the duration of use; deleted at your request or within 30 days after the contract ends. Azure Key Vault keeps deleted secrets for another 90 days in a "deleted" state; they can no longer be retrieved. |
| Test registration without an onboarding code | suspended after 30 days and deleted with all documents 27 days after the suspension, unless it becomes a regular registration |
| Proof of acceptance of the data processing agreement | 4 years after the end of use of the Ariba gateway (deletion of your last registration), also beyond the end of the contract (Art. 17(3)(e) GDPR) |
| Operational logs | 12 months, then automatically deleted |
Your Obligations as Controller
You inform your buyers and their staff about the processing in your own privacy policy and answer requests from data subjects. Where needed, we support you within the scope of the data processing agreement.
© 2026 ALTENBRAND Datentechnik GmbH. All rights reserved.