Kutumba is a private family tree. This notice tells you what personal data we handle, why, where it lives, how long we keep it, and what you can do about it. It is designed to align with India's Digital Personal Data Protection Act, 2023 and the rules made under it. A lawyer has not yet reviewed this notice, so it is a draft.
Who we are
Kutumba is run by BrainFrys Private Limited, Visakhapatnam, Andhra Pradesh, India. We are the Data Fiduciary for your data. That means we decide why and how it is used.
You can reach us about anything at hello@kutumba.space. It is our only inbox.
What we collect and why
We only collect what the app needs to work. Here is every kind of data, and what we use it for.
- Your email address. To create your account, sign you in, confirm changes and send you emails about your account, such as a password reset.
- Your password. We never see or store your password as typed. Supabase Auth stores only a hash of it, so it cannot be read back. We use it to check that it is you.
- Your profile. Your display name, the language and script you want relationship names in, how they are shown, and your light or dark theme. We use these to show your tree the way you like.
- The people you add. For each person: their name, nickname, gender, birth and death dates or years, whether they are living, birth order, a custom name you call them, and notes you write. We use this to draw your tree and to work out what each relative is called.
- Relationships. Who is a parent or partner of whom, and the kind of link (for example birth, adoptive or step). We use this to build the tree and to name each relative.
- Places. Towns and villages you attach to people, such as a native place or a birthplace, with the years if you give them. We keep place names and an approximate point on the map, rounded to about 100 metres. We do not store street addresses or house numbers. We use this for the family map and place filters.
- Photos. Photos you upload for people in your tree, and any caption you write. We use them to show faces on the tree and on person pages.
- Your settings. Your language, display and theme choices.
- Connected relatives, if you use them. This is optional. If you invite a relative, or accept an invitation, we keep the link between the two of you, what was chosen to be shared, the suggestions made, a history of what happened, and a record of your consent. The section "Connected relatives" below lists all of it.
- The email address of a person you invite. The person who invites types it once, so we can send the invitation. After the email is sent we keep only a hashed form of it, which cannot be read back as an address. See "Connected relatives".
- Consent and nominee records. We keep a record of which version of this notice and of our terms you accepted, when (our server's time), and which browser you used. If you name a nominee, we keep their name and email address. We only write to your nominee if you tick "Let them know by email" when you add or remove them, and then we send one email. These are our own records, kept so we can show that consent was given and carry out your wishes. Only our server writes the consent records. You can read your own but cannot change them. See "Your rights" below.
- Technical logs. Our hosting and database providers record things like the time of a request, your IP address, the browser you use and errors. We use them to keep the service secure and working, and to investigate problems.
Information about your relatives is entered by you. You are responsible for having a good reason to add it. See the section on people who appear in someone's tree.
What we do not do
- We never sell your data.
- We show no ads.
- We use no tracking or advertising cookies, and no analytics that follow you around.
- We use only the essential cookies that keep you signed in.
Why we may use your data
We use your data only for the purposes above, and only because you gave your consent when you created your account and accepted this notice. We do not use it for anything else. If we ever wanted to, we would ask you first.
Connected relatives
This part is optional. You can use Kutumba without it. It lets you link a person in your tree to that relative's own Kutumba account, so the relative can suggest updates to that one entry, such as a new photo. It does not share your tree.
How an invitation works
- The person who invites (the inviter) picks someone in their tree, types that person's email address, and can add a word for how they are related. We send one email. It names the inviter by their display name and shows the relation word. We add no tracking pixel and no extra images to it.
- The inviter can only invite a living person who is certainly 18 or older. See "Children" below.
- Before the invited person answers, they see only the inviter's display name and the relation word. They do not see the inviter's tree or anyone in it.
- The link in the email works for 30 days. The invited person can accept it, say no thanks, or say "Do not ask me again". Saying no does not need an account. Accepting needs a Kutumba account, so the invited person signs in or signs up, and accepts these documents like anyone else.
- Nothing is shared with anyone until the invited person accepts and chooses what to share.
- To limit abuse, one person can send 10 invitations in 24 hours, and one email address can be invited 3 times in 24 hours.
What can be shared
Only four things, and only the ones the connected relative chooses: name, nickname, photo and birth date. The birth date is off unless the relative turns it on. They can change the choice at any time. Nothing else from their account is shared, and nothing from the inviter's tree is shown to them.
When a connected relative changes one of the things they share, the app offers the new value to the inviter as a suggestion for that one entry. The inviter chooses to accept or decline each suggestion. A suggestion that is waiting is withdrawn if the connection is paused or ended.
Applying suggestions automatically
The inviter can instead choose "apply automatically". A suggestion then applies by itself only if all of these are true:
- it is one of the four things above, and the relative still shares it;
- the connection is active and not paused;
- the person in the inviter's tree is certainly 18 or older;
- the suggestion is less than 30 days old;
- an earlier suggestion for that value has already been accepted, so the first change always asks;
- the inviter has not changed that value by hand since the last accepted change; and
- the inviter has not undone an automatic change of that value.
Every automatic change is recorded in the history. The inviter can undo it. After an undo, that value goes back to asking first. When a photo is accepted, a copy of it is stored in the inviter's own private photo folder. The original stays in the relative's folder.
What we store about a connection
- The link. Which person in the inviter's tree, the two accounts, the status (invited, accepted, declined, cancelled, expired or revoked), the dates, and the relation word.
- A hash of the invited email address. We make it with a secret key held only on our server. It cannot be turned back into the address. We use it to recognise the same address again, for example to honour a refusal and to apply the daily limits. It still relates to a person, so we treat it as personal data and protect it like the rest.
- The invitation token. Stored only as a hash. It stops working after 30 days, and it is deleted once it is used or expires.
- The choices. What is shared, whether suggestions apply automatically, and whether the link is paused.
- Suggestions. The old and new value of each suggestion and what happened to it.
- Where a value came from. A small note in the inviter's tree, such as "Accepted from" the relative's name as it was then, with the date.
- History. Each step: invited, cancelled, accepted, declined, ended, paused, resumed, suggested, accepted, declined, withdrawn, applied automatically, undone, choices changed. It records who and when, never the values themselves. Both people can read it.
- Consent records. When a relative accepts, changes what they share or stops, we record which things, the version of the connection notice, and when. These are our own records, kept so we can show what was agreed.
- Refusals. If someone says "Do not ask me again", we keep a hash of their email address, or their account, so that invitations are not sent.
We do not look up whether an email address already has a Kutumba account. The inviter sees the same answer whether or not the address could receive an invitation, so the app cannot be used to find out who has an account.
Who sees what
Both people can see the link, its status, what is shared and the history. The inviter can see the suggested values for their entry. The invited person cannot see the inviter's tree, any other person in it, or the inviter's email address.
Stopping, and what stays
- Pause or end. Either person can pause or end a connection at any time in the app. Pausing stops new suggestions and withdraws those waiting. Ending a connection does the same, for good. A connected relative can also stop sharing a single thing at any time.
- What stays after a connection ends. Values already accepted stay in the inviter's tree. It is their tree and their entry, and they can change or remove it. A photo copied into the inviter's folder stays there until they remove it. The note saying where a value came from stays too. The link, the history and the suggestions stay as a record until the inviter deletes the person or their account.
- If a connected relative deletes their account. The connection ends and waiting suggestions are withdrawn. Suggestions they sent are erased with their account, and so are their consent records. Values already accepted stay in the inviter's tree.
- If the inviter deletes the person or their account. The link, the history, the suggestions and the hash of the address are erased with it. The consent records of the connected relative stay until that relative deletes their own account.
- An invitation that is not accepted. Records of a declined, cancelled or expired invitation, including the hash of the email address, are deleted by a daily clean up about 365 days after the invitation ended. Used or expired tokens are deleted by the same job.
- Refusals. We keep a refusal until the person asks us to remove it or deletes their own account, because forgetting it would let invitations start again.
- Backups. Backups kept by our providers can hold erased data until they expire. It is not used.
If you were invited and have no account
We send the invitation because a person you know asked us to. Until you accept, we hold only the hash of your address, the token hash, the relation word, and the fact that the invitation was made. The plain address is not kept in our database or logs. To have an invitation removed, or to be sure you are never invited again, write to hello@kutumba.space with the subject "Data request:", or use the data request form. We will ask for the address that received the email, so we can match it to the hash. We may ask you a question to check it is yours.
Who handles your data for us
We use a few providers to run the service. They act on our instructions.
- Supabase stores the database, handles sign in, and stores your photos. Our Supabase project is in the ap-south-1 region, Mumbai, India.
- Vercel hosts and serves the app (hosting and serving the app).
- Resend, when we switch it on, sends our account emails, such as the confirmation and password reset emails, from hello@kutumba.space. It then sees your email address and the message. Until then, Supabase sends the sign in and password emails. Invitations to connect are sent only through Resend, so they can go out only once Resend is switched on. For an invitation, Resend sees the invited person's email address, the inviter's display name and the relation word in the message. Resend keeps its own delivery log for its own period.
- Photon, run by komoot, and Ola Maps help you search for places. When you type in the place search, only the text you typed is sent to them. Nothing about your account, your tree or the people in it is sent. Ola Maps is used only if we have switched it on. Otherwise Photon is used.
Because Vercel, Resend (when enabled) and Photon may run outside India, the text or request data they handle may be processed outside India. We only send what each of them needs to do its job.
How long we keep your data
- We keep your data for as long as your account exists.
- When you delete a person, that person and their links, places and photos are erased. If that person was connected to a relative, the link, history and suggestions for that person are erased too.
- When you delete your account, we erase your account and everything in it: your profile, your tree, your people, places and photos, your connections, your nominee, and your consent records. What stays in other people's trees after a connection is described under "Connected relatives".
- Photos are removed from storage together with the person or account they belong to.
- Backups made by our providers roll off within the provider's own backup window. Erased data can sit in those backups until then. It is not used.
- Technical logs are kept by our hosting and database providers. We aim to keep them for at least one year, as the Rules ask, and then delete them. How long each provider keeps them depends on its plan.
How we keep your data safe
- Row level security in the database means each account can only read and change its own rows.
- Photos are in a private store. We show them only through signed links that stop working after a while.
- Our providers encrypt data in transit (HTTPS) and at rest.
- Passwords are stored as hashes.
- Account deletion, password and email changes ask you for your password again.
No system is perfectly safe. If something goes wrong, we will tell you. See the next section.
If something goes wrong
If there is a personal data breach that affects you, we will tell you without delay. We will explain 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, as the Rules require.
Your rights
You have rights over your data. This is how to use each one.
- Access and download. In the app, go to Settings, then Your data and privacy, and download your tree as a file. The file covers your tree, places and settings. It also has a section on connected relatives, in both directions: the links, what is shared, the suggestions with their values, where values came from, the history, your own connection consent records, and whether you have refused invitations. Photos, your nominee and the other person's email address are not in it. A photo suggestion appears as "a photo". You can see every photo in the app.
- Correction. Edit any person or your own profile in the app. Changes save straight away.
- Erasure. Delete a person from their page to erase them and their photos. Delete your account in Settings to erase everything.
- Connected relatives. You can stop sharing one thing, pause, or end a connection at any time. That withdraws your consent to that sharing. See "Connected relatives" for what stays.
- Withdraw consent. You can withdraw your consent at any time. Deleting your account withdraws it and erases your data: in Settings, choose Delete your account and data, type the word shown and enter your password. You can also do this from the screen that asks you to accept an updated notice. We cannot keep your account without your consent, so withdrawing consent means the account goes.
- Nominate someone. In Settings, you can name one person (a name and an email address) who may exercise your rights for you if you die or cannot act for yourself. We keep these details but we do not contact your nominee on our own. If your nominee or your family writes to us, we check who they are by email before we act.
- Grievance. If something is wrong, write to us at hello@kutumba.space. Start the subject with "Privacy request:" or "Data request:" if you can.
We will answer privacy requests and grievances within 90 days, and usually much sooner.
If you are not happy with our answer, you can complain to the Data Protection Board of India. Please use our grievance process first. The Board will expect that.
Children
Kutumba is for adults aged 18 and over. We do not knowingly make accounts for children, and there are no profiles for children.
A child may appear in a family tree as a person, added by the adult who is responsible for them. That adult is the one who gave us the information and is responsible for it. If you are a parent or guardian and want a child's entry corrected or removed, write to us and we will do it.
Connected relatives is for adults only, on both sides. We do not send an invitation about a person who is under 18, and we do not send one when the age cannot be told from what is in the tree. A person counts as an adult only when their full birth date shows they are 18 or older, or when a birth year, allowing for a year that is only approximate, makes it certain. The person in the tree must also be living. An invited person who accepts must be shown as an adult in their own profile too. We do not check ages against any document. We rely on the dates entered, so if an entry is wrong, it can be wrong. If you think a child has been invited, write to us and we will end the connection and erase it.
If you appear in someone's tree
Maybe you do not use Kutumba, but someone in your family added you to their tree. The person who added you entered your name and other details. We keep them only to show that person their own tree. Your details are not shown to anyone else, unless you accept an invitation to connect and choose to share some of them. See "Connected relatives".
You can ask us to see what is held about you, to correct it, or to remove it. Use the data request form, or write to hello@kutumba.space with the subject "Data request:". Tell us who added you if you know, and which entry is yours. We may ask you for proof that it is you before we act.
Earlier versions
Every earlier version of this notice stays readable. Version 1.0, effective 6 October 2026.
Contact and Grievance Officer
BrainFrys Private Limited, Visakhapatnam, Andhra Pradesh, India.
Email: hello@kutumba.space
Grievance Officer: Nithin, Founder. Reach him at hello@kutumba.space.
Changes to this notice
We may change this notice. When we do, we will change the version number and the effective date above, and we will ask you to read and accept the new version the next time you open a page in the app. If you do not agree, you can delete your account.
Read our Terms of use too.