PHP Security Update Service Terms
Plain-English terms for the £149 check, £999 patch, the version upgrade and the annual maintenance plan. Last updated 22 October 2026.
1. Which service applies to you
These terms cover the PHP security update services booked through /services/php-updates: the £149 PHP check, the £999 emergency PHP patch, the PHP version upgrade (from £4,999) and the annual PHP maintenance plan. The general DevPros terms at /terms apply in addition to, not instead of, these service terms.
Your booking is confirmed by payment. Until payment succeeds there is no queue position and no work is scheduled.
The price you pay is the price shown at the moment of booking. Later price changes only affect new bookings.
2. What each service includes
PHP check (£149): a review of your PHP version, patch level and exposure, with a written report. The fee is not credited against a patch or upgrade.
Emergency patch (£999): moving your site to the fixed point release for your PHP version, with a backup, staging test, worker restart and smoke test. It covers the PHP change only — plugin and theme fixes are the optional £149 compatibility pass, and staging setup is the optional £249 add-on.
Version upgrade (from £4,999): migration to a newer PHP version with compatibility testing, staging QA and a rollback plan. Repair of up to 5 broken plugins, themes or code files is included; additional items are £95 each, and the item count is agreed with you before the fixes are written.
Annual maintenance plan (priced by application): monthly patching, backup checks and a written report for a year, beginning after the initial check is delivered. The plan does not include version upgrades; if the introductory check shows an upgrade is needed first, the upgrade is quoted separately and the plan start date moves accordingly.
3. Access and responsibilities
You confirm a backup exists before work starts. If your hosting has no backup facility and you bought the staging add-on, we create the environment; otherwise we will ask you to arrange one.
Access is agreed in advance and provided by deploy key, SSH key or a temporary account — never by sending passwords in email or forms.
You provide the agreed access within one working day of the booking being confirmed. If access is delayed, your place in the queue may move.
For managed hosting (WP Engine, Kinsta, SiteGround-style stacks), your host must apply or approve the change. We prepare the exact instructions your host needs, but the host controls their platform.
We do not work with payment card data. Payment processors (Stripe, PayPal and similar) are never modified as part of a PHP update.
4. Timescales
Emergency patch jobs are worked same or next working day where possible, and are queued ahead of non-emergency work. The phrase 'where possible' is doing honest work: host approval, staging availability and access delays can all extend it, and if they do we tell you as soon as we know.
The £149 check report follows the order of booking and is typically delivered within two working days of access.
Version upgrades are multi-day projects; the timeline in your quote is indicative until staging testing fixes it.
5. Refunds and cancellation
If we cannot start a job — the site turns out to be on an unsupported PHP version, the scope doesn't match what you booked, or we can't be given the agreed access — we refund the payment in full and explain why.
Emergency patch: if you ask to cancel after payment but before work starts, we refund in full. After work starts, the job is charged as delivered.
The £149 check is refundable in full before the report is produced, and that becomes the deliverable after that point.
Annual maintenance plan: full refund if you cancel within 14 days of payment and before the initial check is delivered. After the plan starts, cancellation refunds the unused whole months remaining, calculated from the plan start date.
Version upgrades are charged through an agreed schedule in the quote; the refund terms are stated in the quote itself.
6. Limits of the services
Patching closes the published vulnerability. It does not detect or prove the absence of compromise, malware or previously installed attacking code; if you suspect an incident, ask us separately before booking a patch.
Services do not guarantee that third-party software (plugins, themes, libraries) will be bug-free after the change. Where breakage is caused by the PHP adjustment, the included or purchased repair terms above apply.
Sites on PHP 8.1 or older cannot receive a point release because upstream discontinued fixes in that range; those sites need an upgrade or a vendor backport.
Our aggregate liability for any booking is limited to the amount you paid for it. Nothing here limits liability that cannot legally be limited.
7. Changes to these terms
These service terms may be updated; the applicable version is the one published here at the time of your booking. Material changes affecting an active maintenance plan will be notified in writing before the renewal date.
Last updated: 22 October 2026.
Book With Those Terms in Hand
The booking form shows the price and the add-ons for the plan you select; these terms complete the picture.
Book a PHP service