Privacy Policy
Dumb Luck Routes — mobile app (au.com.securehub.dlr) and website.
Effective . Last updated .
The short version
- Your live location is shared only inside a group adventure you joined, only with the members of that adventure, and only if you turned sharing on. The answer starts at no.
- Location sharing does continue in the background, with the screen off. It stops when you turn it off, leave the adventure, or the adventure ends — plus at most a two-hour wind-down if the organiser allowed one.
- We keep no location history. One row per person per adventure, overwritten in place, deleted when sharing stops.
- You can set a private area around home. It never leaves your phone, and nothing inside it is recorded or sent.
- An account is a username and a password. Email, phone number and display name are optional.
- Photos are stripped of all metadata, including GPS, when they are uploaded.
- No advertising, no analytics or tracking SDKs, no data brokers, and we never sell your data.
- You can export everything and delete your account from inside the app: Settings → Data & export.
1. Who we are
Dumb Luck Routes is a group-adventure companion for motorcyclists, drivers, cyclists and walkers. It is operated by Secure Hub (Australia), referred to below as we, us and our. We are the data controller for the personal information described here.
This policy covers the mobile app, the website, and the servers behind them. It is published at https://www.noptic2.com/dlr-privacy-policy.html. Privacy questions and requests go to spam@securehub.com.au.
In this policy an adventure (called a group ride on some screens in the app) is a time-boxed group that people join with a code from the organiser, or by asking and being admitted.
2. What we collect and why
The guiding rule is that we collect the least that makes the app work. A usable account is a username and a password; everything in the "optional" column below can be left empty, and the app works without it.
| What | Why we have it | Optional? | Who else can see it |
|---|---|---|---|
| Username | Signing in, and the label on your marker on the map | Required | Members of adventures you join |
| Password | Signing in. Stored only as a salted hash — we never hold the password itself | Required | Nobody |
| Email address | Password reset, account recovery, service notices, the inactivity warning below | Optional | Nobody, unless you switch share email on — then co-members only |
| Phone number | So people you are travelling with can reach you | Optional | Nobody, unless you switch share phone on — then co-members only |
| Display name and marker colour | How you appear in a member list and on the map | Optional | Co-members (display name only if you switch it on) |
| Precise location | Showing you on the live map of an adventure — see section 3 | Optional, off by default | Members of the adventure you turned sharing on for |
| Recorded tracks and imported GPX files | Your own ride history, statistics and the track editor | Optional | Nobody — private by default, unless you create a share link |
| Photos | Attaching to a map marker or a post in an adventure's thread | Optional | Members of that adventure |
| Comments, marker notes, poll answers, reactions | The thread and the markers of an adventure | Optional | Members of that adventure |
| Device record: a name, whether it is a phone or a browser, when it was created and last seen | Session management, so you can see and revoke your signed-in devices | Required | Only you |
| The IP address you registered from | Abuse and spam-registration throttling. Deleted after 30 days | Required | Nobody |
| Web-server access logs (IP address, time, request path) | Security, abuse prevention and diagnosing faults | Required | Nobody |
| Content reports you submit | Acting on reports of objectionable content | Optional | The adventure's organiser and us |
What we do not collect. No advertising identifier. No analytics, crash-reporting or attribution SDK — the app contains none. No contacts, no calendar, no microphone, no health data, no Bluetooth. We do not build a profile of you, we do not track you across other apps or websites, and we do not sell or rent personal information to anyone.
3. Location, in detail
Location is the reason this app exists, so this section is specific.
When it is collected
- Location is only sent to our servers while you have turned sharing on for a specific adventure. Sharing is asked for when you join, and the answer starts at no. Dismissing the prompt is a no.
- Sharing is per adventure, not global. You can be sharing with one and not another, and the member list shows who is sharing and who is not.
- There is no always-on friend tracking in this app, and no way to switch it on.
- Recording a track for yourself is separate, and also opt-in. A recorded track lives on your device and in your own account, and is private unless you share it.
Background collection
While sharing is on, the app collects location in the background — that is, even when the app is closed or not in use, and with the screen off. That is the normal case: someone travelling is not holding their phone, and without it the map goes stale for everyone else at exactly the moment they need it. Before the operating system asks for permission, the app shows its own explanation and asks you to agree or cancel.
Background collection stops when you turn sharing off, leave the adventure, sign out, revoke the device, or the adventure ends. On Android an ongoing notification is shown the whole time sharing is active; on iOS the system's blue location indicator is left on. If you grant only "While Using the App", the app still works — updates stop when it is backgrounded and resume when you return to it.
What is stored, exactly
One row per person per adventure, holding your latest position, and overwritten in place. There is no location history table. No trail is kept, and no journey can be replayed from what we store.
Turning sharing off deletes that stored row rather than merely stopping the broadcast — a last-known point sitting in a database is exactly what someone turning sharing off is asking us not to keep. The same happens when you leave an adventure, when an organiser removes you, and when the adventure ends. If you are not sharing with an adventure, there is no row for you in it at all — hidden or otherwise.
The wind-down
When an adventure ends, an organiser may allow a short wind-down so people can watch each other get home. It is capped at two hours, cannot be extended, and is enforced by the server, not by the app. You can end your own sharing at any point during it. An organiser can stop sharing for everyone; an organiser can never switch your sharing back on.
The private area
You can set a circle around home — Settings → Location. Inside it, nothing is recorded and nothing is sent: the fix never becomes a stored row and never reaches our servers. Co-members see you as present in the adventure with no position on the map.
The circle itself never leaves your device. We are not told where it is, how big it is, or whether you have set one at all. The cost of that is stated in the app: it does not follow you to another phone, and reinstalling the app forgets it.
4. Photos, comments and markers
Adventures carry user-generated content: a thread with text, photos, pinned posts, reactions and polls, and map markers with an icon, a title, a note and a photo. It is visible to the members of that adventure and to nobody else.
- Photo metadata is destroyed on upload. Every image is re-encoded on our server with no metadata written at all — EXIF, GPS coordinates, camera and device identifiers, and colour profiles are gone from the stored file. This happens before the photo is visible to anyone.
- Measured location is deleted; what you wrote is kept. Markers and comments survive after an adventure ends, because you deliberately wrote them. You can delete your own content, and deleting your account removes it.
- Reporting. Objectionable content can be reported with the flag control on a comment. Reports reach the organiser and us, and we act on them. Report anything urgent directly to spam@securehub.com.au.
- Blocking. An organiser can decline and block a join request; blocked accounts are listed and can be unblocked at Settings → Blocked riders.
5. What stays on your device
Some things never reach us at all, and are removed if you uninstall the app:
- The private area — its centre, its radius, and the fact that one exists.
- Your app settings: theme, map style, GPS accuracy profile, route display.
- Downloaded offline map packs.
- Your sign-in token, held in the platform keychain (iOS) or encrypted storage (Android).
- Tracks you are recording, until and unless they sync to your account.
6. Who your data is shared with
Other people
Within an adventure you joined: your username, your marker colour, your live position while you are sharing, your distance along the route, anything you post, and any optional profile field whose sharing switch you turned on. Shared profile fields are scoped to that adventure and access ends when it completes. There is no way to look up a person's details from a username, and no directory of users.
Service providers
We use a small number of providers to run the service. They process data on our instructions and for no purpose of their own:
- Hosting — our servers and database, which hold everything described in section 2.
- Backups — encrypted on our own machine before they leave it, so the backup provider never holds readable positions or email addresses.
- Email delivery — for password resets, confirmations and service notices, if you have given us an address.
- Map tiles — unless you are using an offline map pack, your device requests map imagery from a tile server, which necessarily sees your IP address and the map area you are looking at. By default this is the OpenStreetMap Foundation's public tile service; the app also lets you point it at your own tile server, or download packs from our own map-pack host and use no tile server at all.
Everyone else
Nobody. We do not disclose personal information to advertisers, data brokers or analytics companies. We will disclose data if we are legally required to — a court order, a warrant, or a comparable legal obligation — and we will tell you when we are permitted to. If the service is ever transferred to another operator, we will say so here before it happens, and this policy will continue to apply until you are told otherwise.
7. Legal bases
We handle personal information under the Australian Privacy Act 1988 and the Australian Privacy Principles. Where the GDPR or UK GDPR applies to you, our legal bases are:
- Contract — your account, your tracks, and the operation of the adventures you join.
- Consent — location sharing, and each optional profile field you choose to share. You can withdraw either at any time, in the app, with immediate effect.
- Legitimate interests — keeping the service secure and free of abuse (the registration IP, access logs, rate limiting) and acting on content reports.
- Legal obligation — where we must retain or disclose something by law.
8. How long we keep things
| What | How long |
|---|---|
| Live position | Until you stop sharing, leave, are removed, or the adventure ends — plus at most a two-hour wind-down if the organiser allowed one. Then deleted. No history is kept at any point. |
| Account, tracks, markers, photos and comments | Until you delete them, or until you delete your account. |
| Points removed by trimming a track | The pre-edit original is kept for a 7-day undo window, or removed immediately if you choose remove the original now. See the backups row below. |
| Registration IP address | 30 days, then erased. |
| Expired or revoked session tokens | 30 days, then erased. |
| Web-server access logs | 365 days. |
| Dormant, empty accounts | An account that has been inactive for 180 days and holds no content is deleted. If we have an email address for you, a warning is sent at 150 days. An account holding tracks, adventures or posts is never deleted this way. |
| Encrypted backups | 7 days. Deleting something removes it from the live service immediately; a copy remains in backups until they roll off. We state this rather than pretend otherwise. |
9. Your rights and controls
In the app, without asking us:
- Export everything — Settings → Data & export produces an archive containing your profile, your tracks as GPX, your markers and your photos.
- Delete your account — the same screen. It asks for your password, and it is irreversible. It removes your account, your tracks, your markers, your photos, your comments, your positions and your sessions. It also deletes any adventure you organise, and everyone else's membership of it — the app tells you before it happens.
- Correct your details — profile fields are editable in Settings. A username is chosen once and cannot be changed, because other people's saved copies of an adventure refer to it.
- Stop sharing location — the sharing switch on any adventure, at any moment.
- Sign devices out — your device list revokes a session, which ends that device's access.
10. Security
- All traffic between the app and our servers is encrypted with HTTPS/TLS.
- Passwords are stored as salted hashes and are never recoverable, by us or anyone else.
- Sessions can be revoked server-side, so a lost phone can be signed out immediately from another device.
- Backups are encrypted on our own machine before they are uploaded, and are stored with a different provider than the servers.
- Whether you can see someone's live position is decided by whether the organiser admitted you to that adventure — checked on the server on every request, never by the app.
- The app uses no cryptography of its own beyond HTTPS and the platform keychain.
No system is perfectly secure. If a breach affecting your personal information occurs, we will notify affected users and the relevant regulator as required by the Notifiable Data Breaches scheme and, where applicable, the GDPR.
11. Children
Dumb Luck Routes is not directed to children. You must be at least 16 years old to create an account, or the minimum age of digital consent in your country if that is higher. We do not knowingly collect personal information from children.
12. International transfers
Our servers and backups are located outside Australia, so using the app involves transferring your information overseas. Where the GDPR applies, transfers rely on the European Commission's standard contractual clauses or an adequacy decision. We take reasonable steps to ensure any overseas recipient handles your information consistently with the Australian Privacy Principles.
13. Self-hosted copies
Dumb Luck Routes is free software under the AGPL, and anyone may run their own server from the source. This policy covers only the service operated by us and the official builds in the App Store and Google Play. If you sign in to somebody else's instance, their operator handles your data and their policy applies, not this one. Every page of the app carries a footer naming the licence, the source and the exact commit the build came from.
14. Changes to this policy
If we change what we collect or what we do with it, we will update this page and the date at the top, and we will tell you in the app before the change takes effect. Material changes to how location is handled will ask for your agreement again rather than assume it. Older versions are in the project's public source history.
15. Contact and complaints
Privacy questions, requests and complaints: spam@securehub.com.au.
Support and content reports: span@securehub.com.au
We will acknowledge a complaint within 5 working days and resolve it within 30 days. If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au, 1300 363 992), or — if you are in the EU, the EEA or the UK — to your local data protection supervisory authority.