Local queries. Optional remote AI.
RawQL is local-first. SQL runs in your browser via DuckDB WASM. Workspace definitions live in browser localStorage, and a local archive keeps imported files and supported DuckDB tables available after a reload. Ordinary SQL and file imports stay on your device. If you submit workbench feedback, RawQL stores the message in Redis and links it to your signed-in account. We include your account email only when you ask us to contact you. Optional Jev calls send their input texts and questions after you authorize Jev for the editor session.
Capy Agent
After provider consent, Capy sends your question, authorized workspace object names and types, business definitions and action metadata through RawQL directly to Google AI Studio for Gemini 3.5 Flash-Lite, or through OpenRouter for other models. The Gemini API key stays on the server. Google free-tier quotas or API charges apply to the configured key. Workspace access includes all objects unless excluded. File content and bounded result sharing are enabled by default and can be disabled in Capy settings. Raw files stay local; explicit result pages can contain raw rows and sensitive values. Local, preview and production offer the same model selector with separate consent for provider logging. Free providers may retain prompts and outputs and use them to improve their models. Use non-confidential context for free-model calls in every environment.
Conversation text stays in browser memory. Continuations travel as authenticated encrypted tokens and are not stored in Redis. The server stores only account-linked run control metadata, nonces, deadlines and budget counters. Run metadata expires within one hour and daily counters within two days. Logs contain status, model, timing, token and budget metadata, without prompts, SQL or rows. Reloading interrupts a conversation; created files and dashboard definitions remain in normal local workspace storage. Refreshing a saved dashboard makes no AI call. See the Capy Agent guide.
Optional Jev decisions
The first prompt_jev run previews its texts and questions and asks you to enable Jev for the editor session. Subsequent Jev queries send their input values through the RawQL server to OpenRouter and TypeSafe without another dialog. Disable Jev from the status bar, leave the editor session or reload the tab to require authorization again. Raw files are not uploaded. The API key stays on the server. RawQL does not store the submitted texts or responses server-side. A per-account request lease lasts at most two minutes and a row quota counter lasts one hour in Redis. Provider retention and data residency depend on OpenRouter and TypeSafe; RawQL does not add provider residency or retention guarantees.
Jev results stay on your device and query pages may use temporary IndexedDB storage. If you save values into a local table, the normal automatic workspace save includes that table. Exports create separate local files. Repeating a Jev query can incur another charge. Read OpenRouter privacy documentation before sending private data.
Who runs RawQL
RawQL is built and maintained by Mickaël Rakotoarinivo, who is responsible for the personal data described in this policy. For support or privacy questions, email support@rawql.ch.
What stays on your device
- Imported files (CSV, JSON, Parquet, Excel) and supported DuckDB tables — saved in an unencrypted archive in this browser's IndexedDB and restored when you reopen the editor. Clear all workspace data or sign out to delete it.
- SQL worksheets (
rawql-storage) and notebooks (rawql-notebooks) — browser localStorage. - Linked workspace files and folders stay on your disk. RawQL remembers their handles and relative paths in IndexedDB. Only the selected archive is read; changes save back to its local
.rawqlfile. Unlinking removes a shortcut without deleting the file. Read the local workspace guide for permissions and backups. - Dashboard definitions (
rawql-analytics-definitions) contain saved SQL, database context, parameter defaults, widget settings and saved filter defaults in browser localStorage. - SQL result pages may be written temporarily to browser IndexedDB for the current session; they are not restored as query results after reload. Analytical dashboard results, caches and filter options stay in memory. Dashboard refreshes use local data and do not call Jev or send analytical values to the server.
- dbt branch databases and cached run results are saved in browser IndexedDB (
rawql-dbt-runtime). Clear all workspace data or sign out to remove this cache. - Data in the browser workspace (My Workspace) is automatically saved to this browser's IndexedDB after imports and DuckDB changes. It is not synchronized to another device. Clear all workspace data or sign out to delete the local archive. You can also download a
.rawqlcopy; it includes data and definitions in a compressed, unencrypted archive. Integrity checks do not authenticate its author. Imported analytical definitions stay inactive until you explicitly refresh them.
Consequence: signing in on a new device restores access, not your local workspace. Files and queries must be re-imported there. Clearing workspace data or signing out clears this browser's workspace archive, dbt cache and remembered connections. Linked files and downloaded snapshots remain on disk.
What we store server-side
| Data | Storage & retention |
|---|---|
| Capy run control and conservative budget counters | Redis run metadata expires within one hour; daily budget counters within two days. No prompts, SQL, result values or encrypted conversation blobs. |
| Name + email (pending signup) | Redis `beta:pending:<email>` — same as the beta PIN duration (30 days by default), deleted on verification |
| Signup / login PIN (6 digits) | Redis `beta:pin:<email>` — configurable duration (30 days by default); signup code deleted on use, login code reusable until expiry |
| Verified account (name, email, join date) | Redis `beta:registry:<uuid>` + `beta:email:<email>` — kept until you ask for deletion |
| Access cookie `rawql_beta_access` | HttpOnly, SameSite=Strict; lifetime follows the remaining beta PIN duration (up to 30 days by default), identifies your verified account |
| Editor appearance preference (palette, light/dark mode) | Redis `beta:editor-theme:<uuid>`; kept until account deletion |
| Workbench feedback (message, account ID, optional contact email) | Redis `feedback:editor:<uuid>`; kept until deletion is requested. Per-account rate-limit key expires after one hour. |
Workbench feedback
Sending feedback from the SQL Workbench stores your message in Redis under your verified account ID. The optional contact checkbox controls whether we also store the email on your account to follow up. We keep feedback until you request deletion at support@rawql.ch.
Emails & cookies
- Signup and login codes are sent by email (EmailJS) and contain only your name and the 6-digit code.
- The access cookie is HttpOnly and cannot be read by JavaScript.
- We save your choice to dismiss the cookie notice in your browser, so it stays closed on future visits.
- No analytics, no advertising, no sale of personal data.
Your rights
Access, correction, or deletion of your account (registry entry, email index, editor appearance preference, and feedback linked to your account): email support@rawql.ch. Deletion removes server-side data; local browser data is cleared by clearing site data.
Last updated: November 2026.
RawQL