Read-only
Queries are validated before running and run in read-only mode. The AI never executes instructions directly.
Security by design
The platform queries your data, processes it temporarily and presents the result. We do not build a repository of your business information.
Encrypted credentials
Database passwords and AI keys are stored with authenticated encryption and never appear in technical logs.
Encrypted connections
We use TLS whenever the engine supports it and connect only from fixed IP addresses you authorize.
Isolation between companies
Every account is separate. Per-customer and per-database limits keep one workload from affecting others.
AI sees structure, not records
We send the AI table and field names so it can propose KPIs, not your rows of data.
Perimeter protection
The platform is protected by Cloudflare against attacks and bots, with verification at sign-in.
What we store and what we do not
| Information | Stored? |
|---|---|
| Accounts, users and subscriptions | Yes |
| Connection settings | Yes, with encrypted credentials |
| Approved table structure and relationships | Yes, as metadata |
| KPIs, dashboards and permissions | Yes |
| Business data from your queries | No, not permanently |
| Query results | No, not permanently |
To build a chart, the required data passes through our execution environment temporarily. That is why we apply encryption, isolation and access control along the whole path.
What we recommend
- Create a dedicated database user with read-only permissions
- Restrict access to Flubyx IP addresses in your firewall
- Enable TLS on your database server
- If your database is on a private network, use a VPN or private connection