In short
- Lunaway shows no ads, uses no tracker or audience measurement tool, and sells no data.
- Browsing the map, searching and computing a route need no account. Until you create one, your favourites, your settings and your vehicle stay on your device.
- The account is created when you contribute for the first time or sync your favourites. It asks for no e-mail, no phone number and no password. Once it exists, your favourite lists are kept with it.
- Your location is used on the device. It goes to our servers to compute a route, rounded to about 5 km to look for the cheapest fuel around you, to rank the list of places beside the map or, when the map follows you, to rank a search, with a place you add where you stand, and with a road report you make, kept for 14 days. Routes are neither stored nor logged.
- Searches and translations run on our servers, which keep neither what you search for nor who asks for a translation. To look up an address, our server also passes the text and the map's centre rounded to about 5 km (your rounded position, when the map follows you) to IGN's public geocoding service, without your IP address.
- Some places, reviews and photos come from an external community source, under a written agreement, and from open sources; your device contacts none of them.
- Our servers are in Germany. Access logs truncate IP addresses and are erased after about 14 days.
- You can delete your account at any time, in the app or on the Delete my account page.
Who is responsible
Lunaway is published by a private individual, as a personal, non-commercial project, the controller of the processing described here. For a question or to exercise your rights: contact@lunaway.net.
This policy covers the Lunaway app (Android, iPhone and iPad, macOS, Windows, and the web version at lunaway.net/app), this site, and our servers: api.lunaway.net for the data, the photos, the searches, the translations and the routes, tiles.lunaway.net for the basemap and the offline maps, status.lunaway.net for the state of our services.
On your device
The app keeps its data in its own storage, which other apps cannot read:
- The places of the regions you keep on the device, on phones, tablets and computers, so that the map, the search and the place pages work without a network. At the first launch, the app offers the region where you are, chosen on the device from your position if you allowed it, otherwise from the map or the device's country. It also remembers the regions it has already offered, so as not to offer them twice. The web app keeps no region.
- The place pages, photos, first page of reviews and shops and services around the places you opened, erased after 90 days without being opened again.
- The offline maps you download, on phones and tablets.
- Your own data: your favourite lists (places, and addresses or points of the map saved with their name, your note and their coordinates), your home (its name, address and coordinates), your settings (language, filters and stay dates, theme, list sorting, coordinate format, preferred navigation app, route options, voice mode, places shown during guidance, exact speed camera positions in France, automatic translation of reviews, region updates over mobile data), your vehicle's profile (kind, trailer, height, width, length, weight, fuel, consumption, cruising speed), the regions kept, and the contributions waiting for a connection to be sent (ratings, reviews, prepared photos, new places, road reports).
- An approximate position and the centre of the map's last view, rounded to a tenth of a degree (about ten kilometres), so that the light or dark theme follows sunset, the map reopens where you left it, and to offer your region. The web app keeps this view, its theme and your filters in the browser's storage, to draw the map as soon as the page opens.
- The danger zones and speed cameras of the countries your routes cross, with the list of those countries, so that guidance started without a network has them. If you turn off "Exact speed camera positions in France", the app at once erases the points it had received for that choice.
- Your account's private key, if you have one, encrypted by the system's protected storage: a Keystore key on Android, the keychain on iPhone, iPad and Mac, Windows data protection on a PC; in the web app, a key the browser does not let anyone extract. It never leaves the device.
- Your search history: up to 15 entries, the results you opened (places, towns, addresses, shops and services) and the texts searched without opening a result, shown when you touch the search field. It stays on the device: it is never sent nor synced, and the Android or iCloud backup does not carry it. A cross removes an entry, "Clear the history" empties it, and it goes with the app's data.
The app keeps neither your routes nor your trips. Of your searches it keeps only the history described above, where an address you opened, a destination for instance, stays with its position until you remove it. A computed route stays in memory for two minutes, to show it again; translations stay in memory until the app closes. In the web app, the address of a route's page holds the destination, rounded to about ten metres: it goes into the browser's history.
To add a photo, or to read the code of your recovery card from an image, the app opens the camera or the photo library when you ask, and reads only the image you choose; the code is read on the device. The app does not use the microphone. If you save the image of your recovery card to your photos, it follows your photo library's settings, online backup included: keep it like a password.
On Android, your device's backup, which goes to your Google account, may hold your favourites, your home, your settings, your vehicle, your account's identifier and the contributions not yet sent, and nothing else from Lunaway: neither the account's key, nor the places, nor the photos waiting to be sent. The app allows it only when that backup is end-to-end encrypted, which Android offers from version 9 when the screen is locked; Android 7 and 8 do not support this condition and follow their own backup settings. A transfer to a new phone carries the same data. On iPhone and iPad, the iCloud or computer backup holds the same data, without the photos waiting to be sent or the offline maps; the account's key, kept in the keychain for this device only, does not move to another device. On a computer, your backups, and on Windows a company roaming profile, may also hold the app's data, search history included, depending on their settings.
In the web app, this data is in the storage your browser keeps for lunaway.net. Uninstalling the app, or clearing the site's data in the browser, erases everything.
What goes through our servers
The app connects only to our servers, always over HTTPS. It embeds no third-party service: no ads, no audience measurement, no crash reporting service, no basemap, photo or font loaded from elsewhere. Only the links you choose to open (a place's website or phone number, the original page of a photo or a review, OpenStreetMap, Google Maps, your navigation app, this site, the source code) lead elsewhere.
With or without an account:
- The place sync, on phones, tablets and computers, downloads the regions you keep on the device: one file per region, then its changes, at launch, when you come back to the app and after a contribution. The request names the region, never where you are; at the first launch, that region is the one where the app located you. On a phone, updates wait for Wi-Fi unless you allow mobile data.
- The offline maps download from tiles.lunaway.net, one file per region. The access log replaces the file's name with the same name for every file.
- The basemap, the places and the shops and services on the map come from tiles.lunaway.net and api.lunaway.net. Each piece of map shown matches an area: the logs keep only its zoom level, never the area. To check whether it is online, the app also regularly asks tiles.lunaway.net for a small file, sending nothing with it.
- Fuel prices on the map: when the fuel layer is on and the map close enough, the app asks for the stations of the visible area, widened to a grid of about 5 km, with no record and no log.
- The cheapest fuel around you: when the map is zoomed far out, or shows too many stations to read them all, the app asks for the stations around your position or the map's centre, rounded to about 5 km on the device and again by our server, with no record and no log. Distances are computed on the device. A station's page asks for its price history, with no position at all.
- Opening a place's page asks for the place itself when the device does not hold it, its reviews, photos and description, and the shops and services around it: the request names only the place. If you have an account, the request for the Lunaway community's reviews and photos carries your session, to show your own review and leave out the authors you muted; the server keeps from it only the session's last-use date, updated at most once an hour, and the account's day of activity, which counts towards the trust level. The page of a shop or a service asks for its reviews in the same way. Neither the content of these requests nor the address of the photos downloaded is recorded or logged. Every photo, those of other sources included, comes from api.lunaway.net (see Content from other sources).
- The search for places and towns asks our server whenever the network answers, on phones, on computers and in the web app: the text searched, the app's language and the map's centre, rounded on the device to about 5 km, go in the body of the request, without a session, and are neither recorded nor logged; a device that keeps regions adds its own places to the answer. Offline, or when our server does not answer, it runs on the device, in the regions it keeps, and says so. That centre is the centre of the map shown: when the map follows you, it is your position, rounded the same way.
- The address search (a number and a street, a street, a town, a postcode) asks our server when typing pauses, from three characters, on phones, on computers and in the web app: the text searched, the app's language and the map's centre, rounded to about 5 km to rank the results, go in the body of the request, without a session. Our server passes the text and that rounded point, without your IP address or any identifier, to our own geocoding server (OpenStreetMap data), with the language, and to IGN's geocoding service (the Géoplateforme, data.geopf.fr, a French public service), which answers for France; IGN thus receives the text and the point of every address search, whatever the country, and handles them under its own terms. That point is the centre of the map shown: when the map follows you, it is your position, rounded to about 5 km. Our servers neither record nor log the text or the point. Offline, no address is looked up and the search for places and towns continues on the device.
- The list of places beside the map: when the map shows a large area, the app asks our server for the places of the visible area, widened on the device to a grid of about 5 km, ranked from your position when the map shows it, else from the map's centre, that point rounded the same way, with your filters, with no record and no log; the count of places in the filters panel makes the same request. If you filter on your stay dates, the days of the year concerned, without the year, go with these requests. Closer in, the list is made on the device from the pieces of map already shown, and goes back to our server only if they are slow to arrive. For each place's rating and the start of its description, the app then asks our server for those of the places received (the request names only those places) or, close in, those of the visible area widened to the same grid (around your position when the map follows you), with no record and no log; it keeps them in memory only. Your exact position is not sent: the distances shown are computed on the device.
- Places along a route: in a route's preview, on a device that holds no places (the web app, a phone before its regions arrive), the app asks for the places around the route, stretch by stretch, each stretch widened to the same grid. On the preview and guidance maps, the photo and price of the places near the route are requested by those places' identifiers.
- The translation of a review or a description, when you tap "Translate" or when the setting "Translate reviews automatically" is on (it is off by default): the request names the text (the kind, the identifier of the review or the place, the source and the language of the description) and the app's language, without a session and without the text itself. Our server reads the stored text again and has it translated by our own translation server, with open models: no third-party service receives it. The translation is kept with the original text as long as it does not change, so as not to translate it twice, and erased with it or when it changes; neither the request nor the text is logged.
- The search for shops, services, restaurants, places to stay and leisure goes in the same request as the search for places, towns and addresses: the text searched and the map's centre, rounded on the device to about 5 km to rank the results (your rounded position, when the map follows you), go in the body of the request, and are neither recorded nor logged. The distances shown are computed on the device.
- The link "See the reviews on Google Maps" on the page of a shop or a service opens Google Maps (the app or the website) with the point's name and position, when you tap it: your device then talks to Google, under Google's own rules. Lunaway sends no request to Google and reads none of its reviews.
Directions and guidance
- A route: the start (where you are, or a place, a town or an address you chose), the destination, the stops (five at most), the size, weight and kind of the vehicle and its trailer, the vehicle's cruising speed, the roads to avoid and the language of the instructions go in the body of the request, without a session. Our own engine computes the route on our server; neither the request nor the route is recorded, and neither our API nor the engine writes a position in its logs. When the preview can offer other routes, our server sends the best one first, then keeps the others in memory under a random token, bound to the device's IP address (its block of addresses, in IPv6), until the app asks for them, once and within a minute; past that minute they can no longer be read, and the server erases them from memory as soon as it handles another request of this kind. Neither the token nor these routes are written to disk or logged.
- During guidance, on every device: the app asks for a new route from where you are, with your heading, when you leave the route, when a closure lies ahead, and when you add or remove a stop; before you confirm a stop, it asks for the route through it to show the time it adds. Each request follows the rules of the previous item.
- Fuel and places "On the way": when you open this list, the app sends the route's line as our server drew it, from 2 km after the start in the preview, or 2 km ahead of the vehicle during guidance, with the chosen category, the vehicle's profile, and for fuel the fuel and the consumption. Our server removes two more kilometres at each end of the line before any use; neither the request nor the line is recorded or logged.
- Fuel prices under the stations during guidance: when the guidance map shows fuel stations, the vehicle's profile names its fuel, the network answers and the vehicle is in France (or the app does not know which country it is in), the app asks for the stations of the cell of about 5 km the vehicle is in, widened by about 2 km on each side, as soon as the guidance knows your position, then at each new cell, about every 4 to 5 km. The request holds neither your exact position, nor the fuel, nor a session: the app picks the price to show on the device. Nothing of it is recorded or logged.
- Roadworks and road closures: during guidance, the app downloads the changes to road events every three minutes. The request holds no position.
- Danger zones and speed cameras: when a route is previewed, when guidance starts, after each new route, when you change the setting below, then every six hours, the app asks for the data of the countries the route crosses, which it works out on the device. The request holds the list of those countries, never a position. If you turn on the setting "Exact speed camera positions in France", it also holds that choice (the country code, FR); our server neither logs nor keeps it. The country you drive in, which decides what the app may show, is also worked out on the device: in France, the app shows danger zones, and the cameras' positions only if you turned that setting on.
- The location during guidance: guidance you start keeps receiving the location with the screen off or another app in front, using only the permission to access location while the app is in use. The system shows it (a notification on Android, which, from Android 13, the app asks you to allow the first time you start guidance; an indicator on iPhone and iPad), and everything stops on arrival or when you leave guidance. On a computer, the Mac and Windows apps follow the location while the app runs. In a browser, the location comes from the browser, which asks you first, and only while the page is open; on a computer without GPS, the browser works it out through its maker's location service, as a phone's system may do; the page keeps the screen on during guidance. The instructions are spoken by the voices installed on the device; in a browser, only by those it reports as present on the device, never by a voice that sends the text to its maker.
- A route in another app: when you open a route in another navigation app, Lunaway passes it the destination, and for some apps your position as the start; that app handles it under its own rules.
Your account, without e-mail
Browsing the map needs no account. The app creates one the first time you contribute (a rating, a review, a photo, a confirmation, an answer about a shop or a service, a report about a place or about the road, a place or a vending machine, a muted author) or choose to sync your favourites. As soon as the account exists, your favourite lists are imported into it, then updated at each change.
The account rests on a key pair made on your device. To sign in, the app sends the public key, a signature and the app's language, which serves to draw the pseudonym and is not kept. When an account exists, the app reads it again at each launch with your session. Our server keeps:
- the public key of each device linked to the account, with its creation and last-use dates, without the device's name or model;
- a pseudonym drawn at random, such as "Curious hedgehog of the Vercors", which you can change and which is public;
- your sessions: a random token of which we keep only the hash (SHA-256), valid for 60 days after its last use, erased within the hour after it expires;
- the hash of your recovery code (argon2id), if you made one. The code is shown only once, on your device, and we cannot recover it;
- your trust level, from 0 to 4, worked out from the account's age, the number of days it was used and the last of those days, its published contributions, the removals decided by moderators, and the sponsorship of an account of a higher level, if any;
- your favourite lists (their names, the places they hold, and the points you saved in them outside our places: an address, a town, a point of the map or a shop, with the name you give it, your note if any, its address when known and its coordinates, seen by your account alone) and the authors you chose to mute;
- your home, if you set one: the point chosen (an address, a town, a point of the map or a shop), its name, its address when known and its coordinates, seen by your account alone;
- for each contribution sent, a technical key that avoids recording it twice if the app sends it again: the key, the kind of operation and a hash of its content (for a road report, of its kind and value only), kept for 30 days (14 for a road report), or until the contribution is deleted.
If an account is banned for abuse, the reason for the ban is noted with it and the text of its reviews is erased. If it is then deleted, the hashes of its keys are kept for two years, so that it cannot come straight back.
Using another account on a device. If you open another of your accounts on a device with its recovery card, the app lets you choose. Merge: the favourites, the home, the hidden authors and the contributions of the device's account move to the account opened, and its published contributions take that account's pseudonym; the device's account is then deleted. Someone who had hidden the device's account then hides the account opened, which appears under its pseudonym in their list of hidden authors. A merge needs the signatures of the keys of both accounts. The deletion journal notes the merged account with the identifier of the account that received it, so that a backup brought back into service merges it again instead of bringing it back. Our server keeps for one year the hashes (SHA-256) of the merged account's keys, with the account that received it, so that its other devices learn where it went. If that account is banned, they are kept as long as it is, then for two years after its deletion, as the hashes of its own keys are. Replace without merging: the device's account stays on our server, this device's key is detached from it, and only its recovery card brings it back; if it has neither a recovery card nor another device, it is deleted, since nothing could open it again.
What you publish
| Contribution | What is public | Licence |
|---|---|---|
| Rating alone (1 to 5 stars) of a place, a shop or a service | its average rating, without your name | CC BY 4.0 |
| Review of a place, a shop or a service | the text, its language and the rating, with your pseudonym, and the date of visit if you give it (and the kind of vehicle, for a place) | CC BY 4.0 |
| Photo | the re-encoded image, with your pseudonym | CC BY 4.0 |
| "Still there?" confirmation of a place | the date of the place's last confirmation, without your name; any note you add goes to the moderators only. Each confirmation is erased after two years; the place keeps their count | places database, ODbL 1.0 |
| "Still there?" answer about a shop or a service | no answer on its own; together, they date the point's last confirmation or take it off the map if it is gone. Each answer is erased after a year | points of interest database, ODbL 1.0 |
| Problem report about a place (no overnight stay, service out of order, no access, danger) | the number of reports of each kind over the last 30 days, without your name; any note you add goes to the moderators only. Each report is erased after 90 days | places database, ODbL 1.0 |
| Road report | a road event without your name (see Road reports) | ODbL 1.0 |
| New place, new vending machine, edit of a place | once applied, the place's details and position, with the date of the proposal, in the places database, credited to the "Lunaway contributors" | ODbL 1.0 |
| Report of a review, a photo or a place | nothing: only the moderators read it, and it is erased a year after their decision | none |
The places, with their additions and edits, form an open database under the ODbL 1.0 licence, like OpenStreetMap, whose data it reuses. Ratings, reviews and photos are published under the CC BY 4.0 licence; reviews and photos are credited to your pseudonym. Our server also keeps, for each new place or edit, a revision (its content and position) that links it to your account; it is not public. The content of a rejected or withdrawn proposal is erased 30 days after the decision; only an empty history line stays.
Photos. Before sending, the app shrinks the photo to 2560 pixels a side at most and saves it again without its metadata: no GPS position, date or device model is sent. The server decodes it, then re-encodes it from the pixels alone into two WebP files (2048 and 512 pixels a side). The original is not kept.
What your contributions show. Your reviews and photos are public with your pseudonym, and a stable account identifier links them. Put together, with their dates, they can show where you have been. The date of visit of a review is optional.
Moderation. Texts go through simple automatic rules (links, contact details, repetition, a word list). A text that trips them waits for a moderator before it is published. A review or a photo reported by three trusted accounts is hidden until a moderator decides. The moderators (the publisher and the contributors it appoints) read the reported content and the notes attached to confirmations and reports; each decision is erased a year after it was made.
You can delete each of your contributions, or your whole account: the Delete my account page details what goes and what stays.
Road reports
In France, Spain and the Netherlands, during guidance or from a point on the map, you can report a closed road, roadworks, a narrow passage, a low clearance or another problem, and say it is still there or that it is over. Like any contribution, the first report creates your account if it does not exist yet.
- The report sends its kind, the exact position (the vehicle's when you tap the button during guidance, or the point chosen on the map), your heading during guidance, and the height or width given, if any. Saying that a reported problem is still there sends that event's position and heading; saying that it is over sends its identifier, and our server then notes, with your account, the event's position and the time; if that event changed routes, a moderation entry linked to your account is created too. Without a network, the report waits on the device and is sent when the connection returns.
- Our server keeps it with your account for 14 days, then erases it. Before that, it cannot be deleted on its own; it is also deleted with the account.
- What is public: a road event without author or heading, at a position rounded to about ten metres, with its kind, its value and the times of the first and the last report. When two trusted accounts report the same thing, routes avoid it, and a moderation entry linked to your account is created, erased a year after the moderator's decision.
- Police checks cannot be reported.
Content from other sources
Place pages also show content published elsewhere, each with its source, its author and its licence: photos from Wikimedia Commons and Panoramax, extracts from Wikipedia, the descriptions and photos of tourist offices (DATAtourisme), reviews from Mangrove Reviews. Our servers download them, re-encode the photos without their metadata and serve them themselves: your device contacts none of these sites, and these sites see only our servers.
An external community source. Some places, descriptions, ratings, reviews and photos come from a travellers' community platform, under a written agreement with it. Its reviews carry their author's pseudonym, vehicle and month of visit, its photos their author's name; the platform's author identifier is never shown, and no contact details of its members are collected.
- This data is collected, under that agreement, by our own collection tool, which runs on our main server, in Falkenstein, and keeps its working copy there. It makes files of it and drops them into that server's drop box; the server imports them as soon as they arrive and erases them after 4 days. Each photo is downloaded by our server the first time a device asks for it, then served by our server: the platform sees only our server, never your device or your address.
- For the copy it keeps and shows, Lunaway is a controller, separate from this platform, which is the controller of its own data.
- When the platform removes a place, a review or a photo, our copy loses it at the next import that carries the removal. When it sends us an author's erasure, their reviews and photos are deleted from our main server, their texts are removed from the files the import keeps and, before its next file, from the working copy of our collection tool, and only a hash (SHA-256) of their identifier is kept, without time limit, so that later files do not bring them back. If a failure forced us to bring a backup back into service, the authors' erasures received since its date would have to be applied again by hand; until then, our collection tool, which keeps those hashes, does not send their reviews again.
- If you are the author of one of these reviews or photos, you can write to contact@lunaway.net about our copy, and to the platform about its own.
Your location
If you allow it, the app reads the device's location while you use it, to place you on the map, compute distances, follow sunset, offer your region and, during guidance, follow you and apply the rules of the country you drive in. These calculations run on the device, which keeps only a position rounded to about ten kilometres. The app does not ask for permission to read the location in the background; only guidance you start continues with the screen off, as described in Directions and guidance.
Your location leaves the device in these cases:
- as the start of a route, and of each new route during guidance. None of it is recorded or logged;
- rounded to about 5 km, for the list of the cheapest fuel around you, for the order of the list of places beside the map when the map shows you and, during guidance, for the prices of the fuel stations around the vehicle;
- with a road report: the exact position and your heading, kept for 14 days with your account (see Road reports);
- as the position of a place or a vending machine you add: it is the point you set on the map, and after "Show my position", or when the map opens on you, the map's centre is your position. It is kept with your proposal (see What you publish);
- as your home, if you set it at your current position: it is kept on the device and, if you have an account, with it;
- indirectly: through the region asked for at the first launch, through the pieces of map asked for when the map is centred on you, through a route's line sent for the "On the way" list, which starts 2 km ahead of you, and through the places near the route whose photo the app asks for during guidance. The log keeps only the zoom level of the pieces of map, and nothing of the line or of these places.
Confirmations, reports about places, roadworks and danger zones hold no position of the device. Searches carry the map's centre rounded to about 5 km, which is your rounded position when the map follows you; for an address search, that point also goes to IGN. You can withdraw the permission at any time in the system's settings.
Taking a place down
If a place on the map shows your home or concerns you, write to contact@lunaway.net. When we take a place down, its details, reviews, photos, confirmations and reports are deleted. So that a backup brought back into service or a new import does not bring it back, the takedown is noted in a journal kept apart: the place's identifier, the date, a short reason (private home, GDPR, court decision, other) and keyed hashes of the area, without name, position or the text of the request. This journal is kept without time limit and copied, encrypted, with the backups. A new place proposed near a place taken down waits for a moderator. In the web app, a place taken down may still show for one more visit, the time it takes the page to read the new version of the map.
Logs and abuse limits
Like any web server, ours note the requests they receive, for security and troubleshooting:
- The access log notes the date, the method, the server's name, the path asked for without its parameters, the response and its duration, and the headers sent by the app or the browser (the version of the app and of the system, the processor type or the device model for the basemap, the browser and its language), with a truncated IP address: the first two numbers of an IPv4 address (203.0.113.7 becomes 203.0.0.0), the first 32 bits of an IPv6 address. It notes neither the port, nor cookies, nor session tokens, nor the content or size of requests, nor the area of the pieces of map, nor the address of photos, nor the name of the regions downloaded. A new file starts every day, and each line is erased after about 14 days.
- The servers' system journal (starts, errors) also receives the web server's lines, with addresses truncated the same way. Our API writes into it, for a failed request, its method and path; for each route, its computing time and its outcome; for a search or a translation that fails, the service involved or the two languages; for a photo from another source that fails to download, its identifier. Neither the API nor the routing engine writes a position, a searched text or a translated text into it. The files of this journal are erased after six weeks at most.
- The abuse limits (number of requests, searches, translations, sign-ins, account creations, recovery code attempts) count per IP address, or per block of addresses in IPv6, in the server's memory only: they are never written, and a restart resets them.
Backups
To bring the service back after a failure, the database is copied every night, and so is each new photo:
- on the main server, for 3 nights: unencrypted on its data disk, and encrypted with age on its system disk and in the folder where the publisher's computer comes to fetch them;
- encrypted with age, on a computer belonging to the publisher, the only holder of the decryption key, which fetches them every night directly from the main server and keeps them for 30 days. The server and the computer erase copies that are too old during their nightly task, which the computer also runs at start-up if it was off.
Anything deleted from the database thus leaves every backup within about 30 days, longer only if that computer stays off, until it starts again. The encrypted copy of a deleted photo leaves the main server the same night, and the publisher's computer after 26 days.
The deletion of an account is also noted, with the account's identifier and the time (and, for a merged account, the identifier of the account that received it), in a journal kept apart from the copies of the database, for 45 days at most; an encrypted copy of it is made every hour on the server, and the publisher's computer fetches it every night, in place of the previous one (46 days at most, longer on that computer while it stays off). If a failure forces us to bring a backup back into service, the account deletions made since its date are applied again before it goes back into service. Only one failure escapes this: the loss of the server itself, its system disk and its data disk together. The accounts deleted after the last copy fetched by the publisher's computer (up to about 25 hours, longer if that computer stays off) would then come back with the backup.
Hosting and service providers
- Hetzner Online GmbH (Germany) hosts our main server in its Falkenstein data centre: the API, the database, the photos, the routing engine, the basemap, the address geocoding server and the translation server, which keep nothing of the searches or the texts, this site, the status page, and the collection tool of the external community source with its working copy. Temporary Hetzner servers build the road graph every two weeks from open data, with no user data.
- IGN (Institut national de l'information géographique et forestière, France) receives from our server, for each address search, the text searched and the map's centre rounded to about 5 km, without your IP address or any identifier, and answers with the addresses of the Base Adresse Nationale.
- Infomaniak Network SA (Switzerland) receives the e-mails sent to contact@lunaway.net. Switzerland is covered by an adequacy decision of the European Commission.
- Cloudflare runs the domain names of lunaway.net, as DNS only: it gives our servers' address, then the traffic goes straight to us, without passing through it.
- GitHub hosts the source code and the road graph files our server downloads. No user data goes there.
Our servers also download the open data and the content the app shows (OpenStreetMap, public datasets, Wikimedia, Panoramax, DATAtourisme, Mangrove Reviews, the external community source); these requests carry no user data. The basemap is built by Protomaps from OpenStreetMap, then copied and served by our own server. Neither the app nor this site loads a map, a photo, a font or a script from another host. If you install Lunaway through Google Play, F-Droid or the App Store, those services handle the download's data under their own rules.
We neither sell nor rent any data, and pass none on for advertising or another commercial use. The text and the rounded point of address searches, sent to IGN as described above, are the only data from the app that our servers pass to a third party.
How long data is kept
| Data | Kept |
|---|---|
| Account: public keys, pseudonym, level, synced favourites, home, muted authors | until the account is deleted |
| Sessions | 60 days after their last use |
| Ratings, reviews, photos, places added or edited | until they or the account are deleted; some then stay without author (see Delete my account) |
| "Still there?" confirmations of places | 2 years, or until they or the account are deleted if that comes first |
| Answers about shops and services | 1 year, or until they or the account are deleted if that comes first |
| Problem reports about places | 90 days, or until they or the account are deleted if that comes first |
| Road reports | 14 days, or until the account is deleted if that comes first |
| Reports of content, moderation decisions | 1 year after the decision |
| Content of a rejected or withdrawn proposal | 30 days after the decision |
| Technical keys of contributions sent | 30 days (14 for a road report), or until the contribution is deleted |
| Translations of a review or a description | as long as the original text exists and does not change |
| Hashes of the keys of a banned account that was then deleted | 2 years |
| Hashes of the keys of an account merged into another | 1 year; if the account that received it is banned, as long as it is, then 2 years after its deletion |
| Hash of the identifier of an external community source author erased at their request | without limit |
| Files of the external community source in the drop box | 4 days |
| Working copy of the collection tool of the external community source | For each place of the platform, its page as published: name, position, descriptions, services, practical details (prices, pitches, opening, height), rating, the addresses of its photos and its 200 newest reviews (pseudonym, date, rating, text, vehicle). Kept as long as the platform publishes the place, and read again about every 30 days, sooner when the platform shows a change on it: a review the platform removed leaves the copy at that reading. When the platform removes a place, its reviews and the rest of its page leave the copy as soon as the tool sees the removal; only its identifier and the summary the platform's map showed remain. An author erased at our end leaves the copy as soon as the tool reads our list of erasures again, before each of its files: every 3 hours while it collects, at least once a day. Their reviews are no longer kept, and only the hash of their identifier remains. The last file sent stays on that server until the next one. |
| Routes, searches for places, addresses, shops and fuel, list of places beside the map, "On the way" | nothing is kept |
| Access log | about 14 days |
| System journal | 6 weeks at most |
| Abuse counters | in memory, from one minute to one day, erased at each restart |
| Backups | about 30 days (see Backups) |
| Journal of account deletions: identifier of the deleted account and time | 45 days at most (46 in its copies) |
| Journal of places taken down, without personal data | without limit |
| E-mails received at contact@lunaway.net | the time it takes to handle your request |
| Data on your device | until the app is uninstalled, or the site's data is cleared in the browser; place pages and photos already opened, 90 days after they were last opened |
Legal bases
- Providing the service you ask for (article 6(1)(b) of the GDPR): syncing places, searches, translations, directions and guidance, the search for shops and fuel, the account, your contributions, your synced favourites.
- Our legitimate interest in protecting the service and its users (article 6(1)(f)): logs, abuse limits, moderation, the weighing of road reports, backups, the deletion and takedown journals.
- Our legitimate interest in showing travellers the reviews and photos published about places (article 6(1)(f)): the content of the external community source and of the open sources, with the names of their authors that their licences ask us to credit.
- Your consent, given to the system, for reading the device's location (article 6(1)(a)): you can withdraw it at any time.
Your rights
The GDPR gives you the right to access your data, to have it corrected or erased, to restrict its use, to object to its processing and to receive it in a reusable format.
- In the app, your profile shows your pseudonym, which you can change, your level, your devices and your contributions, which you can delete one by one.
- You can delete your whole account in the app or with your recovery code.
- For any other request, write to contact@lunaway.net. We answer within one month.
Your account is linked to no e-mail address: before answering a request, we must check that the account is yours, for instance by asking you to change your pseudonym in the app to a word we give you.
If you believe your rights are not respected, you can lodge a complaint with the French data protection authority, the CNIL, online at cnil.fr or by post: CNIL, service des plaintes, 3 place de Fontenoy, 75007 Paris, France. You can also contact the authority of the EU country where you live.
Audience and changes
Lunaway is meant for adults.
When this policy changes, the new version appears on this page with its date. The page's history is public in the code repository, at tool/site/src/pages/en/privacy.html.