Trust Centre
NLSQL installs into your own cloud subscription, and our backend never executes your analytical SQL. The numbers your team sees are returned by your database — never generated by a language model.
Compliance
Every item below links to its evidence, and each is labelled for what it actually is — a self-attestation, a regulatory registration, or a platform designation.
UK GDPR and EU GDPR. NLSQL acts as a processor under Article 28, with data processing agreements available on request.
Privacy Policy →
California Consumer Privacy Act. Access, correction, deletion and opt-out rights are honoured for California residents.
Privacy Policy →
Registered with the UK Information Commissioner’s Office, the United Kingdom’s independent data protection regulator.
Data protection →Signatory to the pledge published by the US Cybersecurity and Infrastructure Security Agency, committing to build security into software by default.
CISA pledge →
Reviewed by Amazon Web Services and listed in AWS Marketplace, deployable into your own AWS account.
AWS Marketplace →
Publisher identity verified by Microsoft, with NLSQL listed and transactable on the Microsoft commercial marketplace.
Azure Marketplace →We list only what we hold. NLSQL is not currently SOC 2 or ISO 27001 certified; where an independent audit is required for your procurement process, please get in touch so we can discuss timelines.
Architecture
The strongest guarantees we offer are structural — they come from where the software runs and what it is built not to do.
NLSQL is installed from the Azure or AWS marketplace into your own cloud subscription. Your database credentials, your query results and your business data remain inside your infrastructure and under your access controls.
We hold schema metadata you choose to map — table and column names — not the contents of your tables.
NLSQL returns a SQL statement plus an answer template containing placeholders. Your own client runs the query and fills the numbers in. A figure shown to your team therefore always originates from your database.
This is enforced in code, not by policy: every digit in a generated sentence must also appear in the user’s question, or the sentence is discarded and replaced with a mechanical one.
Generated SQL passes three ordered, non-AI gates before it is ever returned:
Parse — exactly one statement, SELECT only.
Policy — every table, column and join checked against an allow-list built
from your own mapped schema. Literals — string values must already exist in
your data.
A statement that fails any gate is never served. There is no path around these checks.
Secure by design
NLSQL has signed CISA’s Secure by Design pledge. The principle behind it matches how this product was built: the safe behaviour is the only behaviour, and customers should not have to configure their way to it.
That is why the SELECT-only restriction, the schema allow-list and the no-generated-numbers rule are properties of the engine rather than options an administrator can switch off.
Read the pledge at CISA →Platform controls
Every API request carries a bearer token scoped to a single account. Tokens are issued per user and can be revoked at any time.
The Claude / MCP integration uses an OAuth 2.0 authorisation-code flow with PKCE and a hardcoded redirect allow-list. Issued tokens expire after 24 hours.
Accounts can be restricted to named source addresses. The check runs before any query processing begins, and non-matching requests are rejected outright.
Enterprise accounts can be bound to a dedicated endpoint path, so traffic for your organisation is separated from the shared route.
All traffic is served over TLS, and platform database connections are themselves TLS-protected against a pinned certificate authority.
Every request is recorded with its account, question and generated SQL, giving your team a complete history of what was asked and what was produced.
Legal entity
Security review
We answer vendor security questionnaires, sign DPAs and NDAs, and support architecture reviews. If you have found a vulnerability, use the same channel and we will route it to engineering.
