Trust & Safety.

Protuno runs maintenance work on the WordPress sites you connect: updates, clean ups, fixes and checks. This page explains the limits it works inside, in plain language. The legal versions are our Terms and Privacy Policy.

1. The short version

• Your key, your rules. Protuno connects with an application password you can revoke at any time. It never stores your WordPress admin password, and never asks for SSH or FTP logins.
• Read only by default. A live site starts in Read only. Nothing changes until you switch it to Execute. We suggest trying Protuno on a staging copy first.
• You decide when. On Copilot, work waits for you to press Run. On Autopilot, it also runs on the schedules you set.
• Roll back a run. Most changes keep their earlier value, ready to put back, and the report tells you which ones cannot be undone.
• Hard limits. Changes that can never be recovered are refused before they run.
• Encrypted. Site passwords and tool keys are encrypted at rest, and every connection uses TLS.

2. What the agents can do

You install the Protuno plugin on your site, or let Protuno install it for you (see section 3). The plugin sets up a connector that lets an agent work on WordPress, and creates the application password Protuno signs in with, for an administrator account. Depending on the job, the agent can:

• Read the site: WordPress, PHP, plugin and theme versions, settings, posts, pages, comments and site health.
• Install, update and switch plugins on or off, and install or update themes.
• Create, edit and trash posts, pages and their custom fields.
• Edit page builder layouts.
• Change WordPress settings and options.
• Moderate comments and upload media.
• Read and edit theme and site files, when a job needs to.
• Run PHP or a WP-CLI command for a check or fix that has no dedicated tool. Rollback cannot record these, which is why they are held to the rules in section 3 and listed on the run report.

Because the agent can run PHP, its reach is close to a server administrator’s, not only what the WordPress account can click in wp-admin. That is why the limits in sections 3 to 7 exist.

Most work runs as a playbook: a named list of steps you can read before it runs, and a report afterwards of what each step did. You can also ask for a one-off change in chat.

3. What they will not do

• Anything that cannot be recovered. Force deleting a post (skipping the trash), deleting a WordPress user, dropping or emptying a database table, and unbounded deletes run straight on the database are refused before they reach your site. The agent is pointed to the recoverable route instead, such as moving a post to the trash. This applies on every plan, in every mode, and to playbooks you write yourself.
• Change a site that is in Read only. See section 5.
• Run a schedule on a Copilot site. Only Autopilot sites run playbooks on a schedule.
• Keep your passwords. If you choose “Install it for me”, Protuno uses your WordPress admin login once to install the plugin and create the application password, then drops it. It is never stored or logged. Protuno never asks for SSH or FTP logins, and a hosting tool is only connected if you add its API key yourself.

4. Copilot and Autopilot

Your plan decides whether work only runs when you start it. Everything else on this page, read only mode, rollback, the backup check and the refusals in section 3, is the same on both.

Two more layers sit inside either plan:

• Team roles. Each person’s role decides whether they can run playbooks, apply updates or disconnect a site. Anyone you invite, a client for example, can be given a narrower role.
• API keys. A key you issue acts as you and reaches only the sites you can reach.

5. Read only by default

Every connected site has an access mode, shown in the Manage top bar: Read only (analyse and report, change nothing) or Execute (may change files, the database and settings). A live site starts in Read only. A site you mark as staging starts in Execute, because that is where you test.

On a Read only site:

• Playbooks still run, but every tool that can change the site is removed first, and each remaining call is checked again before it reaches the site.
• One-off actions and automations are refused, with a note saying why.
• Rollback is also off, because putting a value back is a change too.
• A scheduled playbook that could write is skipped, and the skip is shown with its reason.

The check happens in Protuno’s own code, at the point a tool is called. It does not depend on the AI choosing to behave.

We suggest connecting a staging site first

Before you let Protuno change your live site, connect a staging copy of it and see what the agents do there:

1. Connect the staging copy and mark it as staging. It starts in Execute, so playbooks can make their changes.
2. Run the playbooks you plan to use, and read their reports.
3. When you are happy, connect your live site. It starts in Read only, and nothing changes there until you switch it to Execute.

6. Undoing a change

Every write Protuno makes through its site tools is recorded as it happens: the value is read, the change is made, and the earlier value is kept. That covers settings and options, posts and pages, custom fields, page builder layouts, plugin activation, plugin updates, comment status, and theme and site files.

A run that changed something reversible shows a Roll back button on its report. The site has to be in Execute. It is never one click:

1. Protuno reads your site live and shows what would be put back, and what would be skipped, for example a value that has been changed again since the run.
2. Nothing changes until you confirm.
3. The result shows exactly what was reversed, skipped or failed. A run can be rolled back once.

Some changes cannot be recorded: anything done by PHP or WP-CLI, installing a plugin or theme, updating a theme, and uploading media. When a run made one of those, the report lists it as a change that cannot be undone, before you rely on the button. Posts an agent deletes go to the WordPress trash, so you can also restore them from there.

7. Backups

Rollback covers what Protuno recorded. Playbooks whose changes rollback cannot fully cover, such as database optimisation, hardening and fixes that run code, carry a backup step before they write. Protuno checks that the step is there before the run starts, and refuses to start a playbook that would write with no backup step at all, or with the backup after the first change, including one you built yourself.

Protuno is not your backup system. Keep your own backups with your host or a backup plugin, as section 3 of our Terms asks. If your membership, payment or store plugins matter to you, try each job on a staging copy first, as section 5 suggests.

8. Connected tools

You can also connect tools such as Slack, ClickUp or Cloudflare, by pasting a key you create in that tool. Each connection lists what it can do. By default, reads run on their own and anything that changes something in the tool asks you first. You can change either, one capability at a time, and remove the connection whenever you like.

9. Your data and where it lives

What we store to run the service:

• Your account: name, email, and your password in hashed form.
• Connected sites: the domain, the WordPress username, the application password (stored encrypted), WordPress and PHP versions, and the installed plugins and themes.
• Findings and run history: what each check found and what each step of a run did. To make rollback possible, a run also keeps the earlier value of each thing it changed, for example the previous text of a post it edited. That record belongs to the run and is deleted with it.
• Server and security logs, kept for 12 months.
• Billing records. Paddle takes the payment. Your card details never reach us.

Where it lives:

All traffic is encrypted in transit over TLS, and credentials are encrypted at rest. The full list of companies that process data for us is in section 7 of the Privacy Policy, and how long we keep each kind of data is in section 9.

10. AI models

Agents use AI models to read findings, plan fixes and write reports. Agent work runs on Anthropic’s Claude. When an agent works on a job, the parts of the site that job reads, for example a setting it is checking or a post it is editing, are sent to the model so it can do the work.

A few features also use OpenAI: Brain, which remembers what agents learned about your site, and the step that matches a chat message to the right tools. The text those features handle is sent to OpenAI for that purpose.

• Your WordPress application password is never sent to a model.
• Our agreement with Anthropic prohibits training their models on your data.
• If you use Protuno inside ChatGPT, ChatGPT gets an access token limited to the permissions you approve, never your WordPress credentials, and nothing changes on a site until you approve the plan. Details are in the Privacy Policy.

11. Disconnecting and deleting

You can cut Protuno off from a site in any of these ways:

• In Protuno, disconnect the site. This stops any run in progress, deletes the stored application password, asks your site to revoke it, and stops uptime checks. The site’s scans and history stay, so you can reconnect later. To remove those as well, delete the project.
• In WordPress, open the Protuno screen and disconnect. This deletes the application password. You can also revoke it under Users, Profile, Application Passwords. Neither depends on us. Uninstalling the plugin on its own does not remove the password, so disconnect first.
• In ChatGPT settings, if you connected Protuno there.

To delete your whole account, email [email protected]. We acknowledge within 1 to 2 business days and finish within 30 days. Encrypted backup copies roll off within 90 days. The steps, and what the law makes us keep, are on Delete My Data.

12. What we do not claim

• Protuno is not a security product. It is not a firewall, a malware removal service or a replacement for your host’s protection.
• No system is perfectly safe. If we confirm a personal data breach that puts your rights at risk, we notify the authority within 72 hours and tell you without undue delay. See section 10 of the Privacy Policy.

13. Reporting a problem

If an agent did something you did not expect, or you think you have found a security issue in Protuno, email [email protected] with the site and, if you have it, the link to the run.