Kiimbu — student accommodation marketplaceLast updated: 5 October 2026 · Effective from: effective date
Text in double square brackets, like this, is a blank the company must fill in before publishing (legal name, address, officer names, dates). See the checklist at the end of the covering note.
1. About this policy
This Privacy Policy explains how Company legal name ("Kiimbu", "we", "us", "our"), a company incorporated in India with its registered office at registered address, collects, uses, stores, shares and protects personal data when you use the Kiimbu website at kiimbu.com and any related pages, features and services (together, the "Platform").
Kiimbu is a marketplace that helps students find and request student accommodation, and helps landlords and property managers list it. Kiimbu staff ("Kiimbu Team") review listings, coordinate booking requests and answer questions. This policy applies to everyone who uses the Platform:
- Students and prospective tenants ("Students"),
- Landlords, property owners and property managers and the people who work for them ("Landlords"),
- Visitors who only browse public pages,
- Kiimbu staff (administrators and support personnel), for the data we hold about them as staff.
It should be read together with our Terms and Conditions. If you do not agree with this policy, please do not use the Platform.
Who is responsible for your data. For the personal data described in this policy, Kiimbu decides why and how the data is processed. In data protection language we are the "Data Fiduciary" under the Digital Personal Data Protection Act, 2023 ("DPDP Act") and the "body corporate" under the Information Technology Act, 2000 ("IT Act") and the rules made under it.
2. The short version
| Question | Answer |
|---|---|
| What do you collect? | Account details (email, phone, name, password), profile details, the bookings and messages you send through Kiimbu, landlord verification documents and listing information, and basic technical data (IP address, browser, session records). |
| Do you sell my data? | No. We do not sell personal data and we do not show third-party advertising. |
| Do landlords see my details? | Landlords see a student only by first name and the booking information needed to run a request. They do not receive your email or phone number through the Platform. Students and landlords cannot message each other directly; all messages go through the Kiimbu Team. |
| Do you take payments? | No. Kiimbu does not process payments, cards or bank details in this version of the Platform. |
| Who else handles my data? | Infrastructure providers that run the Platform for us: Supabase (database), Amazon Web Services (server), Cloudflare (network security, file storage and email delivery). Maps use OpenStreetMap. Details in section 7. |
| How long do you keep it? | Only as long as needed. Examples: sign-in codes 10 minutes, search history 90 days, closed accounts are anonymised after a 30-day grace period. Full table in section 10. |
| What can I do? | Access, correct and delete your data, withdraw consent, download your data, and complain to us or to the Data Protection Board. See section 12. |
3. Personal data we collect
We collect only what we need to run the Platform. The tables below list what we collect, from whom, and why.
3.1 Data you give us
| Category | Examples | Who | Why we need it |
|---|---|---|---|
| Account and sign-in | Email address; password (stored only as a one-way hash, never in readable form); phone number (where asked); one-time codes sent to your email (kept only briefly as a protected digest) | Everyone with an account | To create and secure your account, verify that the email is yours, and let you sign in and recover access |
| Student profile | First and last name, preferred name, phone number, current university or intended university | Students | To personalise search, let the Kiimbu Team contact you about requests, and run bookings |
| Landlord profile and organisation | Name, display name, phone number; organisation name, legal name and type; members of the organisation | Landlords | To identify who is listing, to verify the business, and to run listings |
| Verification documents (KYC) | Identity or ownership proofs and other business documents you upload, with their file name and type | Landlords | To check that listings are genuine and protect students from fraud. These are kept in private storage and are viewable only by authorised Kiimbu staff through short-lived, logged links |
| Listing content | Property name, address and map location, description, photographs, room types, prices, amenities, house rules, availability | Landlords | To publish and operate your listings |
| Booking requests | Property and room type, preferred move-in date, length of stay, number of occupants, a message to the Kiimbu Team, a snapshot of your phone number and the quoted price at the time | Students | To process your request and let the Kiimbu Team coordinate with the landlord |
| Messages and attachments | Messages to the Kiimbu Team and any files or images you attach | Students, Landlords | To answer your questions and keep a record of what was said |
| Emergency requests | The type of emergency, your description, messages and attachments you send through the emergency feature, and the case history | Students | To get urgent help from the on-call Kiimbu Team. This feature is not a replacement for calling 112 or 108 |
| Rent records | Charges and payments that the Kiimbu Team records against a tenancy (amount, date, method, reference, notes), and reminders sent about them | Students, Landlords | To keep a clear record of rent due and rent paid outside the Platform. Kiimbu does not collect rent |
| Support and privacy requests | What you write to us, and what we reply | Everyone | To help you and to keep evidence of how we handled your request |
3.2 Data created when you use the Platform
| Category | Examples | Why |
|---|---|---|
| Activity | Properties you favourite or view, searches you run (filters, sort order, university or city), notifications sent to you and whether you read them | To show you saved homes and recently viewed homes, improve search, and tell you about your requests |
| Device and session data | IP address, browser and device type ("user agent"), time of sign-in, last activity, session expiry, reason a session ended | To keep your session secure, detect misuse, and let you review and end active sessions |
| Security and audit records | A log of important actions (sign-ins, changes to listings, staff access to documents, role changes), including who did it, when, and from which IP address | To protect users, investigate abuse, and meet legal obligations. Audit records are append-only |
| Usage analytics | Event records such as "a property was viewed" or "a booking request was submitted". The person is represented by a pseudonym (a keyed code), not your name or email. We run this ourselves; no third-party analytics service receives it | To understand how the Platform is used and fix problems |
| Approximate and precise location | If you are a Landlord and choose "use my location" while pinning a property, your browser (with your permission) gives us coordinates for the pin. If you type an address, the text is sent to a map search service (see section 7) | To place the property accurately on the map. We do not track your location in the background |
3.3 Data we receive from others
- From Landlords: information about a property you request, such as availability and price, and the identity of the organisation that manages it.
- From the Kiimbu Team: notes entered while reviewing listings, verifying documents and handling requests. These are internal.
- From your device or browser: standard technical data sent with every request.
We do not buy data from data brokers and we do not combine your data with data from advertisers.
3.4 What we do not collect
We do not collect your Aadhaar number, PAN, bank account, card or UPI details, health information, caste, religion or biometrics through the Platform. Please do not upload such information in messages or attachments. If a landlord verification document contains such details (for example, an ID proof), upload only what the document type requires and cover anything that is not needed.
3.5 Staff data
For Kiimbu staff accounts we also keep work email, name, employee code, department, roles and permissions, assignments, authenticator (MFA) settings, and a record of administrative actions. Staff data is kept for as long as the person is staff and then for the audit period in section 10.
4. Why we use your data (purposes) and our legal basis
We use personal data only for the purposes below and not for anything incompatible with them.
| Purpose | Data used | Basis |
|---|---|---|
| Create and secure your account; verify your email; sign you in; recover access | Account data, one-time codes, session data | Your consent when you sign up, and the need to provide the service you asked for |
| Show listings, run search, favourites and recently viewed | Profile, activity | Consent / provision of the service |
| Handle booking requests, coordinate with landlords, record rent due and paid | Profile, booking, messages, rent records | Consent / provision of the service |
| Verify landlords and review listings; prevent fraud and fake listings | Landlord profile, documents, listing content, audit records | Consent; legitimate use to protect users and prevent fraud; legal obligations |
| Answer messages and handle emergencies | Messages, attachments, emergency data | Consent; legitimate use to respond to a medical emergency or threat to life or safety where you ask for urgent help |
| Send service notifications (request status, new message, security alerts) by email and in the Platform | Email, notification data | Provision of the service. We do not send marketing email without separate consent |
| Keep the Platform secure; detect and block abuse, bots and attacks; enforce rate limits | IP address, device data, session data, audit records | Legitimate use; legal obligations (including cyber-security directions issued by the Indian Computer Emergency Response Team, "CERT-In") |
| Improve the Platform and measure what works | Pseudonymised analytics | Legitimate use; consent where required |
| Comply with law, respond to lawful orders, and establish or defend legal claims | Any data needed | Legal obligation; legitimate use |
| Provide you with a copy of your data and process deletion requests | Account data, activity | Your request / legal rights |
"Legitimate use" refers to the lawful grounds for processing without specific consent that the DPDP Act recognises, such as compliance with law, responding to emergencies, and acting for purposes the person has voluntarily provided data for.
Consent. When we rely on consent, we ask for it in clear language at the point of collection (for example, when you create an account) and you may withdraw it at any time (section 12). Withdrawing consent will not affect what we did before, but we may not be able to continue providing features that need that data.
No automated decisions with legal effect. Search results are ordered by published rules (for example distance, price and freshness). We do not make decisions about you using automated profiling that has legal or similarly significant effects, and we do not build advertising profiles.
5. Who can see your data inside Kiimbu
- Access is limited by role. Kiimbu staff see only what their role and assignments allow. Staff with narrower roles cannot open data outside their assigned queue.
- Sensitive actions are logged. Opening a private document, changing a role or exporting data creates an audit record.
- Two-step verification. Staff accounts are protected with an authenticator app code in addition to a password and an email code.
- Database-level protection. The database itself enforces row-level rules so that one user's records are not returned to another user even if the application had a fault.
6. What Landlords and Students see of each other
- A Landlord sees a student who has made a booking request for their property by first name and the request details (dates, room type, occupants, relevant message). A Landlord does not receive the student's email address or phone number from the Platform.
- A Student sees the property and landlord-provided listing information, not the landlord's private documents or personal details.
- Students and Landlords cannot message each other directly. The Kiimbu Team relays information where needed.
- If, after a booking is confirmed, the Kiimbu Team must share contact details so you can move in, we will tell you first and share only what is needed for that purpose.
7. Who we share data with (our service providers)
We do not sell or rent personal data. We share it only with the following kinds of recipients, and only as needed.
7.1 Service providers ("Data Processors")
| Provider | What they do for us | What data is involved | Location |
|---|---|---|---|
| Supabase (managed PostgreSQL database) | Hosts our main database | Almost all Platform data, stored encrypted at rest by the provider | India (AWS Mumbai region) |
| Amazon Web Services — Lightsail | The server that runs the Platform | Data in transit and in memory; temporary application files; server logs | India (Mumbai region) |
| Cloudflare, Inc. — network and security | DNS, TLS encryption, content delivery, firewall, bot and attack protection, secure tunnel | Technical data in every request (IP address, headers, requested page) and the content passing through the network | Global network; traffic is served from the nearest data centre |
| Cloudflare R2 (object storage) | Stores property photographs (public) and private files such as landlord documents and message attachments (private) | Photographs; private documents and attachments | Cloudflare storage |
| Cloudflare Email Sending | Delivers one-time codes and notification emails | Your email address, and the email text | Cloudflare network |
| Redis (self-hosted) | Short-lived cache, queues and rate-limit counters on our own server | Temporary technical data and codes | Same server as above |
| Google Fonts | Provides the typefaces used on the website | Your IP address and browser details are sent to Google when fonts load | Global |
| OpenStreetMap Foundation | Map tiles and address search (Nominatim) | Map areas you view; address text you type into the location search | Global |
We choose providers that offer contractual or published security and confidentiality commitments, and we give them only what they need. They may process data only on our instructions for the purposes above.
7.2 Other recipients
- Landlords — as described in section 6.
- Professional advisers — lawyers, auditors and insurers, under confidentiality.
- Authorities — where we are required by law, court order or a lawful request from a government agency, or where it is necessary to protect the rights, safety or property of users, Kiimbu or the public. We review such requests and share only what is legally required.
- A successor business — if Kiimbu is involved in a merger, acquisition or sale of assets, personal data may be transferred under the same protections, and we will tell you if the owner or the purposes change materially.
We will not share your personal data with advertisers or data brokers.
8. Transfers outside India
Our database and server are located in India. Some providers, such as Cloudflare and Google Fonts, operate global networks, so limited technical data (for example your IP address) may be handled outside India as part of delivering the website. The DPDP Act permits transfers outside India except to countries the Government of India restricts by notification. We will comply with any such restriction, and we use providers that apply contractual security commitments.
9. Cookies and similar technologies
We use only the cookies and browser storage that the Platform needs to work and to keep you secure. We do not use advertising or cross-site tracking cookies.
| Name / item | Type | Purpose | Lifetime |
|---|---|---|---|
__Host-kiimbu_session | Cookie (essential, HTTP-only, secure) | Keeps you signed in; holds a random token, only a one-way digest of which is stored on our server | Until you sign out, or when the session ends (60 minutes of inactivity or 24 hours total for Students and Landlords; shorter for staff) |
__Host-kiimbu_access | Cookie (essential, HTTP-only, secure) | A short-lived signed pass used to authorise requests | 10 minutes, renewed while you are active |
kiimbu_preauth | Cookie (essential, HTTP-only) | Remembers that you are part way through signing in (for example, entering your email code) | Minutes |
| CSRF / request protection | Cookie and token (essential) | Protects against forged requests | Session |
| Local copy of public lists | Browser local storage | Speeds up repeat views of public lists such as cities and universities (contains no personal data) | Until cleared, refreshed regularly |
| Chat cache | Browser IndexedDB | Keeps a copy of your own messages on your device so conversations open faster. It is cleared when you sign out or when your session ends | Until sign-out |
Because these items are strictly necessary, they are set without a cookie banner. You can block cookies in your browser, but the Platform will not work without the essential ones.
10. How long we keep data (retention)
We keep personal data only as long as needed for the purposes in section 4, then delete or irreversibly anonymise it. The periods below are the current defaults; they may be adjusted, and legal requirements can require longer retention.
| Data | Retention |
|---|---|
| One-time email codes | 10 minutes; single use; destroyed after 5 wrong attempts |
| Access pass | 10 minutes |
| Sign-in sessions | Idle timeout 60 minutes and maximum 24 hours (Students and Landlords); shorter for staff (20 minutes / 8 hours; Super Admin 15 minutes / 4 hours). Session records are then kept for a short period for security review |
| Sign-ups that were never verified | Deleted after 7 days |
| Search history | 90 days |
| Recently viewed properties | 180 days |
| Notifications | While your account is active; deleted when your account is anonymised |
| Messages and attachments | While your account is active; text replaced with "[removed]" and files deleted when your account is anonymised |
| Emergency requests | While your account is active (descriptions and messages removed and files deleted when anonymised); closed cases may be kept longer in de-identified form to review service quality, unless a legal hold applies |
| Booking requests and rent records | While your account is active, and afterwards in de-identified form (phone and free-text removed) for as long as needed for accounting, tax, dispute and legal purposes |
| Landlord verification documents | While the organisation is active; deleted when the last member of the organisation closes their account, unless needed for a legal claim or investigation |
| Property listings and public photographs | While the listing is active. Archived or abandoned uploads are removed after 24 hours to 30 days |
| Audit records | 2 years (730 days) by default, then deleted |
| Pseudonymised analytics events | Until aggregated; erased with your account |
| Data export files | Available for 7 days after you request them, then deleted |
| Closed accounts | Access ends immediately. After a 30-day grace period the account is anonymised: email, name, phone, messages and files are removed or replaced |
| Security and infrastructure logs | Up to 180 days, kept within India, in line with CERT-In directions confirm log retention on the server before publishing |
| Database backups | Encrypted and kept on a rolling basis (currently about 14 days). A deleted record may therefore persist in a backup until that backup expires, and is not restored into live use |
Legal holds. If data is needed for a legal claim, a complaint, a fraud or security investigation or a lawful order, we may keep the relevant data for longer and will remove it when the reason ends.
11. How we protect your data
We use technical and organisational measures that are appropriate to the risk, including:
- encryption of connections (HTTPS/TLS) and encryption of stored data by our storage and database providers;
- passwords stored only as salted one-way hashes; sign-in sessions stored only as hashed tokens;
- email one-time codes with short expiry, attempt limits and rate limiting; protection against repeated wrong-password attempts;
- mandatory authenticator-app verification for staff;
- role-based access and database row-level security, so each person sees only the records they should;
- private file storage with short-lived, logged download links; uploaded files are checked for type, size and basic safety markers before use;
- rate limiting, firewall and bot protection at the network edge;
- append-only audit logs, monitoring, and encrypted backups;
- staff access on a need-to-know basis and confidentiality obligations.
No system is completely secure. You can help by using a strong, unique password, not sharing your sign-in codes, signing out on shared devices, and telling us at once if you suspect misuse.
If there is a data breach. If a personal data breach affects you, we will inform you and the Data Protection Board of India as required by law, describing what happened, what data is involved, what we are doing and what you can do. We also report cyber-security incidents to CERT-In within the time required.
12. Your rights and how to use them
Under the DPDP Act, and as we commit regardless, you have the right to:
- Access — get a summary of the personal data we process about you, the processing activities, and the other parties we have shared it with.
- Correction and completion — have inaccurate or incomplete data corrected or completed.
- Erasure — ask us to erase personal data that is no longer needed for the purpose you gave it, unless we must keep it by law.
- Withdraw consent — at any time, as easily as you gave it.
- Grievance redressal — have a complaint answered quickly (see section 14).
- Nominate — nominate another person to exercise your rights if you die or become unable to act.
- Download your data — you can request a copy of your data in a common format from Account → Privacy once signed in.
How: the easiest way is Account → Privacy inside the Platform, where you can download your data or close your account. You can also email privacy email, e.g. [email protected] from the email address on your account. We may need to verify your identity before acting, to protect you from someone else asking for your data.
Closing your account. When you close your account you lose access immediately. After the 30-day grace period the account is anonymised as described in section 10. Some records may remain in de-identified form where the law requires us to keep them.
Time frame. We acknowledge requests within 48 hours and aim to complete them within 15 days; if a request is complex or we must wait for verification, we will tell you why and complete it within the period allowed by law.
Your duties under the DPDP Act include providing accurate information, not impersonating anyone, and not filing false or frivolous complaints.
13. Children and minors
The Platform is for people who are 18 years or older. We do not knowingly collect personal data from anyone under 18, and we do not allow accounts to be created by them. If a parent or guardian believes a child has given us data, please contact us and we will delete it. Under the DPDP Act, processing a child's data requires the verifiable consent of a parent or lawful guardian, and we do not track or target children or show them advertising. If we later add support for students under 18, we will first add verified parental consent and update this policy.
14. Grievances and contact
If you have a question, a complaint or a privacy request, please contact our Grievance Officer:
- Name: Grievance Officer name
- Designation: designation
- Email: grievance email, e.g. [email protected]
- Address: registered address
- Hours: days and hours
We acknowledge complaints within 24 hours and aim to resolve them within 15 days. If you are not satisfied, or have not received a reply, you may complain to the Data Protection Board of India once the Board is operational and you have first used our grievance process.
For Data Protection matters you may also write to our Data Protection contact: name, email.
15. Links to other sites
The Platform may link to websites we do not operate, such as map directions. We do not control them. Read their privacy policies before you share information.
16. Changes to this policy
We may update this policy when our practices, providers or the law change. We will post the new version here with a new "last updated" date. For material changes, such as new purposes or new categories of recipients, we will notify you by email or in the Platform before they take effect and, where the law requires, ask for your consent again. Earlier versions are available on request.
17. Laws that apply
This policy is governed by the laws of India, including the Information Technology Act, 2000; the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011; the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 (as they come into force in phases, with the main obligations of data fiduciaries taking effect by May 2027); the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021; and directions issued by CERT-In. Where a law gives you a right that is broader than this policy, the law applies.
Questions? Email privacy email or write to the Grievance Officer above.