Seepegel

Transparent and in your control

Privacy

This page explains which data Seepegel processes, which settings remain in your browser and when external services are used.

Last updated: 19 September 2026

The essentials

Public use of Seepegel requires no account and no personal profile data.

Favourites, appearance and several convenience settings generally remain locally in your browser.

Google Analytics and future Google advertising are used only in line with your privacy choice through Google's certified TCF CMP.

Data controller

Mächler Media, Patrick Mächler, Hauptstrasse 63, 9434 Au SG, Switzerland (see imprint).

Server log files

When this website is accessed, the web server processes technically required information such as IP address, date and time, requested resource, referrer and browser/device details. It is used to deliver the website, analyse errors and maintain IT security, and is not combined into advertising profiles.

Cookies and local storage

Seepegel uses cookies, Local Storage and Cache Storage sparingly. Some are required for features you select; none of this information is used for advertising.

Language
NEXT_LOCALE remembers the selected language. This necessary setting contains no unique user ID.
Privacy choice
While advertising is inactive, seepegel:consent stores the analytics choice locally. When AdSense is enabled, Google's certified CMP stores the choice as a standardised TCF signal.
Convenience features
Favourite lakes, light/dark appearance and local push and threshold settings are stored in the browser. Favourites and appearance are not sent to Seepegel. Dismissing an app suggestion is remembered locally for 30 days under seepegel:app-promo-dismissed-until. This expiry time contains no user identifier and is not sent to the server. Google Play links include fixed campaign labels for each placement, without personal identifiers.
Offline feature
A service worker stores only the static offline notice and an app icon. Current level and weather pages are deliberately not cached for offline use.

Seepegel Android app

The Android app uses the same current content as seepegel.ch and adds native notifications and a home-screen widget. No account or sign-in is required.

Technical delivery
The app retrieves current content and readings from the Seepegel server. The same technically necessary connection data as for a website request is processed. For its own reach measurement, the app sends only a fixed broad category such as Lakes, Rivers, Alerts or Detail page and the app language. Specific lakes, stations, thresholds, device identifiers and individual usage histories are not stored for this purpose.
Data on the device
Selected lakes, language, appearance, completed onboarding, consent choice and alert settings remain in the device's local app storage. Favourites and alerts can be changed or deleted in the app at any time; consent to Google Analytics can be withdrawn under ‘More’.
Home-screen widget
For each widget, the selected lake and language are stored locally. The widget retrieves current public readings from seepegel.ch approximately every 30 minutes and after a manual refresh. It sends no contacts, advertising ID, location or other personal information.
Permissions
The app needs internet access for current readings. Android's notification permission is requested only when you activate an alert. Seepegel does not request access to location, contacts, photos, camera or microphone.
Google Play and app services
Installation and updates are provided through Google Play. Google acts as an independent provider and processes account, device, download, diagnostic and security data under its own terms. The Seepegel app includes Google Analytics for Firebase, whose collection is disabled by default and is activated only after voluntary consent in onboarding or under ‘More’. AdMob ads are planned for an upcoming app version. When advertising is enabled, Google processes IP addresses, ad interactions, diagnostic data and SDK identifiers for advertising, measurement and fraud prevention. Access to the Android advertising ID remains disabled. Google UMP manages ad privacy choices separately from Analytics; required privacy options remain accessible under “More”.

External services and recipients

External connections are made only where required for a visible feature or after you have consented.

First-party anonymous reach measurement

Seepegel counts website pages that were actually displayed and fixed broad app categories on its own server independently of cookie or analytics choices. A website view is reported only after a visible navigation, so technical prefetches are not counted as reach. For direct partnerships, visible sponsor placements and clicks are additionally stored as daily totals. Only aggregated values by normalised path or app category, language, broad device class and referring website host are retained. Recognised machines are counted separately. Five-minute totals used for real-time and 24-hour views are deleted after 72 hours. No IP address, full referrer, user agent, query string, cookie or user identifier is stored; individual people, sessions and usage histories cannot be identified.

Google Analytics

After your consent, Seepegel uses Google Analytics 4 on the website and Google Analytics for Firebase in the Android app, provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. It processes pages or app areas, session and lifecycle events, a Firebase-generated app instance identifier, approximate region and general browser, app and device details. Google uses the IP address to derive an approximate region and discards it before logging for traffic from Switzerland, the EU and the United Kingdom. Further processing may also take place in the USA. Google's privacy policy applies.

Seepegel disables Google Signals and advertising personalisation. In the Android app, analytics collection, advertising ID collection and personalisation are disabled by default; only analytics collection can be enabled after consent and switched off again under ‘More’. On the website, Analytics is likewise loaded only after consent. With AdSense, Google Consent Mode starts with storage denied; optional Analytics cookies are set only according to the CMP choice. The website cookies _ga and _ga_* are limited to six months.

Consent is voluntary and can be withdrawn at any time for the future:

Map services

For interactive maps, your browser loads map styles and tiles from OpenFreeMap. If the official flood warning layer is enabled, map data from the federal spatial data infrastructure operated by swisstopo is added. The providers technically receive your IP address and request information. Seepegel sends no account or profile data. In the Android app, the OpenFreeMap map loads after opening and confirming the map provider notice. Device location is not requested.

Push notifications

Web push is activated only at your request and after browser permission. Seepegel stores the push endpoint, public encryption keys, selected lake, language and thresholds; unsubscribing removes the relevant subscription from the server. The Android app regularly checks the lake and river alerts stored locally by the user in the background and displays a local notification after a confirmed threshold crossing. Alert target, threshold, duration and repetition remain in app storage and can be changed or deleted at any time.

Advertising

Seepegel is technically prepared for Google AdSense. Once advertising is enabled, Google's certified CMP, integrated with the IAB Transparency and Consent Framework, manages the required choices for Switzerland, the EEA and the United Kingdom. No personalised ads are served without the appropriate consent. The choice can be changed at any time through ‘Cookie settings’. AdSense is not loaded in the Android app, widgets or embeds.

Retention

Local settings remain until changed or deleted in the browser. Push subscriptions remain until unsubscribed. Server logs are retained only as long as required for operation, troubleshooting and security; longer retention occurs only where legally required or needed to investigate a specific security incident. Google Analytics is also subject to the retention configured there.

Your rights

Under the Swiss Data Protection Act, you may in particular request access, correction, deletion or delivery of your personal data and object to processing. Contact the controller named in the imprint. Further information is available from the Federal Data Protection and Information Commissioner.

Changes to this policy

We update this policy when features, services or legal requirements change. The current version published here applies.