Privacy and security
What happens to your family’s details
Plain answers, with nothing promised that we cannot check. The legal text is the privacy notice. This page explains it, and says where it falls short.
Privacy notice version 2.0 · effective 8 October 2026 · designed to align with the DPDP Act, 2023
What we collect and why
We collect only what the app needs to work. This is every kind of data, and what it is for.
| Data | Why we have it |
|---|---|
| Your email address | To create your account, sign you in, and send account emails such as a password reset. |
| Your password | To check that it is you. We never see or store it as typed. See How sign in works. |
| Your profile | Your display name, language, how names are shown, and light or dark theme. |
| The people you add | Names, nicknames, gender, dates, notes and your own word for each. To draw the tree and work out names. |
| Relationships | Who is a parent or partner of whom, and the kind of link. |
| Places | Town or village names and an approximate point, for the family map and filters. |
| Photos and captions | To show faces on the tree and on person pages. |
| Connected relatives (optional) | If you use it: the link between two accounts, what is shared, suggestions, a history of what happened, and your consent record. For an invited person who has not answered yet: a hash of the email address, the word for how they are related, and a link token. |
| Consent and nominee records | Which version of the notice and terms you accepted, and when. If you name a nominee, their name and email. |
| Technical logs | Our hosting and database providers record request times, IP addresses, browsers and errors. This keeps the service secure and working. |
What we never do
- We never sell your data.
- We show no ads.
- The Kutumba code has no analytics and no tracking scripts, and sets no advertising cookies.
- The only cookies are the ones that keep you signed in.
- We use your data to run Kutumba for you and for nothing else. If that ever changed, we would ask you first.
The fonts you see are served from our own site, not fetched from another company each time a page opens.
Where your data lives, and who helps us run it
Your tree and photos are stored with Supabase, in Mumbai, India. The pages and the app’s code run on Vercel. We have not pinned Vercel to a region in India. When we checked on 6 October 2026, it was running in the United States, so your tree travels from Mumbai to a server in the US and on to you each time a page is built. These are the companies that handle data for us.
| Provider | What it does for us | What it sees | Where |
|---|---|---|---|
| Supabase | Stores the database, handles sign in, stores photos. | Everything you save, and your sign in details. | Mumbai, India (ap-south-1) |
| Vercel | Hosts and serves the website and the app. | Requests as they pass through, and request logs. | Not pinned to India. Running in the United States when last checked, 6 October 2026. |
| Photon (run by komoot) | Place search. | Only the place text you typed. Nothing about you or your tree. | May be outside India. |
| Ola Maps | Place search, only if we switch it on. | Only the place text you typed. | Not confirmed. |
| Resend | Account emails, and invitations to connect. Planned, not switched on yet. Until then Supabase sends the sign in and password emails, and no invitation can go out. | Your email address and the message. For an invitation: the invited person’s address, the inviter’s name and the word for how they are related. | To be confirmed when it is switched on. |
Place searches are made by our server, not your browser, so your own IP address is not sent to the place services.
Who can see your tree
Only you. Every table that holds your data has row level security, which means the database itself only hands an account its own rows. There is no public page, and no other user can see your tree or anyone in it. If you invite a relative to connect, that relative can only suggest changes to one entry, as described in Connected relatives below. If we add sharing, you will be asked before anything of yours becomes visible to anyone else.
There is one honest exception. The people who run Kutumba can reach the database, because someone has to run it. See What we cannot promise.
Connected relatives
Connected relatives is optional. You can invite a relative to connect with one person in your tree, so that relative can suggest updates to that one entry, such as a new photo. It does not share your tree. The relative never sees your tree or anyone in it.
Can someone add me without asking?
A relative can type your name into their own tree, as in any family tree, and you can ask for it to be removed. They cannot connect you to an account without your answer. An invitation is an email to your address, and nothing about you is shared until you accept. Accepting needs a Kutumba account. Saying no does not.
What the invited person sees and shares
- Before answering, only the inviter’s display name and the word they chose for how you are related. Not their tree.
- After accepting, you choose what to share, from four things only: name, nickname, photo and birth date. Your birth date is off unless you turn it on.
- Both of you can see the link, its status, what is shared and a history of what happened. The history never holds the values themselves.
- Connected relatives is for adults only. An invitation about a person under 18, or whose age cannot be told from the dates in the tree, is refused.
What the inviter can do with it
- What you share arrives as a suggestion for the inviter’s entry about you. The inviter accepts or declines each one.
- If the inviter chooses to apply suggestions automatically, one applies by itself only when the connection is active, the person is certainly an adult, the suggestion is less than 30 days old, and the inviter has not changed that value by hand since. Every automatic change is recorded, and the inviter can undo it.
- An accepted photo is copied into the inviter’s own private photo folder. Your original stays in yours.
What we keep about an invitation
- We never store the invited person’s plain email address. After the email is sent, we keep only a keyed hash, which cannot be turned back into an address. We still treat the hash as personal data.
- The invitation link works for 30 days. Only a hash of it is stored, and it is deleted once it is used or has expired.
- We never look up whether an address has an account. The inviter sees the same answer either way.
- To limit misuse, one person can send 10 invitations in 24 hours, and one address can be invited 3 times in 24 hours.
- The email is sent through Resend, so invitations go out only once Resend is switched on. We add no tracking pixel to the message.
- An invitation that ended without being accepted is deleted by a daily clean up about 365 days later. A refusal is kept until the person asks us to remove it, because forgetting it would let invitations start again.
How to stop it, and what stays
- Either person can pause or end a connection at any time. Waiting suggestions are withdrawn. A connected relative can also stop sharing a single thing.
- Values the inviter has already accepted stay in their tree. It is their tree, and they can change or remove it. A copied photo and the note saying where a value came from stay too.
- If the inviter deletes the person or their account, the link, history, suggestions and hash are erased with it.
- If you were invited and want it removed, use the data request form and choose the invitation option, or write to hello@kutumba.space. We delete the invitation and make sure you are not invited again. We ask for the address that got the email, to match it to the hash. We do this by hand.
- The download in Settings has a section on connected relatives, in both directions.
How photos are protected
- Photos live in a private store, not a public folder. Each file sits under your own account’s folder, and the rules of the store only let your account read it.
- The app shows a photo through a link that stops working after an hour, then makes a new one.
- A photo is deleted from storage when you delete the person or your account.
One caution. Anyone who holds a live photo link can open that photo until the link expires. The link is shown only to you, but if you copy it and send it to someone, it works for them for that hour.
How sign in works
- You sign in with your email and a password of at least 10 characters.
- Supabase Auth keeps only a hash of your password, which cannot be turned back into the password. We never see it and cannot read it back to you.
- Changing your email or password, and deleting your account, ask for your password again.
- Changing your password signs you out everywhere else.
- You can turn on two step sign in in Settings, with an authenticator app. It asks for a 6 digit code after your password. You also get recovery codes, shown once, each usable once.
- Too many wrong codes pause code entry for a few minutes.
Encryption, exactly
Pages and data travel over HTTPS. Supabase states that all customer data is encrypted at rest with AES-256 and in transit via TLS. We rely on that. We add no encryption of our own on top, so your tree is not end to end encrypted: the database, and so the people who run it, can read it.
If something goes wrong
We have a written plan for a personal data breach. It covers who does what, how to contain it (replace a leaked key, sign people out, close the hole, roll back a release), and what to write down from the first minute.
If a breach affects you, we will tell you without delay: what happened, what data was involved, what we have done, what you can do, and how to reach us. We will also tell the Data Protection Board of India, and send it a detailed report within 72 hours of becoming aware, as the DPDP Rules, 2025 ask.
The plan is written and ready. It has not yet been checked by a lawyer, and it has not been tested by a real incident.
How long we keep things
- As long as your account exists.
- Delete a person, and that person with their links, places and photos is erased.
- Delete your account, and everything in it is erased: profile, tree, people, places, photos, nominee and consent records.
- Our providers keep their own backups. Erased data can stay in a backup until that backup expires. It is not used.
- Technical logs are kept by our providers. We aim to keep them for at least a year, as the DPDP Rules ask.
What we cannot promise
Read this part
- No system is perfectly safe. Nobody can promise there will never be a breach. We can promise to tell you if there is one.
- One person runs Kutumba today. The person who runs it can reach the database. We do not browse trees. But that is a promise from us, not a rule the software enforces.
- Your tree is not end to end encrypted. See Encryption, exactly.
- Two step sign in is optional, and there is no way around it. If you turn it on and lose both your phone and your recovery codes, we cannot let you back in. Without it, your account is protected by your email and password.
- We rely on other companies. If Supabase, Vercel or a place service has a problem, we are affected, and we do not control them.
- We are not certified. We wrote Kutumba to be designed to align with the Digital Personal Data Protection Act, 2023. No lawyer or auditor has certified that it does, and we hold no security certificate.
- The age check is a tick box. Kutumba asks you to confirm you are 18 or older. It does not check.
- Backups are not in our hands. How long a backup keeps erased data depends on our providers.
Found a security problem? Write to hello@kutumba.space.