Privacy Notice

Version 2

WHO HOLDS YOUR DATA

Bunk-a-Biker LLC is the data controller. Contact: [email protected]

This notice covers the Bunk-a-Biker website, map and account system. It does not cover the Facebook groups, which Meta operates under its own terms.

WHAT CHANGED IN THIS VERSION

Two things, and both are corrections rather than new practices.

Routes you upload to plan a trip are now SAVED, if you choose to save them. Version 1 said they were always discarded. They are yours, only you can see them, you can delete one at any moment, and any you have not opened for eighteen months is deleted for you.

Version 1 also said we do not run advertising or analytics. That is true today and is not a promise about the future — advertising and traffic measurement are planned. Rather than leave a sentence in place that is going to stop being true, this version says plainly what is intended. If either is switched on, this notice gets another version and you will be asked to read it first.

WHAT WE HOLD, AND WHY

Your account: your email address and the name you choose. We need these to sign you in and to reach you about verification, password resets and — if you host — the annual check that your listing is still current. Held for as long as you have an account.

Your rider profile, if you fill one in: what you ride, roughly where you are from, how many of you usually travel, whether you bring a pet, and any links you choose to add. Hosts read this before deciding whether to host you, which is the whole reason it exists. It is not public; only a host you have contacted can see it.

Your listing, if you host: the name you want shown, what you offer, your house rules, your contact details, and two positions. One is where you actually are, which stays private. The other is a deliberately displaced point, which is what the map shows. You choose how far apart they are.

Trips you save: the route itself, its length, and the settings you planned it with. Nobody else can see a saved trip — not other riders, not hosts, not anyone browsing. We know this is sensitive: a route says where you intend to be and roughly when. Delete one at any time from your trips page, and any you have not opened for eighteen months goes automatically.

Your sessions: which devices are signed in, with the IP address and browser so you can recognise a session that is not yours and end it. Kept for 90 days after a session ends.

Records that you accepted the terms, and records of any data request you make. We are required to be able to show these happened.

WHAT WE DO NOT HOLD

We do not collect a rider's home address. There is no reason for us to have one.

We do not take payment between guests and hosts, so we hold no payment details for that at all.

ADVERTISING AND MEASUREMENT

At the time of writing there is no advertising on this site and no analytics. The only cookie is the one that remembers you are signed in.

Both are intended. When advertising arrives it will be through Google AdSense, which means Google receives a request from your browser and may set its own cookies. When traffic measurement arrives it will mean counting visits and which pages get used.

Neither is switched on without a consent banner that asks first and does not load anything until you answer — and this notice gets a new version you will be asked to read before it happens. What we will not do is turn either on quietly and leave you holding a copy of this document that says otherwise.

THE LAWFUL BASIS

Your account and sign-in: performance of a contract — you asked us to run an account for you.

Your profile, your listing and your saved trips: consent. You chose to add them and you can remove them.

Session records: legitimate interest in keeping accounts secure and letting you see where you are signed in.

Consent and request records: legal obligation. We have to be able to demonstrate compliance.

WHO ELSE SEES IT

A host you contact sees your profile and the contact details you gave. That is the point of contacting them.

Our email provider handles verification and reset messages, which means it processes your email address.

The map tiles are served by OpenFreeMap, which sees your IP address when you view the map. We send them nothing else.

If you use the address lookup when creating a listing, the address you type is sent to OpenStreetMap's Nominatim service to find it on the map. If you place your pin by hand instead, nothing is sent.

Saved trips are sent to nobody. The matching runs here.

We do not sell your data.

HOW LONG WE KEEP IT

Your account and everything attached to it: until you erase it or ask us to.

Saved trips: eighteen months after you last opened one, or the moment you delete it.

Sessions: 90 days after they end. Sign-in links: 24 hours or once used. Records of changes to a listing: two years.

Proof that you accepted the terms, and records of data requests: six years after the account closes, and only in a form that no longer identifies you.

These are enforced automatically, not by anyone remembering.

WHAT YOU CAN DO

You can do the first two yourself, right now, from your profile page. You do not need a reason and nothing bad happens for asking.

Get a copy of everything we hold, in a machine-readable file. That covers both your right of access and your right to take your data elsewhere. Saved trips are included.

Erase everything. Your account, profile, listing and trips go. Two records survive in a form that no longer identifies you: that someone accepted the terms on that date, and that this request was made.

Correct anything wrong — most of it from your profile, and your email address with a confirmation step so a typo cannot lock you out.

Ask us to restrict how your data is used, or object to it. Use the form linked from your profile. We have one month to answer.

Withdraw consent for anything you gave it for, which for practical purposes means deleting your profile, your listing or a trip.

If you are unhappy with how we have handled something, you can complain to your national data protection authority. In the UK that is the ICO; in the EU it is the authority for the country you live in.

WHERE YOUR DATA IS

The system runs on a server in the United States. If you are in the UK or the EU, that is a transfer outside your jurisdiction and you should know about it before you sign up.

SECURITY

Passwords are hashed with Argon2id and cannot be read back, by us or anyone else. Sessions are opaque tokens stored hashed, so a copy of the database does not let anyone sign in as you. Host contact details are not on the public map and require an account to see. Exact positions are never published. Saved trips are readable only by the account that owns them.

We cannot promise a system is never breached. We can promise that we know exactly what we hold and where, which is what makes an honest answer possible if it ever happens.

CHANGES

If this notice changes in a way that matters, you will be asked to read the new version before carrying on. Old versions stay on record, because what you agreed to matters more than what we would prefer you had agreed to.

v2 corrects two statements in v1 that were not accurate: that uploaded routes are always discarded, and that advertising and analytics will not run.