Privacy Policy
Last updated: November 6, 2026
This Privacy Policy describes how Rootscope ("we", "us", or "our") collects, uses, and protects your information when you use WP Admin Online ("the Service") at wp-admin.online.
1. Information We Collect
Account Information
When you create an account, we collect:
- Name and email address — to identify your account and communicate with you
- Password — stored in a securely hashed format; we never store or have access to your plaintext password
- Profile photo — optionally uploaded by you
- Two-factor authentication data — if you enable 2FA, we store the encrypted secret required to verify your codes
- How you found us — the first page you visited on our site, the website that linked you there and any campaign tags in that link, stored with your account when you sign up
Social Login
If you sign in using a third-party provider (such as Google or GitHub), we receive and store an access token and basic profile information (name and email) from that provider. We do not receive or store your password from any third-party provider.
WordPress Site Data
When you connect a WordPress site, the following data is collected from your site via our companion plugin:
- Site name and URL
- WordPress version and PHP version
- Installed plugins and themes, including names, versions, active/inactive status, and available updates
- Administrator user list (WordPress user ID, display name, and username)
- Sync logs including timestamps, HTTP status codes, and error messages
This data is synced automatically on a daily schedule and can also be triggered manually.
Uptime Monitoring Data
When uptime monitoring is enabled for a site, we collect:
- HTTP response status codes and response times from periodic checks
- Downtime start and end timestamps
- The geographic location from which the check was performed
Uptime checks request the full page over HTTP but we do not store or analyze page content — only status codes, response times, and headers are recorded.
Backup Data
When backups are enabled, we store:
- A compressed copy of your site's files and database on our cloud storage (Hetzner S3 or Backblaze B2, depending on your region preference)
- Backup metadata including file sizes, timestamps, and integrity checksums
- Backup job status and error logs
Backup data is stored encrypted in transit (HTTPS) and access-controlled by your account. We do not inspect or analyze the contents of your backups.
Login Activity Data
We record WordPress login events reported by the companion plugin:
- Successful and failed login attempts, including the username tried
- IP address and user agent of the login attempt
- Approximate geographic location (country and city) derived from the IP address via a third-party geolocation service
This data is used to detect brute force attacks and logins from unusual locations. IP geolocation results are cached for up to 7 days.
File Integrity Data
We store SHA-256 hashes of critical WordPress configuration files (such as wp-config.php and .htaccess) to detect unauthorized modifications. We do not store or transmit the actual file contents — only the cryptographic hash.
Performance Data
We collect Core Web Vitals metrics (LCP, INP, CLS, TTFB, FCP) and Lighthouse scores from Google's PageSpeed Insights API. This data contains no personally identifiable information — only technical performance measurements for your site's URL.
Client Data
You may optionally store client records (name, company, email, and notes) within the Service. This data is provided entirely by you and is used only within your account.
Authentication Credentials
- API keys and secrets are generated for each connected site to authenticate communication between the Service and your WordPress plugin. These are stored securely.
- Account tokens used for plugin auto-registration are stored as SHA-256 hashes — we do not retain the plaintext token after generation.
- Basic auth credentials, if your site uses HTTP basic authentication, are stored in encrypted form.
- One-click login tokens are short-lived, cryptographically signed tokens used to authenticate you into your WordPress sites. We log the IP address used when generating them.
- AI app connections — when you connect an AI app to the MCP server, we store identifiers of the tokens issued to it, not the tokens themselves (see section 3).
Payment Information
If you subscribe to a paid plan, payment processing is handled by Stripe. We store your Stripe customer ID but do not store your credit card number or payment details — those are held securely by Stripe in accordance with their privacy policy.
What We Do NOT Collect
- Your WordPress content (posts, pages, media) — except within backups you explicitly enable and automatic database snapshots taken before batch plugin/theme updates (used for rollback and retained for 7 days)
- Customer or visitor data from your sites
- Any sensitive or personal information from your WordPress sites beyond what is listed above
2. How We Use Your Information
We use your information to:
- Provide, maintain, and improve the Service
- Display your connected WordPress sites, their status, plugins, themes, and security vulnerabilities
- Monitor your sites' uptime and performance
- Back up your site files and database
- Detect and alert you to security threats (brute force attacks, file tampering, vulnerabilities)
- Facilitate one-click login to your WordPress sites
- Process payments and manage subscriptions
- Send transactional emails (account verification, password resets, security alerts, uptime notifications)
- Detect and prevent abuse or unauthorized access
We do not sell, rent, or share your personal information with third parties for marketing purposes.
3. MCP / AI Integration
The Service provides a Model Context Protocol (MCP) server that lets an AI app you choose, such as Claude or ChatGPT, look up your fleet data and start a small set of actions on your behalf. Nothing reaches an AI app through the MCP server unless you connect one yourself.
How MCP access is controlled
- You connect an app by signing in to WP Admin Online with your own account and approving the request. Your password is never shared with the AI app
- The approval screen names the app, where you will be sent back to, and everything the app will be able to read and start
- Access is tied to your user account: a connected app can only see and act on sites you own
- Sign-in can only hand control back to Claude, ChatGPT, or an app running on your own computer
- Browser-based MCP clients are restricted to approved origins (Claude and ChatGPT domains by default)
What a connected app can access
- Your sites with their status and health scores, plugins and themes, available updates, known vulnerabilities, backup history and uptime
- The activity log of your sites, which names the WordPress usernames behind logins and changes
- Your client records: each client's name, company and email address
- Actions in your account: a data sync, a vulnerability scan, a health score recalculation, a client report emailed to your account address, and a backup of a site or of its database. None of them changes your WordPress sites
- A request for the download link of a finished backup. The link is emailed to your account address and is never given to the app
What we store for a connection
- The app's registration: its name and the address it returns you to, as the app supplied them. This says nothing about you
- A sign-in record for each time the app signs in or renews its access: when that happened, what the app is allowed to do, and when that access runs out
- Identifiers of the access and renewal tokens issued to the app. The tokens themselves are held by the app, not by us
Access lasts 30 days and is renewed automatically while the app stays in use. An app that has not renewed its access for 90 days has to ask you to sign in again. Disconnecting an app deletes its sign-in records and token identifiers for your account straight away. Otherwise they are kept until you delete your account.
Disconnecting an app
Every app connected to your account is listed under Connected apps in your profile settings, where you can disconnect any of them at any time. Disconnecting ends the app's access straight away: it has to ask you to sign in again before it can come back. Removing the connector inside the AI app stops that app from using it, but the connection stays open on our side until you disconnect it here or it runs out. Deleting your account ends every connection.
Data sent to AI providers
What a connected app looks up is sent to the provider of that app (Anthropic for Claude, OpenAI for ChatGPT) to answer you, and is then subject to that provider's privacy policy and data handling practices. This includes the personal data named above: client names, companies and email addresses, and WordPress usernames. We recommend reviewing Anthropic's Privacy Policy or OpenAI's Privacy Policy before you connect an app.
You are in control of this data flow: an app only receives what it looks up while it is connected, and you can disconnect it at any time.
4. Third-Party Services
We use the following third-party services:
- Stripe — for payment processing. Your payment data is subject to Stripe's Privacy Policy.
- WordPress.org API — to check for plugin and theme updates. No personal data is sent; only plugin/theme slugs and versions are queried.
- WPVulnerability.net — to check plugins, themes and WordPress versions for known security vulnerabilities. Only plugin/theme identifiers and versions are sent.
- Wordfence Intelligence — we download its public vulnerability feed. Nothing about your sites is sent.
- Anthropic — for the AI-written update risk assessments and site audit summaries inside the Service. A risk assessment sends the plugin's name, the versions involved, its changelog and the site's PHP and WordPress versions. An audit summary sends the site's name and the technical findings of that audit. No account details, client records or WordPress usernames are sent. Subject to Anthropic's Privacy Policy.
- Google PageSpeed Insights API — to measure Core Web Vitals performance. Only your site's public URL is sent.
- ip-api.com — for IP address geolocation of login events. Only the IP address is sent; results are cached locally. Subject to ip-api.com's terms.
- Globalping — for distributed uptime checks from multiple geographic locations. Only your site's URL is checked; no personal data is sent.
- Hetzner Cloud and Backblaze B2 — for backup file storage. Data is stored encrypted in transit and access-controlled.
- OAuth providers (Google, GitHub, etc.) — if you use social login. Subject to each provider's respective privacy policy.
5. Data Security
We implement industry-standard security measures to protect your data, including:
- Encryption of sensitive data at rest and in transit (HTTPS)
- HMAC-signed API communication with replay protection (nonce-based) between the Service and your WordPress sites
- Hashed passwords, hashed account tokens, and encrypted authentication secrets
- Origin-validated MCP endpoints to prevent cross-site request attacks
- SSRF protection on all outbound HTTP requests (DNS rebinding prevention, redirect blocking, protocol pinning)
- SHA-256 integrity checksums on backup files
While we strive to protect your information, no method of transmission or storage is 100% secure.
6. Data Retention
We retain your data for as long as your account is active. Specific retention periods:
- Account data — retained until you delete your account
- Site sync data — retained for the lifetime of the connected site
- Backup files — kept for 180 days when the backup finishes on the 1st of a month, 70 days when it finishes on a Sunday, and 30 days otherwise
- Update snapshots — retained for 7 days after creation
- Login activity events — retained for 30 days
- Uptime check history — retained in hourly aggregates for 90 days
- Performance metrics — retained indefinitely while the site is connected
- HMAC nonces — purged hourly after expiration (10 minutes)
- AI app connections — sign-in records and token identifiers are kept until you disconnect the app or delete your account (see section 3)
If you delete your account:
- All your account data is permanently deleted
- Every connected AI app loses access, and its sign-in records and token identifiers are deleted
- All connected site data is removed
- All backup files are deleted from cloud storage
- This process is irreversible
We may retain certain records where required by law.
7. Your Rights
You have the right to:
- Access the personal data we hold about you
- Update or correct your account information at any time through your profile settings
- Delete your account and associated data
- Export your data — plugins, themes, activity logs, and performance metrics can be exported as CSV from the dashboard
- Disconnect any AI app connected to your account at any time, from your profile settings
- Withdraw consent for data processing
If you are located in the European Economic Area (EEA), you may also have additional rights under the General Data Protection Regulation (GDPR), including the right to restrict processing and the right to data portability.
8. Cookies
We use essential cookies to maintain your session and authentication state. We do not use third-party tracking or advertising cookies. See our Cookie Policy for details.
9. Children's Privacy
Our Service is not intended for users under 16 years of age. We do not knowingly collect data from children.
10. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of significant changes by posting a notice on the Service or sending you an email. Your continued use of the Service after changes take effect constitutes acceptance of the updated policy.
11. Contact Us
For privacy-related questions or to exercise your rights, please contact us or email [email protected].