Fonts and Trackers​

Summary: Antimanual Builder Pro avoids third-party font CDNs and hidden trackers by default. This article explains how system fonts, external services, and saved content safeguards work, plus practical steps for administrators who want predictable typography, privacy-aware behavior, and controlled external requests.

Antimanual Builder Pro does not load third-party fonts or tracking scripts by default. The editor and generated pages are designed to stay lightweight, use the operating system’s native font stack, and avoid unnecessary external requests unless you explicitly trigger a supported AI action or add your own integrations.

This approach is intentional. It helps keep page rendering predictable, reduces privacy risk, and prevents hidden dependencies on services such as Google Fonts, Adobe Typekit, Bunny Fonts, or Font Awesome. In practice, your typography and tracking behavior remain under your control rather than being added automatically by the plugin.

Fonts: What the Plugin Loads and What It Does Not

Antimanual Builder uses a system font stack in its editor interface, typically based on Apple, Windows, and common sans-serif defaults. AI-generated pages are instructed to follow the same safe baseline, so the plugin does not inject remote font imports into your content.

For documentation and design consistency, this means the builder avoids automatic font loading from external CDNs. If you want custom typography, it should be added deliberately through your theme or your own WordPress setup, not as an implicit plugin behavior.

• No automatic Google Fonts loading from the editor or generated pages.
• No Bunny Fonts, Adobe Typekit, or Font Awesome CDN calls added by the plugin.
• System fonts are used to keep the interface consistent and reliable.
• Remote font imports are stripped from saved CSS or HTML when they match known font CDNs.

How to Install the Docy Core Plugin for the Docy WordPress Theme is a useful reference if you want to confirm the platform environment supported by the builder before customizing typography or deploying pages at scale.

Why External Fonts Are Restricted

Restricting font CDNs improves reliability and reduces unexpected rendering differences between the editor and the live page. It also helps keep the builder aligned with business and compliance requirements where external asset loading must be minimized.

Because fonts can affect layout, line wrapping, and spacing, loading them automatically can make a page behave differently in preview and production. Antimanual Builder avoids that class of problem by using local defaults unless you intentionally configure otherwise in your site stack.

Trackers: When External Requests Occur

Antimanual Builder Pro does not include hidden analytics trackers or third-party marketing pixels. External communication occurs only in specific situations, such as when you trigger AI-powered actions and have connected a supported provider through the optional companion plugin or your chosen integration path.

In addition, some generated pages may request placeholder images from placehold.co if unreplaced placeholder URLs are still present. That request is limited to the image dimensions and optional label text in the URL. The plugin itself does not transmit personal data in that process.

• No built-in advertising pixels or marketing trackers are injected by default.
• AI providers are contacted only when you explicitly request AI-generated content or edits.
• Placeholder image services may be used only when a page still contains placeholder image URLs.
• External services are documented so administrators can review them before use.

7 Essential WordPress Security Tips for Businesses is the best next step if you want a complete list of the services the product may contact and the exact circumstances under which those requests happen.

Server-Side Protection for Saved Content

As an additional safeguard, Antimanual Builder strips known third-party font imports from saved HTML and CSS before persisting content. This prevents accidental storage of remote font references that could otherwise reappear on the frontend later.

This protective behavior is especially useful when pages are generated or migrated from existing sites. It helps keep imported content clean and ensures that typography decisions remain intentional instead of being inherited from unknown external sources.

Practical Recommendations for Site Owners

If you manage a site with strict performance, privacy, or branding requirements, review your theme and any custom CSS for external font or tracking references. Antimanual Builder is built to avoid adding them, but your overall site can still load them through other plugins or theme settings.

• Audit your theme for remote font links and analytics snippets.
• Use local fonts when consistent rendering is a priority.
• Confirm AI provider settings before enabling content generation features.
• Test published pages in an incognito browser to verify that no unexpected requests occur.

is helpful if you want to understand when AI requests are sent and how to connect your preferred provider safely.

Summary

Fonts and trackers are handled conservatively in Antimanual Builder Pro. The plugin avoids third-party font CDNs, uses system fonts for its interface, strips known remote font imports from saved content, and limits external communication to clearly defined AI and placeholder-image scenarios. This keeps your workflow predictable, secure, and easy to manage.