Security & your data
For both readers — plain-English first, precise details after. This page states exactly what leaves your site and what never does. It was written against the running system, not aspirations.
The short version
- Your database is never exposed to the internet. Nothing connects into your site. Your site makes outbound, encrypted (HTTPS) requests to the SigzenBI service, picks up pending questions, answers them, and posts back the results.
- Reads only. SigzenBI's query channel refuses anything that isn't a read: no inserts, updates, deletes or schema changes. Your users, passwords and system credentials tables are blocked from queries outright, and every query is time-capped.
- Charts are rendered by SigzenBI's hosted analytics service, so query results — the numbers on your dashboards — are processed by our infrastructure. That's what makes dashboards work without exposing your database.
Exactly what leaves your site
| Data | When | Where it goes |
|---|---|---|
| Company name; your name and email | At signup | SigzenBI service (your account record) |
| Site database connection details, including the database password (stored encrypted) | At the "Connect database" step you approve | SigzenBI service — it also authenticates your site's private query channel |
| Query results (business figures needed for each chart or answer) | Every dashboard view and chat answer | SigzenBI's analytics service, over HTTPS; cached for up to 24 hours so repeat views are fast |
| Questions you type in chat, plus the metric definitions needed to answer them | Each chat question | Processed by our model provider (Anthropic) to select the right verified metric. Your database credentials are never included. |
| Teammates' names, emails and seat types | When you invite them | SigzenBI service |
What never leaves your site
- Your database as a whole — there is no bulk copy, no sync, no replica.
- Your ERPNext users' passwords and API keys — the tables holding them are blocked from the query channel by name, regardless of the query.
- Card details — payments are entered on Razorpay's own secure form; SigzenBI stores only a masked reference (e.g. "Visa •••• 4999") if you choose to save a card.
Access control
- Seats limit capability: Viewers see only dashboards assigned to them; only Analysts can author. Row-level restrictions you set on the Team page are enforced server-side in every surface — dashboards, charts and chat answers.
- Each customer's data path is isolated: your site's query channel is authenticated with credentials unique to your account, rotated automatically.
Self-hosted hardening (optional)
On your own bench you can additionally give SigzenBI a database user that can only read — then the database itself refuses writes even in principle. Steps in Install on your own server. (On Frappe Cloud this extra layer isn't available; the software read-only guards above apply.)
Data retention
If your subscription lapses, your data and configuration are kept for at least 60 days and may be removed after that — stated on your Billing page. You can request deletion earlier via support.
Questions
Security questions or disclosure requests: support@sigzen.com.