Backup & restore — service terms and data processing agreement

Version 1 · 18 September 2026. These apply to the £8/month website backup and restore service. Setting up the Direct Debit accepts them.

Part A — Service terms

1. What the service is

• Every night we take a copy of your website's files and its database, encrypt it, and keep it on our own server in Milton Keynes and in Backblaze B2 cloud storage in the European Union (Amsterdam).
• We keep every nightly copy for 30 days, one copy a week for 12 weeks, and one copy a month for 12 months.
• Once a month we restore a real file and your database from the cloud copy, check that the database opens, and email you what came back and when.
• When you ask, we restore a file, a folder or the whole site to any of the kept copies. We aim for the same working day; we do not guarantee a time, because restoring depends on your hosting being reachable.
• If a nightly backup fails we are alerted the same night and fix it.

2. What it is not

• It is not hosting, security patching, uptime monitoring or website edits. Those are part of our separate £39/month care plan, which already includes backups — care-plan sites do not need this service.
• It does not cover email, or websites on platforms that do not give outside access to files and databases (for example Wix, Squarespace, Shopify).
• It does not guarantee that your host will stay up or that a restore will fix a problem caused by something other than lost or damaged files.

3. What we need from you

• Access to the site over SFTP or SSH, and to its database, kept valid for as long as the service runs. If access stops working we tell you; we cannot back up what we cannot reach.
• An email address that is read, so restore-test emails and any alerts about access reach a person.
• Confirmation that you are entitled to give us access to the site and to the personal data in it.

4. Price and payment

• £8 a month, collected by Direct Debit through GoCardless Ltd under the Direct Debit Guarantee. It appears on your statement as REDWAY STUDIO. The first collection is taken a few working days after you set up the mandate, then on the same date each month.
• No setup fee, no minimum term, no notice period.
• If, after you sign up, we find we cannot back up your site, we cancel the Direct Debit and refund anything already collected.
• We can change the price with 30 days' notice by email; you can cancel before the change takes effect.

5. Starting and stopping

• We email you within one working day of your Direct Debit being set up to arrange access. The first backup runs within 48 hours of us receiving working access.
• You can cancel at any time by email or by cancelling the Direct Debit with your bank. No further payments are taken; the month already paid runs to its end.
• Within 30 days of cancellation we remove your copies from our server and from cloud storage, unless you ask for a final export first. Earlier versions held in cloud storage expire automatically within a further 90 days.
• We may end the service with 30 days' notice, or immediately if we are unable to reach the site for 30 days despite asking, or if the service is used for unlawful content.

6. Responsibility

• We take reasonable care to keep the copies complete and restorable, and we test that monthly. If we fail to do so, our liability to you for any claim in a 12-month period is limited to the fees you paid us in that period.
• We are not liable for losses we could not reasonably foresee, for loss of profit or business, or for anything caused by your host, your other suppliers, or access details you did not keep working.
• Nothing here limits liability for death, personal injury, fraud, or anything the law does not allow us to limit.

7. General

• These terms are governed by the law of England and Wales and its courts.
• If we change these terms we give 30 days' notice by email; carrying on after that date accepts the change.

Part B — Data processing agreement

This part is the written contract required by Article 28 of the UK GDPR. It applies to the personal data inside the copies of your website.

8. Roles and subject matter

9. Our obligations as processor

• We process the data only to provide the service and on your documented instructions (this agreement and your requests for restores). If we believe an instruction breaks data protection law, we tell you.
• Only Armin Shirazi has access to the copies. He is bound to keep them confidential.
• Security: copies are encrypted with AES-256 before they leave our server, with a key held only by us; transferred over SSH/SFTP; stored on a server in a private premises with access limited to us; the cloud copy is written with credentials that cannot delete, and earlier versions are kept for 90 days. We test a restore every month.
• Sub-processor: Backblaze, Inc. (a US company) stores the encrypted cloud copy in its B2 EU Central data region in Amsterdam, Netherlands. No one else. The copy is encrypted with a key Backblaze does not hold. We tell you by email at least 14 days before adding or replacing a sub-processor; you may object, in which case you may cancel without charge.
• The copies themselves stay in the United Kingdom (our server) and the Netherlands (Backblaze EU Central).
• We help you respond to requests from individuals about their data, and with your security and impact-assessment duties, so far as the copies are concerned.
• If we become aware of a personal data breach affecting the copies, we tell you without undue delay and in any case within 48 hours, with what we know and what we are doing.
• At the end of the service we delete the copies as set out in clause 5, or return them to you first if you ask.
• We give you the information you reasonably need to show that this agreement is being met, and allow an audit on reasonable notice, at your cost, no more than once a year unless a breach has occurred.

10. Your obligations as controller

• You are responsible for having a lawful basis to hold the personal data in your website and for the instructions you give us.
• You tell us if your website holds special-category data (health, biometrics and the like) or data about children, so we can agree whether extra measures are needed before the first backup.