Privacy Policy

This policy covers three groups of people whose data flows through JestBot: account holders and agents who use the dashboard and agent panel, and visitors who chat with a JestBot-powered widget embedded on a customer’s site. For widget visitors and leads, the business that owns the bot is generally the data controller and JestBot acts as a processor on their behalf — see our GDPR & Data Subject Rights page for the full controller/processor breakdown and how to exercise your rights.

• Account holders: name, email, a hashed password or Google authentication identifier, and billing details processed via Razorpay.
• Agents: name, email, login credentials, and performance stats (assigned/resolved/missed conversations, points) tied to their agent account.
• Widget visitors & leads: the content of their conversation with a bot, and — where a bot owner has enabled it — name, email and/or phone submitted through the pre-chat lead form, plus its verification status.
• Widget session metadata: hashed IP address, domain, referrer, and country where available, used for widget analytics rather than individual tracking.
• The documents you add to your bots — files, pasted text, and ingested URLs — plus basic usage metrics (message counts, document counts) needed to run the product and enforce plan limits.

We use this data to authenticate you, run retrieval for your bots, calculate billing, enforce plan limits, and email you about your account — verification codes, password resets, and subscription status. Widget session metadata is used in aggregate for product analytics; it is not used to build individual visitor profiles for advertising, and JestBot does not run advertising of any kind on its own products.

For account holders and agents, we process data under the legal basis of contract — it’s necessary to provide the service you’ve signed up for — and, for analytics, legitimate interest in improving the product. For widget visitor and lead data, the legal basis is set by the bot owner as controller, typically consent captured via the pre-chat form or their own legitimate interest in responding to a customer inquiry.

Payments are processed by Razorpay, which handles your card/UPI details directly — JestBot never stores your full card number. Google sign-in and OTP delivery run through Firebase Authentication, and agent push notifications through Firebase Cloud Messaging. If you use BYOK, your prompts for that bot are sent to the provider you configured (OpenAI, Anthropic, Google Gemini, Groq, or Mistral) under their own privacy terms, separate from this policy. The full, categorized list of providers we rely on — and exactly what each one can access — is in our Subprocessors page.

Sensitive data gets specific technical protections, not just a general promise to “keep things safe”:

• Encryption in transit: all traffic between your browser, the embedded widget, and JestBot’s servers is encrypted via TLS — this covers the dashboard, agent panel, chat API, data API, and the widget’s streaming responses.
• Encryption at rest: if you configure your own OpenAI, Anthropic, Gemini, Groq, or Mistral key, it’s encrypted with AES-256-GCM before being written to disk, decrypted only in memory per request, and never logged, returned in an API response, or exposed client-side.
• Password & session security: passwords go through standard salted hashing before storage — we never store or have access to your actual password. Sessions use a short-lived (15 minute) JWT paired with a longer-lived (30 day) refresh token that’s itself stored hashed, not in plaintext.
• Access control: dashboard account owners, agent accounts, and JestBot’s own internal admin accounts are separately scoped — agents cannot access billing, API keys, or bots they haven’t been assigned to, and internal access to customer data is limited to what’s necessary for support, debugging, or a specific abuse investigation.
• Data isolation: every bot’s documents, embeddings, and conversation history are logically scoped to that bot and its owning account — there is no cross-bot or cross-account retrieval path.
• Real deletion: deleting a document, bot, or account removes the underlying content and vector embeddings rather than just hiding them, and deleted content is not retained for model training or any other secondary purpose.

The full technical detail behind each of these is in our Security page.

Google sign-in is offered as a convenience for creating and logging into your JestBot account, handled through Firebase Authentication. When you sign in with Google, we receive only the basic profile information Google provides for authentication — your name, email address, and a Google account identifier — and use it exclusively to create your account, log you in, and identify you within the platform. We do not request or receive access to your Gmail, Google Drive, Google Photos, or any other Google Workspace data through this sign-in flow.

JestBot’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Concretely, this means data obtained through Google Sign-In is:

• Never used to develop, improve, or train any AI/ML model — including generalized or foundational models, self-hosted or third-party
• Never transferred to any third-party AI/ML model provider (OpenAI, Anthropic, Google Gemini, Groq, or Mistral), including on bots where you’ve configured your own key for that provider
• Never fed into JestBot’s own self-hosted chat model as training or context data
• Never sold, and never used for advertising — JestBot does not run advertising of any kind
• Used solely for the authentication-related purposes disclosed in this policy

On the separate, unrelated question of how JestBot’s AI features work: the platform’s default chat model runs on Ollama, self-hosted entirely within our own infrastructure — a bot’s visitor conversation content is processed locally on our own servers when using this default model, and is never transmitted to a third party for training or any secondary purpose. If a bot owner chooses to bring their own OpenAI, Anthropic, Gemini, Groq, or Mistral key, that bot’s visitor conversation content is sent directly to the configured provider under that provider’s own terms — but this data path is entirely separate from, and never includes, any data obtained through Google Sign-In.

We keep your data for as long as your account is active, or as long as needed to provide the service. If you delete a document or a bot, its content and vector embeddings are removed from the retrieval index. If you delete your account, that cascades to remove your bots, documents, embeddings, conversation history, and leads — billing transaction records may be retained separately for a limited period where required for tax or accounting compliance.

You can delete any document, regenerate or revoke a bot’s secret key, or delete your entire account and all associated data at any time from Settings → Account. For a full walkthrough of how to access, correct, or export your data — including as a widget visitor or lead — see our GDPR & Data Subject Rights page.

JestBot uses strictly necessary cookies to keep you signed in, plus optional functional and analytics cookies. What each cookie does, how long it lasts, and how to manage your choices is covered in full in our Cookie Policy.

JestBot is not directed at children, and account holders must not knowingly configure a bot to specifically target or collect data from children in a way that would require special protections under applicable law. If you believe a child’s personal data has been submitted to a bot without appropriate consent, contact us via Section 11 and we’ll assist in routing the request to the relevant bot owner.

We may update this policy as the product evolves. We’ll update the date at the top of this page when we do, and where a change materially affects how your data is processed, we’ll notify active account holders by email in advance of it taking effect.

Questions about this policy, or a request to exercise a data right, can be sent via the contact page.