Sensitive data protection
Protecting sensitive data works best in layers. No single control is enough on its own. They reinforce each other.
The layers
Database permissions
A read-only, least-privilege user is the primary boundary.
A read-only, least-privilege user is the primary boundary.
Odoo permissions & record rules
Where Odoo is involved, keep them clean and current.
Where Odoo is involved, keep them clean and current.
Workspace membership
Only the right people belong to a workspace.
Only the right people belong to a workspace.
Table visibility
Hide sensitive or irrelevant tables from the members who should not use them, in the AI Guide.
Hide sensitive or irrelevant tables from the members who should not use them, in the AI Guide.
Secrets always hidden
Passwords, tokens, keys, and card or bank numbers are shown as [hidden] and never sent to the AI model.
Passwords, tokens, keys, and card or bank numbers are shown as [hidden] and never sent to the AI model.
Careful prompting & review
Validate sensitive answers and avoid exposing data unnecessarily.
Validate sensitive answers and avoid exposing data unnecessarily.
Names, emails and phone numbers are not hidden
Answers can show names, email addresses and phone numbers when the question needs them. They are not masked, and they can be part of what STYD sends to its AI provider to write the answer. The AI Guide flags columns that look like personal data so that no example values of them are kept, but detection is not perfect and is not a compliance guarantee. Read What leaves STYD.
No certification claim
These layers help you protect sensitive data, but STYD does not provide a compliance certification. Meeting your own regulatory obligations remains your responsibility.