FlatQL
Sign in Start free

Legal

Privacy policy

Last updated October 2026 · Applies to flatql.com and the FlatQL app

What FlatQL stores and why. Questions go to the contact page.

1. Account data

Your name, email and a salted password hash, plus the team you belong to. Used to sign you in, send transactional email (invitations, password resets, billing receipts) and nothing else.

2. Cluster credentials

In the desktop app, connection credentials stay on your computer, encrypted with a key held in your operating system's keychain; they reach FlatQL servers only if you choose to sync a connection to the web. Credentials used on the web are encrypted at rest on FlatQL servers with a key that is not stored alongside the data. Team members never see credentials; they see only the indices they were granted.

3. Query data

Statements you run and summary metrics (duration, row count) are kept as query history for the period your plan allows, and as an audit log for Team workspaces. Result rows pass through FlatQL servers only for the duration of a request or export and are not retained.

4. Ask FlatQL

When you use the assistant, your question, the schema of the indices you may see, one sample document per index mentioned and the current worksheet are sent to the model provider to produce an answer. Questions and answers are logged for your team's usage view and daily limits.

5. Payments

Card details are entered on and stored by Dodo Payments. FlatQL stores the subscription status, plan, seat count and invoice references.

6. Email

Transactional email is sent through Amazon SES. We do not send marketing email without consent.

7. Deletion

Ask from the Account page or by contacting us; accounts, teams, connections and history are deleted within 30 days.

Guides

How FlatQL handles the jobs Elasticsearch makes hard.