Cookie Policy

1. What Are Cookies?

Cookies are small pieces of data that are stored on your device (computer, tablet, or mobile phone) by your web browser when you visit a website (domain). When you navigate to the next page of the same website/domain, your browser automatically sends the previously created cookie to that page’s server. Cookies help website operators improve and secure the visitor’s browsing experience, as the server can make decisions about what to deliver to the user before serving the page.

You visit a website for the first time and need to “log in” with a username or through your social media account. Since a web server normally closes all connections after delivering a web page and immediately forgets everything, it needs a way to remember that you are already logged in. The simplest method is to make a request to your browser after successful login, along with the page, to store secret information. This secret information is not your name or password, but rather a long, hard-to-guess random value (ID token) that the web server can associate with your user account. It is only valid as long as you are logged into the system. On the next page request, the browser sends the cookie to the web server, which can then use the ID token contained within to determine whether you are logged in and what content to deliver. (“Session Cookie/Auth Cookie”) This procedure is common standard practice, “relatively secure,” and benefits you because you don’t have to log in again every time.

Problems typically arise when a website operator integrates a script from another website operator - a so-called “third party” - into their site, such as an advertising network script designed to display relevant ads on the sidebar (e.g., Google Ads). This “third party” would also set a cookie with a random ID token in their script, which would be sent to the third party (in this case googleadservice.com) with every page request. In addition to the cookie, the so-called “referrer” is also automatically transmitted, meaning the third party typically also knows from which website the cookie was sent.

Let’s say you visit the following pages in sequence for the first time. All pages integrate Google Ads to display advertising:

https://www.myshopping.tld (Your browser doesn’t yet send a cookie to the third party (Google), but the Google Ads script asks it to save a new cookie, e.g., “clientId=a1b2c3”. In the next step, you visit a new website.

https://www.myporn.tld/user/fakename (If this page also integrates the Google Ads script, the cookie with “clientId=a1b2c3” is now automatically sent to Google. The browser passes the embedding page as the referrer, i.e., www.myporn.tld). After some time, you visit a third page:

https://www.mycryptocoins.tld/user/realname (If this page also uses Google Ads, the browser sends the cookie with the ID and www.mycryptocoins.tld as the referrer again.

With each additional page you visit, Google Ads or the third party can complete the profile, conclusion for Google Ads: “The current visitor with ID a1b2c3 is interested in shopping, porn, and presumably trades bitcoins.”

This scenario assumes possible maliciousness on the part of the “third party.” In reality, providers like Google will not use this information to morally judge your browsing behavior, but only to show you relevant advertising, which could lead to you suddenly seeing banners for porn websites or bitcoin trading on the side during a business presentation with your private PC because advertising partners place ads on Google Ads targeting users interested in porn. If this example seems too scandalous and goes too far, you can alternatively imagine visiting a job board instead of a porn website and consider what impression it might make if advertising for a new job at a competitor appeared during a presentation with your boss.

In any case, without additional tools like ad blockers, you have no way to suppress the sending of third-party cookies. Therefore, the legislature has mandated that users must explicitly consent to the use of cookies.

2. How We Use Cookies

engineerix uses cookies to enhance your experience on our website. We use cookies for the following purposes:

  • Essential Cookies: These cookies are necessary for the website to function properly and cannot be disabled. These are typically session cookies as described in the example above.
  • Functional Cookies: These cookies enable enhanced functionality and personalization, such as remembering your preferences.

3. Types of Cookies We Use

Session Cookies

These are temporary cookies that expire when you close your browser. They help us maintain your session while you navigate through our website.

Persistent Cookies

These cookies remain on your device for a set period or until you delete them. They help us remember your preferences for future visits.

Third-Party Cookies

We may use third-party services that set cookies on our website. These services may include analytics providers or social media platforms. These third parties have their own privacy policies governing the use of cookies. In any case, we will ask for your consent BEFORE integrating third-party scripts.

4. Managing Cookies

You have the right to decide whether to accept or reject cookies. You can manage your cookie preferences through your browser settings:

  • Browser Settings: Most browsers allow you to refuse or accept cookies. Check your browser’s help section for instructions.
  • Delete Cookies: You can delete cookies that have already been set through your browser settings.
  • Ad Blocker: Ad blockers are browser extensions or programs that block cookies until you explicitly allow them to be set.

Please note that if you disable cookies, some features of our website may not function properly.

When you visit our website, whenever new cookies are to be set that are not technically necessary, you will be asked via a so-called “consent banner” to consent to the use of these cookies. You can change the settings made in this cookie banner at any time.

6. Data Protection

The use of cookies is covered by our Privacy Policy. Please review our Privacy Policy to understand how we collect, use, and protect your personal data.

7. Contact Information

If you have any questions about our use of cookies, please contact us:

Engineerix Software Services UG (haftungsbeschränkt)
Wachholderheide 3
D-12623 Berlin
Email:

Responsible Contact Person for Data Protection and GDPR

Christian Messow (external)
Email:

8. Changes to This Policy

We may update this Cookie Policy from time to time. Any changes will be posted on this page with an updated revision date. We encourage you to review this policy periodically.

Last modified: 2026-01-13