Terms of service

1. Who we are, and who you are

BunkhousePage is provided by Bill Horsman, trading as BunkhousePage (“we”, “us”). You can reach us at hello@bunkhouse.page.

“You” are the business that runs the bunkhouse or hostel signed up, and the person who signed it up confirms they may agree to these terms for it. BunkhousePage is for businesses, not for consumers.

“Guests” are the people who book with you. Your agreement with your guests, including your own terms and privacy notice, is between you and them.

2. What BunkhousePage does

BunkhousePage is online booking software: booking pages for your guests, payments through your own Stripe account, emails to guests on your behalf, and staff pages to run the bunkhouse. It changes as we improve it, and the changelog says how. We will not take away something you rely on without telling you first.

3. Your account and your staff

• The person who signs up is the bunkhouse’s first admin. Admins choose who else may sign in, and what they may do. You are responsible for what your staff do with BunkhousePage.
• Staff sign in with links sent to their email address. Keep those addresses ones only they can read.
• Keep the details guests see accurate: your name, contact details, prices, terms and privacy notice.
• Any member of your staff can let us sign in as them, for a while, to help with something (support access). While it is on, we can also read your bookings through the API, by reference, dates, rooms and money, and the emails sent about them with addresses cut to their domain, without your guests’ or staff’s names or contact details, to look into what you asked about, with the AI assistant our privacy policy names. What we do while signed in that way is ours, not yours, and is recorded as ours. Without support access we see only what running the service and charging our fee needs: your figures, your payments through Stripe, and the kind and outcome of each email sent, with guests’ addresses cut down to their domain. We do not see your bookings, or your guests’ names or contact details.
• Admins can make API keys, which let a program, such as an AI assistant, read the bunkhouse, as the API reference describes. Which programs you give keys to, and what they do with what they read, is your choice and your responsibility: a program you choose is not one of our sub-processors. Keep keys as you would passwords. A key stops working when it is removed, when it runs out, or when the admin who made it stops being one.

4. Test mode and going live

A new bunkhouse starts in test mode: payments are pretend, and emails go only to your staff and to people who have agreed to receive your test emails. You go live yourself, once your Stripe account can take payments. Until you go live, BunkhousePage costs nothing.

5. Payments and Stripe

• Guests pay into your own Stripe account. Opening it is an agreement between you and Stripe, under Stripe’s Connected Account Agreement, which you accept with Stripe when you connect. Guests’ money is yours, and never passes through us.
• Stripe’s own fees, including its fee for handling a dispute, are charged to your Stripe account by Stripe.
• Disputes and chargebacks are between you, your guest and Stripe, and you answer them in your Stripe dashboard.
• We cannot see or keep guests’ card numbers: those are entered on Stripe’s pages and held by Stripe.

6. Our fee

• Our fee is 2% of each payment a guest makes through Stripe, and your Payments page shows it. Stripe takes it as the payment is made, so there is no invoice. There is no subscription, and no fee in a month without online payments.
• When you refund a guest through BunkhousePage, our fee on what you refund goes back to you. A refund made in your Stripe dashboard instead, or money taken back by a dispute your guest’s bank decides against you, does not return our fee.
• We will email your admins at least 30 days before we raise our fee, and a higher fee applies only to payments made after that. A lower fee applies from your next payment, and we will tell you of that too.
• Fair use. BunkhousePage is for taking bookings online. Bookings taken by phone, at the desk or imported from a spreadsheet are welcome beside them, but if you use it mostly for those and for its emails, without taking bookings online, we may ask to agree a fee with you.

7. Using it properly

You will not use BunkhousePage to break the law, to mislead guests, or to try to get into anyone else’s bunkhouse. It sends only the emails a booking needs, such as confirmations, reminders and receipts, and no marketing. Those emails go out from our address on your behalf, so we watch how they are received, and we may hold emails, or suspend a bunkhouse, whose emails are marked as spam or bounce unusually often.

8. What is whose

• BunkhousePage, its software and its design are ours. While these terms last, you may use it to run your bunkhouse, and your staff may too.
• Your name, logo, photographs, prices and words are yours. You let us show them on your booking pages and in your emails, and use them to provide BunkhousePage to you.
• What you put into BunkhousePage is yours: your settings, your bookings and your guests’ details. You can download every booking as a spreadsheet at any time.

9. Personal data

• For your guests’ personal data you are the controller and we are your processor. Section 10 sets out how we process it for you.
• We are a controller in our own right for the details of you and your staff, and for the address and outcome of each email BunkhousePage sends, which we use to keep email working for every bunkhouse. Our privacy policy says what we keep and why.

10. Processing your guests’ data for you

This section is the contract the UK GDPR asks for between a controller and its processor.

• What, why and for how long. We process personal data to run your bunkhouse’s bookings: taking and changing them, payments, the emails your guests are sent, and your staff pages. We do it for as long as you use BunkhousePage, and until it is deleted as section 13 says. The data is guests’ names, email addresses, phone numbers, the notes they write, their stays, their group and their payments; the people it is about are your guests and the members of their groups they tell you of.
• Your instructions. We process it only to provide BunkhousePage, on your instructions, which are these terms and what you do in the app, including making an API key that reads guests’ details, which instructs us to give them to whatever uses the key, unless the law requires otherwise, in which case we will tell you unless the law forbids it. We will tell you if we think an instruction of yours breaks data protection law.
• Confidentiality and security. Anyone who can reach your data is bound to keep it confidential, and we keep it secure with measures suited to the risk. We look at it only to run and support the service: to put something right, to answer a question from you, or through support access, including with the AI assistant our privacy policy names.
• Sub-processors. We use only those our privacy policy lists, under terms that protect your data as these do. We will email your admins before we add or replace one, so you can object; if you do, and we cannot meet the objection, you may stop using BunkhousePage. A program you connect with an API key is yours, not one of ours.
• Outside the UK. Where a sub-processor handles your data outside the UK, it is protected by the safeguards UK law requires.
• Helping you. We help you answer guests who exercise their rights: you can correct or forget a guest’s details yourself, from their booking, and we pass on to you without delay any request a guest sends us. We also help with security, breach notification and impact assessments, as far as our part allows, and tell you without undue delay if we become aware of a breach of your data.
• At the end. When you stop using BunkhousePage you choose: download your bookings, and we delete your data as section 13 says. We keep only what the law requires us to.
• Checking. We give you the information you need to show this is done, and let you or your auditor check it on reasonable notice.

11. Keeping it running

We work to keep BunkhousePage available and your data safe. Its database is backed up continuously, so it can be restored as it was moments before a failure. We cannot promise it will never be interrupted, and we are not responsible for what we cannot reasonably control, such as the failure of Stripe, email providers, our host or the internet, though we will do what we reasonably can when they happen.

12. Confidentiality

Each of us keeps confidential what we learn about the other’s business through BunkhousePage, such as your bookings and figures, and uses it only for what these terms are for, unless it is already public or the law requires otherwise.

13. Stopping

• You can stop using BunkhousePage at any time: write to hello@bunkhouse.page from one of your admins’ addresses, and we will close your bunkhouse. Its staff can still sign in for 30 days after that, to download its bookings.
• We can suspend a bunkhouse that breaks these terms, or puts guests, other bunkhouses or our service at risk. We will email its admins to say why, and, unless it is urgent, give you the chance to put it right first. A suspended bunkhouse’s guest pages say it is not taking bookings, and its staff can still sign in and download what they have.
• We can end the service for you, or stop offering it, with at least 60 days’ notice.
• 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 bookings’ payments and our fees, with guests’ details taken out, which we keep for six years because the law requires it, and then delete too.

14. Liability

• Nothing in these terms limits liability for death or personal injury caused by negligence, for fraud, or for anything else the law does not allow to be limited.
• Otherwise, neither of us is liable to the other for loss of profit, revenue, bookings or goodwill, or for indirect loss.
• If data is lost or damaged through our fault, our part is to restore it from our backups as quickly as we reasonably can.
• Otherwise, our total liability to you in any 12 months is limited to the greater of the fees you paid us in those 12 months and £500.

15. Changes to these terms

We may change these terms. We will email your admins at least 30 days before a change that matters to you takes effect, and we keep every version, so you can ask for the one you agreed to. If you do not agree to a change, you can stop using BunkhousePage before it takes effect.

16. The rest

• Notices. We write to your admins at the addresses they sign in with; you write to hello@bunkhouse.page. An email counts as received on the next working day.
• Passing it on. We may pass these terms on to a business that takes over BunkhousePage, such as a company we form to run it, and will tell you if we do. You may pass them on to whoever takes over your bunkhouse, with our agreement, which we will not refuse unreasonably.
• The whole agreement. These terms are the whole agreement between us about BunkhousePage. Nobody else has rights under them.

17. The law

These terms are governed by the law of Scotland, and the Scottish courts have exclusive jurisdiction over any dispute about them. If you have a complaint, write to hello@bunkhouse.page first: most things are put right by talking.