Les pages légales sont en anglais.
Privacy Policy
Who we are
The Krona Werke apps are developed and operated by Lord Skippy LLC, based in St. Petersburg, Florida, United States ("we", "us"). For anything in this policy, contact us at info@lordskippy.group.
The short version
Krona Sunlight needs your location to show the weather where you are. Before your position is sent to our weather server, the App rounds it to at least roughly 500 meters (a third of a mile; about a kilometer on the Basic plan); our server fetches the forecast and keeps in its request statistics only a coarse grid cell of about 5 km — never your precise position. If you additionally allow background location ("Allow all the time" — optional, asked once in the App), the App also reads your position while it is closed, so the widget and watch face follow you when you travel: the position Android already holds each time it refreshes, and a fresh fix at most about once an hour.
Krona Moonrise uses your location to know which sky is yours, and computes that sky on your device — the Sun, the Moon, the planets, eclipses and satellite passes. What it asks our server for is the cloud forecast, for a grid cell of about 5 km; the aurora forecast, for your position rounded to a whole degree; and the satellites' orbital elements, which carry no location at all. When you look for a satellite of your own to add, what you type is sent to our server, which answers from its own copy of the satellite catalogue and does not keep it. It asks for no weather unless you subscribe to Premium Weather, which asks for the weather at a point rounded to about a kilometer. It offers the same optional background updates as Krona Sunlight. Its compass and its view of the sky where you point the phone read the phone's compass and motion sensors, and what they read stays on the phone.
Krona Tidewater does not follow you at all. It shows one surf spot that you pin, and it asks for your location only if you tap "add my current location" — it cannot use background location, because the permission is not in the app. The spot's coordinates are sent exactly as you placed them rather than rounded: a break moved a kilometer is a different break, and often a point inland where no wave model has anything to say. What our server keeps is the same coarse grid cell either way.
None of the apps runs ads, sells data, wants your name, or has an account to create. Everything our server stores about your use is tied only to a random, anonymous Data ID, auto-deletes after 90 days of inactivity, and can be deleted instantly at kronawerke.com/delete-data. Our host's ordinary access logs record each request as well, and rotate out on their own within about a month; since the October 2026 versions the apps send your Data ID and position in a part of the request those logs do not keep.
When you switch on weather warning notifications, the App files a notification ID for your device (a random token from Google's Firebase Cloud Messaging, or on an iPhone from Apple's push service) with our server, together with your approximate location (the place the App shows, rounded as for the forecast), the least severe warning you want to hear of and the App's language — without your Data ID. Our server then wakes the App when a warning at that place begins, changes or ends; the message itself carries no warning and no place, and the App fetches the warnings from us. Switching the notifications off takes the ID back.
On an iPhone, Krona Sunlight's rain alerts (Premium, or Premium rain on the Custom plan) work the same way: switched on, they add to that filing the rain strength you chose, whether to follow the rain live, and the tokens Apple gives the App for its Live Activities. Every 15 minutes our server reads the minute-by-minute rain prediction for the place (rounded to about 500 m, as on the Premium plan) and sends the alert, or starts, updates and ends the Live Activity. Those messages carry the rain's times and strength, never the place. On Android the App does all this on the phone and files nothing.
What we collect, and why
| Data | Where it goes | Why | Kept for |
|---|---|---|---|
   All three apps | |||
| Place names and place search: your position (to name the place you are at) or the words you type (to find a place) | Android's own geocoder, which on most phones is a Google service, asked directly by your device. When it does not answer, the App looks the place up in a list of towns stored inside the App (from GeoNames), and nothing leaves the device. | Showing the name of your town, and finding a place or spot you search for. | Nothing is kept by us. Google's handling is governed by Google's privacy policy. |
| Official weather warnings: the position of the place shown (rounded as for the forecast, about 1 km, or about 500 m on Krona Sunlight's Premium plan), or your Krona Tidewater spot | Our server, with the forecast request or on its own. It looks the position up in the warnings it has collected from the national weather and emergency services (listed in our terms); the position is not passed to them. | Showing the warnings in force at that place, and notifying you of them when you switch warnings on. | Only as the request statistics below (the grid cell, never the position). Which warnings you were notified of is kept on your device alone. |
| Weather warning notifications, while you have them switched on: a notification ID for your device (a random token that Google's Firebase Cloud Messaging, or on an iPhone Apple's push service, gives the App), your approximate location (the place shown, rounded as for the warnings above) or your Krona Tidewater spot, the least severe warning you chose to hear of, and the App's language | Our server, which files them on our data server (Hetzner, see below) without your Data ID. When a warning at that place begins, changes or ends, our server asks Google's Firebase Cloud Messaging or Apple's push service to wake the App. That message carries no warning text and no position (on an iPhone, only the words "Weather warning" until the App has fetched the warning); the App then asks our server for the warnings itself. Firebase on your phone talks to Google only while these notifications are on. | Notifying you of a warning within minutes, even while the App is closed. | Until you switch the notifications off, Google or Apple report the ID no longer valid (for instance after you uninstall the App), or 30 days pass without the App checking in (it does daily); replaced when the place or your choice changes. Which warnings were announced is kept with the ID, to announce each one once. Google's and Apple's handling is governed by their own privacy policies. |
| Rain alerts on an iPhone (Krona Sunlight, Premium or Premium rain), while you have them switched on: with the weather warnings' filing above (the same notification ID and approximate location, at Premium's rounding of about 500 m), the rain strength you chose, whether to follow the rain live, and the tokens Apple's push service gives the App to start and update its Live Activities | Our server, which files them on our data server (Hetzner, see below) without your Data ID. Every 15 minutes our server reads the rain prediction for that place (from the providers below, as for the Premium plan) and asks Apple's push service to deliver the alert, or to start, update or end the Live Activity. Those messages carry the rain's start, end and strength and no place (an alert shows only the words "Rain on the way" until the App has written its own text). | Telling you of rain before it starts, and following it while it falls, even while the App is closed: an iPhone app cannot check the forecast on its own every 15 minutes. | As the weather warnings' filing: until you switch rain alerts off, Apple reports the ID no longer valid, or 30 days pass without the App checking in; it stops within a day of your Premium subscription ending. When the last alert went out and whether a Live Activity is running are kept with it, so a rain is announced once. |
| Anonymous Data ID (a random key your App creates on first use) and request statistics linked to it (timestamp, grid cell, cache status, response time, HTTP status) | Our server (hosted by DreamHost in the United States). | Service reliability, per-install rate limiting, abuse prevention, capacity planning, verifying premium entitlements. The Data ID is not linked to your name, email, device identity, or any advertising identifier — you can see it in the App under Terms & privacy. | Up to 90 days after last use — or deleted instantly on request at /delete-data. |
| Standard web-server access logs: the time of each request, your IP address, and the request's address (which service it asked for, and with which plan). The apps send your Data ID and the coordinates in the request's headers, which these logs do not record; versions of the apps from before October 2026 sent them in the address, where these logs did record them. Separately, rate-limit counters filed under a one-way hash of the IP address. | Our hosting provider's ordinary access logs, and our server's own counters. | Security, abuse prevention and troubleshooting (an inherent part of operating any web service). | Access logs: up to about 30 days; they rotate out on their own, and deleting your Data ID does not reach them. Rate-limit counters: up to a day. |
| Purchase information | Handled entirely by Google Play. We receive a purchase token confirming your entitlement and keep it, with its expiry date, under the Data ID of each device it unlocks (one subscription unlocks up to eight), and our server confirms it with Google about once a day so that a canceled or refunded subscription stops — never your payment details, name, or address. | Unlocking premium features you paid for. | For as long as your entitlement is active, plus statutory record-keeping periods. |
| Settings and cached data on your device | Stay on your phone and watch, passing between the two through the Wear OS data connection of Google Play services — including your precise position, so that the two devices agree on where you are. Never uploaded to us. If your phone backs up apps to your Google account, Android's own backup includes the App's settings and the places you saved; since the mid-October 2026 versions it leaves out the cached forecasts and your last known position. | The App working the way you configured it, including offline. | Until you clear the App's data or uninstall it (in your Google backup, until Android replaces or removes that backup). |
 | |||
| Device location (coordinates, rounded on-device before transmission: to about 500 m on the Premium plan, about 1 km on Basic) | Sent from your watch or phone to our weather server over an encrypted connection (TLS). The server forwards the rounded coordinates to the weather data providers to obtain the forecast: Open-Meteo on the Basic plan; on the Premium plan Apple Weather and Rainbow Weather, Open-Meteo for the clear-sky UV and the time zone, and near Norway and Austria MET Norway or GeoSphere Austria for the first hour of the rain prediction. When a provider is unavailable, the server asks the other one instead: Apple Weather for the Basic plan, Open-Meteo for Premium. In its request statistics the server keeps only a coarse geohash grid cell of about 5 km — not the coordinates. On the Custom plan, rounded coordinates go directly from your device to OpenWeatherMap with your own key; if OpenWeatherMap does not answer or refuses the key, the App shows the included Basic plan's forecast from our server instead, exactly as on the Basic plan, and says so. When you switch on Premium rain on the Custom plan (with a Premium subscription), the App also sends the coordinates, rounded to about 500 m, to our server for the minute-by-minute rain prediction, which the server obtains as on the Premium plan (Rainbow Weather, and near Norway and Austria MET Norway or GeoSphere Austria). With your opt-in (see Background location), the App also reads your position while it is closed and requests a fresh forecast when you have moved more than a few kilometers. If our server cannot be reached, the App keeps showing the last forecast it received and says how old it is; it does not turn to any other provider. | Showing the forecast for your location; noticing that you traveled so the widget and watch face stay current; caching so nearby users share one upstream request. | Grid cell in request statistics: up to 90 days. Caches, not linked to your Data ID, filed by the rounded position: the forecast for a few hours, the clear-sky UV for up to three days, the time zone (for a cell of about 30 km) for a month. Precise position: not kept by us. |
 | |||
| Device location, reduced on-device before transmission: for the cloud forecast, a grid cell of about 5 km; for the aurora, your position rounded to a whole degree (about 100 km); with Premium Weather, a point rounded to about 1 km | Sent from your phone or watch to our server over TLS. Our server passes the cloud cell — nothing else, no Data ID and no IP address — to our own cloud-data server, which holds the weather models' cloud forecasts and returns the cloud around that cell. The aurora is answered from the space-weather forecast our server holds for everyone; nothing about you goes further. With Premium Weather, our server forwards the rounded point to Open-Meteo (the forecast and its air-quality data) and to Rainbow Weather (minute-by-minute rain) to obtain the weather for your sky; without it, the App asks for no weather at all. The satellites' orbital elements are asked for by catalog number only, and a search for a satellite to add sends only what you type, answered from our copy of the catalogue and not stored; so does a search for a sky object (a star, a galaxy, a comet). A dwarf planet, an asteroid or a comet you keep is asked for by its catalog designation, and our server fetches its positions from NASA JPL — nothing about you goes with it. The Sun, the Moon, the planets, eclipses and satellite passes are computed on your device, and nothing about them is sent. Background location works as in Krona Sunlight, with your opt-in. | Showing the sky where you are, whether cloud stands in the way of what is in it and whether the aurora may come into sight — and, with Premium Weather, the weather under that sky. | The same coarse grid cell in request statistics, up to 90 days. Cloud forecast cache: until the next model run, a few hours, filed by grid cell only. Premium Weather cache: up to a day, filed by a cell of about 1 km. Precise position: not kept by us. |
| The phone's compass and motion sensors (its orientation), while the compass or satellite-pass page is open | Nowhere: read and used on the device only. Android asks no permission for these sensors. | Pointing the compass needle north, turning the compass over when you hold the phone above your head, and drawing the sky in the direction the phone points. | Not kept — each reading is used the moment it arrives. |
 | |||
| The coordinates of a surf spot you pin, at full precision | Sent from your phone or watch to our server over TLS, which forwards them to the marine and weather models (Open-Meteo) and the tide service (WorldTides), and to Apple Maps to draw the little map of the spot. They are sent unrounded on purpose: a break shifted by a kilometer is a different break, and frequently a point on land, where the wave models return nothing. This is a place you chose and named, not a measurement of where you are — Tidewater never reads your position unless you tap "add my current location", and it cannot read it in the background at all. If you add a spot from where you are, that spot is your position at that moment, sent unrounded like any spot. | Showing the tide, waves, wind and the surf verdict for that spot. | The same coarse grid cell in request statistics, up to 90 days. Caches, not linked to your Data ID: waves and the spot's weather up to 3 hours, tide predictions up to 4 days and a "no marine data here" answer up to a week, all by grid cell; the spot's map image up to 90 days (the free example spot's indefinitely), filed under a code derived from its coordinates. The spot itself: on your device, and synced to your own watch. |
Background location — Sunlight and Moonrise, optional, off until you say yes
Krona Tidewater does not have this permission at all. It is removed from that app's manifest, so nothing in it can read your position while it is closed, whatever Android's settings say. The rest of this section is about Krona Sunlight and Krona Moonrise, which ask the same question and use the answer the same way.
On first launch the App asks a plain question: should it keep itself up to date in the background? If you choose "Allow all the time" and grant Android's "Allow all the time" location permission, the App may read your position while it is closed — the position Android already holds, each time the App refreshes (as often as every 15 minutes), and a fresh fix at most about once an hour (every two hours on Krona Sunlight's Basic plan) — so that when you travel, the home-screen widget, the watch face and the ring refresh for where you actually are without you opening anything. The position is used exactly as in the foreground: reduced on the device as described above, sent only to request the forecast (Krona Sunlight) or the sky data (Krona Moonrise) for where you are, never stored server-side beyond the coarse grid cell, and never used for anything else.
If you choose "Only while using the app", everything still works — the App simply learns a new position only when you open it (the data itself still refreshes in the background for the last known place). You can change your mind anytime: in the App under Location, or in Android's settings by setting Krona's location permission to "Allow all the time" or "While using the app".
What we do not do
No advertising, no ad identifiers, no analytics SDKs, no selling or renting of data, no cross-app tracking, no profiling, no accounts, no collection of names, email addresses, contacts, health data, or message content. The App requests exactly one sensitive permission: location — and its background variant only ever with your explicit opt-in, which you can withdraw at any time. (The watch apps also ask for permission to set their own watch face, which concerns nothing but the watch face.) Krona Moonrise also reads the phone's compass and motion sensors, which need no permission, and only on the device.
Third parties we rely on
- Open-Meteo (weather, marine and air-quality data, EU-based) — receives coordinates from our server, never from your device: to produce your forecast on Krona Sunlight's Basic plan, and on its Premium plan the clear-sky UV, the time zone, and the forecast itself when the other providers are unavailable; in Krona Tidewater, the wave and swell models and the weather for your spot; in Krona Moonrise with Premium Weather, the forecast for your sky and its aerosol data (from the Copernicus Atmosphere Monitoring Service). See the Open-Meteo terms.
- Apple Weather / Apple Inc. (weather data, USA) — receives coordinates from our server to produce your forecast on the Premium plan (WeatherKit), and on the Basic plan when Open-Meteo is unavailable (never for Krona Tidewater). See Apple Weather attribution and Apple's privacy policy.
- Rainbow Weather / rainbow.ai (minute-by-minute rain nowcast, USA) — receives rounded coordinates from our server to produce the rain prediction on Krona Sunlight's Premium plan, on its Custom plan when Premium rain is switched on, and with Krona Moonrise's Premium Weather. See rainbow.ai.
- MET Norway and GeoSphere Austria (national rain nowcasts) — on Krona Sunlight's Premium plan (and on its Custom plan when Premium rain is switched on), receive rounded coordinates from our server for places in and around their countries, for the first hour of the rain prediction. Deutscher Wetterdienst's radar nowcast is downloaded whole and receives nothing.
- OpenWeatherMap (weather data) — on the Custom plan only, the App sends your rounded coordinates directly from your device using your own API key; our server is involved only when OpenWeatherMap does not answer, or for the rain prediction when Premium rain is switched on. See the OpenWeatherMap privacy policy.
- WorldTides (tide predictions) — in Krona Tidewater only, receives your spot's coordinates from our server to return the tide heights and the high- and low-water times. See the WorldTides privacy policy.
- Apple Maps / Apple Inc. (map imagery, USA) — in Krona Tidewater only, receives your spot's coordinates from our server to render the small map shown on the spot page. See Apple's privacy policy.
- NOAA (the HRRR model and the Space Weather Prediction Center's aurora forecasts, USA) and Deutscher Wetterdienst (the ICON models, Germany) — the cloud and aurora forecasts in Krona Moonrise. They receive nothing from you or about you: our servers download the files they publish on a schedule, the same files for everyone.
- CelesTrak (satellite orbital elements and catalogue, USA) — in Krona Moonrise, receives requests from our server for a satellite's elements by catalog number and, once a day, for its satellite catalogue, and nothing about you.
- GCAT (Jonathan McDowell's satellite catalogue, USA) and Wikidata (Wikimedia Foundation, USA) — the names Krona Moonrise's satellite search knows. Our server downloads them on a schedule, the same files for everyone; they receive nothing about you. What you type into the search goes to our server only.
- NASA JPL (the Horizons system and the Small-Body Database, USA) — in Krona Moonrise, receives requests from our server for a dwarf planet's, an asteroid's or a comet's positions by its designation, and once in a while for the list of named small bodies; nothing about you.
- The HYG Database, OpenNGC and the IAU Working Group on Star Names — the stars, galaxies, nebulae and clusters, and the names, of Krona Moonrise's sky-object search. Our server holds a copy; they receive nothing about you.
- DreamHost (server hosting, USA) — processes all server-side data above on our behalf.
- Hetzner Online (server hosting, data center in Ashburn, Virginia, USA) — runs our data server on our behalf: Krona Moonrise's cloud data, the official warnings, and the weather warning notifications and Krona Sunlight's rain alerts on an iPhone. It receives from our own server the grid cell of about 5 km that a cloud forecast is asked for, and, while you have warning notifications or rain alerts on, the notification details described above, with the minute-by-minute rain prediction for the places of the rain alerts — never your Data ID or your IP address.
- Google Firebase Cloud Messaging (Google LLC) and Apple Push Notification service (Apple Inc.) — deliver the message that wakes the App when a warning at your place changes, only while you have weather warning notifications on, and on an iPhone Krona Sunlight's rain alerts and their Live Activities while you have those on. They receive the notification ID and a message with no warning and no place in it (for rain, its times and strength). Governed by Google's and Apple's privacy policies.
- Google Play / Google LLC — app distribution, billing, the fused location service that supplies your position to the App, Android's geocoder, which names your place and finds the places you search for, the Wear OS data connection between your phone and your watch, and Android's app backup if you use it. Governed by Google's privacy policy.
Legal bases (GDPR / UK GDPR)
Where the GDPR applies, we process location and request data to perform our contract with you (delivering the forecasts the App exists for, verifying purchases) and under our legitimate interest in operating a reliable, abuse-free service (statistics, logs). Background location is the one exception: it is processed only on the basis of your consent — the in-app opt-in plus Android's "Allow all the time" grant — and you can withdraw that consent at any time by changing the permission, with no loss of the App's core function.
International transfers
Our servers are located in the United States. If you use the App from the EU/EEA, UK, or elsewhere, the request data described above is processed in the United States. We minimize what is transferred (grid cells, not coordinates; no identity data).
Your rights
Depending on where you live (EU/EEA, UK, California, and other jurisdictions), you may have the right to access, correct, delete, or export data about you, to object to or restrict processing, and to complain to your data-protection authority. One honest caveat: we cannot identify you in our data by name — the only link is the anonymous Data ID held by your App. That is also what makes your rights easy to exercise: access and deletion are self-service at /delete-data using the Data ID shown in the App under Terms & privacy. For anything else, email info@lordskippy.group and we will respond within 30 days. We never discriminate against you for exercising any right.
Data deletion
The App requires no account. To remove on-device data, uninstall the App or clear its storage. Server-side data (your anonymous Data ID and its request statistics) can be deleted instantly and self-service at kronawerke.com/delete-data — your Data ID is shown in the App under Terms & privacy. Independently of any request, server-side data is deleted automatically after 90 days of inactivity. You may also email us at any time and we will delete it for you.
Children
The App is not directed at children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us personal information, contact us and we will delete it.
Security
All traffic between the App and our server uses TLS. Server credentials and upstream API keys are stored outside the web root with restricted access. No system is perfectly secure, but our best protection is structural: we simply don't hold data worth stealing.
Changes to this policy
If we change this policy, the new version will be posted here with an updated effective date. Material changes (for example, a new category of collected data) will additionally be announced in the App's store listing changelog.