Last Updated: August 29, 2026 · Effective: August 29, 2026
Wayline turns your location history and your camera roll into one shareable trip map: the path you travelled, with photo hotspots on it. This policy explains what the app accesses, what stays on your phone, and the few specific moments when anything leaves it.
This policy covers the Wayline mobile app for iOS and Android. Wayline is published by the same developer as Bernikins but is a separate app with a separate policy; the Bernikins policy does not apply to Wayline, and this one does not apply to Bernikins. The two apps do not share data.
| Data | When it is accessed | What it is used for | Where it goes |
|---|---|---|---|
| Location (precise GPS), including in the background | Only when you turn on recording for a trip, and only during that trip's dates. | To draw the route you actually travelled. | Written to a file on your device. See Section 3 for the one case where route coordinates are sent for road lookup. |
| Photos and their metadata, including embedded GPS tags and timestamps | When you let Wayline scan for photos taken during a trip's dates. | To place photos on the map and group them into hotspots. | Stays on your device. Photos are never uploaded. |
| A location history file you choose (Google Maps Timeline export, GPX, KML/KMZ) | Only the file you explicitly pick from the file picker. | To reconstruct the route of a trip you already took. | Parsed on your device. The file is never uploaded. |
| Trip content you create — titles, dates, hotspot names, favourites | As you use the app. | To build and display your trips. | Stored on your device. |
All of this is stored in Wayline's own storage area on your device (the app's Documents directory). We do not collect your name, email address, phone number, contacts, advertising identifier, or any account identifier, because Wayline has no account system and no server to store them on.
Wayline collects location data to draw your route on your trip map, even when the app is closed or not in use.
Recorded positions are appended to a log file in Wayline's storage on your device. They are used to build that trip's route and for nothing else. They are not used for advertising, profiling, or analytics, they are not shared with the developer, and there is no server for them to be sent to.
Wayline has no backend. There are exactly three ways information leaves your phone, and you control all three.
The map background is fetched as image tiles from tile.openstreetmap.org, operated by the
OpenStreetMap Foundation. Like any request to a website, this reveals your device's IP address and which map
tiles you are looking at — which indicates the general area you are viewing — to that service. Your route, your
photos, and your trip content are not sent. Tile requests are governed by the
OpenStreetMap Foundation privacy policy.
Location exports often record only the start and end of a drive, so the line between them cuts across country. The optional "follow the roads" step looks up the actual road between those points and redraws the line.
To do this, the coordinates of those route segments are sent to an OpenStreetMap-based routing service
(currently the public OSRM service at router.project-osrm.org). This is the one feature that sends
anything derived from your location off your device. Specifically:
We do not control the OSRM service and receive nothing back from it about you. Note that the public OSRM endpoint is a shared community service; its operators may log requests according to their own policies.
Wayline can export a map poster PNG, a recap video, individual photos, or a .trip bundle. Nothing is
shared automatically. When you choose to share, the file is handed to your operating system's share sheet, and
you pick the destination — Messages, Instagram, AirDrop, or anywhere else. That destination's own privacy policy
then applies.
Be aware of what a .trip bundle contains. It is a complete copy of the trip: the
path you travelled, the hotspots, and the photos themselves (re-encoded to a smaller size). Anyone you send it
to can open the full, explorable map, including where you were and when. Share bundles only with people you
trust, exactly as you would with the photos themselves.
Because everything is stored locally, you are in full control of retention:
There is no server-side copy to request the deletion of, and no account to close. If your device is backed up to iCloud or Google's backup service, Wayline's local data may be included in that backup under those services' own policies.
Privacy laws such as the GDPR, the UK GDPR, and the CCPA/CPRA give you rights to access, correct, delete, and port your personal information, and to object to its processing. Wayline is built so that these rights are exercised directly on your device: the data is already in your possession, you can view it in the app, export it with the share tools, and delete it at any time.
We cannot fulfil an access or deletion request on your behalf, because we hold no copy of your data and have no way to identify you. If you have a question about this policy or believe Wayline is behaving differently from what is described here, email support@bernikins.com and we will respond within 45 days. If you are in the EEA or UK, you also have the right to complain to your local data protection authority.
Your trip data lives in Wayline's private storage area, protected by your device's own sandboxing and full-device encryption, and by your passcode or biometric lock. Network requests to the map and routing services are made over HTTPS.
Because there is no server and no account, there is no central database of user routes to breach. The main
practical risks are physical access to an unlocked device, and files you choose to share — so use a device
passcode and be deliberate about who receives a .trip bundle. No system is perfectly secure, and we
cannot guarantee absolute security.
Wayline is not directed to children under 13, and we do not knowingly collect personal information from children under 13. The app has no account system, no messaging, no user-to-user content, and no way for us to receive any information about any user. Where local law sets a higher age of digital consent, that age applies. Parents with questions can contact support@bernikins.com. Because location recording is powerful, we recommend that a parent or guardian set up and supervise any use by a minor.
| Service | Purpose | What it receives |
|---|---|---|
| OpenStreetMap Foundation tile servers | Map background imagery | IP address and the map tiles requested (the area being viewed). |
| OSRM routing service (router.project-osrm.org) | Optional "follow the roads" lookup | IP address and the coordinates of the route segments being redrawn. |
| Apple App Store / Google Play | App distribution and updates | Handled entirely by those platforms under their own policies. We receive only aggregate, anonymous download and crash statistics from them, which do not identify you. |
| Apps you share to | Whatever you chose to send | The file you shared, only when you initiate it. |
We may disclose information if legally required to do so — though in practice we hold no user data that could be produced in response to such a request.
We may update this policy as the app changes. The "Last Updated" date above shows the most recent revision, and the updated version takes effect when posted. If a future version of Wayline collects data in a materially different way — for example by adding an account or a sync server — we will update this policy and present the change in the app before the new behaviour takes effect.
Questions, concerns, or reports about this policy: support@bernikins.com.