Your data, plainly explained.
Last updated: 23 July 2026 · Applies to the RagSap beta.
This policy explains what RagSap ("we", "us") collects when you use the service, why we collect it, who processes it, and how you can get rid of it. We tried to keep it short and readable.
Two kinds of people, two data flows
RagSap has two very different users, and we treat their data differently:
- Builders — people who sign in with Google to create and manage chatbots.
- Visitors — people who chat with a builder's bot via its public link or embedded widget. Visitors don't need an account.
What we collect from Builders
| Data | Why |
|---|---|
| Google account: email, name, profile picture, unique Google id | To sign you in and show a friendly name in the dashboard. We never ask for a Google password. |
| Bots you create: name, theme, rules, contact form settings, source URL | To run your chatbot. |
| Files you upload as knowledge | To ingest as your chatbot's knowledge base. Files are chunked, embedded, and stored on our servers. |
Session cookie (chatresp_session) | A signed, HttpOnly cookie that keeps you logged in for up to 14 days. |
What we collect from Visitors
| Data | Why |
|---|---|
| Message text you send and the bot's replies | So the builder can review conversations and improve their bot. |
| Anonymous session id (from your browser) | To thread messages into a single conversation. Not tied to your identity. |
| Salted SHA-256 hash of your IP address | Rate-limiting and abuse prevention. We never store your raw IP. |
| Thumbs 👍 / 👎 you give on answers | To help the builder see which answers were helpful. |
| Contact details you fill into a bot's lead form | Delivered to the builder — RagSap doesn't market to you. |
Who processes your data
We use the following processors:
- OpenAI — we send message text and knowledge-base chunks to OpenAI's embedding and chat completion APIs so the bot can answer. OpenAI does not use API traffic to train their models. See their policies.
- Cohere — when enabled, we send message text and top retrieval candidates to Cohere Rerank for improved answer quality. Cohere does not train on this traffic.
- Google — sign-in via Google OAuth. Google returns your profile to us; nothing goes the other way.
- Our own servers — SQLite or Postgres and a Qdrant vector index, running on our infrastructure.
What we don't do
- We do not sell your data.
- We do not use visitor conversations to train any AI model.
- We do not share a builder's bot data with other builders.
- We do not use third-party analytics or advertising trackers.
How long we keep it
- Bot data (files, conversations, analytics) — until you delete the bot from your dashboard, then it's removed from our database and vector index. Backups may retain data for up to 30 days after that.
- Your account — until you ask us to delete it. Email [email protected].
- Session cookie — up to 14 days, or until you sign out.
Your rights
You can ask us to:
- Export the data we hold about you.
- Delete your account and all data associated with it.
- Correct anything wrong or out of date.
Email [email protected] and we'll respond within 30 days.
Children
RagSap is not intended for children under 13. Don't create a chatbot on behalf of a child, and don't build a bot targeting children unless you have appropriate parental consent flows in place — that's on you as the builder.
Security
Session cookies are signed and HttpOnly. Ownership checks live in the API — one builder cannot read or modify another's bot. If you discover a vulnerability, please email [email protected] before disclosing publicly.
Changes to this policy
We'll update the date at the top when we change anything. For material changes affecting signed-in builders, we'll send an email.
Contact
Questions about privacy? [email protected]. General enquiries: contact page.