Data Handling Summary
Last updated: July 22, 2026. This document requires legal review before production launch.
Data flow
Authentication and cloud records use Supabase. SOP generation and AI edits send the authorized request context to OpenAI. Local history and some knowledge text may remain in browser storage. Public templates are separately published records.
Security boundaries
Secrets remain server-side, private database records are protected by row-level security, uploads are validated and parsed as data, and payment proofs are verified server-side. Logs are designed to exclude prompts, documents, credentials, and full SOP content.
Retention and deletion
Users can delete supported SOP, knowledge, template, and workspace records where authorized. Backup retention and complete account deletion procedures must be finalized for the production operator.
Current limitations
Local browser storage is device-specific. The default application rate limiter is process-local unless a production distributed store is configured. No formal security or regulatory certification is claimed.