Reference

Legal terms for Indian accounts

Terms, privacy, cookies, and account checks sit together here, so you can see how we handle access, data, and requests before you open an account.

TermsPrivacyCookiesIndia

explore lobby Read FAQ

Access, privacy, and policy scope

kabook Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

This section explains the legal frame behind the site. We use it to set access conditions, language rules, account checks, and the way we store records tied to your account. If local law does not allow access in a place, we do not present the service

1
there; if it does, you can proceed under the published terms. Changes to payment handling, identity checks, or record keeping are reflected here, and the newer text replaces the older version from the moment it is posted. For UPI, Paytm, PhonePe, and Google Pay, the rules
2
shown before you confirm a payment stay linked to the same account and verification steps, so you can see what applies before you send a request or make a payment. We also use this page to explain who can ask for a correction, a copy, or
3
a removal where the law allows it. If a clause changes, we keep the wording direct and date the update so you can tell what applies today.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

REQUEST CHANNELS

Ways to send a request

If you need to change a detail, ask for a copy of your account record, or question a policy step, use the contact paths below.

Email request desk Send privacy, access, or correction requests here when you want a written trail. We use it for policy questions that need a proper record and for follow-up after identity checks.

In-app form Use the form inside your account for changes to contact details, consent choices, or record requests. It helps us match the message to the right profile without asking you to repeat the same facts.

Mail address If you need a formal letter trail, send a written request by post. Include your registered name, account email, and the change you want, so we can verify the account and act on it.

DATA AND ACCESS

How we handle your data

We keep only the data needed to run accounts, handle payments, stop misuse, and meet lawful duties.

Data use

We keep registration details, account contacts, and relevant transaction records only as long as we need them for service, security, and lawful duties. Once the retention period ends, we archive or remove what no longer has a purpose.

Cookie use

Cookies help us remember your language choice, keep a session open, and confirm that a browser request is really yours. Some cookies are needed for sign-in and security; others support preference storage and form behaviour.

Account security

We use device checks, login history, and session controls to flag unusual access. If a sign-in looks unfamiliar, we may ask for extra proof before we change account settings or show sensitive records.

Retention

Different records have different retention periods. Payment logs, identity checks, and request history may stay longer than profile details because law, audit needs, or fraud checks can require them for a longer period.

Change requests

To request a correction, deletion, or copy of your data, use the contact paths and tell us exactly what you want changed. We may ask for a match to the registered email or phone before acting.

Request handling

Only staff who need the request for their role can see it, and they work from the details you send. If we need more detail, we ask through the same channel and keep the thread together.

Common legal questions for kabook

These answers cover access, data handling, cookie use, record keeping, and change requests. We keep them short because the exact steps can shift with local law and the kind of request you send. If your case is specific, use the contact paths above and include the email or phone linked to your account so we can find the right record.

Access depends on local law. If a state or region does not permit the service, we do not offer it there. Where local law permits, you can open an account and use the published terms.

We keep registration details, contact data, device signals, and transaction records that help us run the account, verify requests, and meet lawful duties. We do not keep more than we need for those purposes.

Send the change through the contact paths and tell us what needs updating. If the request affects account identity, we may ask for a matching email, phone number, or another proof point before we change it.

Cookies help remember your language, session state, and certain security choices. If you clear them, some settings may reset and you may need to confirm the account again, which is normal for protected access.

Retention depends on the record type. Payment logs, identity checks, and request history may stay longer than profile details because law, security, or audit duties can require them after the account is quiet.

Only staff who need the request for their role can see it, and they work from the details you send. If another team must help, they get only what is needed to finish the task.

Use the contact paths and tell us whether you want a correction, deletion, or a copy. We will check your identity first and then act where local law allows.

Legal terms for Indian accounts

Ways to send a request

How we handle your data

Data use

Cookie use

Account security

Retention

Change requests

Request handling

Common legal questions for kabook

01 Can I access kabook from every state in India?

02 What data do you keep after I open an account?

03 How can I ask for correction to my details?

04 Do cookies change how my account works?

05 How long do you store account records?

06 Who reads my legal request?

07 What if I want my data changed or removed?

Related Pages