Every autonomous web specification and reverse-engineering audit executed by SarembokVE runs within a dedicated, ephemeral headless Chromium container (sarembok-browser). The container operates under non-root permissions with strict memory ceilings (768MB) and dropped Linux capabilities (cap_drop: ALL).
All temporary cookies, DOM trees, local storage, and cached network frames generated during an audit are destroyed in memory immediately upon task completion.
SarembokVE collects only the operational data strictly necessary to provide verification and compute orchestration services:
/session broker with an automated 3600-second time-to-live (TTL).remember that ...). All memories are scoped to the active tenant and can be cleared instantly via /clear or the UI Memory Rail.All communication with SarembokVE is encrypted in transit using Transport Layer Security (TLS 1.3) terminated at the Caddy edge proxy. Strict security headers are enforced across every endpoint:
Strict-Transport-Security: max-age=31536000; includeSubDomains (HSTS)X-Content-Type-Options: nosniffX-Frame-Options: SAMEORIGINPermissions-Policy: camera=(self), microphone=(self), geolocation=()Under GDPR and CCPA standards, users possess absolute control over all stored data:
/clear or clicking the Purge Memory button deletes all recorded session history, conversation turns, and vector records from the persistent SQLite database immediately./api/spec/export in open, non-proprietary JSON/TS formats.For enterprise security inquiries, SOC 2 compliance reports, or vulnerability disclosures, contact the security engineering team at [email protected].