Skip to content

Privacy Policy

Last updated 2026-08-03.

Granthia stores your Claude Code conversation history so your team can search it. This page describes, in plain terms, what we hold, where it lives, who can reach it, and how you remove it.

What we collect

  • Account data: your name, email, and organization, from your sign-in provider.
  • Conversation data: the Claude Code conversations you choose to sync, stored as the conversation text plus a search index built from it.
  • Usage data: metering counters (storage used, searches run) to operate and bill your plan.
  • Billing data: your organization's legal name, billing address and tax identifier, and a description of your payment method - the card brand, its last four digits and expiry date, or your UPI or mandate reference. We never receive or store your full card number; payment details are entered directly with our payment provider.

Secret redaction

Before a conversation leaves your machine, the Granthia client scans it for credentials that match a set of well-known secret formats (such as cloud access keys, common API tokens and personal access tokens, PEM private keys, JSON Web Tokens, and bearer tokens) and replaces any it finds. Our ingest service re-applies the same checks as a backstop before anything is stored or indexed.

This is a best-effort, pattern-based filter, not a guarantee that every secret is removed. It recognizes only these known formats, so a credential in an uncommon or custom format, or a plain password or value with no distinctive prefix, may go undetected and be stored and indexed. It also does not attempt to remove other personal information that may appear in a conversation.

Where your data lives

Your data is hosted on our own infrastructure on Civo, in a United States data center. Your conversation text and its search index live in our primary database; a separate cache holds background jobs and search-query lookups (queries are hashed, not stored as text). Data is encrypted in transit (TLS) and at rest. We do not run third-party product analytics over your conversation data.

Tenant isolation and access control

Each tenant's data is isolated by database row-level security: the application connects with a database role that is itself subject to those policies (not a superuser), and every query is scoped to your tenant by the database, not by application code alone. Within your workspace, owners and admins can restrict members to specific projects, so a restricted member only searches what they are allowed to see.

How we secure access

Sync and search are reached only with an OAuth 2.1 access token from our identity provider, validated on every request; your tenant is resolved on our side and is never taken from the token. The command-line client signs in with PKCE, and tokens are short-lived. You can sign in with Google, Microsoft, or GitHub: in that case you authenticate with the provider directly and we never receive or store your provider password. You can revoke an individual device or session from your dashboard.

Model use and training

Your conversations are never used to train or fine-tune any model, and are never sent to any third-party model provider. The search index that powers search is produced by an open-source model that we run ourselves; computing it never leaves our infrastructure. The only time your stored conversations reach a model is when you run a search and the results are returned to your own Claude Code client.

Subprocessors

We share data only with the third parties below, each used solely to operate the service. None of them receives your conversation content:

  • Civo: cloud hosting and storage (United States)
  • Cloudflare: DNS, content delivery, and TLS
  • Amazon SES: transactional email (invites and notifications)
  • Stripe: payments (rest of world) - billing identifiers and usage counts only
  • Razorpay: payments (India) - billing identifiers and usage counts only

Retention and deletion

We keep your conversation history for as long as your workspace is active. There is no automatic expiry while you are a customer, because the accumulated knowledge is the point. You stay in control:

  • Delete on demand. From the dashboard you can permanently delete a project's data or a developer's data at any time. Deletion is immediate and removes the conversation text and its search index together.
  • Close your account. Closing your workspace stops all syncing and schedules your conversation data for deletion. After a short grace period a disposal job hard-deletes it, within 30 days of closure. We retain minimal account records and a compliance audit log of the deletion.
  • Suspended workspaces. If your workspace is suspended (your trial ended, or your subscription was cancelled) and you do not resubscribe, your conversation data is permanently deleted 60 days after suspension. We email you at suspension, after 30 days, and a week before deletion, each stating the exact date.
  • Inactive Free workspaces. A workspace on the Free plan that captures nothing and runs no searches for 90 consecutive days may have its conversation data deleted. We warn the workspace owner by email twice before that happens, each warning stating the exact date. Any capture or search resets the 90 days. Upgrading to a paid plan removes the policy entirely. We retain minimal account records and a compliance audit log of the deletion.
  • Backups. Deletion removes your data from the live service. Where it has also been written to operational backups, it is removed as those backups age out on their retention schedule rather than instantly.
  • Billing records. Closing your account deletes your stored payment method straight away. Your billing profile - legal name, billing address and tax identifier - is kept for 8 years after closure, because tax and company law require us to retain it. A deletion request does not remove it.

Contact

Privacy questions: [email protected].

Granthia is operated by Server Pundits Pvt Ltd in India and by Server Pundits in the United States.

Registered office (India): D. No. 15-6-298A, 1st Floor, Mangesh Mangal Building, Balmatta Bridge Road, Mangaluru, Dakshina Kannada, Karnataka 575003, India.

Business address (United States): 20 North Orange Ave, Suite 1100, Orlando, FL 32801, USA.