Privacy Policy

1. Controller

Contiva GmbH, Yokohamastr. 2, 20457 Hamburg, Germany. Email: [email protected]. Further details in the Imprint.

2. Principle: privacy by design

CPI Transporter is built so that your SAP credentials stay with you. In the default mode they are stored exclusively in your own browser and are never written to our database.

One technical qualification, stated plainly: your browser cannot address an SAP CPI tenant directly, because the tenant does not send CORS headers. Every call therefore passes through our server. Your credentials travel with the individual request, are used to authenticate against your tenant, and are discarded when the request ends. Artifact contents are held in memory for the duration of a transport only.

3. Local storage in your browser

3.1 What is stored

• System vault (IndexedDB): the CPI systems you configure — host, user name, password or client secret, token URL, group and stage. Encrypted with AES-256-GCM. The key is a non-extractable CryptoKey generated in your browser; it cannot be read out by JavaScript, including ours.
• Interface preferences (localStorage): selected colour theme and — if you were shown a consent banner — your consent decision.
• Session cookie: only if you actively sign in for the optional account mode. Signed, HTTP-only, SameSite.

3.2 Legal basis

Storage of the vault and of interface preferences is necessary to provide the service you requested (Art. 6(1)(b) GDPR, § 25(2) no. 2 TTDSG). Optional analytics is based on your consent (Art. 6(1)(a) GDPR, § 25(1) TTDSG) and is never active without it.

3.3 Retention and control

Locally stored data remains until you delete it. You can remove individual systems in the systems management or clear all site data in your browser settings; nothing of it exists on our side that would need to be deleted.

4. Data processed on our servers

4.1 Server log files

Our hosting provider processes IP address, date and time, requested resource, HTTP status, referrer and user agent. This is necessary to operate and secure the service (Art. 6(1)(f) GDPR). Logs are deleted after seven days at the latest.

4.2 System credentials

In the default local mode we do not store your SAP system credentials at all. If you explicitly opt into the account mode, host, user name and secret are stored in a PostgreSQL database in Germany, encrypted with AES-256-GCM using a server-side key (Art. 6(1)(b) GDPR). You can switch back and delete them at any time. One exception applies in both modes — see 4.6 on parameter profiles.

4.6 Parameter profiles, API tokens and approvals

If you save the externalized parameters of an integration flow as a profile, we store the values you entered — encrypted with AES-256-GCM using a server-side key — together with the target host and the artifact ID (Art. 6(1)(b) GDPR). These values can themselves contain access data for third systems (endpoints, user names, passwords, API keys). Profiles are only created when you explicitly ask for it, never automatically during a transport, and this applies in both storage modes including the default local one. We further store, where you use the respective function: a SHA-256 hash of each API token together with its name and last use (never the token itself); approval requests for protected target systems including the artifact and package identifiers of the plan, the requester and the email address of whoever decided, kept as an audit record; your notification preferences; and, per recorded run, the artifact versions that existed in the target beforehand, so that a run can be rolled back. If you mark a system as shared, everyone holding a seat in your subscription can see it and transport with it — the stored secret itself is never disclosed to them. Deleting your account removes all of this.

4.3 Account and billing data

If you create an account, we process your email address for authentication. For a Team subscription we additionally process subscription status, the number of licenses, the email addresses you assign seats to, and the customer identifier provided by Paddle. If you run transports while signed in, we store your transport history (source and target host, artifact metadata and the transport log) until you delete it — individual entries or your whole account.

4.4 Support and feedback

If you use the feedback form, we process the name, email address and message you provide in order to answer your enquiry (Art. 6(1)(b) and (f) GDPR). The message is deleted once it is no longer needed and no retention obligation applies.

4.5 Fair-use metering

To enforce the monthly transport allowance we store a SHA-256 fingerprint of the target system’s host name together with a monthly counter (Art. 6(1)(f) GDPR). The fingerprint cannot be reversed into the host name and, for the free allowance, is not linked to any person; for licensed users the counter is associated with the subscription.

5. External services

5.1 Paddle

The Team plan is sold by Paddle as merchant of record (Paddle.com Market Ltd.). Paddle is the seller of the subscription, issues the invoice and remits any applicable VAT. It processes the payment and billing data you enter as an independent controller, not as a processor on our behalf. We receive only the subscription status, the number of licences and a customer identifier — never complete payment card data.

Because Paddle is the seller, it is legally required to retain invoice data for the statutory periods. If you delete your account here, your data is removed from our database; data held by Paddle is not affected by that deletion. Requests regarding that data must be addressed to Paddle.

5.2 Hosting

The service is operated in a Kubernetes cluster on infrastructure of Hetzner Online GmbH in Germany. A data processing agreement pursuant to Art. 28 GDPR is in place with the provider.

5.3 Analytics — only with consent

We use no analytics, advertising or tracking services unless you explicitly consent. No tag manager, no advertising pixel and no third-party script is loaded before consent. If you consent, anonymous usage statistics are collected via Google Tag Manager and Google Analytics with Google Consent Mode; you can withdraw your consent at any time by clearing this site’s data in your browser.

The previous version of this site performed a GeoIP lookup on every request and loaded a LinkedIn pixel without consent. Both have been removed.

6. Your rights

You have the right to access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21). Consent can be withdrawn at any time with effect for the future. You also have the right to lodge a complaint with a supervisory authority, for example the Hamburg Commissioner for Data Protection and Freedom of Information.

7. Data security

All connections use TLS 1.2 or higher. Credentials are encrypted with AES-256-GCM both in the browser vault and — in account mode — at rest on the server. Encryption keys are provided exclusively through the runtime environment and are not part of the source code.

8. Changes to this Privacy Policy

We adapt this policy when the service or the legal situation changes. The current version always applies and is available on this page.

9. Contact

For any question regarding data protection, please write to [email protected].