Security
How customer data
is protected
Bringing analysis together in one place only works if that place is defensible. This is what is built and verified.
The platform is in development. Demos are arranged by appointment.
What is built
Row- and column-level permissions
Rules are defined per user or per profile, and they combine. What is forbidden is not hidden afterwards: a row or a column without permission never enters the query. And if a rule cannot be applied, the data is not shown.
One definition, one control
Permissions live in the model, together with the relationships and the measures. Dashboards, the tree and the spreadsheet read from there, so there is no second surface where a permission could be lost.
Second factor
Two-step authentication with an authenticator app (TOTP), written against the standards and verified end to end. The secret is stored encrypted. When the production server exists it becomes mandatory for administrators.
Sessions tied to their domain
Session cookies carry the prefix that ties them to the exact host that issues them, and the application lives on its own domain, separate from this site. That is why there is no sign-in form here: it is a link.
Who signed in and what changed, on record
Every sign-in and every failed attempt, every password change, every time the second factor is turned on or off and the use of the connections to other analysis tools is noted with the time and origin. Each customer’s administrator reviews it in the “Actividad de la cuenta” (account activity) screen, and the application has no way to edit that record.
A stolen session is cut off
Passwords are not stored: only an irreversible fingerprint is kept. If the system detects someone reusing an old session, it closes all the sessions in that chain, and deactivating a person cuts their access from their very next request.
Local mode
The data may never leave the machine
File preparation can run on the computer of whoever does it: what travels to the cloud is the blueprint of the process, not the contents of the files. Today it works with CSV and Parquet files, in Chrome or Edge. Models and dashboards do not run in the browser.
Is something missing that your team needs to see?
If there is a specific requirement —a review, a vendor questionnaire, a requirement from your IT area— it is best to raise it before the demo.