Support
Start here
Check the guide before you write a support post
If Page Content Guard is not behaving as you expected, there is a good chance the answer is already in the Help & Documentation pages. They cover installation, monitor setup, current problems, scheduled checks, email, data removal and diagnostics.
I would rather help you rule out a setting, an unsupported content source or a WordPress scheduling problem first than make you wait for an answer that simply points back to the documentation.
Page Content Guard FREE
Use the public WordPress.org support forum
Once Page Content Guard FREE is approved and published, its WordPress.org forum will be the support route for the free plugin.
Before posting, open the Technical Report inside Page Content Guard. It collects the version and diagnostic details that usually matter, without requiring a database export or access to your site. Read it before sharing and remove anything you do not want to place in a public forum.
Page Content Guard PRO
Use the customer Gumroad Community
If you have an active PRO subscription, open Page Content Guard PRO from your Gumroad receipt or Library and choose Community. That keeps PRO questions with the people who have access to the same paid features and current downloads.
Support is best effort and response times are not guaranteed. To make a report useful, include the FREE and PRO version numbers, your WordPress and PHP versions, what you expected, what happened instead, the steps that reproduce it and the exact error message when one exists.
A focused screenshot or a redacted Technical Report is usually more useful than a long description. Do not post credentials, private page content or a full database export.
Security reports
Found a possible vulnerability? Report it privately.
Do not describe a suspected vulnerability in the public WordPress.org forum or the Gumroad Community before there has been time to investigate it.
Send the technical details to [email protected]. This address is only for security reports, not ordinary support. You do not need to provide your name, site address, login details or any other personal information that is not required to explain the issue.
One important boundary
Support does not require access to your website
Do not send passwords, temporary administrator accounts, database exports, customer information or copies of private monitored content. A reproducible description, version details, diagnostics and a carefully cropped screenshot should be the starting point.