Data Processing Agreement
Version: 1.0
Effective: 13 November 2026
This Data Processing Agreement (“DPA“) forms part of the agreement between Blaze Online Pty Ltd, ABN 43 159 286 987, trading as Blaze Commerce (“we“, “us“, “our“) and the client receiving our Services (“you“, “your“), under section 13.2 of our Terms and Conditions at blazecommerce.io/tc (the “Terms“).
It applies automatically where we process personal data on your behalf and that processing is subject to Data Protection Laws. You do not need to sign it. If you need a signed copy, email hello@blazecommerce.io.
If you and we have signed a separate data processing agreement, that signed agreement applies instead of this DPA.
1. Definitions
1.1 “Personal Data“, “Processing“, “Controller“, “Processor“, “Data Subject“, “Personal Data Breach” and “Supervisory Authority” have the meanings given in the UK GDPR and the EU GDPR.
1.2 “Data Protection Laws” means the laws that apply to the Processing of Personal Data under our Agreement, including (where applicable) the UK GDPR and Data Protection Act 2018, the EU GDPR, the Australian Privacy Act 1988, and United States state privacy laws, each as amended or replaced from time to time.
1.3 “Sub-processor” means a third party we engage to Process Personal Data on your behalf.
1.4 “SCCs” means the European Commission’s Standard Contractual Clauses (2021/914), Module Two (controller to processor).
1.5 “UK Addendum” means the UK Information Commissioner’s International Data Transfer Addendum to the SCCs (version B1.0).
1.6 Other capitalised terms have the meanings given in the Terms.
2. Roles and Scope
2.1 You are the Controller of the Personal Data described in Annex I. We Process that Personal Data as your Processor, only on your behalf and only for the purposes described in Annex I.
2.2 This DPA covers Processing under any Service we provide to you, for as long as we Process Personal Data on your behalf. This includes any warranty or ongoing support period.
2.3 This DPA does not cover:
- (a) the Processing carried out by providers you engage directly, such as your own hosting, payment, email, marketing and tracking providers. This applies even where we access or manage those services for you under your own contracts. Our own Processing on those systems remains within this DPA.
- (b) business records we hold about you and your personnel as an independent Controller, such as contact details, correspondence and billing records. Those are governed by our Privacy Policy.
- (c) Storemation. Storemation does not involve us Processing your customers’ Personal Data.
2.4 You are responsible for having a lawful basis for the Personal Data you ask us to Process, and for the notices and consents your customers are entitled to.
3. Processing on Instructions
3.1 We will Process Personal Data only on your documented instructions, unless the law requires otherwise. Your instructions are set out in our Agreement and this DPA, and in written requests you make to us for work on your Client Site.
3.2 If the law requires us to Process Personal Data in another way, we will tell you before doing so, unless the law prohibits this.
3.3 We will tell you without delay if we believe an instruction infringes Data Protection Laws.
3.4 We do not sell Personal Data. We do not use it for our own purposes or combine it with data from other sources, except as section 5.1.4 of the Terms allows for de-identified, aggregated information.
4. Confidentiality
4.1 Everyone we authorise to Process Personal Data is bound by confidentiality obligations and Processes Personal Data only as needed to perform the Services.
4.2 Confidentiality terms in our Agreement do not restrict a disclosure that Data Protection Laws require or that is made to a Supervisory Authority.
5. Security
5.1 We implement and maintain the technical and organisational measures described in Annex II.
5.2 We may update these measures from time to time. We will not materially reduce the overall level of protection.
6. Sub-processors
6.1 You give us general authorisation to engage the Sub-processors listed in Annex III.
6.2 Before we add or replace a Sub-processor, we will update Annex III and email clients who have an active Project or Ongoing Service with us, at least 30 days before the change takes effect. Where a change is needed urgently for security or continuity reasons, we will give notice as soon as practicable.
6.3 You may object within the notice period on reasonable, documented data protection grounds. We will work with you in good faith to resolve the objection. This may include not using the Sub-processor for your Personal Data.
6.4 If the objection is not resolved before the change takes effect, you may end the Services that use that Sub-processor by written notice. We will refund fees you have paid in advance for those Services that have not been performed. Services that do not use the Sub-processor are not affected.
6.5 We ensure each Sub-processor is bound by data protection obligations materially equivalent to those in this DPA, including through the Sub-processor’s own data processing terms. We remain liable to you for each Sub-processor’s performance.
7. Data Subject Rights and Assistance
7.1 Taking into account the nature of the Processing, we will assist you with appropriate technical and organisational measures in responding to Data Subject requests (access, rectification, erasure, restriction, portability, objection).
7.2 If a Data Subject contacts us directly, we will forward the request to you within 2 Business Days. We will not respond on your behalf unless you instruct us to.
7.3 We will give you reasonable assistance with your obligations concerning security, breach notification, data protection impact assessments and prior consultation with Supervisory Authorities. We will also give you the information you reasonably need for a transfer risk assessment.
7.4 Assistance under 7.1 and 7.3 that takes more than two hours in any month is chargeable at our then-current hourly rate. We will tell you before charging. This does not apply to assistance needed because of a Personal Data Breach caused by us.
8. Personal Data Breach
8.1 We will notify you without undue delay, and within 48 hours, after becoming aware of a Personal Data Breach affecting your Personal Data. We will send updates as facts emerge.
8.2 The notice and updates will describe, to the extent known:
- the nature of the breach
- the categories and approximate numbers of Data Subjects and records affected
- the likely consequences
- the measures taken or proposed to address the breach and reduce its effects
8.3 We will cooperate with you and take reasonable steps to help investigate, contain and fix the breach.
8.4 We will not notify a Supervisory Authority or Data Subjects of a Personal Data Breach except on your instruction or where the law requires it.
9. International Transfers
9.1 Our team and Sub-processors access and Process Personal Data from the countries listed in Annex III.
9.2 EU transfers. Where we Process Personal Data that is subject to the EU GDPR in a country that is not covered by an adequacy decision, the SCCs are incorporated into this DPA by reference. You are the data exporter and we are the data importer. For the SCCs:
- (a) Clause 7 (docking clause) does not apply
- (b) under Clause 9(a), Option 2 (general written authorisation) applies, with the notice period in section 6.2
- (c) under Clause 11(a), the optional language does not apply
- (d) under Clause 13, the competent Supervisory Authority is the one for the EU Member State where you are established. If you are not established in the EU, it is the one where your Article 27 representative is established. If you have no representative, it is the one for the Member State where most of the Data Subjects are located
- (e) under Clause 17, the SCCs are governed by the law of Ireland
- (f) under Clause 18, disputes arising from the SCCs are resolved by the courts of Ireland
- (g) Annexes I, II and III of this DPA complete the Annexes to the SCCs
9.3 UK transfers. Where the UK GDPR applies to the transfer, the UK Addendum is incorporated and applies to the SCCs. Tables 1 to 3 are completed by reference to this DPA and its Annexes. In Table 4, neither party may end the Addendum on a change to the Approved Addendum.
9.4 If a competent authority decides that a transfer mechanism in this section is no longer valid, we will work with you in good faith to put an alternative lawful mechanism in place.
10. Staging, Development and Copies of Your Data
10.1 Staging. Where our work needs a staging copy of your Client Site, including its database, we create it on managed hosting (in your hosting account where you have one, otherwise in ours) in the region closest to your production site where available. Staging is access-restricted, hidden from search engines, and has outgoing email and live payments switched off.
10.2 Local development. Our team’s local development environments use anonymised database copies. Before a copy is placed on a team device, customer names, email addresses, phone numbers, postal addresses, IP addresses and order notes are replaced with generated values.
10.3 Exceptions. If a task cannot be done on staging or on anonymised data, an unanonymised copy may be placed on a team device only with our Director’s approval, only on a device with full-disk encryption, and only for the time the task takes. It is deleted when the task is complete.
10.4 Retention of copies. A staging or development copy is kept only while it is needed for the work. Unless you have an Ongoing Service that uses it, it is deleted within 30 days of the end of the Project or its warranty period. You may require earlier deletion at any time by written request.
11. Deletion and Return
11.1 When the Services end, and earlier on your written instruction, we will delete or return (at your choice) the Personal Data we Process on your behalf, and delete existing copies, unless the law requires us to keep it.
11.2 Backups we hold are deleted on our standard purge cycle of 30 days.
11.3 On your written request, we will confirm in writing that deletion has been completed and which environments it covered.
12. Information and Audit
12.1 On request, we will give you the information reasonably necessary to show that we comply with this DPA.
12.2 You, or an auditor you appoint who is bound by confidentiality, may audit our compliance with this DPA. We are a fully remote team, so audits are carried out remotely, by written questions and review of records. An audit:
- needs at least 14 days written notice
- may take place no more than once in any 12-month period, except after a Personal Data Breach or where a Supervisory Authority requires it
- takes place during our business hours and must not unreasonably disrupt our work
12.3 Each party bears its own audit costs. Where an audit takes more than four hours of our time, the additional time is chargeable at our then-current hourly rate, unless the audit follows a Personal Data Breach caused by us or finds a material breach of this DPA.
13. Liability, Term and Governing Law
13.1 Each party’s liability under this DPA is subject to the limitations and exclusions of liability in the Terms, except to the extent liability cannot be limited under Data Protection Laws.
13.2 This DPA applies from the date our Agreement with you starts, or the effective date above if later, and continues for as long as we Process Personal Data on your behalf.
13.3 This DPA is governed by the same law as the Terms, except that:
- (a) nothing in this DPA excludes or limits either party’s obligations under Data Protection Laws
- (b) the governing law of the SCCs, and the courts that resolve disputes arising from them, are as set out in section 9.2
- (c) the UK Addendum is governed by its own terms
13.4 Changes. We may update this DPA from time to time, including Annexes II and III. Changes to Sub-processors follow section 6. For other material changes we will give notice as set out in section 3.5 of the Terms.
13.5 Where this DPA and the rest of our Agreement conflict on data protection, this DPA prevails.
Annex I: Description of Processing
A. Parties
- Data exporter (Controller): you, the client named in our Agreement.
- Data importer (Processor): Blaze Online Pty Ltd, trading as Blaze Commerce, Australia. Contact: hello@blazecommerce.io.
B. Subject matter and purpose
Processing needed to deliver the Services you have with us: design, development, migration, maintenance, updates, security work, performance work, monitoring, reporting, hosting management and support for your WooCommerce store and related systems.
C. Categories of Data Subjects
Your customers and prospective customers. Your personnel, where their data appears in your store or related systems.
D. Categories of Personal Data
- Identity and contact data: names, email addresses, phone numbers, billing and delivery addresses
- Online identifiers and IP addresses
- Order and transaction data: order history, amounts, currency and payment method identifiers. We do not Process full card numbers, which are held by your payment providers
- Subscription data, where your store sells subscriptions
- Account data: usernames, hashed passwords, order notes
- Marketing consent records
- Administrative activity logs
- Customer service and review content, where present in your store
- Other data your store collects from customers through its forms and product options
No special category data is intentionally Processed. Free-text fields may incidentally contain information supplied by your customers.
E. Nature of Processing
- Access to your production systems for diagnosis, configuration, updates, fixes, deployment and monitoring
- Staging copies of your Client Site, as described in section 10
- Anonymised database copies for local development
- Reading order, customer and analytics records to diagnose issues and prepare reports
- Hosting of your Client Site, where you are hosted on our hosting account
- Backups we create
F. Frequency of transfer
Continuous, for as long as we provide Services.
G. Duration and retention
For the duration of the Services, including any warranty period. Staging and development copies are deleted under section 10.4. Backups purge on a 30-day cycle. Other Personal Data is deleted or returned under section 11.
H. Competent Supervisory Authority
As set out in section 9.2(d).
Annex II: Technical and Organisational Security Measures
- Credential management. Client credentials and access secrets are stored in an end-to-end encrypted password manager, with access given per engagement. Credentials are not shared by email or chat.
- Authentication. Two-factor authentication is enforced on our password manager, our email and document accounts and our hosting account. We use two-factor authentication on WordPress administrator accounts where your Client Site supports it.
- Named accounts. Our team accesses your Client Site through named individual accounts where the system supports it. For other systems we use a shared client-access account that only the team working on your account can reach.
- Access review. We review who holds access to client systems at least once a year, and when a team member leaves or changes role.
- Offboarding. When a team member leaves, their password manager access is revoked immediately. This cuts off the credentials and two-factor tokens that depend on it.
- Least privilege. Access to Personal Data is limited to the people working on your account.
- Encryption. Data in transit is protected by TLS. Full-disk encryption is required on team devices.
- Data minimisation. Local development uses anonymised database copies (section 10.2). Unanonymised Personal Data is not kept on team devices, except under section 10.3. Payment card data is never present in the copies we take.
- Staging. Staging environments are access-restricted and hidden from search engines, with outgoing email and live payments switched off.
- AI tools. We use AI tools under commercial terms that do not permit training on submitted data, with per-user accounts. We keep the Personal Data submitted to AI tools to the minimum needed for the task.
- Secure channels. We ask clients to send Personal Data and credentials through encrypted share links or the password manager, not by email.
- Incident response. Any suspected security incident is escalated to our Director immediately on discovery.
- Backups. Backups of our internal systems are encrypted and kept for 30 days.
- Team obligations. Each team member is bound by a written agreement that includes confidentiality and data handling obligations consistent with this DPA.
Annex III: Sub-processors
Each Sub-processor Processes Personal Data under its own data processing terms. Not every Sub-processor is used for every client. Which ones apply depends on the Services you have.
| Sub-processor | Purpose | Location |
|---|---|---|
| Kinsta (on Google Cloud Platform) | Hosting of Client Sites and staging environments on our hosting account | The region chosen for your site |
| Individual contractors engaged by us | Development, design, QA and support under our direction | Australia, Philippines, Indonesia, Canada |
| Bitwarden Inc. | Encrypted storage and sharing of client system credentials. Zero-knowledge encryption: Bitwarden cannot read vault contents | United States |
| Anthropic | AI-assisted analysis and development tools | United States |
| Google Workspace | Email and document collaboration | Global (Google infrastructure) |
| ClickUp | Project and task management | United States |
| Slack | Team communication | United States |
| Zoom (including meeting notetaker) | Client meetings, recordings and transcription | United States |
| Hetzner Online | Hosting of our internal systems (automation and knowledge base) | Singapore |
| Wasabi Technologies | Encrypted backup storage for our internal systems | Australia (Sydney) |
| Ghost Inspector | Automated front-end testing. No administrator access and no customer records | United States |
| Cloudflare, Inc. | Bot verification on login and checkout forms, where we set it up under our account | Global (Cloudflare network) |
Providers you engage directly under your own contracts are not our Sub-processors, even where we access or manage them for you. Examples are your own hosting account, payment providers, email and marketing platforms, tracking tools, and plugins running on your Client Site. Plugin licensors are not Sub-processors, because licence activation and update checks carry no Personal Data.
This list was last updated on 13 November 2026.