Privacy Policy

2.1 Data you provide to us (optional, with account)

If you create or use an account (email/password or Google login via Firebase Authentication), we process in particular:

• Email address and, if applicable, display name of the account
• Content you have saved in Firebase Firestore, e.g. E.g. favorites, dashboard layout, saved analytics evaluations and personal clipboard under /copypaste
• Technical identifier of the account (Firebase User ID)

2.2 Data collected automatically

When accessing the services, technical data may be generated, e.g. B. IP address, date and time of access, browser type, operating system, referrer URL and requested pages. This data is primarily needed to provide the services, detect errors and ensure security (hosting, Firebase, API calls).

2.3 How we count page requests

For ordinary GET requests to known pages, Firebase Hosting counts responses with status 200 or 304. In Cloud Monitoring we see separate totals for the selected period by site section and, when available, by country using the Firebase Hosting country code. Another total counts requests with both URL parameters utm_source=google and utm_medium=cpc.

Cloud Monitoring retains these counts for six weeks. Google temporarily processes the original requests to produce the counts. We exclude the associated new Hosting request logs from persistent storage and export in our project. This internal analysis stores no individual URLs, query parameters, IP addresses, cities, or user, click or campaign identifiers.

For successful page requests we count browser families and operating system families separately, using the user agent already sent with the request. For known pages we also count successful responses, redirects and errors. Each counter stores only a total for a fixed category. We do not store the full user agent or individual page paths in these counters, or link the totals to countries, accounts or visitor profiles.

Our legitimate interest under Article 6(1)(f) GDPR is to understand demand for our services and the reach of paid referrals. Aggregate counts meet this need without recognising individual visitors. You may object on grounds relating to your particular situation by writing to corvin_hartmann@gmx.de.

If you consent in the analytics settings, your browser also sends the page path to our service when you visit a statistics subpage. We use it to count weekly views of that page. You can withdraw consent at any time in the analytics settings for future visits.

2.4 Usage analysis with Firebase Analytics

Before you choose and if you decline, your browser sends Google Analytics a basic page-view signal to help us estimate reach. The signal also includes the broad public section of the site. No Analytics cookies are read or set for these signals. Google receives connection data such as your IP address, standard browser information and your consent status. PowerMonitor sends no identifier of its own for a user or browser, campaign parameters or detailed events in these signals. They cannot reliably count individual visitors.

With your consent, PowerMonitor uses Analytics cookies and also measures interactions, approximate engagement time and campaign parameters. Advertising cookies, sharing user data for Google advertising and ad personalization remain disabled. You can withdraw consent at any time in Privacy settings for future measurement. The blocking option in section 2.6, Global Privacy Control (GPC) or Do Not Track (DNT) also prevents the Analytics tag from loading and stops further basic signals.

2.5 Local storage in the browser

Without sending it to us, the following can be saved in the browser: map section, clipboard for import into Analytics, cache entries for faster display. You can delete this data in the browser settings.

2.7 Umami

We run Umami ourselves on Google Cloud in Belgium. Whatever you choose for detailed analytics, we estimate how many visitors use our site each UTC calendar month. Umami combines the site, IP address and browser user agent with a salt that changes monthly to generate a pseudonymous identifier. Changing network or device can count one person twice. People sharing a connection and the same user agent can count as one. Visits are estimated in hourly windows. A temporary token in the tab’s memory can link navigation across the hour. Umami sets no cookies and saves no identifier in browser storage.

For each view we record the time and broad site section. Umami derives browser, operating system and device families from the user agent. We estimate the country of the internet connection on our server from the IP address using DB-IP Country Lite (CC BY 4.0). We do not send the IP address to DB-IP. This measurement excludes city, region, query parameters, referrers, account IDs, screen size and language. When a page is viewed, we associate the last known country with the monthly visitor identifier. Individual event and session records are deleted after 35 to 36 days. Backups may retain them for up to seven more days. Only monthly totals are kept in Cloud Monitoring for 24 months. We rely on our legitimate interest in estimating monthly reach (Article 6(1)(f) GDPR). You can stop collection using the opt-out in section 2.6 or GPC/DNT.