This document is a product-specific operational draft and does not replace advice from qualified legal counsel.
Protection model
Dravelyx, operated by Marsh Engineering Services LLC, is designed so the SaaS control plane owns business data while isolated execution workers receive only the minimum scoped context needed for a run. Agent runtimes do not receive direct database or integration credentials.
Core safeguards
- Tenant-scoped authorization and PostgreSQL row-level security for tenant-owned resources.
- Encryption in transit and encryption of integration credentials at rest with authenticated encryption and key versioning.
- Opaque sessions, credential separation, least-privilege access, and auditable administrative operations.
- Permission-controlled external tools and human approval for sensitive actions.
- Bounded retries, timeouts, idempotency controls, execution budgets, and immutable evidence hashes.
- Disposable execution environments with restricted filesystem, process, resource, and network access where supported.
Customer responsibilities
Customers are responsible for user lifecycle management, role assignments, repository permissions, approval policy, secure endpoint use, and reviewing output before deployment. Customers should not place secrets in task descriptions, source comments, or other content that agents do not require.
Incident response and continuity
We monitor service health and security-relevant events, investigate suspected incidents, contain affected systems, preserve evidence, and notify affected customers as required by contract or law. Backup, recovery, and retention controls are tested and improved in proportion to service maturity and risk.
Subprocessors and requests
Dravelyx uses vetted infrastructure and service providers to operate the platform. Enterprise customers may request current subprocessor information or a data processing agreement by contacting [email protected].