{"id":45778,"date":"2026-08-13T09:07:14","date_gmt":"2026-08-13T07:07:14","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/privacy-policy\/"},"modified":"2026-11-10T17:07:04","modified_gmt":"2026-11-10T16:07:04","slug":"privacy-policy","status":"publish","type":"page","link":"https:\/\/www.dbi-services.com\/blog\/privacy-policy\/","title":{"rendered":"Privacy Policy"},"content":{"rendered":"\n

Last updated: 10 November 2026<\/em><\/p>\n\n\n\n

Who we are<\/h2>\n\n\n\n

This blog is operated by dbi services SA<\/strong> (UID CHE-115.853.816), Rue de la Jeunesse 2, CH-2800 Del\u00e9mont, Switzerland (“dbi services”, “we”, “us”). dbi services SA is the data controller for the personal data processed through this blog.<\/p>\n\n\n\n

For any privacy-related question or request, contact us at dpo@dbi-services.com<\/a> or by post at the address above.<\/p>\n\n\n\n

Scope of this policy<\/h2>\n\n\n\n

This policy covers the processing of personal data on the dbi services blog only. Our corporate website has its own Privacy Statement<\/a>, which applies to services such as job applications and newsletter subscriptions handled there.<\/p>\n\n\n\n

We process personal data in accordance with the Swiss Federal Act on Data Protection (FADP) and, where it applies to visitors from the European Economic Area, the EU General Data Protection Regulation (GDPR).<\/p>\n\n\n\n

What data we process, and why<\/h2>\n\n\n\n

Technical data and server logs<\/h3>\n\n\n\n

When you visit the blog, our web server automatically records technical data such as your IP address, browser type, operating system, referring page, pages visited, and the date and time of access. We use this data to deliver the site securely and reliably, and to diagnose technical problems. Legal basis: our legitimate interest in operating a secure website (Art. 6(1)(f) GDPR). Log data is kept only as long as needed for these purposes.<\/p>\n\n\n\n

Analytics<\/h3>\n\n\n\n

With your consent, we use Google Analytics 4<\/strong> (Google Ireland Ltd. \/ Google LLC) to understand how the blog is used \u2014 for example which articles are read and how visitors find them. Google Analytics 4 does not log or store full IP addresses. Analytics cookies are only set after you accept them in the cookie banner, and you can withdraw your consent at any time (see our Cookie Policy<\/a>). Legal basis: your consent (Art. 6(1)(a) GDPR).<\/p>\n\n\n\n

Also with your consent, we use Microsoft Clarity<\/strong> (Microsoft Ireland Operations Ltd. \/ Microsoft Corporation) to see how the blog is used in practice \u2014 for example how far articles are read and which parts of a page are clicked. Clarity produces heatmaps and replays of individual sessions; what you type into forms and other personal data on the page are masked before anything is sent to Microsoft. Its cookies are only set after you accept analytics cookies in the cookie banner, and you can withdraw your consent at any time (see our Cookie Policy<\/a>). How Microsoft handles this data is described in the Microsoft Privacy Statement<\/a>. Legal basis: your consent (Art. 6(1)(a) GDPR).<\/p>\n\n\n\n

We also count article views, how often the blog’s hidden easter eggs are discovered and how many games of the Snake game behind them are played, with a counter that runs on our own server, stores no identifier and is not shared with third parties. Your Snake scores stay in your browser; we keep none of them. The counts restart every 1 January and the previous years’ totals are kept as an archive.<\/p>\n

If you are logged in to the blog with a dbi services account (authors, editors and administrators), your egg finds and Snake games are also recorded under your account: which egg you found first and when, how many games you played and your best record, per year. Only administrators see these records, in the site’s dashboard; they are kept as long as the account exists and are deleted with it. This applies to staff accounts only, never to readers.<\/p>\n\n\n\n

Cookie consent records<\/h3>\n\n\n\n

Our consent banner (CookieYes) stores your cookie choices so that we can respect them on later visits and demonstrate that consent was given. Legal basis: legal obligation and legitimate interest (Art. 6(1)(c) and (f) GDPR).<\/p>\n\n\n\n

Contact form<\/h3>\n\n\n\n

If you use our contact form, we process the data you provide (such as your name, e-mail address, and message) solely to handle your inquiry. Legal basis: performance of pre-contractual measures or our legitimate interest in answering you (Art. 6(1)(b) and (f) GDPR). We keep contact inquiries only as long as needed to deal with them and any follow-up.<\/p>\n\n\n\n

Comments<\/h3>\n\n\n\n

If you comment on an article, we store the content of your comment together with the name and e-mail address you provide and your IP address. Comments are checked for spam by the Akismet<\/strong> service (Automattic Inc., USA); for this purpose, the comment data is transmitted to Automattic. Legal basis: our legitimate interest in enabling discussion and preventing spam (Art. 6(1)(f) GDPR). Published comments remain visible until you ask us to remove them.<\/p>\n\n\n\n

Embedded content<\/h3>\n\n\n\n

Articles may include embedded content from other platforms (for example YouTube videos). Embedded content behaves as if you visited the other website directly: the platform may collect data about you and set its own cookies. Where such embeds set non-essential cookies, they are only loaded after you have given consent in the cookie banner.<\/p>\n\n\n\n

Recipients and processors<\/h2>\n\n\n\n

We share personal data only with service providers that support the operation of this blog, under data processing agreements where required:<\/p>\n\n\n\n