Your mail is yours.

Our default deployment has no persistent volumes in fly.toml. All analysis happens in RAM on ephemeral machines. auto_stop_machines wipes RAM when the machine stops. We do not write email bodies to disk, object storage, or log streams.

• 0 days retention of email body content
• 30 days retention of metadata (sender, timestamp, category, risk score) for reporting
• 60-second purge cycle of analysis artifacts
• RAM-only processing: no database or disk cache of message content

EmailCos does not use your messages to train, fine-tune, or improve models. Your data is not mixed into any model training set, and we do not retain prompts or outputs beyond the operational windows above.

• Zero-retention flags are set at the model layer on every request
• No human review of message content
• Prompts and completions are discarded with the analysis artifacts

Message bodies exist only in memory for the duration of the analysis. Derived signals — category, priority, risk score, and sender authentication results — are the only outputs kept, and only for the metadata window. Nothing is written to disk, object storage, or log streams.

• 0 days — email body content
• 30 days — metadata (sender, timestamp, category, risk score)
• 60 seconds — analysis artifact purge

Our architecture is aligned to POPIA, GDPR, and SOC 2 control principles. Alignment is not the same as certification: we do not claim a completed SOC 2 audit report. Where a formal attestation is required, contact us and we will share our current control documentation and DPA.

All transport uses TLS 1.3. Any synced credentials or metadata stored for your account are encrypted with AES-256-GCM using rotated keys.

South African users enjoy POPIA rights; EU/UK users enjoy GDPR rights; everyone gets export and deletion. Contact us at privacy@emailcos.com.

Information Officer: Xoli Dlabantu — privacy@emailcos.com