Cookies and tracking

1. No active advertising measurement at present

The application does not load Google Ads, Google Analytics or remarketing scripts. There is therefore currently no advertising/statistics category in this application that can be activated, and no button demanding supposedly necessary advertising consent. Technical functions of the hosting platform and its operational logs must be considered separately.

2. Necessary technology for operation and internal login

The public information page does not require a customer account. The contact check retains inputs in browser working memory while the view is open. Images and fonts are delivered through the website or its technical storage/delivery service; no Google Fonts or map widgets are embedded for visitors.

When an internal login is expressly started, the security cookie __Host-oauth_state is set with a maximum lifetime of ten minutes. The internal login cookie webdev_app_session may have a lifetime of up to one year and is deleted on logout. These values serve login security, not advertising profiling.

3. Browser storage in the administration/preview area

With internal administration access, the manus-runtime-user-info value in local browser storage may contain user information for login status. In an embedded project preview, manus-cookie may hold internal login proof in session storage. These functions concern internal access or the platform preview; they are not registration for customer advertising.

Session storage generally ends with the respective browser session; local storage may remain until manually removed. Further technically necessary security values of the delivery platform still need to be inventoried on a project-specific basis. Their providers and actual lifetimes will be added on an ongoing basis.

4. How to control and remove stored values

In your browser settings, you can view, block and delete cookies and website data. The entries relate to the domain you visited. Before deleting internal login data, log out of the administration area; blocking necessary cookies may impair that access.

The public contact check is not tied to consent to advertising tracking. Data already stored on the server are not removed by deleting browser cookies; for that purpose, use the data protection contact address and the rights described in the privacy notice.

5. If Google Ads is to be measured later

Before actual integration, the cookie/tracking information and privacy notice will be supplemented with the services and data flows specifically used. Where consent is necessary or required by the provider, measurement will not start before an informed active choice. Refusal and later change or withdrawal must be easily accessible.

A contact enquiry is not consent to advertising. No diagnoses, information about the person receiving care or contact contents may be transmitted to advertising services without review. Corresponding measurement approval and technical integration have not yet taken place.

6. Questions and legal framework

In particular, the Swiss Federal Act on Data Protection (FADP) and the information/refusal requirements for terminal equipment under Article 45c of the Federal Act on Telecommunications, as well as the specific technology used, are relevant. For data protection questions, contact the email address stated in the legal notice. Complete operator, hosting and retention-period information remains to be added.