Privacy policy
What Keja collects, why, who sees it and the choices you have.
Last updated 17 November 2026
Who we are
Keja is a set of tools for buying, building and researching property across African borders, made by Keja Labs LLC, 13730 15th Ave NE, Seattle, WA 98125, USA (“Keja”, “we”, “us”). Keja Labs LLC is responsible for (the controller of) the personal information described here. This policy explains what we collect when you use the Keja website and apps at kejalabs.app, the Keja WhatsApp number and Keja emails, why we collect it, who we share it with and the choices you have.
Questions or requests about your data go to legal@kejalabs.africa, or by post to Keja Labs LLC, 13730 15th Ave NE, Seattle, WA 98125, USA.
What we collect
We collect only what the tools need to work:
- Your account. When you sign in with Google we receive your name, email address, Google account identifier and profile picture. We never receive your Google password.
- What you add. Projects, briefs, budgets, photos, PDFs and other files, comments, tasks, notes, saved places, questions you ask Keja and the answers we give you.
- Bookings. When you book a viewing or consultation: your name, email, phone number if you give it, the time you picked, your time zone and any notes.
- Messages. If you message Keja on WhatsApp: your phone number, your WhatsApp profile name, the messages and media you send, and our replies. If you email us, your email and its contents.
- Waitlist and mailing list. Your email, name, interests, country and anything you write to us, your email preferences, and which links in our emails you open.
- Location you choose to share. The town you type, or, only if you tap the locate button and your browser allows it, your device's location, which we use to find your nearest town. We place building sites by town or neighbourhood, never by exact plot.
- Payments and credits. What you bought, your credit balance and how it was used. Card details go straight to our payment processor; we never see or store your full card number.
- Google Calendar, if you connect it. Described in full below.
- Usage and device information. Server logs (IP address, browser, time, the page asked for, errors) kept for security and to fix problems, and the site analytics described below.
How we use it
- To run the tools you use: show your projects, estimates and files, keep your bookings, answer your questions and send you the emails and messages you asked for.
- To keep accounts and records secure, prevent abuse and fraud, and fix problems.
- To understand which tools and pages are used, so we can improve them.
- To send product updates, only if you joined the waitlist or mailing list. Every such email has an unsubscribe link.
- To meet legal and accounting obligations.
Some features use automated systems, including artificial intelligence, to read what you give them (for example a question, a description of a home or a photo) and produce an answer, estimate, image or summary. These outputs can be wrong; see our terms. We do not use automated decisions that have legal or similarly significant effects on you.
We do not sell your personal information, and we do not use it for advertising.
Google user data and Google Calendar
Team members who host viewings and consultations can connect their own Google Calendar to Keja calendar. Nobody can connect a calendar for someone else. When you connect, Google asks for your consent and Keja receives access to your email address and to the events in your calendar (the calendar.events permission).
What Keja does with it.
- Reads when you are busy, so nobody is offered a time you have already given away.
- Adds each booking you host to your calendar, and changes or removes it when the booking changes or is cancelled.
- Notices when you move or delete a booking's event in Google, so the booking can be updated with you.
- Lets you see, create, change and delete your own events from inside Keja.
What Keja keeps. Your Google email, your access tokens (stored encrypted), and for events in your primary calendar: title, time, location, description and whether it marks you busy. Only you can see your events' details in Keja. Everyone else, including Keja's own administrators in the product, sees only that a time is taken.
Limited Use. Keja's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- We use Google user data only to provide and improve the calendar features described above, which you can see in Keja.
- We do not transfer it to anyone except as needed to provide those features, to comply with the law, or as part of a merger or sale with the same protections.
- We do not use it, or sell it, for advertising, retargeting or interest-based ads.
- We do not use it to build, train or improve artificial intelligence or machine learning models, and we do not send your calendar events to artificial intelligence services. Other Keja features see only whether a time is free.
- No person at Keja reads your calendar data unless you ask us to (for example for support), it is needed for security or to investigate abuse, or the law requires it.
Disconnecting. You can disconnect Google Calendar in Keja calendar at any time. Keja then revokes its access at Google and deletes the copies of your own events it held. You can also remove Keja's access from your Google Account at myaccount.google.com/permissions. Events Keja added to your calendar for bookings stay in your calendar until you delete them.
Signing in with Google gives Keja only your basic profile (name, email, picture), never access to your calendar, email or files.
Business channels: Google Drive, YouTube, Facebook and Instagram
Some Keja team tools let a business that uses Keja, such as a property company, keep its videos in its own Google Drive and post them to its own YouTube channel, Facebook Page and Instagram account. Only people the business has invited use these tools, and only an administrator of the business can connect or disconnect an account.
What Keja asks Google for, and why.
drive.file: only the files a team member picks or that Keja creates in the business's Drive, to open source footage and save finished videos. Keja never makes a Drive file public.youtube.upload: to upload a video a team member has approved and asked Keja to post.youtube.readonly: to read the channel's name and the channel's own videos (title, description, picture, whether each is public, and its views, likes and comments counts), so the team sees every video in one place.yt-analytics.readonly: to read watch time, average view duration, shares and subscribers gained, for each video Keja posted and for the channel day by day, so the team can see what works.youtube.force-ssl: to read comments on the business's own videos and post the replies a team member writes or approves.
From Meta, with the business's consent, Keja posts videos to the chosen Page and Instagram account, reads the Page's and the account's own posts with their numbers and comments, posts the replies a team member sends, hides comments a team member hides, and reads the business's ad spend.
What Keja keeps. The connected channel and account names and IDs; access tokens, stored encrypted; a copy of the business's own newest posts on each connected channel (the words, the address of the post and of its picture, the date and the numbers), refreshed from the platform and deleted once the platform has not shown the post for 30 days or the account is disconnected; the numbers above for each post and each day; and the comments people leave on the business's posts (the commenter's public name, handle and account ID, the words and the time), with the reply that was sent and who sent it. A comment Keja has not seen on the platform for 30 days, for example because the commenter deleted it, is deleted from Keja. Post numbers are also recorded against the post in the business's customer records, so it can see which posts bring enquiries.
People who comment. If you comment on a business's post, its team sees your comment in Keja and may reply under the post. If your comment asks about buying, renting or viewing a home, it can become an enquiry in the business's customer records with your public name and handle, so the team can follow up. Keja never replies on its own: a person on the team decides every reply.
Drafted replies. To help the team answer, Keja sends a comment's words, together with the post's caption and the business's own published listing details, to an artificial intelligence service that drafts a reply. The draft is shown only to the team, who change it or discard it. Nothing else from the business's Google account is sent to artificial intelligence services.
Limited Use. Keja's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use this data only to provide the features described here, which the team can see in Keja; we do not transfer it except as needed to provide them, to comply with the law, or as part of a merger or sale with the same protections; we do not use it, or sell it, for advertising; we do not use it to develop, improve or train generalised artificial intelligence or machine learning models; and no person at Keja reads it unless the business asks us to, it is needed for security or to investigate abuse, or the law requires it.
YouTube. These features use YouTube API Services. By using them you agree to the YouTube Terms of Service, and Google's Privacy Policy applies to what YouTube receives.
Disconnecting. An administrator can disconnect YouTube or Meta in the tool's settings at any time. Keja then deletes the tokens, the comments and the channel's day-by-day numbers it kept for that account. You can also remove Keja's access in your Google Account at myaccount.google.com/connections (or Google's security settings at security.google.com/settings/security/permissions), and in Meta's Business Integrations settings.
Analytics and cookies
kejalabs.app uses Google Analytics to count visits to each tool. We send only the page's path with any record or link identifiers removed, and the tool's name. We never send page titles, search terms, your name, email or account identifier. Google signals and ad personalisation are turned off. Google Analytics sets cookies to tell visits apart; you can block them in your browser or with Google's opt-out add-on.
We also store a few things in your browser that the site needs: that you are signed in, your light or dark choice, and similar settings. We do not use advertising cookies.
Where your data is kept
Our service providers keep data in data centres that may be outside the country where you live. When data moves between countries we rely on the provider's contractual and security commitments to protect it as this policy describes.
How long we keep it
We keep your account and what you add for as long as your account is open. When you ask us to delete your account, we delete or anonymise your personal information within 30 days, except what we must keep for legal, tax, accounting or security reasons, or to settle a dispute. Server logs are kept for a limited period for security. Google Calendar data, and the comments and day-by-day numbers of a business channel, are deleted when the account is disconnected, as described above.
The free-text sentence you may write when you first open Keja, describing what you are looking for, is read to tailor your home screen and is not stored.
Your choices and rights
Depending on where you live (for example under Kenya's Data Protection Act, 2019, the EU and UK GDPR, or other local law), you can ask us to:
- tell you what personal information we hold about you and give you a copy;
- correct it if it is wrong;
- delete it;
- stop or limit how we use it, or object to a use;
- move it to another service in a common format.
Email legal@kejalabs.africa from the address on your account. We will answer within 30 days. You can unsubscribe from emails with the link in each one, tell us on WhatsApp or by email to stop WhatsApp messages, and disconnect Google Calendar at any time. You also have the right to complain to your local data protection authority, such as Kenya's Office of the Data Protection Commissioner.
Security
Data is encrypted in transit, private files are reachable only by the people allowed to see them, calendar tokens are stored encrypted, and access inside Keja is limited to the people who need it. No system is perfectly secure; if a breach affects your personal information we will tell you and the authorities as the law requires.
Children
Keja is not meant for anyone under 18, and we do not knowingly collect information from children. If you believe a child has given us information, contact us and we will delete it.
Changes to this policy
If we change this policy we will update the date at the top, and for significant changes we will tell you in Keja or by email before they take effect.