OpenHarveyOPENHARVEY / SECURITY
Security & Data Boundaries
OpenHarvey combines execution isolation, access control, credential management and persistent storage. This describes the implementation, not an independent security audit or compliance certification.
Where is data processed?
The application stores source files, extracted text, conversation snapshots, deliverables and checkpoints. Cloud execution transfers task materials to E2B and relevant context to the selected model provider. The hosted deployment uses a Railway persistent volume for business data and Supabase for authentication.
What does the sandbox isolate?
E2B isolates agent tool execution. Application permissions control access to documents, workspaces and files. Conversations within a contract workspace may share its runtime, so conversation document policies are not separate operating-system isolation.
Credentials and access
Platform model keys remain server-side, with restricted credentials for trial inference. Personal models require runtime access to their credentials. Stored model configuration is encrypted; operators must protect the master key. Production sessions use Secure, HttpOnly cookies.
Persistence, deletion and backups
A save receipt confirms server persistence. Archiving, soft deletion, permanent deletion and trial expiry are different operations. Destroying a sandbox does not automatically delete server deliverables. Persistent storage does not replace independent backups.
Self-hosting boundaries
Self-hosting gives you control over application and storage deployment. If you keep using E2B or remote models, data still passes through those services. Local process mode does not provide operating-system isolation between users.
References: E2B security and OpenCode permissions.