Last updated:
This policy explains what personal information Roadbooker collects through the roadbooker.co.za website and its trip planner, why, how long we keep it and what your rights are. We wrote it in plain language. It follows the Protection of Personal Information Act 4 of 2013 (POPIA).
The short version
- This covers the roadbooker.co.za website and the Roadbooker Android app. It is one service with one account.
- We store your email address, a scrambled (hashed) password, and the trips, bookings and PDF documents you add, so we can show them back to you.
- Trips are location data. Our admin tools don't show their contents, and nobody else sees a trip unless you invite them or turn on a share link.
- A share link shows a read-only route, days and overnight stops. It never shows your costs, bookings or documents. You can turn it off at any time.
- The app uses your phone's location on the phone to guide you. Your live position isn't sent to us.
- Roadbooker PRO is paid through Google Play. We never see your card details; we keep only the purchase token and its status.
- We send account emails through Google's Gmail service.
- No advertising and no tracking cookies. The site sets two cookies, only to log you in securely. It counts visits with a one-day anonymous code: we keep no IP address for this, set no cookie for it, and can't follow you from one day to the next (section 3, "Counting visits"). If you sign up after following one of our own campaign links, we note that link's name once, with your new account, to count sign-ups (section 3).
- You can delete your account and all your data yourself at any time, or ask us to. We'll do it within 7 days.
- You can ask us for a copy of your data, by email. Questions: roadbooker@gmail.com.
1. Who we are
The Roadbooker website and app are run by App to Something (Pty) Ltd, a South African company. Under POPIA we are the "responsible party" for the personal information described in this policy. In this policy, "Roadbooker", "we", "us" and "our" mean App to Something (Pty) Ltd.
- Registration number: 2026/477391/07
- Registered office: Unit 1, Eucharistia, 8 Paul Kruger Street, Durbanville, Cape Town, Western Cape, 7550
- Email: roadbooker@gmail.com
- Our Information Officer is Andries Jacobus Welgemoed, a director of App to Something (Pty) Ltd. You can reach him at roadbooker@gmail.com.
Use the email address above for any privacy question or request.
2. What this policy covers
This policy covers the roadbooker.co.za website, including the trip planner and planner accounts, and our map and routing server at api.roadbooker.co.za.
This policy also covers the Roadbooker Android app (com.roadbooker). The website and the app are one service with one account: you sign in to the app with the same email address and password as on the website, and your trips are the same trips in both. Everything in sections 3 to 16 applies to the app too. This is the privacy policy for the app in Google Play.
What the app adds
- Location: the app uses your phone's location while you use it to show where you are and to guide you on a route. While you navigate, it keeps running with a notification on your screen. The app doesn't ask for location in the background. Your live position is used on your phone and isn't sent to us. If you record a track, it's saved on your phone and added to your trip when you're online, and then it's part of your trip like any other route (section 3).
- Offline copies (Roadbooker PRO): trips and map areas you save for offline use are stored on your phone, and are removed when you delete them, sign out or uninstall the app.
- Routing requests: when the app asks us for a route, our server handles the request as described in section 7.
- No analytics, no advertising: the app has no analytics or advertising tools, and doesn't sign you in through Google or Facebook.
- Deleting your data: you can delete your account and all your data on the website, on your account page (section 11). If you delete the account, the app signs out.
- Older app versions: versions of the app before 2.0 used a separate account kept with Google (Firebase). Those versions are being retired. Email us if you'd like anything from an old app account deleted.
3. What your planner account stores, and why
We store the information below only to run the trip planner for you and to keep your account secure. We don't use it for advertising, we don't sell it and we don't build profiles of you.
Your account
- your email address, and whether you've confirmed it
- the display name you choose. It doesn't have to be your full or real name.
- your password, stored only as a one-way scrambled value (an Argon2id hash). We never store or see the password itself.
- the version of the terms you accepted, and when
- when you created the account, last logged in and last changed your password
- account security state, such as failed log-in counts and temporary locks
- how much storage your documents use
- an email address you've asked to change to, until you confirm it
- if you followed one of our own campaign links (a web address with
utm_details after it, for example from an advert) before you signed up, the campaign's source, medium, name, content and term, up to five short labels, noted once when you create the account. We use them only to count how many sign-ups each campaign brought. They are not shared, are not matched to your activity and are not used to follow you around. If you sign up without such a link, nothing is noted.
You must confirm your email address before you can log in. If you never confirm it, we delete the sign-up after 7 days.
Trips and routes
Your trips hold trip names, descriptions and dates, days, start and end points, stops and overnights, routes, vehicles and their fuel range, the number of people travelling and your notes. This is location data. It can show where you'll be, when, and where you'll sleep, and it may include your home address if your trip starts there.
Route calculation: to work out a route, your trip's points are sent to our own routing server, on the same machine as the rest of Roadbooker. They don't go to Google Maps or any other outside service.
GPX export: when you download a trip as a GPX file, our server builds the file from your saved trip and sends it to you. We don't keep a copy of the file.
GPX import: when you import a GPX file into a day, the website reads the file on your device and shows you its tracks. If the file has several, you choose one. Only that track's line (its points, in order) and its name are sent to us and saved as the day's route. The file itself is never uploaded or stored, and we never read or keep the times or elevations in it. To estimate the drive time, our server routes through a few points of the track on our own routing server (section 7). If a file is sent to our server instead, for example by the Roadbooker app, a restricted program reads it in memory, keeps only the same line and name, and never writes the file to disk. An imported track is saved like the rest of your trip: until you replace or remove it, or delete the trip or your account.
Place search: when you search for a town, camp or lodge, or click the map to name a point, what you type and a map position (used to show nearby places first) are sent to our own server. It answers from its own copy of OpenStreetMap place names. Searches don't go to any outside service, and we don't store them or write them to our logs (section 7).
Bookings and contacts
For each overnight or stop you can record a booking: the provider's name, phone number and email address, a reference number, check-in, check-out and gate times, amounts, the currency, payment and cancellation dates, and notes. Provider contact details are usually a business's details, but they can be a person's. Only enter details you have the right to use (see our Terms & Conditions).
Documents (PDF only)
You can attach PDF files to a booking, such as a booking confirmation or a permit. We store the file, its name, size and a fingerprint (checksum) that we use to check it hasn't been damaged. Each file can be up to 10 MB, a booking can hold up to 10 files, and your account up to 200 MB in all. Only PDF files are accepted: our server checks every upload to make sure it really is a PDF, and turns away anything else.
Documents often contain other people's names, ID or passport numbers, or vehicle details. They're stored in a private folder on our server that isn't part of the website. Only you and the members of that trip can download them, after logging in, and our team can't open them through our admin tools. Documents added by a member count towards the trip owner's storage.
Deleting a document, its booking, its trip or your account deletes the file too. The file is removed from the server as soon as the deletion is done, and at the latest in our nightly clean-up. The database safety copies in section 4 don't contain the files.
Share links
You can turn on a share link for a trip. The link is a long random address (roadbooker.co.za/s/ and a code). Anyone who has it can open a read-only view of that trip, without logging in. The view shows the trip's name, summary and dates, the number of people, your vehicles' names and fuel range, the route and map, the days with their distances and times, overnight stop names and their check-in, check-out and gate times, warnings and fuel stations. It never shows costs or payments, booking references, providers' phone numbers or email addresses, booking notes, documents, deadlines or anything about your account. Your day notes are included only if you tick "Include day notes", and a GPX download (never with booking details) is offered only if you tick "Let people download GPX".
For each link we store its settings, when it was made, how many times it was opened and when it was last opened. We don't record who opened it. We keep only a scrambled version of the link's code to find it, and ask search engines not to list shared pages. Turning sharing off stops the link working at once, and resetting it replaces it with a new one (the old one stops working). A turned-off link is kept as a record that it's off for 30 days, then deleted. Anyone with the link can pass it on, so only share it with people you trust: a trip shows where you'll be and when.
Trip members and invites
You can invite other people to a trip by entering their email address and choosing whether they can edit it or only view it. We store the address, the role you chose, who sent the invite and when, and send one invitation email. You can resend it twice. The address is deleted when the invite is accepted, cancelled or expires after 7 days, or 7 days after it's declined. If the person accepts, they join with their own Roadbooker account.
Members of a trip can see everything in it, including bookings, documents and day notes, and editors can change it. Everyone on a trip sees the other members' display names and roles, and who last changed the trip. The trip's owner also sees members' email addresses. Members never see your other trips or your account details.
If someone invites your email address and you don't want it, ignore the email: we don't create an account for you. You can also ask us to stop all trip invites to your address. We then keep only a scrambled code made from the address (not the address itself) so that we can recognise it.
Roadbooker PRO and billing
Roadbooker PRO is a monthly subscription that you buy in the Android app through Google Play. Google takes the payment: we never see or store your card or other payment details. Google Play tells us about your subscription, and we store only what we need to know whether PRO is switched on for your account:
- the purchase token Google gives us for the subscription (a code, not a card number), the product, and the subscription's status and dates (for example active, cancelled, on hold or expired)
- a link between that purchase and your Roadbooker account, so that PRO follows you to any phone you sign in on
- a note, if we switched PRO on for you ourselves
We use this only to give you PRO and to deal with refunds and billing questions. Google handles your payment under its own terms and privacy policy. Our team can see whether PRO is on for an account, but not any payment details. Billing records are deleted when you delete your account. Google keeps its own purchase records, which we can't delete.
Sessions and log-in attempts
- Sessions: when you log in, we record the session's start time, when it was last used, the IP address at log-in and your browser's description (user agent). This powers the "Signed-in devices" list on your account page, where you can log any device out. We store only a scrambled version of the session code.
- Trusted browsers: when you log in, your browser also gets a security cookie that marks it as one you've logged in from (section 8). We don't keep a list of these browsers. If a log-in from one of them fails, we count the failure against that browser for 15 minutes.
- Log-in attempts: for each attempt we record a scrambled code made from the email address entered (not the address itself), the IP address, the time and whether it worked. We use this only to lock out password-guessing and to block abuse.
- Email links: the codes in confirmation and password-reset links are stored only in scrambled form, and each one works once.
Emails we send you
We send emails only about your account: confirming your address, resetting or changing your password, changing your email address, security notices such as a temporary lock, and confirming that your account was disabled. We also send an invitation to a trip, when another user invites your address, and a notice when a trip is handed over to you. We don't send newsletters or marketing. Before an email goes out, our server holds it in a queue (the "outbox"). As soon as it's sent, or if it can't be delivered, we wipe the message text and keep only the address, subject, type and delivery status, for 7 days (30 days if delivery failed), so that we can see whether it was delivered. Section 5 explains how Google handles these emails.
Security audit log
We keep a log of security events, such as sign-ups, log-ins, password changes, accounts being deleted, invites and changes to who can see a trip. Each entry holds the type of event, the time, your account's internal ID number, the IP address and your browser's description. It never holds your email address, password or trip contents. We use it to investigate abuse and account takeovers, and to show what happened if something goes wrong.
What our team can see
Our team uses command-line admin tools on the server. They show your email address, display name, account status and sign-up and last log-in dates. They never show the contents of your trips, bookings or documents, and there is no admin tool that opens them. We may disable an account that breaks our terms. Disabling an account doesn't delete its data.
Our administrator can see the list of accounts (email address, display name, whether the email address is confirmed, sign-up date, when the account was last active on the website or in the app, its role, and how many trips each account owns or has been shared with it) to run, support and improve the service. It is never used for marketing.
Usage statistics (counts only)
To run and improve the service, our owner can open a statistics page that shows totals, for example how many accounts and trips there are, how many people used the website or the app in the last day, week or month, how many trips are shared and how many invites are sent and accepted, how many GPX files were exported, how many visitors the website had, and how many visitors and new accounts each campaign link brought. Our server adds these up from the information it already holds, plus a count of GPX exports for each day, and keeps only the totals, one set of numbers for each day. The totals contain no names, email addresses, trips, routes, places or any other detail about a person. The overall totals are shown as plain counts. A breakdown that could single someone out is not shown when it covers fewer than 5 people: trips by country are listed only for countries with at least 5 people, and accounts deleted are shown only as a total for each finished calendar month, rounded to the nearest 5. Only an administrator can open the page, after logging in and confirming their password, and every visit is recorded in the security audit log. It uses no extra cookies and nothing extra from your browser or the app. How visitors are counted is explained next.
Counting visits
To see how many people visit the website, and which of our own campaign links bring them, each public page (the home page, the sample trip, the sign-up and log-in pages, these legal pages and shared trip pages) sends one small message to our own server when it opens. It holds only the page's address (a shared trip's secret link code is replaced by a placeholder before it is sent) and, if you arrived through one of our campaign links, that link's utm_ labels. It sets no cookie and saves nothing on your device. It is not sent from your account pages, the trip editor or the administrator pages, and it is not sent, or is ignored, if your browser has Do Not Track or Global Privacy Control switched on. Known search-engine, link-preview and other automated visitors are not counted.
When the message arrives, our server briefly sees your IP address and your browser's description (user agent), as it does for every request. It mixes them with a random secret that exists for one day only, keeps just the scrambled result, and does not keep the IP address or the user agent. At the end of the day the secret is deleted, so nobody, including us, can turn the scrambled code back into an IP address or recognise the same visitor on another day. The code is stored with the date, the kind of page (for example "sample trip" or "sign-up") and any campaign labels, so each visitor is counted once a day. After two days the codes are deleted and only daily totals remain: how many visitors and visits there were that day, for the whole site and for each campaign link. The totals contain nothing about a person. The same server request also appears in the web server's access log, which is kept separately for 14 days (section 7).
4. How long we keep it
| Information | How long |
|---|---|
| Account details | While your account exists. Sign-ups that are never confirmed are deleted after 7 days. |
| Anonymous visit codes (the scrambled one-day code, the date, the kind of page and campaign labels) | 2 days, then deleted. The secret that makes the codes is deleted at the end of each day. |
| Daily visit totals (how many visitors and visits, for the whole site and for each campaign link) | 13 months, then deleted |
| The campaign link details noted at sign-up | With the account: deleted when the account is deleted, or after 7 days if the sign-up is never confirmed |
| Trips, routes (including imported GPX tracks) and bookings | Until you delete them, or your account is deleted |
| Share links | Until you turn the link off or reset it, or delete the trip or your account. A turned-off or replaced link is then kept for 30 days, and deleted. |
| Trip invites | Until accepted or cancelled, at most 7 days; a declined invite 7 more days |
| Trip memberships | Until you leave or are removed, or the trip or your account is deleted |
| Requests to stop trip invites | Until you ask us to lift them |
| PDF documents | Until you delete them, their booking or trip, or your account |
| PRO purchase records (purchase token, status and dates) | While your account exists. Deleted when your account is deleted. |
| Sessions | Until you log out, or 1 day after the session expires. A session expires after 14 days without use, and after 30 days at most. |
| Email link codes | 7 days after they're used or expire (a reset link expires after 60 minutes, a confirmation link after 24 hours) |
| Log-in attempts | 30 days |
| Email outbox | Message text wiped when sent, or when delivery fails. The address, subject and status are kept for 7 days, or 30 days if delivery failed. |
| Security audit log | 180 days |
| Daily usage totals | Kept without a time limit: they contain no personal information |
| Copies of account emails in our Gmail sending mailbox | Deleted shortly after sending, usually within minutes |
| Website and server access logs | 14 days |
| Application logs | 30 days |
| Routing server logs | Errors and warnings only, with no record of individual routes (section 7) |
| Emails you send us | As long as we need them to deal with your request, and no longer than 12 months after we've finished with it |
Disabled accounts: if we disable an account, we keep its data so that the decision can be reviewed. If it's still disabled after 12 months, we delete it and all its data, and we email the account's address 30 days before we do. You can ask us to delete it sooner (section 11).
Safety copies: before each software update, we take a copy of the database so that we can undo a faulty update. These copies are kept for at most 7 days, so anything you delete is gone from them within 7 days.
5. Emails, and Google as our email provider
We send account emails through Google's Gmail service. They come from Roadbooker <apptosomething.ltd@gmail.com>, and replies go to roadbooker@gmail.com. Emails you send to roadbooker@gmail.com are also held in Gmail.
- What Google receives: your email address, your display name (only once you've confirmed your address), and the email itself. Our emails never contain your password or your booking details. Links in them carry a one-time code that expires.
- Google as our operator: Google delivers these emails for us. Our sending mailbox is a standard Gmail account, so Google handles the emails under its own terms, privacy policy and security commitments. We don't have a separate written data-processing agreement with Google.
- A transfer outside South Africa: Google's servers are in the United States and other countries. This is a cross-border transfer under POPIA section 72. We rely on section 72(1)(c): sending these emails is necessary to provide the account you asked for, because an account can't work without a confirmed email address, a way to reset your password and security notices.
- Copies in Gmail: Gmail saves a copy of every email it sends. Copies of account emails are deleted from our sending mailbox shortly after sending, usually within minutes, and a daily check removes any that were missed. They're deleted permanently, not just moved to the bin. Our own server also wipes the message text as soon as the email is sent (section 3).
- No tracking in emails: our emails come with a plain-text version and a formatted version. They contain no tracking pixels and no tracked links, so we don't know whether or when you open them or click a link. Each email carries a random reference code in its technical headers. Our server uses it only to find and delete its own copy in the sending mailbox. The code contains no information about you, and it can't tell us whether you've opened the email. The Roadbooker logo in the formatted version is loaded from our own website when your email app shows images. That request appears in our access logs like any other (section 7).
6. Where your information is stored
Our website, database, documents, map and routing server is rented from Hetzner, a hosting provider, in its Nuremberg data centre in Germany (European Union). Your account, trips, bookings and documents, our logs and the beta email list (section 10) are stored there.
Storing information in Germany is a transfer outside South Africa. POPIA (section 72) allows this where the receiving country has laws that give substantially similar protection. Germany is bound by the EU General Data Protection Regulation (GDPR), which meets that standard. Hetzner only provides the server. It acts on our behalf as an "operator" under POPIA.
The only other outside service that handles your information is Google, for email (section 5). The website itself loads nothing from outside services: fonts, software libraries, map tiles, routes and place search all come from our own server.
About once a month, our server downloads public OpenStreetMap map data, which includes place names, from Geofabrik, a map-data download service. That download sends no information about you or your trips.
7. Server logs and routing requests
Access logs
When your browser or our app asks our server for a page, a map tile, a route or a file, the server writes a line in its access log. Each line holds your IP address, the date and time, the address requested and whether it worked, your browser's description (user agent) and, for website pages, the page that linked to it (the "referrer"), if your browser sends one.
We keep secrets and locations out of these logs:
- The codes in confirmation and password-reset links sit after a "#" in the address, so they never reach our server.
- The website sends route points inside the request, not in the address, so they're never logged.
- The Roadbooker app asks our routing server for routes directly. For those requests, the list of coordinates is cut from the logged address.
- For place searches, the search text and the map position are blanked out of the logged address, so only the fact that a search happened is kept.
- The code in a share link is replaced by a placeholder in the logged address (and in the referrer), so a share link is never written to our logs.
One exception: if our routing server fails or restarts while a request is in progress, or our planner software is down during a place search, the web server's error log can record that failed request, including its coordinates or search text. Error logs are also deleted after 14 days.
Access logs are rotated daily and deleted after 14 days.
Application logs
Our planner software logs each request's type (for example "open a trip"), result and timing, with your account's internal ID number. It never logs email addresses, passwords, codes, coordinates, booking contents, document names or what you type, including place searches (it counts the results, nothing more). These logs are kept for 30 days.
The routing engine
Routes for the website and the app are calculated by OSRM, routing software that runs on our own server. We've set it to log only warnings and errors, so it doesn't keep a record of the routes people ask for. Apart from the short-lived access logs above, routing requests aren't stored. The only routes we keep are the ones you save in your trips.
Why we keep logs
We use logs only to keep the service running, to fix faults and to spot and block abuse. We don't use them to profile people, and we don't combine them with other information to work out who someone is.
8. Cookies and browser storage
The website sets two cookies, both only when you log in. Neither can be read by page scripts, both are only ever sent over HTTPS, and both are only sent to roadbooker.co.za.
| Name | What it does | How long |
|---|---|---|
__Host-rb_session | Keeps you logged in. It holds a random code and nothing else. | Until you log out, after 14 days without use, or after 30 days at most |
__Host-rb_dev | Marks this browser as one you've logged in from. If someone else keeps guessing your password and your account is locked, you can still log in from here. It holds a random code and a check value made from your account's internal ID number, nothing else. We don't store it on our server. | 1 year. It stops working as soon as your password is changed or reset. Logging out doesn't remove it. |
Both cookies are strictly necessary: one to log you in, the other to keep your log-in secure. So we don't ask for consent and there's no cookie banner. We use no analytics, advertising or tracking cookies. If you use a shared or public computer, log out and then clear the browser's cookies for roadbooker.co.za. You'll still be able to log in from that browser later.
The website also keeps one setting in your browser's own storage (localStorage): rb.basemap, your choice of a dark or light map. It contains no personal information and is never sent to us. The website never saves what you type in your browser's storage.
If you arrive through one of our campaign links, the page also remembers the link's utm_ labels (source, medium, campaign, content and term) in your browser tab's own storage (sessionStorage) for up to 24 hours, only so that they can be sent with your sign-up and with the anonymous visit count (section 3). They contain no personal information, are not sent anywhere else, and go when you close the tab. Counting visits itself stores nothing in your browser.
Our private admin area, which our own team uses to upload map and routing data, has its own strictly necessary log-in cookie. It's only ever set for our team.
9. Location data, GPX files and sharing safely
A trip or a GPX file can show where you'll be, when you'll be there and where you'll sleep. Please think before you share:
- Files you export: once a GPX file or printout is on your device, it's in your hands. Before sharing a file publicly, consider removing your home address or exact camp spots.
- Share links: anyone who has your link can open the shared view, and can copy the link or pass it on. Share it only with people you trust, and turn it off when the trip is over or if it reaches someone it shouldn't.
- Files you import: a GPX file you import on the website isn't uploaded or stored. Only the line of the track you choose and its name are saved with your trip (section 3).
- Sample files: the sample trip, sample GPX and ZIP downloads on this website describe a fictional trip on real roads. They hold no information about you.
10. Closed beta sign-up emails (no longer collected)
Earlier in 2026, the page roadbooker.co.za/beta invited testers to apply for the Roadbooker app's closed beta on Google Play. That page has been retired and now redirects to the home page. It no longer collects anything.
- What we hold: a short list of the email addresses people entered on that page, each with the date and time it was submitted. That's all. No names, passwords or other details were collected.
- Why we hold it: the beta page asked for the Gmail address linked to your Google Play account so that we could invite you to the closed testing group. We keep the list only to manage those invitations and to contact testers about the beta. We don't use it for marketing and we don't sell or share it. If you were invited to the closed beta, your address may also have been added to the Google Play Console testers list, where Google holds it under its own privacy policy.
- Separate from planner accounts: being on the beta list doesn't create a planner account, and we don't use the list to create or contact planner accounts.
- Where it's kept: on our server (see section 6), readable only by us.
- How long: We will delete the beta list when the closed beta ends, or sooner if you ask.
- Want it deleted now? Email roadbooker@gmail.com from the address you signed up with, or tell us which address it was, and ask us to delete it. We'll remove it and confirm. If you're still in the testing group, deleting your address may mean we can't send you beta updates.
11. Your rights, and how to use them
See and get a copy of your information (access)
Everything in your account is visible to you in the planner. You can also email roadbooker@gmail.com from your account's address and ask for a copy of everything we hold about you. That includes your account details, your trips, bookings and PDF documents, the trips you're a member of and the invites you've sent, and, if you ask, your sessions, log-in attempts and security audit entries. We'll send it within 30 days.
Correct your information
You can change your display name, email address and password, and edit or delete any trip, booking or document, or turn a share link off, yourself. If something else we hold about you is wrong, email us and we'll fix it.
Delete your account and all your data
You can delete your account yourself, in the Roadbooker app (Account, then Delete my account) or on the website. On your account page, choose Delete account, enter your password and tick the box to confirm. It's done straight away and we email you a confirmation. This can't be undone, so if you want a copy of your data first, email roadbooker@gmail.com from your account's address and ask us for it before you delete.
If you own trips that you share with others, we'll ask you, for each one, whether to hand it over to one of its editors or delete it. A trip you hand over stays with its new owner, including the documents in it. Trips shared with you aren't deleted. You just stop being a member. Changes you made to them stay in them.
What we delete: your account, all your trips, days, routes (including imported tracks), stops, bookings, documents and share links, your sessions, your email link codes and your log-in attempts. Your document files are removed from the server as soon as the deletion is done, and at the latest in the nightly clean-up.
What's left afterwards, and for how long:
- Our record of the account emails we sent you (your address, the subject and the delivery status, with the message text wiped once sent) is removed after 7 days.
- Security audit entries stay, but with your account link, IP addresses and browser descriptions removed, so they only record that an event happened and when. They're deleted when they're 180 days old.
- Server access logs expire within 14 days and application logs within 30 days. The application logs hold only your account's internal ID number, which no longer leads anywhere.
- Copies of account emails are deleted from our Gmail sending mailbox shortly after sending (section 5). Database safety copies are deleted within 7 days (section 4).
- Emails you've sent to roadbooker@gmail.com stay in that mailbox as described in section 4. Ask us and we'll delete them too.
You can also delete single trips, bookings and documents yourself at any time. If you can't log in, for example because your account has been disabled, email us from the account's address and we'll delete it within 7 days and confirm by email. The steps are also on our Delete your account page, which you can open without logging in.
Your other rights
Under POPIA you also have the right to:
- ask whether we hold personal information about you, and get a copy of it
- ask us to delete information we no longer have a right to keep
- object to us processing your information on the basis of our legitimate interests, such as security logging
- withdraw your consent, where we rely on it (this doesn't affect anything we did before you withdrew it)
- not receive direct marketing you didn't agree to (we don't send any)
- complain to the Information Regulator
To use any of these rights, email roadbooker@gmail.com. We may ask you to confirm your identity first, for example by writing from your account's email address, so that we don't give your information to someone else. We aim to reply within 30 days. There's no charge for a simple request.
Server access logs are deleted after 14 days, and we can't reliably match an IP address to a person. So we may be unable to find log lines about you, or they may already be gone.
Our legal basis
- Your account, trips, bookings, documents, share links and account emails: we need them to provide the planner you signed up for (POPIA section 11(1)(b)).
- Logs, log-in attempts, locks, the trusted-browser cookie and the audit log: our legitimate interest in keeping the service and your account secure (section 11(1)(f)).
- The campaign link details noted at sign-up: our legitimate interest in knowing which of our own campaigns bring sign-ups (section 11(1)(f)). They contain no information about you beyond the link you followed.
- The anonymous visit count: our legitimate interest in knowing how many people visit the website and which of our own campaigns bring them (section 11(1)(f)). The scrambled code can't be turned back into an IP address after the day ends and can't be matched across days, we honour Do Not Track and Global Privacy Control, and only daily totals are kept beyond two days.
- Email addresses you invite to a trip: the legitimate interest, yours and ours, in sending the invitation you asked for (section 11(1)(f)).
- Information about other people that you add, such as a provider's contact details or names in a booking, document or note: you give it to us so that we can show it back to you. We don't use it for anything else.
The Information Regulator
If you're unhappy with how we've handled your information, please tell us first so that we can try to fix it. You can also complain to the Information Regulator of South Africa at any time:
- Website: inforegulator.org.za
- Complaints: POPIAComplaints@inforegulator.org.za
- General enquiries: enquiries@inforegulator.org.za
- Phone: 010 023 5200
- Address: Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191
12. How we protect it
We use reasonable technical and organisational safeguards, as POPIA requires. For example:
- The site is served over encrypted HTTPS only.
- Passwords and every code we issue are stored only in scrambled form.
- Each account can reach only its own trips and the trips it has joined, in the role the trip's owner chose, and only after a log-in check. Documents are stored outside the website, checked when you upload them, and handed out only to the trip's owner and members.
- A share link is a long random code that can't be guessed. The shared view is built from a fixed list of trip details that can't include costs, booking details or documents. Imported GPX files are read in a restricted program with strict limits on memory and time, and are never written to disk.
- Repeated wrong passwords lock the account for a while, except from browsers you've logged in from before (section 8). If it keeps happening, we email you.
- We limit how many account emails we send to one address each day, so that nobody can flood your inbox through our site.
- Access to the server is limited to our team, and our admin tools don't show trip contents.
- Logs are kept for a short time and then deleted.
No system is perfectly secure. If a breach affects your personal information, we'll tell you and the Information Regulator as POPIA requires.
13. Children
This website is meant for adults planning trips. It isn't aimed at children, who under POPIA are people under 18, and you must be 18 or older to create a planner account. If you think a child has created an account or sent us personal information, such as a beta sign-up, contact us and we'll delete it.
If you add a booking or note that names a child travelling with you, you confirm that you're the child's parent or guardian, or have their permission. We use it only to show it back to you.
14. Links to other sites
The website links to other sites, such as the Roadbooker listing on Google Play. Those sites have their own privacy policies, and we're not responsible for how they handle your information.
15. Changes to this policy
We'll update this policy when Roadbooker changes. The date at the top always shows the latest version. If a change significantly affects information we already hold about you, we'll tell you before it takes effect, on the website and when you next log in.
16. Contact
Questions, requests or concerns: roadbooker@gmail.com
Contact: roadbooker@gmail.com