Security & Data Protection
A transparent overview of the safeguards and processing boundaries used by Morillo Hudson.
Application encryption
Supported documents, extracted knowledge, chats and sensitive operational records are encrypted with AES-256-GCM. Each protected vault uses a data-encryption key that is wrapped by the server master key. Enterprise workspaces use an organization-scoped key.
Access controls
Supabase Row Level Security, private storage, authenticated server routes and tenant ownership checks restrict access. Wrapped data keys have no authenticated-browser grants and are unwrapped only by authorized server processes.
Transport and infrastructure
Production traffic should use HTTPS. Credentials and OAuth refresh tokens are separately encrypted. Provider secrets remain server-side. Enterprise customers can document regional, model, networking and retention requirements in the Agent OS.
Processing boundaries
Application encryption protects stored data against direct database readability without the relevant key. It is not the same as end-to-end encryption: authorized server operations decrypt required content, and selected external providers may process plaintext context during authorized requests.
Responsible disclosure
Security researchers should report suspected vulnerabilities privately and avoid accessing, changing or retaining customer data beyond what is necessary to demonstrate the issue.
Contact
Questions about these documents or data handling may be sent to privacy@morillohudson.com.