Protections
Where Parable runs, what it is allowed to store, and who can see which rows are all your decisions. The platform applies them itself, so the rule holds even when a query, a report or an agent forgets to ask.
Access rules usually live in a spreadsheet, a wiki page and somebody's memory. The database reads none of them, so the rule holds right up until a report, a dashboard or an agent asks for something nobody thought to check.
Where Parable runs, what it is allowed to store, and who can see which rows are your decisions. They are applied by the platform itself — in the database, under keys you hold, inside a boundary you choose — so the rule holds even when the thing asking forgets to.
A person in the app, a scheduled report and an agent over MCP all hit the same tables under the same roles, so an agent cannot see what the person running it could not. The controls behind SOC 2, ISO 27001 and GDPR are those same identity, encryption and deployment choices rather than a separate set of promises kept in a binder.
AWS, Google Cloud, Azure, or fully on your own premises. Your data sits in storage you own, in the region you choose, under keys you hold.
Personal fields can be masked or dropped before they are ever stored, and encryption keys can remain yours.
Roles decide which tables a person can reach and which rows inside them, enforced by the database itself rather than by the application remembering to ask.
Because access is decided per role and per row, you can open data across tools that previously had to stay locked inside each one.
Certifications
Get started
