The Loft Back to the website

Privacy notice

The Loft is let directly by its owner — there is no agent and no booking platform in the middle. That means one person is responsible for your details. This notice is the information the Data Protection Act, 2018 requires the owner to give you (section 28): who is responsible, what is collected and why, who else sees it, how long it is kept, and how to ask for a copy, a correction or deletion.

In short

Version 2.0 · in force 30 October 2026
  • We keep what you type when you book: your name, phone and WhatsApp numbers, email address, dates, guest count, extras, any message you add, and your signature.
  • We record which documents you accepted — the terms, the house rules, the refund and cancellation policy, the breakage terms and this notice — with the time and the version you agreed to, so there is a written record of your consent.
  • Card payments are processed by DPO. Your card number goes to them, not to this site, and is never stored here.
  • Your booking emails carry a read receipt, so the owner can tell whether a confirmation reached you. It records the first open and nothing more.
  • No advertising cookies, no analytics scripts, no profiling and no automated decisions about you.
  • Your details are never sold, rented or handed to advertisers or data brokers, and you are not added to a marketing list unless you tick that box yourself.
  • No account to create and no password to remember — a booking reference and your own guest link are all you are given.

What is in this notice

The notice in full

1. Who is responsible for your details

The owner of The Loft, Plot 2989 Madikwe Crescent, Extension 11, Gaborone, Botswana, is the data controller for the personal data collected through this website — the person who decides what is collected and why. The apartment is let directly by the owner, so the same person who takes your booking looks after your details and answers any request you make about them. That address is also the owner's principal place of business for this purpose.

You can reach the owner at [email protected], on +267 72 728 227, or on WhatsApp.

The Act allows a controller to appoint a data protection representative (section 36). The owner has not appointed one: the controller is established in Botswana, the site is run from Gaborone, and the owner handles data-protection requests personally rather than through an intermediary. Nothing in this notice depends on a third party, which is the point of keeping it this way.

2. What we collect and why

Only what a stay actually needs. The table below is the whole list, with the purpose for each item and the lawful basis the owner relies on under section 16 of the Act.

What is collectedWhyLawful basis
Name, phone, WhatsApp number, email address To hold and confirm your dates, send your confirmation and the terms you signed, and reach you during your stay with arrival directions, the gate code and housekeeping times Contract — s16(b)
Arrival and departure dates, number of guests, extras requested To price the stay, check availability, reserve the nights and schedule housekeeping Contract — s16(b)
Your typed signature, the time you signed, and which documents you accepted A written record of the agreement you entered into and of the consent you gave Contract — s16(b); consent — s16(a) for anything optional
Messages, breakage reports and extra requests sent from your booking page To deal with what you report, settle what it costs, and keep a written trail of what was asked and charged Contract — s16(b)
Payment outcome: DPO reference, amount, currency, status, and any refund made To confirm the booking, to pay money back where a refund is due, and to keep the accounting records the law requires Contract — s16(b); legal obligation — s16(c)
A one-way hash of the connection you book from, and the bot-shield proof your browser solves To stop automated abuse of the booking form and to tie a signed agreement to the session that signed it. The hash cannot be turned back into an address Legitimate interests — s16(f): keeping the site and the booking record secure
The first time a booking email was opened, and when So the owner can see that your confirmation arrived, rather than chasing a reply you already gave Legitimate interests — s16(f)
Data-protection requests: your name, email, what you asked for, your message, and the owner's note of what was done To answer you within the 30 days the Act allows, and to show that the request was handled Legal obligation — s16(c)
Your email address, if — and only if — you tick the marketing box Occasional news about the apartment Consent — s16(a)

Nothing else. There is no newsletter unless you ask for one, no advertising pixel, no social-media tracking and no analytics of any kind on these pages.

3. The lawful basis we rely on

The Act permits processing only where one of the criteria in section 16 applies. Three of them are used here, and each is tied to a specific job rather than claimed in general terms:

  • Your consent, in writing (s16(a)). The Act defines consent as a freely given, specific and informed expression of your wishes. Ticking the boxes in the booking form and typing your name is that expression: nothing is pre-ticked, the optional marketing box is separate and starts empty, and the version of each document you accepted is recorded with the time. Consent can be withdrawn at any time (s19) — see section 12.
  • Performance of a contract (s16(b)). A booking cannot be held, confirmed, paid for or run without your name, contact details and dates. This is the basis for the booking itself, for messages about your stay, and for settling breakages and extras.
  • Compliance with a legal obligation (s16(c)). Booking and payment records have to be kept for tax and accounting purposes, and a data-protection request has to be answered and evidenced.
  • Legitimate interests (s16(f)). Used for two narrow things only: keeping the booking form free of automated abuse, and knowing that a confirmation email arrived. Neither overrides your rights — both are described in section 2, and you can object to either.

Your details are used only for the purposes stated above. They are not used for any other purpose without your consent or an authorisation in law (section 15).

4. What we do not collect

  • Sensitive personal data — health, religion, political opinions, trade-union membership, sexual orientation, biometric or genetic data. The Act restricts this class of data (section 20) and a booking does not need any of it, so please do not send it. If it arrives in a message, it is deleted.
  • Your identity-card or passport number. Photo ID is looked at in person at check-in and is not copied, scanned or stored here (section 27 restricts identity-card processing).
  • Card numbers, expiry dates or security codes. They are typed on DPO's own pages and never reach this site.
  • Anything used to make an automated decision about you. No scoring, no profiling, no automatic refusal: the owner decides, by hand, with the information in front of them.
  • Your location, contacts, photos or address book. The site asks the browser for none of them.

5. Marketing and your right to object

There is no marketing list. If you tick the optional box in the booking form, the owner may email you occasionally about the apartment; if you do not tick it, nothing is sent beyond the messages about your own stay. You may object to marketing at any time and at no cost (section 18), and you may withdraw consent for it at any time (section 19) — by replying to any such email, or through the form in section 12. Once you object, no further marketing email is sent, and only the fact that you objected is kept, so that you are not written to again.

6. Who else sees your details

Beyond the owner, your details reach only the services needed to run the booking. Each is chosen for the guarantees it gives about security, and each is bound to the owner by written terms that limit it to the owner's instructions (section 32(3) of the Act):

WhoWhat they seeWhy
DPO Your name, email and the amount, plus the card details you type on their page The card payment, and any refund back to the same card. DPO is a controller of the card data it collects, under its own terms
Supabase Every record described in section 2, in an encrypted database with access rules; uploaded photographs in private storage Database, private file storage and backups for this site
The email delivery service (Resend) Your email address and the message sent to you Delivering your confirmation, your guest link and the owner's notification
The platform that hosts this site and runs the booking function Requests to the site, including the hashed connection record Serving the pages and running the booking code
DPO's and the site's infrastructure providers Whatever passes through the services above Running those services; they act on their customer's instructions
Google Fonts and OpenStreetMap Your IP address, as part of the ordinary request your browser makes Typefaces and map tiles. Nothing else is shared with them
WhatsApp or your phone network Your number and the messages exchanged Only if the owner messages or calls you about your stay; that traffic runs under their own terms

Nobody else. Your details are not sold, rented, brokered or shared for advertising, and they are not passed to anyone who would use them for their own purposes. Should a booking record ever be needed by a court, a regulator or a lawful authority, only what is actually required is provided.

7. Details that leave Botswana

Two of the services above — the payment provider and the email service, and the data centres behind the hosting and database — may process personal data outside Botswana. The Act restricts that (section 48): a transfer to a country that does not ensure an adequate level of protection is prohibited, unless one of the exceptions applies.

Here the transfer is made on the basis that it is necessary for the performance of the contract you have entered into — a card payment cannot be taken and a confirmation cannot be delivered otherwise (section 48(5)) — and the owner requires the contractual safeguards described in section 48(6): the provider's data-processing terms, which limit use to the owner's instructions, require security measures, and require the provider to tell the owner about any breach. If you would prefer to avoid a transfer of this kind, tell the owner before booking and the stay can be arranged with payment by bank transfer instead; the owner will explain what changes.

8. How long we keep it

Personal data must not be kept longer than the purpose requires (section 14(h)). These are the periods actually applied in the system, not aspirations:

RecordKept forWhy
Booking, payment and refund record 7 years after the stay Tax and accounting records, and the limitation period for a contractual claim
Signed terms and the record of what you accepted With the booking, for the same 7 years It is the evidence of the agreement and of your consent
Enquiry that never became a booking 12 months Long enough to answer it and follow up, and no longer
Email open record 24 months It answers "did the confirmation arrive?" and is worthless afterwards
Data-protection request and the owner's answer 3 years after it is closed Proof that a statutory request was handled, in case it is challenged
Marketing consent Until you withdraw it; the withdrawal itself is kept so you are not contacted again Section 18 and section 19
Card details Never kept They belong to DPO, not to this site
Cancelled or expired booking with no payment Anonymised once the 7-year mark is reached, or sooner on request There is nothing left to justify keeping the identifiers

The clean-up is run by the owner from the private console, so nothing is deleted behind their back, and it is idempotent — running it twice deletes nothing extra. Ask for your details to be deleted sooner and they are, unless a record still has to be kept for tax or accounting reasons; in that case the identifiers are removed and only the amounts, dates and what was paid remain, which is what section 14(h) and section 30 strike between your rights and the owner's record-keeping duty.

9. How your details are protected

The Act requires appropriate technical and organisational security measures, having regard to the nature of the data and the risks involved (section 32). These are the measures actually in place:

  • Every page is served over an encrypted connection, and the browser is told not to cache booking responses.
  • The database is reachable only through the booking function, using a key that is held on the server and never sent to the browser. Database access rules keep the records closed to direct public queries.
  • The owner's console needs a named account and a password stored only as a salted hash, plus a proof-of-work challenge and rate limits before a session is issued.
  • Connection addresses are stored only as one-way hashes, so a booking or a signature can be tied to the session that made it without keeping the address itself.
  • No card details are held at any point, which removes the largest category of risk from the site entirely.
  • Guest photographs and documents sit in private storage and are served through short-lived signed links, never as public files.
  • Access to the console is limited to the owner and to the named people the owner creates, and is withdrawn when it is no longer needed.
  • Please do not email card numbers, passwords or a copy of your ID. If identity has to be checked for a request, the owner will ask for it in a safer way.

10. If something goes wrong

The Act requires a controller to notify the Commissioner of any breach of the security safeguards without delay (section 33), and requires a processor to notify the controller just as promptly. In practice: if the owner becomes aware of a breach affecting personal data, the Commissioner is notified without delay, and — where the breach is likely to harm you — you are told what happened, what was involved, and what to do about it, without waiting for a perfect picture. The same applies if a provider reports a breach to the owner.

11. Your rights

The Act gives you direct rights over your personal data. None of them need a lawyer and none of them cost anything here.

Your rightWhat it means hereAct
To be told whether your data is held Ask and you will be told, plainly, yes or no — and what is held s30(1)(a)
To receive a copy A copy of your booking record and the messages attached to it, within a reasonable time of asking s30(1)(b)
To be told the reason for a refusal If a request is refused, you are told why — for example because a tax record must be kept s30(1)(c)
To challenge a refusal You may challenge it with the owner, and complain to the Commission if you are still unsatisfied s30(1)(d)
To have wrong data corrected Anything inaccurate, incomplete or out of date is corrected or completed s14(g), s30(1)(e)
To have data deleted Deleted, or anonymised where a financial record must remain s30(1)(e)
To object to marketing One word is enough, at any time and at no cost s18
To withdraw consent For anything resting on consent, in writing, at any time s19
To be told what is happening with your data The information in this notice — purposes, recipients, retention, and your rights s28

Withdrawing consent does not affect anything done lawfully before you withdrew it, and it does not cancel a booking — the stay itself rests on the contract, not on consent.

12. Making a request

Use the form below, reply to your booking confirmation, or write to [email protected]. Quote your booking reference if you have one — it begins LOFT- and is on your confirmation and your guest link. Every request is given a reference beginning DSAR-, and a written answer is due within 30 days of the day it was received; the date is fixed when the request is logged, not when it is remembered.

To protect your data, the owner checks that a request came from you before releasing or erasing anything: usually a reply from the email address on the booking, or the details of the payment that confirms it is you. If a request cannot be met in full — because a tax record must be kept, for example — you are told which part, and why.

On your confirmation email, or at the top of your guest link.

Do not send card numbers, passwords or a copy of your ID here.

13. Cookies and your own browser

This site sets no cookies. One preference is saved in your browser's local storage: the currency you choose on the rate card, so the indicative prices remember your choice when you come back. It stays on your device, holds nothing that identifies you, and you can clear it at any time in your browser settings.

If you add the site to your home screen, a service worker caches the pages and photographs so they open with a poor connection. That cache is on your device only. The read receipt described in section 2 sits in the email the owner sends you, not in these pages, and stores nothing on your device. The owner's private console keeps its session in that browser tab only, and it disappears when the tab is closed; it is not part of the guest site.

14. Guests under 18

The apartment is let to adults, and the person who books must be 18 or older. No information about children is collected beyond a count of guests, and no account, profile or password is ever created for a guest of any age.

15. Changes and version history

If the way your details are handled changes, this page is updated and the version below changes with it. A booking is handled under the version in force when it was made, and the version you accepted is recorded against your booking — so what you agreed to can always be identified exactly.

VersionDateWhat changed
2.0 30 October 2026 Rewritten to the structure of the Data Protection Act, 2018: lawful basis for each purpose, the recipients and the basis for transfers outside Botswana, a stated retention schedule, the rights in section 30, and a request route that records a 30-day deadline
1.0 4 October 2026 First published notice

16. Questions and complaints

If something about your data is not right, say so — to [email protected] or on +267 72 728 227. A data-protection request is answered within 30 days; a complaint about a stay gets a written answer within 5 business days.

If you are not satisfied, the Act gives you the right to complain to the Information and Data Protection Commission, the regulator established under section 4 of the Act (complaints are dealt with under section 42). Its current contact details are published by the Commission, and the owner will send them to you on request. Complaining to the Commission does not affect any other right you have.

The Loft · Plot 2989 Madikwe Crescent, Extension 11, Gaborone · Let directly by the owner.
Data controller for this site. Notice version 2.0, in force 30 October 2026.
Back to The Loft website · Terms and conditions · Refunds and cancellations