Privacy

Last updated 13 October 2026

Knosite is run by Parikshith, a sole proprietor based in Bengaluru, India, trading as Knosite (“we”). This page explains what we collect when you use Knosite, and what happens to the data of visitors who talk to an assistant on a Knosite customer’s website.

Two roles

For our customers’ accounts (the people who sign up and use the dashboard) we decide how data is used. For website visitors who chat with a customer’s assistant, the customer decides: we process those conversations and leads on their behalf and only to run the service for them. If you chatted on someone’s website, contact that website’s owner about your data: they can give you a copy, stop profiling you or delete it from their Knosite dashboard, and we will help them answer.

What we collect from customers

  • Account details: your email address, name if you give one, and sign-in method (email code, password or Google).
  • Workspace data: websites you add, their settings, team members and invitations.
  • Content you give the assistant: pages we read from your site, and files you upload with their extracted text.
  • Billing details: plan and subscription status. Card and payment details go directly to Razorpay; we never see or store them.
  • Usage: how many AI messages your workspace used, and service logs kept for security and debugging.

What the widget collects from visitors

  • The messages a visitor sends and the assistant’s replies, the page they were on, and a random visitor id.
  • Anything a visitor chooses to enter in the contact form or a short survey, such as an email address, name, message or answers.
  • A Cloudflare Turnstile check before a new conversation or contact form, to stop bots.

Understanding leads

Customers can use Knosite to understand the visitors who interact with their assistant. For those visitors, Knosite notes the pages they viewed on that website (without query strings), how many times they’ve visited, terms they tapped, survey answers, and actions the website marks as meaningful (such as clicking “Book a demo”). AI reads their conversations to note what they need, and estimates how ready they are to buy, with plain-language reasons the customer can see.

  • This information stays in the visitor’s browser until they chat, tap a highlighted term or answer a question. People who only browse are never sent to us.
  • Each customer chooses whether this waits for consent from their own cookie banner. Knosite never shows its own prompts to visitors.
  • Visitors whose browser sends a Global Privacy Control signal are not profiled on any website.
  • Customers can stop profiling a person, give them a copy of their data, or delete it, at any time.

What’s stored in the visitor’s browser

The widget doesn’t set cookies and doesn’t follow visitors across websites. It uses the browser’s storage for this website only:

  • While the tab is open (session storage): the open conversation, so it survives page changes; tips already shown; and, for lead understanding, the pages viewed and marked actions.
  • Across visits (local storage): the random visitor id and a visit count, only where the website allows it; and a visitor’s choice to hide tips.
  • Where consent is needed and hasn’t been given, the visitor id is kept only for the open tab, and only once they start chatting.

How we use it

To run Knosite: answer visitors from the customer’s own content, deliver leads and webhooks to the customer, send account and usage emails, bill subscriptions, prevent abuse and keep the service working. We don’t sell personal data, and we don’t use customers’ content or visitors’ conversations to train AI models.

Who processes it for us

  • Cloudflare: hosting, databases, file storage, search index, page rendering, bot checks (Turnstile).
  • Google Firebase: sign-in.
  • OpenRouter and the AI model providers it routes to, including TypeSafe (Jev): writing answers, noting what visitors need, and judging whether a question can be answered and how ready a lead is. We request providers that don’t keep or train on the data.
  • Resend: sending email.
  • Razorpay: payments.

These providers may process data outside your country. They only get what they need for their part. The full list, and what each one sees, is on our sub-processors page.

How long we keep it

  • Conversations: for your plan’s history window (30, 90 or 365 days since the last message), then deleted.
  • Leads with an email address: for the period the customer chooses (12 or 24 months after the person’s last activity, or until the customer deletes them; new websites start at 24 months). Anonymous visitor profiles (no email) are deleted after the plan’s history window without activity.
  • When a customer deletes a lead, or everything for an email address, we delete the lead, their conversations from every device they used, and webhook logs that mention them.
  • Webhook delivery logs: 30 days.
  • Account and content data: while the account is open. When an account is closed we delete its data within 30 days, except what we must keep for tax or legal reasons.

Cookies

The dashboard uses the cookies and storage that sign-in needs, plus one cookie that only tells this site you are signed in so it can send you to the dashboard. No analytics or advertising cookies.

Your choices and rights

You can ask us to see, correct, export or delete your account data, or withdraw consent, by emailinghello@knosite.fyi. Under India’s Digital Personal Data Protection Act, 2023 you can also nominate someone to exercise these rights for you. If you live elsewhere, you have the rights your local law gives you, and we’ll honour them the same way.

If we get it wrong

Complaints about how your data has been handled go to Parikshith, the proprietor, athello@knosite.fyi. We acknowledge them within 7 days and aim to resolve them within 30. If you’re not satisfied, you can complain to the Data Protection Board of India, or to your local data-protection authority.

Changes

If we change this page in a way that matters, we’ll email account owners before it applies.