Site DoctorPrivacy Policy
Site Doctor is a read-only WordPress diagnosis and monitoring service. This policy explains what we collect, why, how long we keep it, and the rights you have over it. A defining principle of the product shapes this whole document: our connector never modifies your site and never sends the site raw content it does not need — it answers read-only queries our side signs and initiates.
1. Who we are
The "Service" is Site Doctor (sitedoctor.syswp.pro), operated by SYSWP — CNPJ 29.557.871/0001-92, registered at Tv. Moraes Sarmento, 911 - Santa Clara, Santarém - PA, 68005-360, Brazil. For any privacy matter, the controller can be reached at [email protected].
We act as the data controller for your account information and for the operational data of the Service, and as a data processor for the site telemetry you instruct us to collect from the WordPress sites you connect.
2. What we collect
2.1 Account data
- Your name, email address and a hashed password (we never store passwords in readable form).
- The name of the organization you create and your role in it.
- Interface language and basic preferences.
- Authentication and security records: login timestamps, and IP addresses of failed login attempts (to protect the account).
2.2 Data from the sites you connect
When you install our connector plugin on a WordPress site and enter its key, the Service collects telemetry about that site so it can diagnose and monitor it. This includes, depending on the checks you enable:
- Availability checks (uptime, response time, HTTP status).
- Performance metrics (PageSpeed / Core Web Vitals, lab and, where available, real-user field data).
- Inventory: WordPress/PHP versions, installed plugins and themes and their state.
- An audit trail of significant events (logins, plugin/theme/option changes, user changes) reported by the connector.
- Log signal only — PHP fatals, warnings and error patterns. We do not ingest or archive your site's full access or error logs; those remain on your site. Our copy holds recent signal, not a long-term log archive (see Retention).
- Form metadata (which forms exist, whether they still render), scan findings, and incident records.
2.3 Access credentials you choose to store (vault)
You may optionally store site access credentials in the Service's vault. These are encrypted at rest. When an AI assistant connects over MCP, it can see the labels of stored accesses but never their values — the Service brokers a signed request and the AI never receives a credential.
2.4 Usage and site analytics
- Usage events such as MCP tool calls (which tool, when) to operate and improve the Service.
- Landing-page analytics: page path, referrer, device type, approximate country (derived from an edge header, never from looking up your IP with a third party), and campaign tags. We do not place personal data in URLs or query strings.
2.5 Website chat
- If you use the chat assistant on our website, we collect the name and email you enter, the optional number of sites you manage, and the conversation, to answer you and to follow up about the Service.
- The assistant answers from our own documentation. It has no access to any website and cannot scan or inspect one.
- To generate a reply, the text of the conversation is sent to a language-model provider through OpenRouter. Your name, email, IP address and site count are not sent to the model. Please do not type passwords or other secrets into the chat.
3. The AI / MCP interface
Site Doctor does not run a large-language model on your sites' data (the website chat in section 2.5 is the only place we call a model, and only with the chat text). When you connect your own AI assistant over MCP, your AI queries the read-only state of your sites through our broker. Your prompts and the AI's responses are processed by your chosen AI provider under their terms, not ours. We only see the tool calls made against our API.
4. How we use the data
- To provide the Service: monitor availability, run diagnostics, surface findings, keep a history and an intervention timeline, and send alerts.
- To secure accounts and prevent abuse.
- To operate billing for paid plans.
- To understand aggregate usage and improve the product.
We do not sell your data, and we do not use your site data to train any AI model.
5. Legal bases
Under the Brazilian LGPD (Lei 13.709/2018) and, for users in the EU/EEA, the GDPR, we process data on these bases: performance of a contract (to deliver the Service you signed up for), legitimate interest (security, fraud prevention, product improvement, balanced against your rights), legal obligation where applicable, and consent where required (e.g. optional communications).
6. How long we keep it (retention)
Retention reflects the read-only philosophy — we keep the minimum useful signal, not a permanent archive:
| Data | Free | Paid (Agency) |
|---|---|---|
| Health history (PageSpeed, scans/findings, audit events, incidents) | 30 days | 12 months |
| Raw uptime checks (operational) | ~45 days (the raw minute-by-minute data; long-term availability is preserved as summarized incidents) | |
Log signal (sd_logevents) | ~30 days — your full logs stay on your site; we retain only recent signal | |
| Intervention timeline & recorded decisions | Retained while the site is enrolled (institutional memory) | |
| Account data | Until you delete your account, plus any period required by law | |
When you disconnect a site or close your account, we delete or anonymize the associated data within a reasonable period, except where retention is required by law.
7. Who we share it with
We share data only with service providers ("sub-processors") that help us run the Service, under contract and only as needed:
| Provider | Purpose | Data involved |
|---|---|---|
| Cloudflare | Edge network, security, approximate geolocation | Request metadata, IP (at the edge) |
| Stripe | Payments for paid plans | Billing details you provide at checkout — we do not store card numbers |
| Google (PageSpeed Insights API) | Performance measurement | The public URL of the site being measured |
| Browserless (self-hosted by us) | Rendering sites for outside-in scans | The site URL being scanned |
| OpenRouter and the language-model provider it routes to | Generating the website chat assistant's replies | The text of the chat conversation only — never your name, email or IP |
| Our cloud infrastructure provider | Hosting the Service | All Service data, at rest |
We may also disclose data if required by law or to protect our rights, users or the public.
8. Security
- Every connector query is signed with HMAC-SHA256 and is read-only.
- Stored access credentials are encrypted at rest; the AI never receives credential values.
- Passwords are hashed; sessions and tokens are protected and expire.
- No third-party AI model receives your data from us.
No system is perfectly secure, but we design the Service to minimize what could be exposed.
9. International transfers
The Service is operated from Brazil and its providers may process data in other countries. Where data is transferred internationally, we rely on appropriate safeguards recognized under the LGPD and GDPR.
10. Your rights
Under the LGPD (Art. 18) and the GDPR you may request to: access your data, correct it, delete it, restrict or object to processing, obtain a portable copy, withdraw consent, and know with whom it is shared. To exercise any right, contact [email protected]; we respond within the timeframes required by law. You may also complain to the Brazilian ANPD or your local data-protection authority.
11. Cookies and local storage
We use the minimum necessary: a session cookie to keep you logged in, and browser local storage to remember your language choice. Landing analytics are aggregated and do not profile you across other sites. We do not run third-party advertising trackers.
12. Children
The Service is for professionals and is not directed to children. We do not knowingly collect data from anyone under 18.
13. Changes to this policy
We may update this policy; the "last updated" date above will change and, for material changes, we will notify account holders. Continued use after an update means you accept the revised policy.
14. Contact
Questions or privacy requests: [email protected] — SysWP, Brazil.