Security
We build around established security practices rather than rolling our own. Here's what that looks like in practice.
Authentication
Accounts and sessions are handled by our own backend, with bcrypt-hashed credentials and signed session tokens.
Encryption in transit
All traffic between your browser, the application, and the backend is served over HTTPS.
Access control
The product dashboard and account data are only reachable once you're signed in - protected routes are enforced server-side, not just hidden in the UI.
Data storage
Account and application data is stored on our own dedicated backend service, which also handles query processing.
Found a security issue?
Please report it to labeeleai@gmail.com — we take reports seriously and will respond promptly.