Aimogen ProDocumentation
Product page Support

Security and privacy

The security and privacy considerations of running Aimogen Pro - credential storage, permissions, data flows to AI providers, and production hardening.

Aimogen Pro sends your content to third parties, stores credentials, exposes endpoints and — with agents and extensions — takes actions on your site. Each of those deserves a decision rather than a default.

Where credentials are storedHow API keys are held, who can read them, and how to keep them out of the database. Permissions and access controlWho can do what, and how to restrict it. Data, GDPR and retentionWhat leaves your site, what is stored, and for how long. Production hardeningA checklist before the plugin faces the public.

The four risks worth understanding#

1. Credentials in the database. Provider API keys are stored as plain text in the WordPress options table. Anyone with database access or manage_options can read them. See Where credentials are stored.

2. Content leaving your site. Every AI request sends your prompt — which may include post content, visitor messages, database rows or uploaded files — to a third-party provider. See Data, GDPR and retention.

3. Public endpoints spending money. A chatbot, an AI form, the REST API, a webhook — each is a way for someone else to trigger paid API calls. Usage limits are the control.

4. Prompt injection into action-taking features. When an AI that reads outside content also has tools that act, content can carry instructions. See Agent security.

What the plugin does well#

Nonces and capability checks on admin actions.

API keys are never printed in diagnostics. The key health system stores HMAC fingerprints, never key material, so the System Info report is safe to share.

Sensible defaults. Database access defaults to SELECT only. Webhooks and the REST API are off by default. God Mode is off. AI-generated snippets are stored inactive. Snippets without conditions run on the front end only. Script stripping on chatbot HTML is on.

Fatal-error protection in the Snippets Engine, with a wp-config.php kill switch.

A sandbox for agent file tools, restricted to uploads/aiomatic-exports with an extension allowlist.

What you have to decide#

The plugin cannot decide these for you:

  • Whether to expose front-end AI tools, and with what limits
  • Whether to enable action-taking extensions, and which
  • Whether to store chatbot conversations, and for how long
  • Whether provider retention should be on
  • Which roles get access_aiomatic_menu
  • Whether God Mode or write database access is ever appropriate on your site

Each of those is covered on the pages in this section.

Reporting a security issue#

Report suspected vulnerabilities privately through support rather than publicly. Version 2.8.5 and 2.8.4 both included fixes for responsibly reported issues.

Still stuck? Open a support ticket and include the diagnostics from Aimogen Pro › System & Logs › System Info.