Security

No SOC 2, no ISO 27001, no HIPAA attestation, no PCI DSS. These are paid external audits and we have not undertaken them. Any vendor questionnaire asking for them should be answered “no”.

If your procurement process requires one, we are not the right supplier yet, and it is better to know that now than after a pilot.

Each customer’s knowledge base and call history live in a separate database file. A query that forgets its scope cannot reach another customer’s data, because the data is not in the file it is reading.

Passwords use scrypt, which is memory-hard and shipped with the language — no dependency, and no hand-rolled cryptography. Session tokens are stored only as hashes, so reading the database yields nothing anybody could sign in with.

SIP passwords and tool API keys are kept outside the main database in files readable only by the service account, and are write-only through the interface: they can be replaced, never read back.

A crawl, a webhook tool, and an MCP server all involve fetching a URL somebody typed into a form, from inside our network. Every one of those resolves the hostname and refuses private, loopback, link-local, and cloud-metadata addresses — checked after DNS, and re-checked on redirect, because a public name that resolves inward is the whole attack.

Attempts to talk an agent out of its instructions are screened before they reach the prompt they target. Threats end a call. Someone in distress is handed to a person rather than hung up on.

Card numbers, Aadhaar and PAN numbers are removed before a transcript is written. The agent hears them during the call because it must; nothing is kept.

If you find a vulnerability, write to [email protected]. We will acknowledge within three working days and tell you what we are doing. We do not currently pay bounties and will not pretend otherwise.