Skip to content

We use optional Google Analytics to improve aAlabu. Cookie Policy

aAlabu
Explore stays Find my booking Sign in

Privacy Policy

Version 1.0 · Effective 5 September 2026 · Privacy Policy last updated 12 November 2026

Terms & Conditions Privacy Policy Cookie Policy Cancellation Policy

1. Who we are

AALABU LIMITED (company number 16660516), registered office Office 13953, 182–184 High Street North, East Ham, London, United Kingdom E6 2JA, is the data controller for the personal data described in this policy.

2. What we collect

When you make a booking, we collect: your name, email address and phone number; your stay dates and guest composition (including children's ages, where relevant to pricing); whether you are travelling for work and your trip type, if provided; any special requests you choose to give us; your transfer selection, where applicable; messages you send us about your booking; and any review you choose to submit. aAlabu does not require you to create a customer account.

If you create an account. You can choose to create an aAlabu account, on the website or in the app. We then hold your first and last name, your email address and whether it has been verified, and either a password (which we keep only in a protected, scrambled form, so we cannot read it) or a link to the Google or Apple account you used to sign in. We connect to your account the bookings you make while signed in or later add to it, your booking messages and, in the app, the properties you save (“Loved stays”).

Signing in with Google or Apple. If you choose Google or Apple, you sign in on their own page or app, under their own privacy policies, and we never see your Google or Apple password. They tell us your name (Apple gives it only the first time, and you can choose to hide your email address from us), your email address, whether they have verified it, and a unique identifier for you. We keep these so that we recognise you next time and so that the account stays linked to the right person.

Account sign-ins. We keep a record each time you sign in to your account: the date and time, whether you used the website or the app and, for the website, the method (email and password, Google or Apple). This record does not itself include your network address, device details or password. Separately, our security records note failed sign-in attempts on our website sign-in forms (see section 10).

Visits to our website. When you open our home, search or property pages, we count the visit with our own counter. It uses your network address (IP address) and browser details, which your browser sends to every website it visits. We scramble them into a code using a secret key that changes every day, and the counter does not keep the network address or browser details themselves (our ordinary server logs do, for a short time: see section 10). What the counter keeps is that code, the date (Maldives time), when it was first and last seen, and which kind of page it first viewed (home, search or property). Because anyone holding our secret key could still match that code to a browser, we treat it as personal data, not as anonymous data. We do not use it to recognise you from one day to the next, and we keep no record of what you do on the site beyond that first page type. From the counter we also keep hourly totals of page views and visits, which contain no personal data.

3. Payment data

Card details are entered directly into our payment provider's own secure interface and are not stored on aAlabu's systems. We do not store your full card number. We keep a payment reference from our payment provider so we can match your payment to your booking.

4. Booking recovery data

Because aAlabu does not require an account, we let you access a booking using your booking reference together with the email address you booked with, or a recovery link we send to that email. Your browser also stores a small, device-local recovery token so your booking stays accessible on that device.

5. Technical data

We collect standard technical and session information needed to operate the site securely. Our own visit counter (see section 2) does not use cookies or any storage on your device, and it does not count visits from browsers that send a Global Privacy Control or Do Not Track signal. See our Cookie Policy for details of the specific technologies involved, including Google Analytics, which only runs if you accept it.

6. Special requests and sensitive information

The special-requests field on our booking form is free text intended for ordinary booking preferences (for example, a room location preference). We do not ask you for health, religious, or other sensitive information. If you voluntarily include information of that kind in a special request (for example, an accessibility need), we process it only to try to fulfil that specific request, and we ask that you share only what is necessary for us to act on it.

7. Why we use your data

We use your booking and stay details, and any special request you give us, because it is necessary to perform your booking (a contract with you). We use your payment reference because it is necessary to perform your booking and to meet our own accounting obligations. We do not use your data for marketing, and we do not currently offer a marketing opt-in.

We use your account details because it is necessary to provide the account you have chosen to create (a contract with you) and to keep it secure.

We count visits to our site, keep sign-in records and keep security records because it is in our legitimate interests to run, secure and improve the service, to protect accounts and the site from misuse, and to understand how many people use it. We have weighed this against your privacy: we keep very little of the visit counter's data, for a short time, we do not link visits across days, and we do not use this information to profile you, target you or contact you. We also notify our own team when someone registers for an account (a first name and how they registered), so we can spot problems and follow up.

8. Who we share it with

  • The accommodation provider you book with, to the extent needed to fulfil your booking (for example, your name, stay dates, and any relevant request or transfer selection).
  • Our payment provider, to process your payment.
  • Our transactional email provider, to send booking confirmations, recovery links, and service messages about your booking, and notifications to our own team (see section 7).
  • Our hosting and infrastructure providers, who store and run the platform on our behalf.
  • Google and Apple, only if you choose to sign in with them (see section 2).

Google Analytics. If you accept analytics in our cookie banner, Google provides us with an analytics service. Your browser then sends Google information about your visit — as with any website resource, this includes your network address and browser details — together with what we record about how you search and book (such as the destination, dates and number of guests searched, the properties and rooms you view or select, and the stage of booking you reach), as described in our Cookie Policy. We do not send your name, email address, phone number, booking reference or payment details. Google may process this information outside the UK. If you do not accept analytics, none of this is sent. See how Google uses information from sites that use its services.

The information from our visit counter and sign-in records stays on our own servers and is not shared with anyone other than the hosting and infrastructure providers who run the platform for us. Our visit alerts to our own team contain only a time and a page type.

When you explicitly request a Google rating, our server sends the property’s Google Place identifier to Google to retrieve its current public rating and review count. This request does not send your booking or contact details. We do not retain Google ratings, review counts or review text in persistent storage for this feature. Opening a page does not automatically retrieve or refresh Google ratings.

If you follow a Google Maps or reviews link, you visit Google directly and Google may receive information from your browser. See the Google Privacy Policy.

9. International transfers

Some of our service providers may process personal data outside the UK. Where international data-transfer rules apply, we assess the relevant legal requirements and safeguards for the provider and destination.

10. How long we keep it

We keep personal data only for as long as necessary for the purposes described in this policy, including to fulfil your booking, to meet legal, accounting, and tax record-keeping obligations, to handle disputes or fraud, and for reasonable operational purposes such as security logs. Where we have not yet set a fixed deletion period, we say so below rather than imply one.

What applies today:

  • Bookings and what is attached to them (the details given when booking, payment and refund records, and messages about a booking): no fixed period yet, as explained further below.
  • Your account: until you delete it (see below).
  • Security records — failed sign-in attempts on our website sign-in forms, and sign-ins and password changes or resets on staff and partner accounts, each with the network address used and, for a failed attempt, the email address entered: no fixed deletion period yet.
  • Records of the emails we send you about a booking or your account: no fixed deletion period yet.
  • Website sign-in records: 13 months. App sign-in sessions: until your account is deleted.
  • Visit counter: the scrambled daily codes are kept for the current and the previous day (Maldives time) and are then deleted. After that we keep only hourly totals, which contain no personal data, for up to 25 months. Our internal notification records are kept for up to 90 days: for a visit, only a time and a page type (no code); for a new registration, a reference to the new account (and, for a partner, the name given).
  • Server and application logs (network address, page requested, browser details): 14 days.
  • Backups of our database, which can contain any of the above: we keep regular backups so that we can restore the service. Automatic deletion of historical backups is not currently enforced, so information that has passed a period above, or that you have asked us to delete, may remain in backups for longer.

We will update this policy when we set the periods that are still open.

Deleting your account. You can delete your aAlabu account yourself from your account page or in the app, or ask us to (see how account deletion works). When an account is deleted we remove your sign-in details, including any linked Google or Apple sign-in, and replace the name and email on the account so it can no longer be used. We keep booking records and the information attached to them: the details given when booking (such as name, email, phone number and special requests), payment and refund records, and messages sent about a booking. If you reviewed a stay, your name is removed from the review but the review stays. If the account used Sign in with Apple we show you how to remove aAlabu from your Apple Account. Deleting an account does not cancel a booking or refund a payment. We keep only a minimal record that the account was deleted, which contains no name or email. We do not yet apply a fixed period after which booking details are removed or anonymised; that is still to be decided.

11. Your rights

Under UK data protection law you have the right to access, correct, delete, restrict, or object to our use of your personal data, and the right to receive certain data in a portable format. Contact aalabu@aalabu.com to exercise these rights.

Objecting to visit counting. You can object to our visit counter at any time. The technical way to opt out is to turn on Global Privacy Control or Do Not Track in your browser; we then do not count your visits. If you cannot or prefer not to use either, contact us at the address above and tell us that you object; we will consider your request and reply within one month, telling you what we can do. The counter does not collect anything that identifies a particular browser from one day to the next, so the two signals are at present the only way we can apply an objection to your future visits by technical means; an email objection is not refused for that reason, and we will still consider it and respond. Because the code changes every day and we do not keep your network address or browser details with it, we may not be able to find a particular past visit, but every code is deleted within about two days in any case.

12. Complaints

If you believe we have mishandled your personal data, you can complain to the Information Commissioner's Office (ico.org.uk), the UK's data protection regulator.

13. Changes to this policy

We will update the “last updated” date shown above whenever this policy changes, and the version and effective date if it changes materially.

14. Contact

aalabu@aalabu.com

aAlabu
Terms & Conditions Privacy Cookies Cancellation Policy Partner portal
© 2026 aAlabu · AALABU LIMITED · Registered in England and Wales