Security and Data Handling

Summary: Antimanual Builder Pro uses controlled imports, server-side API key storage, and sanitization at save and render time to protect site data. This guide explains how the plugin handles security, temporary files, AI requests, and administrator best practices for safe, reliable page building.

Security and data handling in Antimanual Builder Pro are designed to keep imports, AI actions, and stored assets under administrative control. The plugin follows a conservative processing model: it accepts only authorized requests, sanitizes content at save and render time, and limits external service usage to actions you explicitly start. This helps reduce exposure while keeping page building predictable and manageable.

How Antimanual Handles Security

The core security approach is to avoid arbitrary code execution and to restrict unsafe input surfaces. Imported markup is processed through a script-free allowlist, and event-handler attributes are removed before content is stored or displayed. This means the plugin is built to preserve usable page structure while filtering out risky elements that could create security issues.

In practice, this gives administrators a controlled environment for page generation and migration. The system focuses on safe content handling rather than unrestricted file processing, which is especially important when working with AI-generated pages or imported assets.

• No custom CSS, JavaScript, or PHP input surfaces are exposed for content import.
• Sanitization runs both when content is saved and when it is rendered.
• Import jobs are tied to the user who started them.

External Services and AI Data Flow

Antimanual uses external AI providers only when you trigger an AI action. The plugin does not continuously transmit site data in the background. Instead, content is sent only during specific operations such as page generation, conversational refinement, knowledge-base indexing, or supported import workflows.

The API key is stored server-side and should remain accessible only to authorized administrators. This helps ensure that AI connectivity stays controlled by your WordPress installation rather than exposed in the browser or available to untrusted users.

When planning your implementation, review the provider you choose, the data it receives, and the permissions attached to the key. If your organization has internal requirements for privacy or retention, align those policies before enabling AI-based workflows.

Import Security and Temporary Storage

Large imports are handled with chunked uploads so the process is less likely to fail because of timeouts, memory limits, or interrupted connections. Temporary chunks are stored in a protected folder while the archive is assembled, and that storage is not treated as normal site content. Once the import job finishes, temporary data is cleaned up.

This design reduces the risk of exposing incomplete files during processing. It also supports more stable handling for large projects, since the system can validate and reassemble content before it becomes part of the live site.

• Chunks are stored temporarily in a restricted import folder.
• The archive is reassembled before import processing begins.
• Temporary data is removed after the job is completed.

Recommended Security Controls for Administrators

Antimanual Builder Pro includes built-in safeguards, but a secure deployment also depends on operational discipline. Apply least privilege, review access regularly, and confirm that your WordPress and PHP versions meet supported requirements. These basic controls help ensure that import and AI tools remain available only to trusted users.

For business environments, it is also sensible to document a repeatable workflow for updates, access reviews, and recovery testing. Security becomes stronger when it is part of routine administration rather than a one-time setup task. 7 Essential WordPress Security Tips for Businesses

• Restrict plugin access to trusted administrators.
• Keep WordPress, PHP, and related plugins current.
• Review logs and import activity after major changes.
• Test recovery procedures before a real incident occurs.

Data Handling Best Practices

When imported content contains media, design assets, or reusable sections, keep track of where those files are stored and who can modify them. Use the component library deliberately so updates remain traceable. If content is migrated from existing pages, verify that the original data should be replaced or preserved before finalizing the import.

For teams managing multiple properties, standardize storage, review, and approval processes across all sites. Consistency improves governance and makes it easier to detect unexpected behavior, especially when several people contribute to the same build workflow.

What to Expect from the Plugin

Antimanual Builder Pro is designed to support productive page building without expanding attack surface unnecessarily. It uses authorized access checks, controlled import handling, and conservative sanitization to reduce risk. Combined with proper administrative practices, this gives organizations a practical security posture for AI-assisted and manual page creation.

If you are preparing a broader deployment, document your internal policy for API keys, import permissions, and asset review. A clear policy helps your team use the plugin safely and consistently while preserving business continuity.