Encrypted provider secrets
Saved API credentials are encrypted locally and are not re-displayed after they are stored.
Security, privacy & control
Keep editorial access, secrets and external connections explicit.
PressAI is designed so administrators can see who may act, which external services are configured and where human review remains required.
Control model
Security starts with fewer hidden decisions.
Granular WordPress capabilities
Access can be separated across sources, AI, search, publishing, automation, integrations and other operational areas.
Guarded outbound requests
External requests use URL, redirect, response-size, media and webhook safeguards appropriate to the integration.
Explicit integrations
PressAI contacts external providers only when you configure and use the corresponding source, AI or search integration.
Human publishing control
Publishing actions remain subject to workflow state, permissions and the operating mode your team selects.
Customer-owned content
Your WordPress content remains part of your site and editorial operation. PressAI organizes the workflow around it.
Data flow
Know when information can leave WordPress.
Most PressAI workflow state is handled inside WordPress. Data leaves your site only when a configured feature must contact an external service.
WordPress content & settings→PressAI workflow→Configured external service, when needed
Typical external connections
- Sources your team asks PressAI to monitor.
- AI providers configured with your own credentials.
- Search or analytics connectors you explicitly enable.
- Webhooks or integrations your administrator configures.
Clear responsibility boundaries
PressAI protects the editorial workflow; it does not replace site operations.
Editorial workflow controls
Source monitoring, evidence, AI-assisted editorial processing, review gates, search preparation, queue visibility and governed publishing actions.
Infrastructure and WordPress maintenance
Hosting, backups, server administration, WordPress/core/plugin/theme maintenance and broader infrastructure security remain separate responsibilities.
Trust through inspectability
Critical editorial states stay visible.
Evidence conflicts, Fact Guard decisions, quality blockers, queue failures and source health are surfaced for review instead of being silently hidden behind automation.
Evidence conflicts
Critical contradictions are surfaced for editorial review rather than auto-resolved.
Operational failures
Failed jobs, retries and source health remain visible so teams can diagnose the workflow.
Publishing readiness
Readiness and permissions remain part of the decision before draft, schedule or publish actions execute.
Review the controls before you automate.
Use the security, data-safety and team-access guides to decide how PressAI should operate on your site.