20 % off all paid plans with code

Privacy Policy

Last updated: November 9, 2026

This is a translation. Only the German version is legally binding.

This privacy policy applies to the website everydata.io, the customer portal (dashboard) and the application programming interface (API) at api.everydata.io. The German-language version is binding.

1. Data protection at a glance

General information

The following information provides an overview of what happens to your personal data when you visit this website, create an account or use our API. Personal data is any data with which you can be personally identified. Detailed information can be found in the following sections.

Who is responsible for data collection?

The operator of this website is responsible. You will find the contact details in the section "Information on the controller".

How do we collect your data?

On the one hand, you provide data to us yourself, for example your e-mail address when registering or company and payment data when taking out a plan. On the other hand, our IT systems automatically collect technical data when you visit the website and with every API call, for example IP address, time, requested address and response status.

What do we use your data for?

To provide the website without errors, manage your account, authenticate API calls, enforce quotas and rate limits, bill services, prevent misuse and inform you about the status of your account. To improve the website we use cookieless, anonymised audience measurement (Vercel Web Analytics, section 4). We do not engage in cross-site tracking or advertising.

What rights do you have?

You have the right at any time to receive information free of charge about the origin, recipients and purpose of your stored data, to rectification, erasure and restriction of processing, to data portability and a right to object. You also have the right to lodge a complaint with the competent supervisory authority. Details can be found in section 3.

2. Hosting and infrastructure

We host the components of our service with the following providers. Data processing agreements (Art. 28 GDPR) are in place with all providers, ensuring that data is processed only on our instructions and in compliance with the GDPR.

Vercel (website, customer portal, DNS)

Provider: Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA

Vercel delivers the website and the customer portal via a worldwide content delivery network and manages the DNS records of our domain. When the website is accessed, Vercel processes the server log data described in section 4, in particular your IP address, as well as the audience measurement also described in section 4 (Vercel Web Analytics).

Legal basis: Art. 6 (1) (f) GDPR. We have a legitimate interest in fast, secure and reliable delivery of our website.

Transfer to third countries: Processing in the USA cannot be ruled out. Vercel is certified under the EU-US Data Privacy Framework (DPF); in addition, the transfer is based on the EU standard contractual clauses. Further information: vercel.com/legal/privacy-notice.

Fly.io (API and background services)

Provider: Fly.io, Inc., 321 N Clark St, Suite 2550, Chicago, IL 60654, USA

Our API and our background services (processing of dataset jobs, availability checks, cost control, deletion routines) run on Fly.io servers in the Frankfurt am Main region, Germany. Your API requests, including IP address, request parameters and API key, are processed there. Fly.io stores system logs for a short period for error analysis.

Legal basis: Art. 6 (1) (b) GDPR (provision of the contractually owed API service) and Art. 6 (1) (f) GDPR (legitimate interest in secure operation).

Transfer to third countries: Data processing takes place in Germany. Administrative access from the USA cannot be ruled out; it is based on the EU standard contractual clauses. Further information: fly.io/legal/privacy-policy.

Neon (database)

Provider: Neon, Inc., San Francisco, CA, USA

The database containing account, contract and usage data is operated by Neon. The data is stored on Amazon Web Services servers in the Frankfurt am Main region (eu-central-1), Germany.

Legal basis: Art. 6 (1) (b) and (f) GDPR.

Transfer to third countries: The data is stored in the EU. Administrative access from the USA is covered by the EU standard contractual clauses. Further information: databricks.com/legal/privacynotice.

Upstash (cache and counters)

Provider: Upstash, Inc., USA

We use the Redis service of Upstash for rate limits and abuse protection (for login links this includes your IP address), the cache of API responses and the stored results (section 5). The data is stored in the Frankfurt am Main region (eu-central-1), Germany, and is deleted automatically after short periods.

Legal basis: Art. 6 (1) (b) and (f) GDPR.

Transfer to third countries: The data is stored in the EU. Administrative access from the USA is covered by the EU standard contractual clauses.

3. General information and mandatory information

Data protection

We treat your personal data confidentially and in accordance with the statutory data protection regulations and this privacy policy. Please note that data transmission over the internet can have security gaps; complete protection against access by third parties is not possible.

Information on the controller

Julian Wagner
everydata.io
Im Gründchen 7a
61389 Schmitten
Deutschland
E-mail: support@everydata.io

The controller is the natural person who alone decides on the purposes and means of processing personal data.

Data protection officer

No data protection officer has been appointed, as the requirements of Art. 37 GDPR and § 38 BDSG (German Federal Data Protection Act) are not met. Please send data protection enquiries to support@everydata.io.

Storage period

Unless a more specific storage period is stated in this privacy policy, your data remains with us until the purpose of processing no longer applies. If you assert a legitimate request for erasure or withdraw your consent, your data will be deleted unless we have other legally permissible reasons for storing it, such as retention periods under tax or commercial law. We implement the periods stated in the following sections through automatic deletion routines that run daily.

Legal bases for processing

  • Art. 6 (1) (a) GDPR – consent. We currently do not obtain any consent because we do not use any services that require consent.
  • Art. 6 (1) (b) GDPR – performance of a contract or pre-contractual measures, in particular account, API access and billing.
  • Art. 6 (1) (c) GDPR – legal obligation, in particular retention obligations under tax and commercial law.
  • Art. 6 (1) (f) GDPR – legitimate interest, in particular in security, protection against misuse and stable operation.
  • § 25 (2) no. 2 TDDDG – storing information in, and accessing information on, your device insofar as this is strictly necessary for the service you have requested (see cookies).

Note on data transfers to third countries

We use service providers based in the USA. For companies certified under the EU-US Data Privacy Framework, the USA is considered a safe third country within the meaning of an adequacy decision of the EU Commission. For providers that are not certified, we base transfers on the EU standard contractual clauses pursuant to Art. 46 (2) (c) GDPR. Wherever possible, we choose data centres in the EU.

Recipients of personal data

We only pass on personal data if this is necessary to perform the contract, if we are legally obliged to do so or if we have a legitimate interest. We only use processors on the basis of a contract pursuant to Art. 28 GDPR. Sections 2, 6 and 7 contain an overview of all recipients. We do not sell personal data.

Withdrawal of your consent

Many data processing operations are only possible with your express consent. You can withdraw consent you have given at any time. The lawfulness of the processing carried out until the withdrawal remains unaffected.

Right to object to data collection in special cases (Art. 21 GDPR)

If data processing is based on Art. 6 (1) (e) or (f) GDPR, you have the right at any time to object to the processing of your personal data on grounds relating to your particular situation; this also applies to profiling based on these provisions. If you object, we will no longer process the personal data concerned unless we can demonstrate compelling legitimate grounds for the processing that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims. If your personal data is processed for direct marketing purposes, you have the right to object at any time to processing for this purpose. We currently do not carry out any direct marketing.

Right to lodge a complaint with the competent supervisory authority

In the event of breaches of the GDPR, you have the right to lodge a complaint with a supervisory authority, in particular in the member state of your habitual residence, your place of work or the place of the alleged breach. The authority responsible for us is: Der Hessische Beauftragte für Datenschutz und Informationsfreiheit (Hessian Commissioner for Data Protection and Freedom of Information), Gustav-Stresemann-Ring 1, 65189 Wiesbaden, datenschutz.hessen.de.

Your rights as a data subject

  • Access (Art. 15 GDPR): You can request information free of charge at any time about the data stored about you.
  • Rectification (Art. 16 GDPR): We correct inaccurate data without undue delay.
  • Erasure (Art. 17 GDPR): You can request the erasure of your data unless a retention obligation prevents it. We delete an account completely on request to support@everydata.io.
  • Restriction (Art. 18 GDPR): for example if you contest the accuracy of your data or the processing is unlawful.
  • Notification obligation (Art. 19 GDPR): We inform recipients of rectifications, erasures and restrictions.
  • Data portability (Art. 20 GDPR): We provide data that we process on the basis of a contract to you in a common, machine-readable format.
  • Objection (Art. 21 GDPR): see above.

SSL/TLS encryption

The website, portal and API are accessible exclusively via HTTPS. Unencrypted requests are redirected to HTTPS. We store API keys only as a cryptographic hash, not in plain text.

4. Data collection on this website

Server log files

When the website is accessed, our hosting provider Vercel automatically collects information that your browser transmits: IP address, date and time, page accessed, referrer URL, browser type and version, operating system and HTTP status code. This data is not merged with other data sources. The legal basis is Art. 6 (1) (f) GDPR; our legitimate interest lies in the technically error-free presentation and the security of the website. The logs are automatically deleted by the provider after a short time.

Audience measurement with Vercel Web Analytics

To understand which pages are used and to improve the website, we use Vercel Web Analytics from Vercel Inc. (provider: see section 2). When a page is accessed, the requested address (without URL parameters), the referrer URL, the country, browser, operating system and device type are recorded. No cookies are set and no information is stored on or read from your device. To distinguish visits, Vercel generates a hash from the request, which is discarded after 24 hours; IP addresses are not stored and recognition across days or websites is not possible. We only receive aggregated statistics, no data on individual persons. The legal basis is Art. 6 (1) (f) GDPR; our legitimate interest lies in designing and improving our service to meet demand. You can object to the processing at any time (section 3); technically, you can prevent the measurement by blocking /_vercel/insights/* in your browser or with a content blocker. Further information: vercel.com/docs/analytics/privacy-policy.

Cookies and browser storage

We use only technically necessary cookies and browser storage. There are no cookies for analytics, marketing or advertising purposes (the audience measurement above works without cookies) and no third-party cookies. We therefore do not need consent; the legal basis is § 25 (2) no. 2 TDDDG in conjunction with Art. 6 (1) (b) GDPR.

NameTypePurposeDuration
sessionCookie, HttpOnlyKeeps you logged in to the customer portal after login. Not readable by JavaScript.30 days or until logout
session_hintCookieContains only the value "1" so that the navigation shows "Dashboard" instead of "Log in". No personal data.30 days or until logout
themeLocal StorageStores your choice between light and dark design.until you delete it
API key in the dataset areaSession StorageHolds an API key you have entered for the current browser session so that you can create dataset jobs. Never transmitted to third parties.until the tab is closed

You can set your browser to reject cookies or delete them when it is closed. Without the session cookie, logging in to the customer portal is not possible.

Fonts

The fonts used on this website are embedded locally and served from our own server. No connection is made to servers of Google or other font providers.

Enquiries by e-mail

If you contact us by e-mail, we process your e-mail address, your name and the content of your enquiry in order to answer it. The legal basis is Art. 6 (1) (b) GDPR if your enquiry is related to a contract, otherwise Art. 6 (1) (f) GDPR. We delete the enquiry once it has been dealt with and no retention obligations prevent this.

E-mails to addresses at @everydata.io are received by the forwarding service ImprovMX Incorporated, 8 The Green STE D, Dover, Delaware 19901, USA, and forwarded to our mailbox. ImprovMX does not store the content of the e-mails, only technical delivery data (sender, recipient, time, delivery status) for seven days. The legal basis is Art. 6 (1) (f) GDPR; our legitimate interest lies in being reliably reachable under our own domain. The transfer to the USA is covered by the EU standard contractual clauses. Further information: improvmx.com/transparency/privacy-policy.

Contact form

Via the contact form we collect your name, your e-mail address, optionally your company, the chosen topic and your message. Mandatory fields are marked; without them we cannot answer your enquiry. The form is not stored in our database: your details are sent as an e-mail via Resend (section 7) to our support mailbox (forwarding as described above). There we answer the enquiry and delete it once it has been dealt with and no statutory retention periods prevent this, at the latest after twelve months; enquiries that lead to a contract or an invoice are kept for as long as commercial and tax law requires.

The legal basis is Art. 6 (1) (b) GDPR if your enquiry is related to a contract or pre-contractual measures, otherwise Art. 6 (1) (f) GDPR; our legitimate interest lies in answering the enquiries addressed to us. By ticking the box in the form you confirm that you have read this information. The processing is not based on consent, but you can object to it at any time (section 3).

Protection against misuse: We do not use a third-party captcha and do not set any cookies for this purpose. When the form is loaded, your browser receives a signed timestamp token that is checked on submission. A field invisible to humans detects automated input. We also limit the number of messages per IP address and per e-mail address; for this, hashed counters are kept in our cache for at most 24 hours. The legal basis is Art. 6 (1) (f) GDPR; our legitimate interest lies in protection against spam and misuse.

Cancellation and withdrawal via the website

If you cancel via our cancellation page, we process the details from the form (name, e-mail address, contract, customer or order number, type of cancellation, reason for cancellation, desired termination date), the time of receipt and the IP address in order to assign the cancellation to your contract, execute it, confirm receipt to you by e-mail and prevent misuse. If you are logged in or the e-mail address belongs to a customer account, we assign the cancellation to that account and cancel a paid subscription with Stripe at the end of the billing period. For a withdrawal via our withdrawal page we process name, e-mail address, contract, the time of receipt and the IP address; within the withdrawal period we end the subscription with Stripe immediately and initiate the refund of the payments there. We send the confirmation via our e-mail service provider Resend. The legal basis is Art. 6 (1) (b) GDPR (performance of the contract) and, for proof of receipt and protection against misuse, Art. 6 (1) (f) GDPR. We keep the cancellation and the withdrawal as evidence until the regular limitation period expires (three years from the end of the year in which it was received). If you cancel in the Stripe billing portal, section 7 applies.

5. Customer account and use of the API

Registration and login

For an account we only need your e-mail address. You confirm the registration via a single-use link that we send you by e-mail. The link is valid for 20 minutes; the associated record is deleted seven days after it expires. You can then set a password in the customer portal and log in with your e-mail address and password; alternatively, login via link remains possible. We do not store the password in plain text, only as a cryptographic hash (scrypt). When registering, you confirm that you are acting as an entrepreneur, because we only conclude contracts with entrepreneurs. Optionally, you can add your name and company. To protect against misuse, we limit the number of login links and login attempts per e-mail address and per IP address; for this purpose the IP address is kept in memory for only one hour. We log successful and failed login attempts as described in section 8. The legal basis is Art. 6 (1) (b) GDPR, and for protection against misuse Art. 6 (1) (f) GDPR. We store account data for the duration of the contractual relationship.

API keys

We generate API keys for API access. We store only a hash, the prefix, your label and the time of creation and revocation. You see the full key only once, when it is created.

Usage data and billing

For each API call we store: assignment to the API key, platform and endpoint, HTTP status, response time, time, whether the response came from the cache, quota units consumed, as well as the data volume transferred and the infrastructure costs estimated from it. We do not store the content of your requests or the data returned. The purpose is to enforce quota and rate limits, to display your usage statistics in the portal, to control costs and to investigate misuse. The legal basis is Art. 6 (1) (b) and (f) GDPR. We delete individual usage records after 13 months; monthly totals are kept for the duration of the contract.

API logs

When the API is called, our servers process your IP address, the requested address with parameters and the time in order to answer the request and analyse faults. These technical logs are kept briefly by the hosting provider Fly.io and are not merged with your account. The legal basis is Art. 6 (1) (f) GDPR.

Cache

If you explicitly request cached results, we store responses for the duration you choose, at most 24 hours. Expired entries are deleted automatically.

Independently of this, for detail requests on products, apps, videos, channels and real estate we keep the most recent successful response for at most one day, for apps, channels and real-estate details at most seven days. If the Target Platform is temporarily unavailable, we deliver this copy and mark it as cached (servedFromCache). We do not keep responses containing reviews, reviewer profiles or seller pages, nor search results and classified ads, for this purpose. The copies are held in the memory of our servers or in the cache at Upstash (section 2) and are discarded automatically when they expire. The legal basis is Art. 6 (1) (b) GDPR (reliable provision of the API service) and, insofar as the responses contain personal data of third parties, Art. 6 (1) (f) GDPR; our legitimate interest lies in a fail-safe service.

Dataset jobs

For bulk jobs we store your job parameters (for example product identifiers or search terms) and the result file. We delete result files 30 days after the job is completed; job data without a file is kept for your job history for as long as your account exists.

Notifications

After registration you receive a welcome e-mail with tips for getting started. We also inform you by e-mail when you have reached 80 % and 100 % of your monthly quota and when a dataset job has been completed. These notifications are part of the contractual service (Art. 6 (1) (b) GDPR). If your account has not made a successful API request two days after registration, we ask once by e-mail whether we can help you get started. For this we only check the stored usage data for whether a request has already succeeded, and we note the sending on your account so that the e-mail is not repeated. The legal basis is our legitimate interest in making it easier for you to get started (Art. 6 (1) (f) GDPR). The e-mail contains no advertising. You can object to this follow-up at any time, informally by e-mail to support@everydata.io. We do not send promotional newsletters.

Distribution via RapidAPI

You can also obtain our API via the RapidAPI marketplace (provider: R Software Inc., San Francisco, USA). In this case you conclude your contract via RapidAPI; RapidAPI is itself responsible for your account there and for payment processing. We only receive a pseudonymous user identifier from RapidAPI, which we process like the other usage data. Information: rapidapi.com/page/privacy.

Stored results

So that you can open answers again in the customer portal, we store the API responses of your last 20 successful requests that you make with your API keys directly, via the CSV variant or in the customer portal, for 7 days – without personal data of third parties: we do not store responses of endpoints that return data about people (for example reviews, comments, profiles and contact or provider details in listings), and we remove reviews and profile details from all other responses. The responses are stored compressed at Upstash in Frankfurt am Main (section 2); they are deleted automatically after 7 days. You can switch off this storage at any time in the account settings of the customer portal; results already stored are then deleted. The legal basis is Art. 6 (1) (b) GDPR.

6. Data retrieved via the API

At the request of our customers, our API retrieves publicly accessible information from third-party websites, such as product data from online shops, real-estate listings, financial figures or video information. This data may occasionally contain personal data, for example the display names of reviewers, names of merchants, names and comments on video platforms or details in real-estate listings.

  • Roles: The purpose and scope of each individual retrieval are determined by the respective customer. Insofar as personal data is processed and delivered to the customer, we act as the customer's processor; the customer is the controller and must ensure that it has a legal basis for its use. We provide a data processing agreement on request. For the price history described below, caching (section 5) and quality checks, we are ourselves the controller.
  • Price history: The data is retrieved in real time and delivered to the customer. For the price history we store only product-related details of products (title, brand, price, availability and the name of the seller or merchant). If the seller is a natural person, their seller name is personal data. The legal basis is Art. 6 (1) (f) GDPR; our legitimate interest lies in providing price histories of products. The details come from the publicly accessible product pages of the respective platform. We do not store reviews or details about reviewers. We delete product data and price histories after 24 months.
  • Proxy service: We retrieve some Target Platforms via the proxy service of IPRoyal (provider: IPRoyal Services FZE LLC, AMC – Boulevard-B Building, 143 Al Hassan Al Basri Street, Jurf 2, Ajman, United Arab Emirates). Only the address of the retrieved target page and its content are transmitted, no account or access data and no IP addresses of our customers. Legal basis: Art. 6 (1) (b) and (f) GDPR. Transfer to third countries: There is no adequacy decision of the EU Commission for the United Arab Emirates. Insofar as personal data is transferred, we base the transfer on the EU standard contractual clauses (Art. 46 (2) (c) GDPR). Further information: iproyal.com/privacy.
  • Quality and availability checks: To monitor our service, we carry out automated test retrievals and store only measurements (success, response time, share of filled fields), no content. We delete these measurements after 90 days.
  • Your rights: If a record retrieved via our API concerns you, you can contact us; we forward your request to the responsible customer insofar as we can identify them, and delete any data we hold.

7. E-mail delivery and payment processing

Resend (sending e-mails)

Provider: Resend, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA

We send login links, welcome and onboarding e-mails, quota warnings, job notifications, cancellation confirmations and messages from the contact form via Resend. Your e-mail address, the content of the message and technical delivery data are processed. Sending takes place via data centres in the EU (Ireland).

Legal basis: Art. 6 (1) (b) GDPR. Transfer to third countries: Access from the USA is covered by the EU standard contractual clauses; Resend is a processor. Further information: resend.com/legal/privacy-policy.

Company details and VAT ID verification (VIES)

Before you book a paid plan, we collect in the customer portal your company name, country, billing address, where applicable your VAT ID or tax number, and your confirmation that you are acting as an entrepreneur. We verify any VAT ID provided via the VAT Information Exchange System (VIES) of the European Commission; we only transmit the country code and the number, and the verification is carried out by the tax administration of the respective member state. We store the result together with the time of the last successful verification in your customer account. These details determine the VAT on your invoices (section 7, Stripe). The legal basis is Art. 6 (1) (b) GDPR (conclusion of the contract) and Art. 6 (1) (c) GDPR (VAT obligations, in particular invoice details and proof of tax exemption or of the reverse charge, i.e. the recipient of the service being liable for the tax). We store the company details for the duration of the contractual relationship; insofar as they are contained in invoices, the statutory retention periods apply. Further information on VIES: ec.europa.eu/taxation_customs/vies.

Stripe (payment processing and invoices)

Provider: Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland

We sell paid plans and request packs ourselves; we process payments through the payment service provider Stripe, which we also use to manage subscriptions and create invoices. When you book a plan or a request pack, you are redirected to a Stripe payment page. You manage payment methods, invoices and cancellation in the Stripe billing portal, which you can access via our customer portal. We transmit to Stripe your e-mail address, company name, billing address, where applicable your VAT ID or tax number, your account identifier, the selected plan or request pack and your confirmation that you are acting as an entrepreneur. Stripe additionally processes the payment data you enter there (such as card details or bank details), your IP address as well as device and transaction data. We receive from Stripe a customer and subscription identifier, the status of your subscription as well as invoices and payment amounts; we do not receive or store complete card details or bank details.

Fraud prevention: Stripe automatically checks payments for fraud risks (Stripe Radar), using payment, device and connection data such as the IP address. High-risk payments may be declined. In that case, you can use a different payment method or contact us.

Legal basis and roles: Art. 6 (1) (b) GDPR (conclusion of the contract, payment processing and billing), Art. 6 (1) (c) GDPR (obligations under tax and commercial law) and Art. 6 (1) (f) GDPR (legitimate interest in preventing payment fraud). For managing subscriptions and creating invoices, Stripe processes the data as our processor (Art. 28 GDPR). For processing payments as a payment service provider, fulfilling its own legal obligations (for example to prevent money laundering) and fraud prevention, Stripe is itself the controller; in this respect, Stripe's privacy policy applies.

Transfer to third countries: Stripe may transfer data to affiliated companies outside the EU, in particular to Stripe, Inc. in the USA. Stripe is certified under the EU-US Data Privacy Framework (DPF) (adequacy decision of the European Commission, Art. 45 GDPR); in addition, the transfer is based on the EU standard contractual clauses. Further information: stripe.com/de/privacy.

Storage period: We retain invoices as well as payment and invoice data (amount, time, Stripe identifier) in accordance with the statutory periods (§ 147 AO, German Fiscal Code; § 257 HGB, German Commercial Code; up to ten years).

Processing of customer and contract data

We process customer and contract data only insofar as they are required for the conclusion, performance, amendment and billing of the contract (Art. 6 (1) (b) GDPR). After the contract ends, we delete them as soon as no statutory retention periods apply. Data are passed on to third parties only insofar as this is necessary to perform the contract, for example to the payment service provider. Data are not passed on for advertising purposes.

8. Internal administration and security

Administrator access to customer accounts, such as plan changes, is recorded in an audit log with time, action and target so that changes can be traced. We delete the log entries after 24 months. To protect against repeated processing of payment events, we store the identifiers of the events received from Stripe for 90 days. The legal basis in each case is Art. 6 (1) (f) GDPR.

We log security-relevant events in your account with the time, type of event and, where available, your IP address: registration, logins and failed login attempts, password changes, creation and revocation of API keys, dataset jobs, connections with applications (OAuth) as well as company details, subscription and payment events from Stripe. The purpose is to investigate misuse and unauthorised access and to be able to trace events in case of queries. We delete the entries after 12 months. We count API calls rejected by quota or cost limits per day, reason and platform; we delete these totals after 13 months. The legal basis is Art. 6 (1) (f) GDPR. We keep paid invoices (amount, time, Stripe identifier) in accordance with the statutory periods (§ 147 AO, Art. 6 (1) (c) GDPR).

9. What we do not do

  • No analytics services such as Google Analytics, no user profiles, no heatmaps or session recordings; audience measurement is limited to the cookieless Vercel Web Analytics (section 4).
  • No advertising networks, no retargeting, no transfer of customer data to advertising platforms.
  • No social media plugins, no embedded third-party content, no external fonts.
  • No third-party CAPTCHA service.
  • No sale of personal data.

Should we use such services in the future, we will obtain your consent in advance where required and adapt this privacy policy.

10. Changes to this privacy policy

We adapt this privacy policy when our services or the legal situation change. The version published here at any given time applies. We inform registered customers by e-mail about material changes that affect existing customer contracts.