Read-only execution
STYD is built for analysis over your connected data, not for administering your database. It reads your data and does not change it.
What STYD does on a database
Every query runs inside a read-only transaction that is always rolled back. No setting turns this off.
One statement at a time, and it must be a SELECT (or WITH ... SELECT). Anything that writes, changes the structure, locks rows or copies into a table is refused before it runs.
A query stops after 15 seconds by default, and a result larger than 5 MB is refused.
Passwords, tokens, keys, and card or bank numbers are shown as [hidden] and are never sent to the AI model.
A new connection must use an encrypted (TLS) connection to your database. Connections saved earlier keep the setting they were saved with.
On Odoo, STYD only calls read methods. It does not create, change or delete a record.
Connect with a read-only user anyway
Connect with a read-only database user. This is the recommended setup and an independent safeguard at the database level.
Limits of these guards
The permissions on the database account you connect with are the real boundary. STYD does not check what that account is allowed to do, and it cannot make an over-privileged account safe. The guards above are STYD's own layer, tested in STYD's test suite; they are not a certification, and no guard is absolute. Use a least-privilege, read-only user.