Privacy — short and honest
Responsible: see legal notice. Linkwache is a private, free service for friends and acquaintances — no business, no advertising, no sharing of data.
Where Linkwache runs
On a private server in Germany (Radeberg, Sachsen), operated by the responsible person. There is no hosting provider, no cloud, no content delivery network. The connection is encrypted (HTTPS, Let’s Encrypt certificate). The name linkwache.maro-datacenter.de is resolved to the server’s address by Synology Inc.’s DDNS service; Synology only sees the name lookup, not what you enter. This applies to normal operation; only when this server is unreachable can the app use a reserve server (see “Reserve server” below).
Reserve server (when the main server is down)
The apps (computer, browser extension, Android) can switch to a reserve server when the main server is unreachable (timeout, no connection, server error). In normal operation nothing goes to the reserve server. It runs as a program at Cloudflare, Inc. (USA) and is used only when the app works with the built-in server address; anyone who entered their own server in the settings never uses it.
During an outage the app sends the same request as to the main server: the link, reduced as usual (scheme, domain and path; query and fragment are removed first), plus the language, the scope, the random installation id and the app name and version. Technically, Cloudflare as the operator of the network also sees your device’s IP address. Nothing is stored on the reserve server: no storage, no logs; the abuse counters (per installation and per IP address and minute) use hashed values in memory. It asks the same lookup services as the main server (see “Where the link goes”), but never starts a sandbox scan. Cloudflare acts as a processor (Art. 28 GDPR; Cloudflare’s Data Processing Addendum is part of its terms). The transfer to the USA is based on the EU-US Data Privacy Framework (Cloudflare is certified) and standard contractual clauses. As for the check itself, the legal basis is our legitimate interest (Art. 6(1)(f) GDPR): the check should keep working when the operator’s server is down.
What is stored
- The checked link and the result — under a random ID so you can forward the result link. It is deleted automatically after 90 days. No names, phone numbers, e-mail addresses or IP addresses are stored — only the link, the technical facts about it and the assessment.
- The rest of a pasted message is not stored. From pasted text we only extract the links; the text itself is discarded.
- Telegram (if offered): the chat ID is only used to reply and is not stored. To prevent abuse we count messages per chat for one day, using a hash kept in memory only.
Logs and abuse protection
The server keeps no access log with IP addresses. To keep anyone from flooding Linkwache with thousands of requests, we count requests per sender per minute and per day; for that, a daily changing hash of the IP address is kept in memory only and vanishes on restart. On technical errors the server’s error message may contain the IP address; those logs are overwritten regularly.
For capacity planning the server counts only in aggregate how many requests and checks there were per hour (by kind of page, by channel such as website, app or Telegram, and by result), how fast it answered and roughly how many different senders there were per day. For the latter a value derived from the IP address that changes daily is kept in memory only; just the number is stored. No addresses, no links and no device data are stored. Hourly figures are kept for 30 days, daily figures for two years.
Where the link goes
To assess a link we query lookup services on the internet — the link (or only its domain name) is transmitted, nothing else about you:
- Name resolution (domain name only): Cloudflare (1.1.1.1) and Google Public DNS, encrypted via DNS-over-HTTPS.
- Domain age and registrar (domain name only): RDAP lookup at the responsible registry via rdap.org.
- Certificates (domain name only): crt.sh (Sectigo).
- Fraud databases (the link): Google Safe Browsing (Google LLC, USA — Advisory provided by Google), URLhaus (abuse.ch, Switzerland), PhishTank (Cisco, USA) and the urlscan.io search — each as far as the service is set up.
- Sandbox screenshot (the link, if set up): urlscan.io opens the page in a sandbox and takes a screenshot. The scan is “unlisted” (not searchable, but reachable with the link). The image is loaded into your result directly from urlscan.io — so urlscan.io sees your device’s IP address as with any image request.
The legal basis is our legitimate interest in giving you an assessment of a suspicious link (Art. 6(1)(f) GDPR). The link itself is usually not personal data; if it is (say, a link containing your name), the same applies: 90 days, then gone — or immediately on request.
Apps (computer and Android) and browser extension
The apps for Windows, macOS, Linux and Android and the browser extension check links on your device first and only ask Linkwache when needed. In that case:
- What is sent is only scheme, domain and path of the link (
https://domain/path). The query string (everything after the ?) and the fragment (everything after the #) are removed first, because that is where access or session data often sits. In “domain only” mode justhttps://domain/leaves your device. - The installation id is a random number without personal data that your device creates on first start. The server only uses it, hashed together with the day, as an in-memory counter against abuse; it is not stored and not linked to an address.
- Results of these checks are not stored — there is no id, no result page and no entry in the server’s storage; only a 10-minute cache in memory so that repeated clicks are not looked up twice.
- History, allow list and cache stay on your device and can be cleared there. There is no telemetry and no usage statistics.
- Update check: the apps ask the GitHub API directly for a new version (the public release list of this project). GitHub sees your IP address when they do; Linkwache learns nothing about it. The check can be switched off in the settings.
Download page
The files on the download page are hosted by GitHub (release storage of the code host, GitHub Inc., USA); when you download, GitHub sees your IP address. Linkwache itself does not serve the files and sets nothing on your device in doing so.
Donation button
The “Buy me a coffee” button leads to PayPal (PayPal (Europe) S.à r.l. et Cie, S.C.A., Luxembourg). Only there, with your click, does PayPal process data under its own rules. Linkwache only learns that a payment arrived.
Cookies, tracking, advertising
None of it. No cookies, no analytics scripts, no fonts or scripts from third-party servers, no advertising. Only your day/night choice is remembered by your browser itself (local storage, never leaves the device).
Your rights
Access, rectification, erasure, restriction, objection, complaint to a supervisory authority (for us: the Saxon Data Protection and Transparency Officer) — write to the address in the legal notice. As we store no personal data there is usually nothing to delete; a result link is deleted on request.
Last updated: 18 November 2026. This translation is for understanding; the German version is authoritative.