Data processing summary

1.Our role

When you connect a website, some of the data we receive is about other people: the users of your site. For that data you are the controller and [Company legal name] is your processor. We process it only to provide the service, on your instructions.

For your own account and billing data we are the controller; the privacy policy covers that.

2.What we process for you

• Site users (from the WordPress plugin’s activity log): username, role, IP address, the country looked up from it, and the type and time of each login, failed login or account change.
• File data: paths, sizes, modification times and fingerprints of code files. File contents are never sent.
• Your contacts: alert email addresses and webhook URLs you enter.
• Anything personal you write into site notes, which the AI features can read.
• Error reports from the app: the error message, the page path and, if included, the browser’s user agent. The sender’s IP address is held only in memory, for up to an hour, to rate limit reports. Reports are scrubbed of email addresses, tokens and keys before they are forwarded to our error-tracking service.

3.Why and for how long

We use this data to show you what happens on your site, spot problems such as a new administrator or a login from a new country, alert you, and write AI security reviews.

Activity-log entries are not stored on the Free plan, are kept for 30 days on Starter and for 90 days on Pro and Agency, then deleted. Other site data is kept until you remove the site or delete your workspace’s data.

4.Sub-processors

We use these providers to run the service:

• Clerk — sign-in and accounts.
• Stripe — payments.
• Anthropic — the AI model (Claude) for the AI features. AI security reviews go only to Anthropic.
• OpenRouter — routes assistant questions to an AI model, when switched on.
• [Error tracking provider] — scrubbed error reports.
• Cloudflare — only if you connect your Cloudflare account.
• [Hosting provider] — servers and database.
• [Backup storage provider] — database backups.
• Our own mail server — alert emails.

Country lookups use the DB-IP Lite database, which we keep on our own servers, so IP addresses are not sent to DB-IP. We download known-malware fingerprints from abuse.ch MalwareBazaar and send it nothing.

We will tell you before adding or replacing a sub-processor, so you can object.

5.Security measures

• Encryption in transit: all traffic to the service and the plugin uses HTTPS.
• Encrypted secrets at rest: third-party secrets such as Cloudflare tokens are encrypted in the database. API keys, plugin connection keys and share links are stored only as hashes.
• Access control: each workspace sees only its own data, only named administrator accounts can use the service’s admin tools, and important actions are recorded in an audit log.
• Backups: the database is backed up regularly and backups are kept for 30 days.
• Data minimisation: the plugin sends fingerprints, not file contents, and the AI features never receive the activity log’s IP addresses.

6.Breach notification

If we become aware of a breach affecting personal data we process for you, we will tell you without undue delay and within [Breach notice period], with what we know and what we are doing about it, so you can meet your own obligations.

7.Helping you

We will help you answer requests from your site users (for example, to see or delete their data) and with any data protection assessments, as far as we reasonably can.

8.Deletion on account closure

You can remove a website at any time, which deletes its data. A workspace admin can delete all the data we process for the workspace in Settings → Delete workspace data: it is deleted immediately and any subscription is cancelled. If we close a workspace ourselves, we delete its data within [Deletion period after closure]. Either way, copies in backups expire after 30 days, and we keep only the records the law requires (such as billing records).

9.Full agreement

This page summarises our data processing terms. To sign a full data processing agreement, write to [Contact email].