You see your data. The AI sees its shape.
Drag the line. On the left, a table as you see it. On the right, exactly what reaches the AI model from that same table.
| idinteger | nametext | emailtext | citytext | signupdate | total_purchasesnumeric |
|---|---|---|---|---|---|
| 10482 | Marta Ibáñez Ruiz | marta.ibanez@correo.es | Zaragoza | 14/03/2021 | €18,420.50 |
| 10483 | Jordi Puig Serra | jpuig@empresa.cat | Girona | 02/07/2021 | €6,115.00 |
| 10484 | Lucía Ferreiro | lucia.f@correo.gal | Vigo | 29/09/2022 | €31,902.75 |
| 10485 | Andrés Molina | amolina@mail.com | Málaga | 11/01/2023 | €2,480.10 |
| 10486 | Nerea Etxeberria | nerea.e@posta.eus | Bilbao | 05/06/2024 | €12,006.40 |
| 10487 | Pablo Sanz Gil | psanz@correo.es | Valladolid | 21/10/2025 | €915.00 |
| Row by row, with every value | |||||
What reaches the AI
- Table and column names, and their types
- How the tables relate to one another
- Aggregate statistics: nulls, number of distinct values
- The descriptions you review and publish
What never reaches it
- Rows and values from your tables
- Query results
- Columns holding personal data
- Your database password, which never leaves your network
Writing to your database would mean breaking three locks. One of them is yours.
- In your database
A user that can only read
Your IT person creates it, with whatever permissions they decide. A verifier checks at start-up, and periodically after that, that it can’t write or step outside them.
- In Cuarzal
Every query, analysed before it leaves
Reads only, only on what the person asking is allowed to see, and no sensitive columns without express permission. The query is rewritten clean before it’s sent.
- In the gateway, inside your network
Validated again, against your real database
And run in a read-only transaction, capped at 30 seconds and 10,000 rows. What doesn’t pass doesn’t run.
SELECT date_trunc('month', date) AS month, SUM(amount) AS sales FROM sales.invoices GROUP BY 1
- It’s a read
- Permitted tables and columns
- No sensitive columns
It passes. It runs on your network and the answer arrives in under a second.
What’s stored, and what isn’t.
Cuarzal stores just enough to work and for you to audit it. The data in your tables isn’t on that list.
Query results
Nothing. They pass through memory so you can be shown them, then they’re forgotten. They’re never written to disk.
120 sAudit
Who ran each query, when, its text and whether it was allowed. Never the values.
730 daysby default, configurableConversations
The questions, the SQL and the explanations. Never rows. Each person can delete their own.
365 daysby default, configurableYour database password
It stays encrypted in the gateway, inside your network. It never reaches Cuarzal.
On your networkVoice dictation
Neither the audio nor its transcript.
NothingEach person’s data
An administrator can export it or remove the person. The audit log is kept without their name.
Until removalWe’re looking for the first companies to try it.
If you have a database holding business information and want your team to ask it questions without waiting for anyone, tell us about your case. We’ll guide you through the installation.
Open in your email We reply in Spanish and English.