What we keep, and what we will never do with it.

The contact form records the adult’s name, email, question, the form’s page and an optional campaign label in KulPortal’s enquiries and invites section. It stays separate from family accounts. We use the email to answer the question, not to subscribe the person to news. An invite is sent only if separately requested. The form records the words agreed to and when. After ninety days without a reply the record is deleted under the existing prospect retention rule. If the person asks us to stop, contact details and the question are cleared and a keyed contact hash remains to prevent re-adding them. Please do not put children’s details, passwords or health records in an enquiry.

The family account: family name, the parent's email and password (hashed with bcrypt), whether you have confirmed that email, a family code, the referral code your family was given and which family invited you — that family can see your family's name and the day you joined, nothing else — or, since 21 September 2026, which Kulraise partner introduced you if you signed up with a partner's code: a partner is a person we pay a share of what your family pays for a plan, and what that partner sees is how many families joined through their code and what those families paid for a plan, as counts and rupees, never your family's name, a child, or anything inside the app — a note you may have written when signing up before 14 September 2026, and each member's name, avatar — the emoji, and since 21 September 2026, for a child, the figure they build on the Avatar screen (which parts they chose, and a small picture of it drawn on their own device, shown to the family in place of the emoji) — colour, a chosen illustration preference (scenery, boy or girl, used only to select app artwork and never inferred from a name or photograph), date of birth (used to fit habits to a child's age and to wish them a happy birthday inside the app — never outside it) and 4-digit PIN (also hashed).

What the family creates: habits and completions, pocket-money transactions, savings, fixed deposits and fund holdings, goals, budgets and spending categories, wishes and shopping requests, perks and redemptions, routines, streak freezes, challenges — including the case a child made for one in their own words — cheers, meals and meal votes, optional daily check-ins (glasses of water, meals, mood and an optional note; who sees them is under Wellbeing check-ins, below), a parent’s encouragement note, calendar events, lessons passed and lessons a parent writes, family posts and reactions — and, since 21 September 2026, a parent’s announcements and which members tapped Got it on each, with the time, and the awards a family invents. Once it arrives, we also keep the family's own lines for the quote card on Today, which a parent writes and the family reads.

Streak levels. For each child, the highest streak level they have opened, the day they opened it, and the highest we have celebrated with them, so their room never goes back. A deleted habit or a broken streak never lowers it.

Room visits. A child's room in My world can be visited, to look only. A visit shows the room and its level name, such as Star room, and whose room it is — never habits, streak days, money or anything else, and nothing can be sent from it. Brothers and sisters can visit a child's room while a parent of that child keeps it on; it is on at first. A linked family's children — the ones that family shares with you — can visit it only if a parent of the child turns it on for that family; it is off at first, and each family decides for its own children. The child sees who can visit and cannot change it. We keep the two choices, and nothing about a visit: not who looked, and not when.

Marked done. A parent can mark a child's habit done for yesterday or the day before, when it was done and not ticked. It counts for that day, as a tick a parent said yes to does. We keep which parent marked it, and show it as Marked by and that parent's name to the family's parents and to the child. If that parent is removed, the day stays marked and the name goes.

Notes on money. A parent can write a note when sending a child a surprise, and can type a name for who gave money towards a goal or a wish, such as Mama. We keep the note, or the name, in the child's pocket record, beside the amount and the day. A surprise also keeps the name of the parent who sent it. A typed name has at most three digits and no @, and it passes the same checks as a message to a child. The person named is not told and needs no account.

Who sees a note or a name. The child and the child's parents see it. It shows on Recent activity in Money, on My pocket on Play, on Recent money on a Grown-up child's Today, in the Money story, on the goal under Given towards it, and in the Log, under Announcements. The child's own devices that have notifications on also get it in a notification, which can show on a lock screen. No parent's device gets one. Brothers and sisters see in the Log that a surprise or a gift came, never the note, the name or the amount. A linked family sees neither. Nobody at Kulraise sees a note or a name.

How long. Once saved, a note or a name cannot be changed or taken out on its own. Both are deleted with the child's record when a parent removes the child, and with the family when the family is deleted.

A child's choice to hide their own amounts on their screen is kept on that phone and never reaches us. Changing your family's currency changes the sign on every amount; nothing is converted.

A spending limit, if a parent sets one for a child: a spend over it waits for a parent's yes. We keep the ask: the amount, what it was for and the child's note; which parent said yes or no, and when; and that parent's note, if they wrote one. If the pocket no longer holds the amount when a parent says yes, the ask is turned down, and we keep that parent's note or, if there is none, the reason. A yes records the spend from the pocket, as every spend is recorded; a no records nothing more. A child can take back an ask still waiting, and it is deleted. An ask goes with the child, and who answered it goes with that parent if they are removed.

School and study, if your family uses them. A child can add, change and delete their own homework, tests, projects and kit, and a parent can do the same for any child. Each item shows who added it. We keep an exam's subject, date and what to revise; a project's title, due date and steps; and, for homework, what it is, the day it is due and about how many minutes it takes. We keep when homework or a step was ticked done. A child can tick off their own homework and a project's steps. A parent can delete any of it at any time, and a child can delete what they added. Each item is deleted 30 days after its date, with its diary photo. An exam's revision habit is an ordinary habit, paused on the day of the exam and kept with the child's other habits. Things to buy for a project go on the family's shopping list as ordinary items, which the rest of the family can see, so they name neither the project nor the child.

A child's week. We keep the timetable a child or a parent enters: fixed things such as school, tuition, classes and activities, their days and times, and the child's own study times. We also keep what the child writes about when and where they study, and whether they want a reminder, and whether the child is at school or college and how marks are shown (percent, letters or points). The reminder is a notification on the child's own devices a few minutes before a study time. It carries the child's own words and can show on a lock screen. No parent's device gets one. The timetable, the child's words about when they study and the reminder choice are deleted when 12 months pass with no change and no use: nobody has changed them, opened the week, or had a plan or a reminder made from them. Delete everything, in Settings under the child, removes them at once. Whether the child is at school or college, and how marks are shown, stay until changed or deleted.

A school diary photo. A homework item can carry one photo, such as a page of the school diary. It is the fourth kind of photo kept as described under Photos and voice notes, below: on our server, in its memory, outside the database and every backup, for as long as its item exists, and deleted with it. If the server restarts, it is cleared and the item says the photo has gone. No machine reads the photo, and nobody at Kulraise can see it.

Who sees School and study. The child and the family's parents see all of it, and the child sees exactly what a parent sees. A brother or sister never does. A linked family never does. Nobody at Kulraise does, with or without a support key. Nothing is sent to any outside service, and no AI reads or writes any of it. A child aged 18 or over decides whether their parents see their study, including deals, reviews, meetings and College; until they say yes, a parent sees none of it.

Study sessions. When a child starts a study session, we keep the day, how long it ran, the subject and topic, the way of studying, and how the child said it went. A child can add a session by hand; it says it was added by hand. A session left running is stopped by the server after a while. Sessions are kept for 13 months.

Topics and the plan. We keep the subjects and topics a child lists, how sure the child is of each, and the plan made from them. The plan is worked out on the child's own phone and on our server, from these and nothing else. We also work out, on our server, how ready a child is for a test or exam; this is shown to the child and the parents and to no one else. A subject goes when nothing has touched it for 13 months.

Test results. We keep each test or result: the subject, the marks, and where the child says the marks went. A parent can mark that they have seen the paper. A result is kept for 13 months from its day.

Recall cards. We keep the question-and-answer cards a child writes and how the child answered each one. A card goes when it has not been answered or made for 13 months.

Past papers and mocks. We keep the papers a child plans or sits: the score, the time taken and the sections. A paper goes 13 months after the day it was done, or planned, or added.

Reward deals. A deal is an agreement between a child and a parent: a reward for marks, for study hours or for keeping to a plan. We keep its steps, who asked, each answer, and what was given. A child can take back an ask, or a change to a deal, of their own while it waits for the other side; nothing is paid and nothing is owed when they do. A parent sets a family limit on what a deal can pay and whether children may ask. A deal a parent has agreed pays by itself. When the result is seen — a parent marks the marked paper as seen, or, for a deal about study hours or a plan, the month or the exam is over — the step the result reached is paid into the child's pocket at that moment, with no parent paying it by hand and none needing to be there. The payment is recorded in the family's ledger as a reward, like any other. A treat is not money: it is listed as owed until a parent taps Given. A deal that is settled, declined or cancelled is deleted 30 days later. Money already paid stays in the ledger when a child's study is deleted.

Notes from teachers and meetings. A parent can write what a teacher said, and the questions to ask at a parents' meeting. The child can read them. A note is kept for 13 months from its day; a meeting 30 days after its day.

The four signs and the Sunday review. We show a child and the parents four signs, worked out from the above: how ready the child is for the next test, how many of the last seven days had study, how many of the sessions started were finished, and how the child's guess of a result compared with the result. We keep the date a family did the Sunday review and nothing else about it; the date is deleted 13 months after its day. The signs show counts, never a card, a paper or a score.

College. For a child set to college, we keep the attendance the student enters: for each subject, the classes held and attended, one class at a time or a week taken from the college portal. We keep the internals a student lists, with the marks it is out of, the marks got and the day it is due. We keep each semester's credits and grade-point average, and the backlogs the student lists with the day of the next attempt. The percentage, the CGPA and what the next semester needs are worked out each time they are shown and are not stored. Only the student enters any of this, and only the student deletes it a piece at a time; a parent's Delete everything (below) removes all of it. A parent sees it, and can set the course, the semester, the college's minimum and the CGPA aimed for. Nothing is sent to any college. Attendance and internals are kept 13 months; a cleared backlog 13 months from the day it was cleared. A semester result, and a backlog still open, are kept until deleted, because a CGPA needs the earlier semesters.

Delete everything. In Settings under the child, a parent can remove every piece of the child's study at once, whether the study coach is on or off. Pocket money already paid through a deal stays in the ledger.

When a child asks a parent to pay at a shop: the shop's UPI ID and name as its QR code gave them, the amount asked, what the parent then paid and how much of it came out of the child's pocket, and the child's note. The QR code is read on the child's phone — no photograph is sent to us or kept — and Kulraise never moves money or holds a payment credential: the parent pays in their own UPI app, and we record that they did.

Pocket money paid by a deal. A deal a parent has agreed pays its step into the child's pocket when the result is seen — or, for a deal about study hours or a plan, when the month or the exam is over — with no parent paying it by hand and none needing to be there at that moment. The payment is recorded in the family's ledger as a reward, like any other, and a parent can see it there. The rest of reward deals is under School and study, above.

Health entries, only when a parent chooses a condition for a child — since 21 September 2026 the condition is the one switch, and every health feature starts and stops with it: the condition chosen for a child and the note describing it, blood-sugar readings with their times and how they were taken, carbohydrates counted, insulin doses with the pen used, the pens themselves, food eaten outside planned meals, the times of day each person is reminded to check, and the two notes a parent types — the doctor's plan and what to do for a low. Since 20 September 2026, for a condition that is not diabetes — an allergy, ADHD, eczema, coeliac disease, or one you name yourself — a diary of what happened, in your own words: when, how bad in three words of your family's, what set it off, where, what happened and what was done; the doctor's words in three slots a parent types; the doctor's name; the next visit; and the expiry date on what the doctor said to carry, which the app reminds you about. Since 15 September 2026 the food log also holds your own list of dishes with their carbohydrate ranges and where each figure came from, and a packet may be looked up by its barcode in Open Food Facts, a public database. Since 16 September 2026 you can also press “What is in it?” on a dish that is on none of our lists, which sends the NAME you typed to that same database and shows what packets called something like it contain, per 100 g, straight off their own labels. You choose which packet and say how much was eaten; nothing is filled in for you. In both cases only the barcode or the typed name leaves our server: never a family, never a child, never a reading, and nothing that comes back is stored by us. Since 16 September 2026 a photograph of a plate can also be used to NAME a dish from our own list: the picture is sent once, is never stored by us, and no number is ever read out of it — the carbohydrate comes from the dish, as it does when you type the name. It is switched off unless the server has been given a picture-reading service, and the screen says so.

A parent's own programme, if they start one: which programme, which child it is about, the day it began, and two numbers each evening — how many flare-ups there were in the house and how many hours the child slept. It records nothing else about the child at all. There is no notes field, no rating and no description, because a parent must not be able to write a sentence about a child that the child could never read.

Money a parent takes back: if your family switches the deduction module on, we keep the amount, the parent's reason in their own words, the parent's name, and whether it was reversed. A reversal adds a row; it never erases the first one, because the child saw it happen.

Private messages between the people in your family, in twos and in the chat the whole family shares: the text itself, stored so it can be delivered and read again. If your family links with another family, the same holds for messages between the two families (below). We also keep the reactions and stickers people add, with who added them and when. And we keep when each message was read, and in the family's chat by whom: that is what shows as read. Each person sees the family's chat from the day they joined. That someone is typing is shown while they type and never stored. A photo or voice note in a message is kept 48 hours at most, under Photos and voice notes below. Taking a message back marks it withdrawn and removes its text, sticker, photo or voice note, and its reactions. The marked row stays so the other person is told something was withdrawn rather than left doubting their memory.

Who can write to a child, and what a parent sees. A child writes with their parents and their brothers and sisters, in twos and in the family's chat. With children of a linked family, a child writes only if a parent allows it. With a linked family's grown-ups, a child writes only in a chat that includes one of the child's own parents. The exception is a grown-up a parent has named and approved for that child, such as an aunt, who can chat with the child privately where that kind of chat is open (Chats across linked families, below). A parent sees which brothers and sisters each child chats with, but never how often or when they last wrote. Across linked families a parent sees the same for a linked family's children, and for an approved grown-up, how often as well. A parent never sees the messages in a chat the parent is not in: not a word, a sticker or a picture. That holds between brothers and sisters, with a cousin, and with an approved grown-up. A child's Messages tells them, in one line, what their parents see.

Photos and voice notes. Four kinds of photo and recording are kept differently from everything else: a photo a child takes with Take photo, a photo sent in a message, a voice note, and a school diary photo on a homework item. Take photo is how a child ticks off a habit that a parent set to be checked by photo. A diary photo is one photo on a homework item, such as a page of the school diary (School and study, above). Each is kept on our server, in its memory — outside the database and outside every backup. A habit's photo, a photo in a message and a voice note are kept for 48 hours at most, and then deleted. A diary photo is kept for as long as its item exists and is deleted with it; an item is deleted 30 days after its date. A habit's photo goes sooner: the moment a parent decides the habit — Approve, Needs another go or Wasn't done. If the server itself restarts, all of them are cleared. If Kulraise switches Messages off, every photo and voice note sent in a message is deleted at once. When the space kept for them is full, the oldest goes first. So any of them can go before its time is up, and the habit, the message or the item stays and says that the photo or voice note has gone. Because no backup holds one, a deletion is final: nobody can bring one back, us included.

Before a photo is kept, our server redraws it, the right way up and no larger than 1600 pixels. That drops what the phone wrote into it, such as when and where it was taken and with which camera. A voice note is at most 60 seconds and is kept as it was recorded: only photos are redrawn. Each is stored under a random name. The database holds that name, whether it is a photo or a voice note, which habit or message it belongs to, and when it was taken or sent. A diary photo's name is held on its homework item. The database never holds the picture or the sound.

A habit's photo is seen by the family's parents and the child who took it, never by a brother or sister. A diary photo is seen by the child whose homework it is and the family's parents, never by a brother or sister or a linked family. A photo or voice note in a message is seen or heard by the people in that conversation. One from a linked family reaches a child only if a parent has switched photos, or voice notes, on for that child. Nobody at Kulraise can see a photo or hear a voice note, with or without a support key: there is no screen for it.

Every habit photo, and every photo and voice note in a message, has Save to phone, for parents and for every child. A diary photo is opened from its item to look at, and has no Save to phone. A saved copy is your family's own, on your own phone, and follows your phone's rules; Kulraise's copy is still deleted on time.

Announcements, posts and praise are not checked. Anyone in the family can write a post, a child included, and a parent can remove any announcement or post.

The switches above are a parent's, for each child, and nobody else can change them. A message that is blocked is not delivered and not kept, and the person who sent it is told why. When a child's message is blocked, we keep who sent it, to whom or to the family's chat, when, and whether it was a rude word or a link. Once link categories exist, we keep which one too. We never keep its words, its link or its picture. The child's parents see a list of these records, and each is deleted 90 days after it was written. A record is made only while that list is there for them. A child can report a brother or sister, or one of their messages, and can block a brother or sister — never a parent. We keep who reported or blocked whom, and when. A report goes to the child's parents only — who, by whom and when, never the message — and nothing of it reaches anyone at Kulraise. A parent sees a child's blocks and can lift one, and so can the child who made it. These checks are a list of words and a list of websites, and no person at Kulraise reads a message to make them.

Wellbeing check-ins. A daily check-in is a mood, glasses of water, the day's meals and, if the person likes, a note. A person's check-ins are seen by that person alone, unless a parent turns on Wellbeing for a child. Wellbeing arrives after this notice: first for a few families, then for every family. We keep a record of which families it reached first, and when. The check-in that comes with Wellbeing marks each meal eaten, some or skipped, with what they had if they want to say.

Wellbeing is off for every child until a parent turns it on, one child at a time. Then that child's mood, water and meals, with what they had, and the notes the child chooses to share, are shown to the child's parents. A parent sees them on the Family screen, on the child's Wellbeing page, and beside the child's readings in Health and the Care diary. The child is told this on their check-in screen before anything is shared, and nothing written before that is shown. From then on, that screen always says who can see what. On Play, notes are shared; on Standard, a child can keep any note just for themselves; on Grown-up, notes are private unless the child shares one. A private note is shown to nobody else: not on a parent's screen, in the report for the doctor, or in a copy of the family's data. A parent is not told that one exists.

Kulraise keeps check-ins and shows them; it does not analyse them. There are no scores, no counts of low days, no conclusions, and no alert or notification because of anything a child wrote or chose in a check-in. Check-ins are never shown to anyone but the child and the child's parents — not a linked family, a Kulraise partner, or anyone at Kulraise, with or without a support key. A parent can choose, one report at a time, to print a child's shared check-ins in the report for the child's doctor, marked as the child's own words. Once printed or shared, that copy is the family's own.

With each check-in we also keep whether its note is shared, and whether it was made while the screen said a parent can see it. For each child, we keep whether a parent turned Wellbeing on, and when the child tapped Got it. We also keep a count of the days each person has checked in, which is how stars for checking in are counted. The count holds no answers and stays when check-ins are deleted. Turning Wellbeing on or off for a child, and deleting a child's check-ins, are written to the family's own audit trail.

From the day your family agrees to this notice, every check-in, a parent's own included, is deleted after 90 days, and is gone from every backup 16 days after that. Once Wellbeing arrives for your family, a parent can delete all of a child's check-ins at any time, and a child on Grown-up can delete any of their own notes. Both stay possible even if Wellbeing is later switched off. The help pages, for a parent who is worried and for a child who wants to talk to someone, record nothing about who opens them.

A record of things that happened to the account: every sign-in and failed sign-in, PIN resets, balance adjustments made by hand, members removed, email and password changes, and refused password prompts. A parent can read this at Settings → Security. It is not deleted, and when a member is removed their name stays in the line recording the removal.

Consent: when you agree to these documents or confirm you are a child's parent, we record your name, the child's name, the wording in force, the date, the IP address you did it from and a short description of your browser. These records are never edited or deleted — that is what makes them worth anything.

Anything you send us for help: what you or your child typed into Settings → Help, every message back and forth with staff, and the answer. Staff read these by design, including tickets tagged as health.

Billing: your plan, its status and renewal date, any discount granted to your family and the label on your bill, plus a staff note about why you are on the plan you are on. There is no payment provider connected to Kulraise at all, so no card or bank detail is ever stored, because none is ever taken.

Email: a record of every message we sent you or decided not to send — your address, which email it was, whether the provider accepted it and what it said if not. We do not keep the subject or the body, because a filled-in email carries names, a join code and sometimes a reset link.

Technical basics needed to run it: a session cookie; a push subscription and browser description for each device where reminders or alerts were switched on; a per-day note of which reminders were sent to whom, and a note of which birthday or anniversary greeting each member has already seen so it is shown once; the IP address on a password-reset request; the hashed, expiring link that confirms your email; and short-lived counters keyed to an IP address or email so that somebody cannot sit and guess a password.

Where a field has a microphone button for speaking instead of typing, the words you say are turned into text by your browser's own speech service, and we receive only the text. Which service depends on the browser: Google's in Chrome on Android and on a computer, Apple's in Safari and on an iPhone, Microsoft's in Edge on a computer. A voice note in Messages is different: the recording itself is sent and kept (see Photos and voice notes).

If you import a calendar, the titles and times of those events are copied into Kulraise and kept like any other event.

Since 17 September 2026 we also count how many times each PUBLIC page — the landing page, the carbohydrate table, the guides, the help answers — is opened. That count is four things and no fifth: the day, which page, where the reader came from, and how many. There is no cookie, no session, no identifier and no IP address, so it cannot tell one person from another and cannot tell anybody from you. “Where the reader came from” is only ever the website's name, never the address they were on. Nothing inside the app is counted, and neither is a family's own share card, whose address carries your invite code. It is kept on our own server and sent to nobody.

Everything above is kept for as long as the family account exists and is deleted with it, except for these. Photos and voice notes are kept 48 hours at most, except a diary photo, which goes with its item. From the day your family agrees to this notice, check-ins are deleted after 90 days. Each School item is deleted 30 days after its date, with its diary photo; what else is kept for study, and for how long, is the next paragraph. A message that is blocked is never kept, and the record that a child's message was blocked is deleted after 90 days (above). A link with another family lasts until a parent of either family ends it, or either family is deleted. The chat between them goes seven days after the link ends. A copy of anything deleted, such as a whole family, a person, a check-in or a message, stays in the backups for a while. It is gone from every backup within 16 days (Where it lives, and who can reach it, below).

School and study. Study sessions, results, recall cards, past papers, teacher notes, attendance and internals are kept 13 months from their day, and a cleared backlog 13 months from the day it was cleared. A subject goes when nothing has touched it for 13 months. The date of a Sunday review is kept 13 months. A parents' meeting is kept 30 days after its day, and a settled, declined or cancelled deal 30 days after. A child's week — the timetable, their words about when they study and the reminder choice — is deleted after 12 months with no change and no use. A semester result, and a backlog still open, are kept until deleted. A parent can delete any of it sooner, and Delete everything, in Settings under the child, removes all of a child's study at once.

Some of it is deliberately never edited or removed while the account lives, because a record you can quietly change is not a record: the consent trail, the family's own audit trail, deductions and their reversals, support conversations, discounts granted and withdrawn, and the email delivery log.

Deleting a member removes everything that belongs to them — every habit, transaction, reading, dose, goal and message. Their NAME survives in a few places that describe things which really happened: the line saying they were removed, a support ticket they opened, a deduction applied to them, and a family post about them. We think that is right, and you should know it before you press the button rather than after.

Besides those, three things are pruned on a schedule, and none of them is anything a family wrote inside the app: the server's own performance readings, which are about the machine and mention no person, kept for thirty days; the invite list described below, which forgets anyone who has not replied in ninety days; and a message sent to one of our addresses, kept under its own rule below.

No advertising, no ad trackers, no analytics that follow anyone around, and no selling or sharing of family data with anyone. Another family sees any of it only through a link a parent of yours made, and only what that parent turned on.

No profiling of children. Health entries are used for your family's own screens and the report you print for your doctor, and for nothing else.

No staff access to the CONTENT of your family — a reading, a note, a message, a dose — unless a parent creates a support key. A photo, a voice note, a check-in or anything in School or Study cannot be reached even with one. Keys are scoped, expire, are revocable in a tap, and every single use is written to an audit trail you can see.

Staff actions are logged whether or not a key exists. Opening your family's account page writes a row naming your family and the staff member who did it, and that record is kept. Somebody looking at your account can always be shown to have looked.

No dosing advice. Kulraise records the numbers a person decided; it never calculates one.

No family in our marketing. When we tell people about Kulraise — by email, WhatsApp or this site — nothing from any family using it is used: not a name, an amount, a reading, a screen, or the fact that you are here. Every family, name and figure we publish is invented; if one matches a real person, that is coincidence, not your data.

No reading of your messages to keep them safe: the checks on a child's chats are automatic, on our own server, and nobody at Kulraise reads a message to make them.

No analysis of check-ins. Kulraise never scores them, never counts good or bad days in them, never raises an alert from them, never uses them for analytics or advertising and never gives them to AI. No reward ever depends on what a child answers.

If you asked one of us face to face, or explicitly requested an email invite through our website enquiry form, to be told about Kulraise, we write down your name, the email address or WhatsApp number you gave us for it, when and where you asked and, for an in-person request, which of us you spoke to, what you agreed to and in which words, a keyed hash of each contact, the secret behind the links in your emails, and a note of each message we send you — which one it was, whether it went and whether it was delivered, never its text. That is the whole record, and it is kept apart from every family's data: nothing in it comes from the app, and nothing in it goes into the app.

It is used to send you the one invite you asked for — on WhatsApp if you gave a number, by email otherwise — and, only if you press the button in an emailed invite saying so, an occasional note about what is new by email: a few a year, never more than four. Nobody can say yes to the notes on your behalf, not even the person you spoke to. Email is sent through our mail provider from an address that is not read. WhatsApp messages go through MSG91 and Meta, who see the text of the message — which is why an invite carries only your first name, the code and a link, and why nothing about any family ever travels that way.

To stop, reply STOP on WhatsApp, press the stop button behind the link in any email, or tell the person you spoke to, and nothing more is sent — not an invite, not a note, on any channel. Your name, address and number are then deleted; the keyed hash of each is kept, for as long as we keep an invite list, so that nobody here can add you again by mistake. If you never sign up, you are deleted ninety days after your last reply — and nothing more is sent after three messages with no reply, whatever the calendar says. If you do sign up, the row is deleted and your family's account is where your data lives from then on, under the sections above.

To complain or to ask what we hold, tell the person you spoke to, write to the address under Getting in touch below, or go to the Data Protection Board of India. Our invites come from an address that is not read; the one under Getting in touch is.

A message sent to any address at our domain reaches the people who run Kulraise, through a mail router (Cloudflare) that hands it to our own server and keeps a delivery log of its own but not the message. We keep the address you wrote from, the name on it, the address you wrote to, the subject, the date and the text of the message, as plain text. An attachment is not kept — we count that one arrived, and drop the file. When a message from a person arrives we send one automatic acknowledgement — at most one a day to the same address, never to a bounce, a mailing list or a follow-up in a thread we have already answered — saying that it landed and repeating what this section says. If we answer, the reply goes through our mail provider (MSG91), and the reply and when it was sent are kept beside your message.

It is used to answer you, and for nothing else. Writing to us does not put you on the invite list, and it is not matched against any family: whoever wrote is a person who wrote, and a reply can only go back to the address it came from.

A message is deleted ninety days after it is marked as dealt with, and any message a year after it arrived, whatever its state. To have it deleted sooner, say so in the message itself and the person who reads it deletes it then — the record of that keeps a reference number and nothing of what you wrote. To ask what we hold, or if you are not satisfied, go to the Data Protection Board of India. Deleting a family (below) does not reach a message you sent us; this rule does.

If you applied on kulraise.com/partner, we keep your name, email address, phone number and city, what you wrote about how you would grow it, the version of the partner terms you agreed to with the IP address and browser you agreed from, your partner code, whether you asked for your phone number and email to be drawn on your card (the card is public — it is what you share), the UPI ID you gave us for payouts (never a bank account number or a card — there is no field for one), the address of your own page, and a ledger: for each month a family you introduced paid for, the month, what they paid, your rate, your share, and whether it is waiting, approved, paid (with the UPI reference) or voided and why. We also keep a note of each email we sent you — which one, when, and whether it went — never its text. Staff may write a short note about handling your application, which you do not see.

It is used to run the programme and to pay you: to approve you, to draw your card, to count the families that typed your code, to work out and pay what you are owed, and to tell you at each stage — approved, first family, first earning, a payout, a step up, and a quiet month. Nothing in it comes from inside any family's account, and nothing a family does inside the app is shown to you: your page shows counts and rupees. Payouts go through your bank and ours, which see the transfer as any bank does; where the law requires tax to be deducted at source, you may be asked for your PAN by email, and it is not stored in the app.

To end the partnership, reply to any email from us and say so, or write to the address under Getting in touch below; nothing more is sent, your code stops working, and what you were owed is still paid. Your name and the ledger are then kept for eight years after the last payout, because a payment we made has to be a payment to somebody and India's tax rules can ask us to show it for that long; the rest — phone, city, what you wrote, the page address — is deleted when the partnership ends. To ask what we hold, or to complain, write to us or go to the Data Protection Board of India.

A child's account is created and controlled by a parent or guardian, who consents on the child's behalf. Children have their own PIN so their pocket money and health log are not open to the whole household.

Health data is sensitive personal data under India's IT (Reasonable Security Practices) Rules 2011, and personal data under the Digital Personal Data Protection Act 2023, which gives a child's data added protection. Where the UK or EU GDPR applies, it protects this data too. It is stored to provide the service to your family, kept for as long as the account exists, and deleted with it.

A parent can delete any member from Settings → Family, and with them every habit, transaction, reading, dose and message belonging to that member. Their name remains in the record of the removal itself, and in anything that describes something which happened — a ticket they opened, a deduction applied to them.

Low and high alerts are sent to the parents of that family only, on devices where a parent switched notifications on.

A child cannot make or accept a link with another family. A child talks with their parents and their brothers and sisters. With children of a linked family, a child talks only if a parent allows it. With a linked family's grown-ups, a child talks only in a chat that includes one of their parents, or with a grown-up a parent approved by name, where that kind of chat is open. A parent sees which brothers and sisters each child chats with, but never how often or when they last wrote. Across linked families a parent sees the same for a linked family's children, and for an approved grown-up, how often as well. A parent never sees what is said in a chat the parent is not in. A child's check-ins reach a parent only if the parent turns on Wellbeing for that child, and only after the child has been told.

Linked families reaches families in stages. Nothing in this section, or in the four after it, happens until it has reached your family and a parent in your family links with another family.

A parent can link your family with another — relatives, usually — so the two can chat, send a child a gift, share a wish list, share announcements and birthdays, and run a challenge together. Only a parent can make a link or accept one. There is no search and no public profile: nobody can find your family unless a parent in it gave them a link code.

A parent makes a link code for one link. It is never the code your children sign in with. It works once. It stops working when it is used, 48 hours after it was made, when a parent of the family that made it cancels it, or when that family already has twenty linked families. A parent who types a code that has stopped working is told only that it is not open — never why, and nothing about the other family. We never keep the code itself, only a one-way scramble of it (a hash), and no screen of ours shows a code to anyone at Kulraise. A family can have five codes waiting and twenty linked families at most.

Each family names the link for itself. The parent who makes the code and the parent who types it in each give the link a name, such as Bua's family or Mama's family. Neither family ever sees the other's name for it.

For each linked family, any parent of your family chooses what it can do and see — chat, gifts, wish lists, announcements, birthdays, challenges and room visits — which of your people it can see, and which of your children may talk with which of theirs. Each starts off, and a parent turns on what they want. A linked family sees only what you turned on: the names and faces of the people you share; a child's wish list if you share it; the announcements you share with them; the birthdays you share; in a challenge you run with them, how many habits each child in it has done; and, if you let their children visit a child's room, that room and its level name (Room visits, under What we store). A face is the small picture and the colour a person has in Kulraise, chosen from Kulraise's own set — never a photo, and never the character a child has built. If a person's name looks like a phone number or an email address, or contains a word our checks stop, the other family is shown someone from and their own name for the link instead.

They never see a balance, a reading, a dose, a care diary, a check-in or anything in School or Study, except how far along a goal is, as a bar and a percentage, when a parent of the child shares that goal with them. Nor do they see a habit or its photo, except the words of a part in a challenge together with parts that a parent of each family agreed to, a conversation they are not in, your email address or the code your children sign in with. They see a parent's UPI ID only if that parent turned gifts on for them (Gifts from a linked family, below).

Nobody at Kulraise sees your links. Our staff screens show no link, no link code, no chat between families, no gift, and no count of any of them. While linked families is being tried with a few families, the owner of Kulraise sees which families are in the trial and since when, and nothing of what they do with it.

A parent can end a link at any time. Ending it stops all sharing from that moment, both ways, and closes every chat between the two families. The chats, and everything else the link held, are deleted for both families seven days later, within five minutes of the seven days. Until then only the family that ended the link can restore it, with every permission it had and its chats. The other family is told that the link was ended and when the chats will be deleted, and cannot ask for it back. After seven days a new link needs a new code.

If either family deletes its account, everything it wrote in a chat with the other family is deleted with it, and the other family sees that the family has left. What remains of the link is deleted within seven days, or at once if the other family removes it.

Ending a link, taking back a person or a permission, cancelling a code and removing your UPI ID always work, even when your plan is unpaid. If linked families is switched off for your family, nothing is shared while it is off, and you can still end a link, restore one you ended, remove a family that has left, cancel a code and remove your UPI ID.

Your family's own records — the record of a stopped message, a report, a block, and a gift that arrived for your child — stay with your family for their usual periods whatever happens to the link, and the other family never sees them. On the screens that list them, a person of the other family is named only while they are still shared with you on a link that is active. After that the record reads someone no longer shared, someone who has left, or your own name for the link. A gift's line in a child's pocket is different: it keeps the sender's name as it was when a parent tapped It arrived, until the sender leaves Kulraise.

The chat between the two families is for the grown-ups each family shares. A child joins it only when their own parent puts them in, reads it only from that moment on, and stays in it only while a parent of their own family is in it. The child's parent can take them out at any time.

Cousins — a child of yours and a child of theirs — chat in twos only when a parent of each family has allowed that pair. Either parent can withdraw it, and the chat closes at once.

A grown-up of a linked family writes to your child privately only if you approve that grown-up, by name, for that child, and only where Kulraise has opened that kind of chat. Today it is open only between two families that are both trying that chat with us. It opens to every family only once each person has a sign-in of their own. You can withdraw an approval at any time, and the chat closes at once. While that kind of chat is not open to your family, nobody can open one: an approval you gave earlier is kept, with what was written, shown to no one, until you withdraw it or the link ends, and it stands again if the chat is opened to your family again.

You see who your child chats with across families and, for an approved grown-up, how often — a count of the messages of the last seven days — never what is said. A parent never sees the messages in a chat the parent is not in.

In every chat a child is in, across families too, our server stops rude words and links, whoever writes them (Keeping children's chats safe, above). A stopped message is not delivered and not kept, and the person who wrote it is told why. Photos and voice notes from a linked family reach a child only if that child's own parent has switched each of them on for that child, and they are kept 48 hours at most, as everywhere in Kulraise. Our checks read words and web addresses only: they do not look inside a photo or a voice note.

When a message your child writes in a chat with a linked family is stopped, we keep who wrote it, to whom or in which chat, when, and whether it was a rude word or a link — never the words. The record is your family's: you see it, the other family never does, and it is deleted 90 days after it was written.

When a message a grown-up of a linked family writes to your child is stopped — in a private chat with your child, or in the two families' chat while your child is in it — we keep who wrote it, to which child or in which chat, when, and whether it was a rude word or a link — never the words. That record is your family's too: you see it on Children's chats, the grown-up's own family never sees it, nobody at Kulraise sees it, and it is deleted 90 days after it was written.

If you are that grown-up: when a message you write in a chat with a linked family's child is stopped, that child's parents are shown that it was, when, and which kind — never your words. Before you first write in a private chat with a linked family's child, and the first time you write in the two families' chat while a child of the other family is in it, one screen tells you this and asks you to agree. We keep that you agreed, and when.

A child can report anyone from a linked family, or one of their messages. The report comes to the child's own parents only — who was reported, by whom and when, never the message — and never to the other family or to us. A child can block a person from a linked family from their chat of two: the block takes effect at once, without a parent's approval, closes that chat both ways, and the blocked person is not told. The child, or a parent of the child, can lift it, and the chat then opens as it was. We keep who reported or blocked whom, and when. A report is kept for as long as your family's account exists, and the reported person's name is removed from it when they leave Kulraise; a block is kept until it is lifted. Both stay with your family whatever happens to the link.

A child's chats across families open only with a PIN the child chose. A PIN that a parent typed for a child opens none of them: the child is asked to choose their own first. A grown-up's private chat with a child opens only with a PIN that grown-up set themselves. If a child's PIN is set by anyone but the child, a grown-up's PIN by anyone but that grown-up, or either person is renamed, every chat of two that person has across families ends, a child is taken out of the two families' chat until a parent puts them back, and both families' parents are told that a chat ended — never which, and never why.

When a parent hands their phone to a child without the child's own PIN, the two families' chat opens for the child only while every parent of your family is in that chat. A cousin's chat and a grown-up's private chat do not open. In the two families' chat opened that way, Report is not offered: a child reports from a phone opened with their own PIN.

When a chat of two closes — a pair or an approval is withdrawn or ends, or a person is no longer shared — nobody can open what was written in it any more, and it is deleted seven days later. Allowed or approved again, the chat starts empty. A block is different: while it stands nobody can write in the chat, and its words are kept, because lifting it opens the chat as it was. The two people in it still see what was written before the block.

A notification about a linked family names the link, by your own name for it. It never carries a message's words, the name of a person of the other family, an amount or a UPI ID.

What we cannot tell. Kulraise checks which PIN a phone was opened with, not who is holding it. Anyone who signs in as an approved grown-up, with that grown-up's PIN, can use that grown-up's chat with your child; anyone who signs in as a child, with that child's PIN, can use that child's chats. A PIN a parent typed for a child, and that the child has not yet replaced, is known to that parent. Approve only a person you know. The screens where you approve a grown-up and allow a pair of cousins say this.

If a parent turns on gifts for a linked family, that parent's UPI ID is saved — only once that parent has ticked a box, on that screen, which says which linked family's grown-ups will be shown it. Those grown-ups — the ones that family shares with you — see it on the screen where they send a gift, and nowhere else. It is shown as a QR code, a button that opens their own UPI app with the UPI ID and the amount filled in, and the UPI ID to copy. The money goes from their bank to yours, in their UPI app: Kulraise never moves it, never sees a bank account or a card, and cannot check that a payment was made. Gifts are in rupees, from ₹1 to ₹1,00,000.

Nothing marks itself as arrived. After paying, the sender types the UTR — the 12-digit reference their UPI app shows. The gift then waits until a parent of the child checks the bank and taps It arrived or Didn't arrive. It arrived adds it to the child's pocket, once, with who sent it; the parent can correct the amount to what arrived.

A gift can be towards a shared goal or a wish. It still waits until a parent of the child taps It arrived; it then goes into the child's pocket and, from there, into the goal, and the pocket's record shows both. A gift towards a wish makes a goal for that wish. We keep what a gift was for. On the goal, the child and the child's parents see each gift that arrived towards it: who gave it, the amount and the day it arrived.

A prize for the other family's child. In a challenge together with parts, one family can agree to pay the prize for every child in it. A prize for a child of the other family is then a gift like any other: paid by UPI in the paying parent's own UPI app, recorded with the UTR, and added only when that child's parent taps It arrived. Kulraise never moves the money.

We keep who sent it, for which child, the amount, the sender's note, the UTR, which parent's UPI ID the sender was shown (which parent, never the UPI ID itself), whether a parent tapped Didn't arrive, and when a parent tapped It arrived — and no other time: not when it was recorded, and not when it was marked Didn't arrive.

The person who sent a gift sees whether it is waiting, arrived or did not arrive — never when. On their own page for the link they see each gift they recorded: the child, the end of the UTR, that one word and, until a parent has tapped It arrived, the amount they typed. Once it has arrived they are shown no amount, because the child's parent may have corrected it. No notification tells them it changed, and the other parents of their family do not see the list. A gift marked Didn't arrive leaves the child's parents' screens. It is deleted when the person who sent it removes it from their list — they can then record it again — when they leave Kulraise, when the link is deleted, or with the child or the child's family.

Your UPI ID is yours alone: other parents in your family, your children, and we at Kulraise are never shown it, and it is in no notification, no log and no export. It is stored encrypted in our database, under a key that is kept on our server and not in the database. You change or remove it in Money → Bank rules. It is deleted when you remove it, as soon as no linked family has gifts turned on with it, and with you or your family. Once a grown-up of a linked family has seen it, we cannot take it back from them.

The record of a gift that arrived stays with your family after the link ends, for as long as your family's account exists: the amount, the child, the UTR, which parent it was paid to and when It arrived was tapped. If the person who sent it leaves Kulraise — they are removed from their family, or that family deletes its account — their note is deleted and their name is taken out. The record and the line in the child's pocket then say only which linked family the gift came from or, once that link is gone, that it came from a linked family.

A child never sees a gift that is waiting, a gift's note, a UTR, a UPI ID or the screen that sends one. After It arrived, the child sees the gift in their pocket, with who sent it. Brothers and sisters see that there was a gift, never the amount or who sent it. Nobody at Kulraise sees a gift: not its record, its amount, its note, or how many are waiting.

A wish list is shared one child at a time: the other family's parents see the title and price of each wish that is open, and nothing else about it. The child's own wish list says who it is shared with.

I'll buy it myself. A grown-up of a linked family who can see a child's wish can say they will buy it, so nobody else buys it too. The child's parents see who said so; the child does not, so it can stay a surprise, and nobody else is shown it. We keep who said it and for which wish, never when. It is deleted when that grown-up takes it back, or with the wish, the grown-up or the link.

A goal is shared one goal and one linked family at a time, by a parent of the child. That family's parents — never their children — see its name, its target and how far along it is, as a bar and a percentage; never the amount saved, or who gave what. The child's own goal says who it is shared with.

Announcements. An announcement you choose to share with a linked family reaches that family's parents. It reaches their children only if their own parent has turned that on for your link, and only after the same checks as a message to a child. No reaction and no Got it crosses a link.

Birthdays. The other family sees the day and month of the people you share, never the year or an age. A line on the day reaches their parents, and their children only if both families share birthdays.

A challenge together comes in two kinds. Counting habits together is a number of habits and two dates, worded by Kulraise — neither family can write anything into it. The children in it and both families' parents see how many habits each child in it has done, never which.

A challenge together with parts is one thing the children do together, a part each, one after another or in any order. The parent who asks writes what each part is and an award both families see, such as Movie night together; those words pass the same checks as a message to a child before the other family sees them. The other family's parents see every part, who does it, the dates and the award before they say yes, and choose which of their shared children takes each part left for them. While it runs, the children in it and both families' parents see each part's words, who does it and whether it is to do, waiting for the part before it, waiting for a parent's yes, or done — never a child's other habits, rewards, money or prize. Each family's parents give the yes to their own child's part, and each family pays its own child's reward and any prize of its own: no money passes between the families, unless one family agrees to pay every child's prize; it is then sent as a gift by UPI and recorded only when a parent of the child says it arrived (Gifts from a linked family, above). Kulraise never moves money. Neither family sees what the other pays its own children. Either family's parent can stop it. A child who is no longer shared, or whom their own parent takes out, leaves it, and that part waits for another child of their family. When the link ends, it stops for both families, and it is deleted with the link.

About a link we keep: which two families are linked; each family's own name for it and its switches; which people each family shares; which pairs of cousins each family has allowed; which grown-up is approved for which child; which of your children's rooms each linked family's children may visit; who said I'll buy it myself on which wish; a challenge together with parts: its name and its award, each part's words, whose family each part is for and which child does it, its order, rounds and dates, who pays and the prize for every child, and how many rounds each part has counted; which goals each family shares; and the moments below.

The moments we keep: when the link was made, kept on the link and on each family's side of it; when each person was shared; when a child was put in the two families' chat; when each family allowed a pair of cousins; when a grown-up was approved; when a grown-up agreed, before first writing where a linked family's child is; when a child's part in a challenge together with parts began; and, if the link is ended, when, by which family, and when its chats will be deleted. For a link code that has not been used: when it was made and when it stops working. For a chat of two that has closed: when it closed and when its words will be deleted. For each chat between the families: when it was first opened and when it was last written in, and for each message, when it was written. These are what let a chat show a person only what came after they joined, and let the 48 hours and the seven days run. The ids we make for a link carry no time: the id of a link, a code, a shared person, a pair, an approval, an agreement, a gift, a record, a report and a block is random. A chat and a message are numbered as every chat and message in Kulraise is, by an id that begins with the moment it was made — the same moment as above.

Access and portability: the bank statement and the 30-day health summary download as CSV from inside the app, and a full copy of your family's data can be requested at any time.

Correction: everything is editable in the app by a parent — readings, doses, goals, wishes and the plans you have typed.

Erasure: a parent deletes the family from Settings → Delete family. It needs no reason, no email to us, and nobody at Kulraise can refuse it. It is scheduled for seven days so that a press nobody meant can be undone — every parent is told immediately, any of them can cancel, and the date is on every screen until it happens; the same screen will also do it straight away for anyone who would rather not wait.

What deleting the family removes: everything above, except a message you sent to one of our addresses, which is kept and forgotten under its own rule in the section before this one. Every habit, transaction, reading, dose, message, award and calendar entry; your own audit trail; the consent records; the support conversations; the emails we have a record of sending you. Deleted, not marked deleted, and no shadow copy is kept for anything, marketing included — the people we write to about Kulraise are adults who asked us in person, never anyone taken from this database. Backups age out on their own, so a deleted family is gone from every backup within 16 days rather than at once, and a backup is never restored to undo a deletion. What the backups are, and where they are kept, is under Where it lives, and who can reach it.

What survives a deletion, so that you know before rather than after: our staff's own record of any time a Kulraise person opened your account — the who, the what and the when — with anything naming your family stripped out of it. That trail is the promise that staff can always be shown to have looked, and it would be worth nothing if leaving erased it. And one line recording that a deletion happened, when it was asked for and when it ran, holding no name, no email, no address and not even which parent asked. And, in another family's records, a gift somebody in your family sent to a child of a linked family: the amount, the child, its bank reference (the UTR) and when It arrived was tapped, without the sender's name or their note. And a linked family's own records about a person of your family, with no name: that its child reported or blocked them, or that a message they wrote to its child was stopped — a report for as long as that family's account exists, a block until it is lifted, a stopped message for 90 days at most.

Withdrawing consent: set the child's condition back to none and no further readings, doses or diary lines are recorded; delete the member or the family to remove what is already there.

Notifications: push is off until someone turns it on for a device, and can be turned off again on that device.

Save to phone keeps your own copy of a photo or voice note before ours is deleted. Links stay off in a child's chats unless a parent turns them on, and a blocked kind of website stays blocked unless a parent unblocks it. Photos and voice notes from a linked family reach a child only if a parent switches them on. To stop sharing with a linked family, end the link, and restore it within seven days if that was a mistake. To stop a habit asking for a photo, change how it is checked. Once Wellbeing arrives for your family, a parent can stop showing a child's check-ins by turning it off for that child, and can delete them.

Data is held in a PostgreSQL database on a server the family that runs Kulraise controls, in India. Photos and voice notes are held in that server's memory, and never in the database or a backup.

There are two kinds of backup, and both stay in India. Every night the server copies the database onto its own disk, compressed but not encrypted, and each of those copies is deleted within fourteen days. Every day Acronis, a backup service, copies the server, but not those nightly copies, to its data centre in India. Each daily copy is encrypted with a password only the owner of Kulraise holds, and the last 16 are kept. So anything deleted, a whole family included, is gone from every backup within 16 days. A backup is never restored to undo a deletion.

Traffic is served over HTTPS only. Session and staff cookies are HttpOnly and marked Secure whenever the connection is encrypted.

Staff can see account-level facts — family name, the parent's email, plan, discount, counts of habits or readings, and what you wrote when you signed up — without a support key. They cannot see the content of a reading, a note, a message or a dose without one.

The owner of Kulraise — and nobody else on the staff — can also check the payments Kulraise makes on its own for mistakes, such as one made twice. Those payments are the allowance, savings interest, payday for habits, the bonus for days of checks logged, and a fixed deposit that closes. To check them, the owner sees your family's name, each child's name, the dates and the amounts. Every check is written to your family's record in Settings → Help, and the check itself changes nothing.

There are two documented exceptions to the support key, and they are the only ones. Only the owner of Kulraise can use either: the payments check above, and break glass for a family locked out of their own account. Break glass makes a one-time password reset link and opens nothing else. It is audited, and the family is told in plain words that it happened.

When you write to us, staff can also leave short notes to each other on your question — “tried calling, no answer” — which you do not see. They are about handling your question, never about your family or a child, they are deleted when the question is, and anything staff actually DO to your account is shown to you on Settings → Help instead.

If money is involved, we keep what was paid or written off for each month, who recorded it, and any reference you gave us. Nothing in Kulraise can charge you — there is no card on file and no payment provider connected — so a payment is always something a person here recorded after seeing it arrive.

The health features are a family log and a habit tracker. They do not diagnose, do not suggest doses or treatment, and never replace your doctor or diabetes team. Targets, ratios and routines come from them.

The timings shown next to a pen — for example that a regular human insulin is given some minutes before food — are the values a parent entered after being told them by a clinician. Kulraise repeats them; it does not decide them.

For a data request, a correction or a complaint, use Settings → Help inside the app, which reaches the people who run Kulraise directly. If you are not a member of a family — a parent who finds a child in a family that is not theirs, or anyone with a question about this page — write to hello@kulraise.com, which a person reads. Under the DPDP Act you may also complain to the Data Protection Board of India if you are not satisfied with the response.

Grievance officer: Krsnaha Suthar, the owner of Kulraise. Write to hello@kulraise.com. We acknowledge a grievance within 24 hours and resolve it within 15 days.