WPSecureOps

Terms

Terms of service

These terms cover the WPSecureOps dashboard at this domain and the WPSecureOps Connector plugin that reports to it. They describe how the service is actually provided today, rather than reserving every right a longer document could.

Who provides this service

WPSecureOps is operated by G. Schad, postal address [to be completed]. Questions go to the contact page.

What the service does

The connector reads scans that Wordfence has already completed on your WordPress site and forwards the findings to this dashboard, where they are queued, kept with their history, and triaged. It is a reporting and triage tool. It does not scan your site, does not modify Wordfence, does not remove malware, and does not act on your site in any way.

Detecting a problem remains Wordfence's job, and fixing one remains yours. Nothing here is a guarantee that a site is secure, or that every problem on it has been found.

Your account

You are responsible for keeping your sign-in credentials and API keys confidential, and for what is done through your account. Tell us through the contact page if you believe a key or an account has been compromised, and it can be revoked.

Connect a site only if you are authorised to install plugins on it and to share its security findings. If you monitor sites for clients, telling those clients is your responsibility — the privacy page sets out exactly what leaves their site so you can show them.

Acceptable use

  • Do not attempt to access another account's sites, findings or keys.
  • Do not probe, load-test or attack this service or the infrastructure behind it.
  • Do not use the ingestion API to submit data from sites you do not control.
  • Do not resell access to the dashboard as your own product without agreeing it first.

Using the findings you receive here inside your own security work for your own clients is exactly what the service is for, and needs no further permission.

Availability and support

The service is provided as it is, with no uptime commitment and no guaranteed response time. It runs on a single server and can be down for maintenance, upgrades or failure. Alerts may be delayed or, if the service is unreachable long enough for a connector to exhaust its retry schedule, not arrive at all.

Treat it as one input into your security process, not as the only thing watching a site. If an alert arriving matters to you, keep Wordfence's own email alerts switched on as well.

Fees

There is no charge for the service at present, and no payment details are collected. If that changes, existing accounts will be told before any fee applies, and nothing will start billing automatically.

Your data

The findings you send stay yours. The privacy page describes what is collected, what is never collected, and how it is stored. Nothing is sold, shared with advertisers, or used to train anything. Removing a site deletes its findings immediately and in full.

The plugin's licence

The WPSecureOps Connector plugin is free software under the GPL, version 2 or later. That licence governs the plugin itself — including your right to inspect, modify and redistribute it — and is separate from these terms, which govern the hosted dashboard.

Ending it

You can stop at any moment: press Disconnect in the plugin or deactivate it, and that site sends nothing further. Removing a site from Manage sites deletes its data here. To close an account entirely, ask through the contact page.

Access may be suspended or removed for a breach of the acceptable-use section above, or if the service is discontinued. If the service is discontinued, reasonable notice will be given so findings can be exported first.

Liability

The service is provided without warranty of any kind, to the fullest extent the law allows. It is not liable for a security incident on a monitored site, for a finding it did not report, for an alert that arrived late, or for any loss following from those. This does not limit any liability that cannot lawfully be limited.

Changes

These terms change when the service does. Material changes will be noted on this page, and the version that applies is the one published here at the time.