What Visitor and Site Content QCTNH Does Not Collect

QCTNH is designed around scheduler metadata and service identity, not visitor tracking or transfer of Joomla article/customer content.

What it does not need for its purpose

• Article bodies or category content.
• Frontend form submissions or visitor browsing history.
• Customer account passwords.
• Arbitrary Joomla database tables from unrelated extensions.
• The content of backup archives, support tickets, signatures, memberships, or files managed by other QuantaCade products.

Frontend heartbeat is operational, not analytics

The injected same-site heartbeat is throttled to roughly once every six hours and is used to refresh QCTNH scheduling/service state. It is not a page-view counter and does not turn each visitor request into a QuantaCade tracking event.

What administrators should still protect

The WebCron key and QCTNH service credential are secrets because they authenticate scheduler/service operations. Protect Joomla Administrator, configuration files, database backups, and server logs according to normal security practice.

Public service assumption

What Visitor and Site Content QCTNH Does Not Collect assumes QuantaCade can safely reach the Joomla site from the public Internet. Private development environments can still use Joomla Scheduler through local/CLI/server-cron mechanisms, but they are intentionally outside the central Task Nudge wake-up model.

This is a product security constraint, not a licensing restriction; QCTNH remains free.

Community Discussion

Want to compare scheduler workflows, share practical tips, or discuss how you use this QCTNH feature? Visit the QC Task Nudge & Health Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.