Raskyn is a GPS speedometer and trip recorder. This policy explains, in plain language, exactly what data the app touches and — just as importantly — what it does not do. The short version: your location and trips stay on your device. Raskyn has no user accounts, no analytics, and no server of its own.
At a glance
Raskyn is developed by Nordic Node (Sven van de Pennen), the "data controller" for the limited data described below. You can reach us at nordicnode26@gmail.com for any privacy question or request.
Raskyn is a speedometer, so it needs your precise location (GPS) to work. The app requests the ACCESS_FINE_LOCATION permission and reads your location and satellite signal while you are actively using the speedometer or recording a trip.
How we use it:
Your location never leaves your device. Raskyn does not upload your location, and it does not include location in ad requests. The app does not request background location and does not track you when you are not using it. Your raw latitude/longitude are used momentarily in memory to compute speed and distance, and are not stored.
If you record trips, Raskyn saves them in a database on your device only. There is no cloud sync, no export to us, and no online account.
| What is stored | Details |
|---|---|
| Trip summary | Start time, end time, total distance, and maximum speed. |
| Speed graph points | Timestamps and speed values (down-sampled to about one point per second) so you can see a speed graph for the trip. |
| App settings | Your unit preference (km/h or mph), keep-screen-on, high-contrast HUD, and speed-alert settings. |
No map coordinates (latitude/longitude) are ever stored — Raskyn keeps only times, distance and speed. Automatic system backup is disabled for the app, so this data is not copied to the cloud or transferred to a new device by the app. You can delete individual trips inside the app, and uninstalling Raskyn removes all of this data.
If you use Raskyn on both a paired Wear OS watch and your phone, the phone can relay speed information to the watch when the watch cannot get its own GPS fix. This uses Google's on-device Wearable Data Layer between your two paired devices.
Only derived speed values (speed, accuracy, satellite counts, signal quality, timestamp) are exchanged. No map coordinates, trip history, settings, or purchase information are sent between the devices. The watch version of Raskyn contains no ads and no internet access.
The free version of Raskyn (phone only) shows a single banner ad using Google AdMob. To serve ads, the Google Mobile Ads SDK may access your device's advertising identifier (Advertising ID) and standard technical information (such as device type, general ad-interaction data, and coarse network information) as described in Google's policies.
Google uses this data as an independent controller to deliver and measure ads. See Google's advertising and privacy information and how AdMob handles data.
If you are in the European Economic Area, the United Kingdom, or Switzerland, Raskyn shows a consent form (using Google's User Messaging Platform) before any ads load. You can choose whether to allow personalised ads.
Raskyn offers a one-time purchase, Raskyn Pro (product pro_lifetime), which removes ads. Purchases are handled entirely by Google Play Billing. Raskyn never sees or stores your payment details.
The only thing Raskyn stores about your purchase is a single on-device flag indicating whether Pro is active (so ads stay off). We do not store order IDs, purchase tokens, or account identifiers. Google Play is the source of truth and can restore your purchase on your devices. Google's handling of your purchase is covered by the Google Privacy Policy and the Google Play Terms of Service.
To be explicit, Raskyn does not:
Raskyn relies on the following Google services. Their processing is governed by their own policies:
| Service | Purpose | Policy |
|---|---|---|
| Google AdMob | Banner ads (free version) | Ads & privacy |
| Google User Messaging Platform | Ad consent (EEA/UK) | Google Privacy Policy |
| Google Play Billing | In-app purchase of Pro | Google Privacy Policy |
| Google Play services (Location, Wearable) | GPS on device; watch↔phone link | Google Privacy Policy |
Trips and settings remain on your device until you delete them or uninstall the app. Because Raskyn keeps this data locally with automatic cloud backup disabled, deleting a trip or uninstalling the app removes it. Data processed by Google (for ads, consent and billing) is retained according to Google's policies linked above.
Because Raskyn stores personal data (trip history and settings) only on your own device and holds nothing on any server, you are already in direct control of it: you can view, edit and delete it within the app at any time. Depending on where you live (for example, under the GDPR in the EEA/UK, or the CCPA in California), you may also have rights to access, correct, delete, or object to processing of personal data. For the limited ad-related processing carried out by Google, you can exercise choices through the in-app consent controls and your device's Ad settings, and by contacting Google. For anything else, contact us at nordicnode26@gmail.com and we will help.
Raskyn is a general-audience utility and is not directed at children under 13 (or the equivalent minimum age in your country). We do not knowingly collect personal data from children. Ad requests are configured as not child-directed.
Because Raskyn keeps your trip data on your device and does not transmit it, the main protection is your device itself. We recommend using a device lock (PIN, pattern, or biometric). Data exchanged with Google's ad, consent and billing services travels over Google's secured connections.
We may update this policy as the app evolves (for example, if we add a feature). When we do, we will change the "Last updated" date at the top and, where appropriate, notify you in the app. Continued use of Raskyn after an update means you accept the revised policy.
Questions, requests, or concerns about privacy? Email nordicnode26@gmail.com and we'll respond as soon as we can.