Privacy Policy
Last updated: 29 July 2026
The short version
Polyatic and its tools have no user accounts, set no advertising or tracking cookies, and collect as little data as possible. We do not sell or share personal data.
What we store on your device
Our tools may use your browser's local storage (not cookies) to remember your preferences — for example your last searched location or unit choice. This stays on your device, is never sent to us, and you can clear it any time in your browser settings. Because it is strictly functional, no consent banner is required.
Third-party data sources
The tools on this site do not fetch data from third-party providers. They compute their results in your browser, and the only requests our own JavaScript makes are for files served from polyatic.com — for example the star map loads its star catalogue from this site. Results you share as a link are carried in the # fragment of the URL, which browsers never send to any server.
Some pages do link out: the weather card on the home page points at weatherhack.com, a separate site of ours, and explainer text links to specifications and documentation elsewhere. Following one of those links takes you to that site, where its own privacy policy applies; we send nothing to it on your behalf. The one external request a Polyatic page makes on its own is the analytics counter described below.
Server logs
Our web server records standard technical request logs (IP address, timestamp, requested page) for security, abuse-prevention and reliability. These are retained no longer than 30 days and are not used to profile you. Legal basis: our legitimate interest in operating a secure service (GDPR Art. 6(1)(f)).
Analytics
Every page here loads a small page-view counter from stats.dankdev.com. That is a self-hosted GoatCounter instance we run ourselves — not a third-party analytics network, and the only external script on the site. When a page loads it sends exactly one request carrying: the page's canonical path prefixed with our hostname (e.g. polyatic.com/legal/privacy/), the page title, the referring URL if you arrived from a link, your screen width in pixels, a bot-detection flag, and a random value to defeat caching. That is the entire payload. It does not include anything you type, paste or drop into a tool, and it does not include the # fragment that shareable-result links use. As with any web request, it also arrives carrying your IP address and browser user-agent string, because every HTTP request does.
The counter is cookieless and stores no identifier: it writes nothing to your device, so it cannot recognise you on your next page or your next visit. We re-measured this on 29 July 2026 by loading this page in a browser with the real counter script running and inspecting storage afterwards — document.cookie, localStorage and sessionStorage were all empty. Legal basis: our legitimate interest in knowing which pages people actually use, so we can keep the useful ones working (GDPR Art. 6(1)(f)). On retention we will be plain rather than invent a number: we have not published a retention period for these aggregate page-view counts. They are totals per page and per day, not a record about you, and there is no account or profile they could be attached to.
Advertising
Polyatic currently serves no advertising of any kind. We show no third-party ads, load no ad networks or advertising scripts, and set no advertising cookies today — no ad code runs on this site as of this policy. If we introduce third-party advertising in future, we will update this policy first and, for visitors in the EEA and UK, present a compliant consent banner before any advertising cookies are set.
Your rights
Under the GDPR and UK GDPR you have rights to access, rectification, erasure, restriction and objection. As we hold essentially no identifiable personal data beyond transient server logs, there is usually little to act on — but you can contact us any time.