Privacy Policy
Last updated 30 October 2026
Who is responsible
- For your account as a guesthouse owner or staff member, Aakandu is responsible for your information.
- For guests' information, the guesthouse they stay with is responsible. Aakandu stores and processes it on the guesthouse's instructions, only to provide the service. If you are a guest, contact the guesthouse first about your details; we will help them answer you.
The law
The Maldives does not yet have a personal data protection act in force; a Personal Data Protection Bill is before the People's Majlis. Until it becomes law, we follow widely accepted international practice (in the spirit of the EU's GDPR): collect only what is needed, use it only for its purpose, keep it secure, and respect people's requests about their information. We will update this policy when the Maldivian law takes effect.
What we handle
Guesthouse teams
- Name, email, phone, role and the guesthouse you work for.
- A securely hashed password (we never see or store the password itself).
- A record of actions in the app (for example who changed a booking), which the owner can see in the activity log.
- Billing details for the guesthouse's Aakandu subscription, and bank transfer references you give us.
Guests (entered by the guesthouse, by a booking site, or by the guest through the guest app or booking page)
- Booking details: name, contact details, dates, room, number of guests, requests and notes.
- Registration details required to stay in a guesthouse: full name, nationality, date of birth, sex, passport or ID number and expiry, and optionally a photo of the passport or ID.
- Bills, charges and payments (amounts and method; we do not store card numbers).
- Messages to the guesthouse, service requests, orders and wake-up times made in the guest app.
Why we use it
- To run the guesthouse's bookings, stays, bills and registration records, as the guesthouse asks.
- To let guests check in online, contact the guesthouse and see their bill.
- To send booking confirmations, check-in links and invoices.
- To keep the service secure, prevent misuse, fix problems and back up data.
- To invoice guesthouses for Aakandu and meet our own legal and tax duties.
We do not sell personal information, use it for advertising, or build profiles of guests across guesthouses. Each guesthouse's data is kept separate from every other guesthouse's.
Passports, ID photos and calls
- Passport and ID numbers are encrypted in the database and shown in full only to the guesthouse's front-desk staff; elsewhere only the last four characters appear.
- With the ID scan add-on, a scanned passport or ID photo is sent once to Anthropic's AI service to read the details, then kept by us like any other ID photo. We log only that a scan happened, not what it read.
- ID photos are encrypted and automatically deleted a set number of days after check-out (30 days unless the guesthouse chooses otherwise). Every time staff open an ID photo, it is logged.
- Voice calls between guests and the guesthouse are not recorded. They go directly between the two devices, encrypted, or through an encrypted relay (Cloudflare) when the network requires it.
Where it is kept and who helps us
Aakandu's servers and database are hosted in Mumbai, India. We use these service providers, each only for its part of the service:
- Vercel: hosting the application (Mumbai region).
- Supabase (on Amazon Web Services): the database and backups (Mumbai region).
- Cloudflare: relaying call audio when two phones can't connect directly.
- Resend: sending emails such as confirmations and invoices.
- Channex: exchanging bookings, availability and rates with booking sites, when the guesthouse connects it.
- Bank of Maldives (BML Connect): taking online payments, when the guesthouse turns it on. Card details go to BML, not to us.
- Anthropic: reading a passport or ID photo to fill in check-in details, only when the guesthouse has the ID scan add-on and the guest or staff choose to scan. The photo is used only to read it and is not used to train AI models.
- Telegram and WhatsApp: only when the guesthouse chooses to receive alerts or send messages there.
Booking sites such as Booking.com, Agoda, Airbnb and Expedia send us guests' booking details for the guesthouse; their own privacy policies apply to what they collect.
How we protect it
- All connections use HTTPS encryption; sensitive fields and ID photos are encrypted at rest.
- The database enforces that each guesthouse can only ever reach its own records.
- Staff see only what their role needs (for example, housekeeping doesn't see bills or passports).
- Logins are protected against guessing, and important actions are logged.
- Data is backed up regularly. If a breach ever affects personal information, we will tell the affected guesthouses promptly so they can inform guests.
How long we keep it
- Guesthouse records (bookings, bills, registration details) are kept for as long as the guesthouse uses Aakandu, so it can meet its own record-keeping and tax duties, and afterwards until the guesthouse asks us to delete them.
- ID photos are deleted automatically after the stay, as above.
- Our own invoices and payment records are kept as long as tax law requires.
Your choices and rights
- Guesthouse teams can see and correct their details in My account, and ask us for a copy or deletion of their information.
- Guests can ask the guesthouse to see, correct or delete their details. Some records, such as registration and tax records, may have to be kept by law.
- You can contact us at any time with a question or complaint about privacy.
Cookies
Aakandu uses a single cookie, to keep guesthouse staff signed in. The guest app needs no cookies: it works from the guest's private link. We use no advertising, analytics or tracking cookies.
Changes
If we change this policy, we'll update the date at the top and tell guesthouse owners about important changes. See also our Terms of Service.
Contact
Aakandu
G. Greenlin 4th Floor
Email: hello@aakandu.app
WhatsApp: +960 789 8982