AI, BYOK, Drafting, Summaries, and Tags
Use AI assistance while keeping provider keys under your control.
BYOK means the site owner configures the AI provider key. PressedMail then uses that provider for drafting, summaries, tags, and other AI-assisted workflows where enabled.
AI tools are available only in the separately distributed PressedMail Pro edition. They are disabled by default and are not required for the core email client. PressedMail Free does not send email content or email metadata to an AI provider.
Before AI Can Process Email
An administrator must save a provider configuration and accept the current provider-specific data-use disclosure. The acceptance records the administrator user ID, timestamp, provider type, normalized endpoint, and disclosure version. It never records the provider API key.
The administrator must affirm that the provider and account configuration do not use Google-originated email data to train or improve generalized or foundational AI models. Changing the provider type or endpoint operator invalidates the acceptance and disables AI until the new provider is reviewed. Changing only the selected model does not require new acceptance.
Background auto-tagging or security analysis requires a second, separate automation acceptance because it can run without a separate user action for every message.
Data Sent
When an authorized user invokes an AI action, PressedMail may send the selected subject, sender and recipient information, message body, conversation context, labels, dates, other relevant metadata, and the user's instructions. PressedMail does not currently send attachments or extracted attachment text.
Requests go directly from the customer-controlled WordPress installation to the configured endpoint. They do not pass through a CurbSoftware AI proxy. Generated drafts and replies are returned for review and are not sent as email until the user performs a separate sending action.
Supported Provider Configurations
| Configuration | When contacted | Terms and privacy |
|---|---|---|
| OpenAI Compatible | After an administrator configures an OpenAI-compatible endpoint, accepts the disclosure, and an authorized user invokes AI or an accepted automation runs | OpenAI API, Service Agreement, Privacy Policy when OpenAI operates the endpoint |
| Google Gemini | Under the same conditions, using the Gemini API endpoint | Gemini API, Gemini API Terms, Google Privacy Policy |
| Anthropic | Under the same conditions, using the Anthropic API endpoint | Anthropic API, Commercial Terms, Privacy Policy |
| Ollama or another self-hosted endpoint | Under the same conditions, using the endpoint selected by the administrator | Ollama, Terms, Privacy Policy when Ollama operates the service |
For an arbitrary administrator-supplied endpoint, PressedMail cannot identify or control the operator. The site owner must evaluate the endpoint's terms, retention, security, data location, and training behavior before accepting the disclosure.
Disabling AI stops future requests but does not necessarily erase information already processed or retained by the provider. Use the provider's deletion process for data in its custody.
Use AI Safely
- Review generated drafts before sending.
- Do not ask AI to process secrets that do not belong in an email.
- Keep provider keys limited to the site that needs them.
- Disable AI actions for roles that should not process mailbox content.
- Use API account settings that prohibit model training and minimize retention.
- Review the full PressedMail Privacy Policy before activation.