What is collected
Percival processes the submitted email content, available sender metadata, extracted links, attachment names and attachment metadata needed to produce a result.
Privacy by design
This page reflects how the current implementation behaves today.
It is a product-facing explanation of the present data flow, not a final legal notice. If the implementation changes, the page should change with it.
How it is processed
The current website scanner processes submissions within the request flow. The interface and API should avoid claiming storage behaviour that is not supported by the deployment.
Third-party services
The repository includes space for Mailgun inbound handling and future reputation services, but user-facing privacy wording should only describe third parties that are actually enabled in the deployed environment.
Retention and deletion
Formal retention and deletion controls are not fully defined in the current codebase, so any production deployment should document them clearly before making stronger claims.
Security controls
The current scanner includes request size limits, attachment limits, timeouts, multipart validation, rate limiting and security headers on responses.
Operational caution
Do not submit regulated, highly sensitive or unnecessary personal information unless the service has been approved and documented for that use.