Schema Context and Privacy

Exactly what Querious sends to the assistant service, and what it never sends.

The Query Assistant is most useful when it knows about your table names, column names, types, views, etc, so that it can write SQL statements that are directly related to your actual database and solve your problems.

You can manually type or paste in all of that information yourself as needed, but with your permission, Querious can also automatically provide that context when the assistant itself specifically requests it to provide the answer to your prompt.

The idea is that the Query Assistant can know the structure of the database so it can help you write your queries, but never the data inside the database.

Where Do Prompts Go #

All prompts and context are sent through the Araelium AI Assistant service (which verifies your account and credits) to a third party AI service provider to generate the answer.

It's important to note that Araelium does not store, log, data mine, or share the content of your prompts and context in any way; It is simply forwarded to the AI service provider to generate the answer.

See the Terms of Service and Privacy Policy.

What is Schema Context #

Other than the prompt text you explicitly type into the assistant chat, the context that can be provided includes:

The name of your selected database in MySQL, or names of schemas in your PostgreSQL search path.
The names of tables, views, functions, procedures, events, triggers, types, etc.
The names and types of columns.
The DDL statements / full CREATE statements for any schema object.

When the AI model itself determines it needs to know about the names or structure of schema objects to write the correct SQL queries for you and respond to your prompt, it will ask Querious to provide that context. Querious then will send that context back only if you have turned on the "Provide Schema Definitions" setting.

Typically the assistant asks for the object list, then the definitions of the few tables it needs, then answers. Naming tables in your prompt lets it skip the list.

Data Definition Language (DDL) statements like CREATE describe structure, but some structure contains default and possible values. Before turning on schema context for a sensitive database, consider all that is in DDL statements.

What Is Never Sent #

The assistant is never given:

Row data: The data contents of your tables.
Queries and results: The contents of your query editors or query results.
Connection details: host names, user names, passwords, SSH or SSL settings.
Anything outside the selected schema (or, on PostgreSQL, the search path). Requests for other schemas are refused.
Anything at all while the Query Assistant is turned off in Settings.

The assistant also never executes queries, never automates Querious usage, and never accesses or modifies your database.

What Is Sent With Every Prompt #

Item	Why
Your prompt, and the conversation so far.	It'd be pretty useless without it!
Server type (MySQL vs PostgreSQL etc) and version	So the SQL uses syntax your server supports.
The names of the schemas in scope	The selected database, or the PostgreSQL search path. This lets the assistant qualify names correctly and limits what it can ask for.
Schema context already fetched in this conversation	It'll likely need it again, so this saves a round trip.

Turning Schema Context Off #

Turn off Provide Schema Definitions using the button in the bottom of the sidebar, or Provide Schema Definitions in the AI Assistant settings. They're the same setting and apply to all of Querious.

With it off, Querious sends no object lists or definitions, and the assistant is told it can't look up schema. It can still write SQL from what you tell it, so describe the tables and columns in your prompt or even paste in the raw SQL. For example:

orders table = (id, customer_id, placed_at datetime, total)
customers table = (id, name, email)
		
Show each customer's total spend for 2025, highest first.