The site health preview now works without a TalkToWP account, and the uploads directory is resolved entirely through wp_upload_dir(). No action needed.<\/p>","1.6.0":"
First release on WordPress.org.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.gif":{"filename":"icon-128x128.gif","revision":3734110,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.gif":{"filename":"icon-256x256.gif","revision":3734110,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3734110,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3734110,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.6.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3734110,"resolution":"1","location":"assets","locale":"","width":1267,"height":823},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3734110,"resolution":"2","location":"assets","locale":"","width":1347,"height":872},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3734110,"resolution":"3","location":"assets","locale":"","width":1200,"height":791},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3734110,"resolution":"4","location":"assets","locale":"","width":1623,"height":826},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3734110,"resolution":"5","location":"assets","locale":"","width":1637,"height":865}},"screenshots":{"1":"Overview \u2014 the local checks that need attention, each with a plain-English explanation of what it means.","2":"Security \u2014 the full local scan: core file integrity, injected plugin and theme files, database injections and admin accounts.","3":"Diagnostics \u2014 server environment, PHP version, memory limit, disk use and database table health.","4":"The TalkToWP dashboard \u2014 problems found across every connected site, ranked by severity.","5":"AI Chat \u2014 ask about any problem and get step-by-step instructions for fixing it."}},"plugin_section":[],"plugin_tags":[284963,5603,247,600,151481],"plugin_category":[54],"plugin_contributors":[284964],"plugin_business_model":[],"class_list":["post-330717","plugin","type-plugin","status-publish","hentry","plugin_tags-ai-diagnostics","plugin_tags-monitoring","plugin_tags-performance","plugin_tags-security","plugin_tags-site-health","plugin_category-security-and-spam-protection","plugin_contributors-talktowp","plugin_committers-talktowp"],"banners":{"banner":"https:\/\/ps.w.org\/talktomonitor\/assets\/banner-772x250.png?rev=3734110","banner_2x":"https:\/\/ps.w.org\/talktomonitor\/assets\/banner-1544x500.png?rev=3734110","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/talktomonitor\/assets\/icon-128x128.gif?rev=3734110","icon_2x":"https:\/\/ps.w.org\/talktomonitor\/assets\/icon-256x256.gif?rev=3734110","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/talktomonitor\/assets\/screenshot-1.png?rev=3734110","caption":"Overview \u2014 the local checks that need attention, each with a plain-English explanation of what it means."},{"src":"https:\/\/ps.w.org\/talktomonitor\/assets\/screenshot-2.png?rev=3734110","caption":"Security \u2014 the full local scan: core file integrity, injected plugin and theme files, database injections and admin accounts."},{"src":"https:\/\/ps.w.org\/talktomonitor\/assets\/screenshot-3.png?rev=3734110","caption":"Diagnostics \u2014 server environment, PHP version, memory limit, disk use and database table health."},{"src":"https:\/\/ps.w.org\/talktomonitor\/assets\/screenshot-4.png?rev=3734110","caption":"The TalkToWP dashboard \u2014 problems found across every connected site, ranked by severity."},{"src":"https:\/\/ps.w.org\/talktomonitor\/assets\/screenshot-5.png?rev=3734110","caption":"AI Chat \u2014 ask about any problem and get step-by-step instructions for fixing it."}],"raw_content":"\n
TalktoMonitor<\/strong> connects your WordPress site to the TalkToWP<\/a> platform for continuous AI-powered health monitoring.<\/p>\n\n Local security and health scanning run on your own site and need no account at all. Plain-English explanations, AI diagnostics, and the hosted dashboard are produced on the TalkToWP servers and require a free TalkToWP account. See the External services<\/strong> section below for exactly what is sent, when, and under which terms. TalkToWP receives nothing until you save a TalkToWP API key; the WordPress.org checksum API is contacted automatically, with or without a key, to check core file integrity.<\/p>\n\n Once connected, TalkToWP watches your site around the clock and uses AI to:<\/p>\n\n What data is collected?<\/strong><\/p>\n\n The plugin transmits technical metrics \u2014 WordPress version, PHP version, active plugins, available updates, database health, server memory usage, error log counts, and security scan results \u2014 and, in some cases, small pieces of your site's content: recent PHP error-log lines, the usernames and registration dates of administrator accounts flagged as unrecognised, and post IDs, titles and short excerpts from database scan findings. Error-log lines can contain server file paths and occasionally values from the request that caused the error. The External services<\/strong> section below lists exactly what is sent.<\/p>\n\n Features include:<\/strong><\/p>\n\n This plugin is the site-side agent for TalkToWP<\/strong>, a hosted WordPress monitoring\nservice operated by Beyondt Consultancy & Services Pvt. Ltd. Local security\nscanning and site health checks run entirely on your own server and require no\naccount. Plain-English explanations, AI diagnostics, and the hosted dashboard are\nproduced on the TalkToWP servers and require a free TalkToWP account.<\/p>\n\n 1. TalkToWP (app.talktowp.com) \u2014 required for AI diagnostics and the dashboard<\/strong><\/p>\n\n What it is used for: storing and analysing your site's health data, generating the\nAI diagnostics and incidents shown in your TalkToWP dashboard, and sending alerts.<\/p>\n\n Nothing is transmitted to TalkToWP until you paste a TalkToWP API key on\nSettings \u2192 TalkToWP and save. Removing the key stops all transmission to\nTalkToWP. (The plugin's local security scans still run without a key \u2014 see\nitem 2 below for the one request they make regardless of account status.)<\/p>\n\n Once a key is saved, the plugin sends:<\/p>\n\n The daily snapshot contains the following in addition to technical metrics:<\/p>\n\n The plugin does not deliberately collect passwords or visitor data, but anything\nan error-log line happens to contain is sent with it. The plugin never reads\nwp-config.php, .env files, or private keys.<\/p>\n\n The plugin registers three REST routes under health-data and Service terms: https:\/\/app.talktowp.com\/terms\nPrivacy policy: https:\/\/app.talktowp.com\/privacy<\/p>\n\n 2. WordPress.org checksum API (api.wordpress.org) \u2014 automatic, no account required<\/strong><\/p>\n\n What it is used for: the core file integrity scan. To tell whether a WordPress\ncore file has been modified, the plugin fetches the official checksums for your\nWordPress version from\n https:\/\/api.wordpress.org\/core\/checksums\/1.0\/?version=&locale=en_US\nand compares them against the files on disk locally. This runs as part of the\ndaily local security scan whether or not a TalkToWP API key is saved.<\/p>\n\n What is sent and when: your WordPress version number only, at most once per day\n(the response is cached in a transient). No site URL, no personal data. This is\nthe same WordPress.org service that WordPress core itself uses.<\/p>\n\n WordPress.org privacy policy: https:\/\/wordpress.org\/about\/privacy\/<\/p>\n\n\n Monitoring begins immediately after saving.<\/p>\n\n\n\n
\n
External services<\/h3>\n\n
\n
POST https:\/\/app.talktowp.com\/api\/plugin\/heartbeat<\/code> \u2014 every 3 minutes via\nWP-Cron. Sends a timestamp, the change in PHP error count, memory usage\npercentage, a hash representing your plugin\/theme\/core versions, and the HTTP\nstatus code of your own homepage.<\/li>\nPOST https:\/\/app.talktowp.com\/api\/plugin\/health<\/code> \u2014 once daily via WP-Cron, and\nalso when you save your API key, press \"Test Connection\", switch themes, or\nupdate WordPress core. Sends your site URL and the full technical snapshot:\nWordPress and PHP versions, active plugins and themes with their versions,\navailable updates, database size and table status, server memory and disk usage,\nerror-log line counts and recent error-log lines, WP-Cron status, SSL certificate\nstatus, and security scan results. The next paragraphs list the parts of that\nsnapshot that are more than counts. You can inspect the exact payload before it\nis ever sent using the \"Preview Data Sent for Analysis\" button on the settings page.<\/li>\nPOST https:\/\/app.talktowp.com\/api\/plugin\/uninstall<\/code> \u2014 once, when you delete the\nplugin. Sends only your site URL, so TalkToWP can close open incidents and mark\nthe site as disconnected.<\/li>\n<\/ul>\n\n\n
\/wp-json\/talktowp\/v1\/<\/code>:<\/p>\n\n\n
health-data<\/code> (GET) \u2014 returns the same technical snapshot described above. It\nchanges nothing.<\/li>\nreset-homepage-hash<\/code> (POST) \u2014 fetches your homepage, stores a new fingerprint of\nits text in place of the old one, and clears the recorded \"homepage changed\"\ntime, so the homepage-change check starts again from the current page.<\/li>\npush-now<\/code> (POST) \u2014 sends a fresh health snapshot to TalkToWP and, when the\nrequest asks for it, first runs a new security scan and stores the result.<\/p>\n\nreset-homepage-hash<\/code> require your API key in an X-API-Key<\/code>\nrequest header. push-now<\/code> requires an HMAC-SHA256 signature derived from your API\nkey, with a \u00b15-minute window and replay protection. The only things these routes\nwrite are the plugin's own options in your WordPress database, such as the\nhomepage fingerprint and the last scan result. None of them install, update,\nactivate or deactivate anything, and none modify plugin, theme, core or any other\nsite files.<\/p><\/li>\n<\/ul>\n\n\n