Privacy policy

Who we are

BunkhousePage is provided by Bill Horsman, trading as BunkhousePage. We are the controller, under the UK GDPR, of the details described here. Write to hello@bunkhouse.page about anything on this page.

For guests’ details, each bunkhouse is the controller and we process them on its behalf, as our terms of service set out. The exception is the record of each email we send, below, which we keep for ourselves.

What we keep, why, and on what basis

• Who you are. Your name and email address, the bunkhouses you work at and your role in each, so you can sign in and we can tell you about your bunkhouse. Basis: the contract with your bunkhouse, and our legitimate interest in running the service for it.
• Signing in. Each time you sign in, and the kind of browser and device, such as “Safari on an iPhone”, so you and your admins can see where you are signed in and sign you out, and so we can see how the service is used. Basis: legitimate interests, in security and in knowing how the service is used.
• API keys. For each key an admin makes, its name, who made it, whether it may see guests’ details, when it runs out and when it was last used, so admins can see what reads their bunkhouse; and the same for the keys we make to read the platform ourselves. The key itself we keep only scrambled. Basis: legitimate interests, in security.
• What you change. Your email address against the bookings you take or change, the settings you save and the bookings you import, so everyone at the bunkhouse can see who did what. Basis: legitimate interests.
• Your bunkhouse’s account. Its settings, its Stripe account’s id and name, its fee and its payment figures, and who agreed to our terms for it, and when. Basis: the contract, and for the payment and fee records, the legal obligation to keep accounts.
• Emails. A copy of each email BunkhousePage sends, with its sign-in and booking links taken out, and the address it went to and whether it was delivered, bounced or marked as spam. Bunkhouses use the copies to see what a guest was told; we use the addresses and outcomes to keep email working for every bunkhouse, and for these we are the controller. Basis: legitimate interests.
• Test emails. While a bunkhouse is in test mode, the addresses its staff ask to receive its test emails, and whether they said yes. Basis: legitimate interests; nothing is sent to an address but the one question until it says yes.
• Our server’s logs. Our host keeps a record of what the service does, which can include email addresses and the internet address a request came from, to keep it running and find faults. Basis: legitimate interests.
• Support. What you write to us, so we can answer it. Basis: legitimate interests.

We do not sell personal data, send marketing, show advertising, or use personal data to profile anyone.

Cookies

The website you are reading sets no cookies and runs no scripts. The booking and staff pages set only cookies they cannot work without: one that keeps staff signed in; one that remembers a booking part way through, for up to two days; and one that lets the person who has just booked see its details for an hour. Our own admin pages use one more, for the people who run BunkhousePage, and the demo sets one that gives each visitor a bunkhouse of their own for the visit. Stripe’s payment page, where guests go to pay, sets its own cookies, under Stripe’s cookie policy.

Who helps us

These companies process personal data for us, of owners, staff and guests alike, under agreements that protect it:

• Carloku: hosts BunkhousePage, its database and its backups, keeps its server’s logs, and sends its emails.
• Amazon Web Services: carries the emails, through Carloku.
• Google: our own email, for messages sent to hello@bunkhouse.page.
• Anthropic: Claude, an AI assistant we use to look into problems. It sees each bunkhouse’s figures, and, where a member of its staff has turned on support access and for as long as it is on, its bookings by reference, dates, rooms and payments. It never sees a guest’s name or contact details, or a member of staff’s.

Stripe takes guests’ payments into each bunkhouse’s own Stripe account. It does so as a controller in its own right, under its own privacy policy, as it does for the details it collects when a bunkhouse opens its account.

Some of these may handle data outside the UK; where they do, it is protected by the safeguards UK law requires, such as adequacy regulations or the UK’s standard contractual clauses. We will update this list, and email bunkhouses’ admins, before we add or replace one.

How long we keep it

• Your details are kept while you are on a bunkhouse’s staff. When its admins switch you off and erase you, your name and address go from that bunkhouse, along with where you signed in and the copies of the emails you were sent; what you did there is kept as a former member of staff’s. Ask us, or your bunkhouse, if you want that done.
• A sign-up whose emailed link is not opened is deleted after a day: until it is, nothing has been made.
• Addresses asked onto a bunkhouse’s test list that never answer are dropped after 30 days. Our own sign-in links and sessions are deleted once they run out.
• Ninety days after a bunkhouse is closed we delete its data (a few days later if Stripe is slow to delete its guests’ saved cards), except the records of its payments and our fees, with guests’ details taken out, which we keep for six years because the law requires it, and then delete too. The record of who agreed to our terms for it is kept as long as those records.
• Deleted data goes from our backups and our host’s logs as they are replaced, in the ordinary course of things.

Your rights

You can ask us for a copy of what we keep about you, to correct it, to delete it, to restrict or object to how we use it, or to have it in a form you can take elsewhere. Write to hello@bunkhouse.page, and we will answer within a month. If you are a guest, we will pass your request to the bunkhouse you booked with, which decides it. If you are unhappy with how we have handled your details, you can complain to the Information Commissioner’s Office, though we would like the chance to put it right first.

Changes

If we change this policy in a way that matters, we will email bunkhouses’ admins before it takes effect.