The short version
- This applies when we handle personal data in your clients' projects. You and your client decide what happens to that data, and we act only on your instructions.
- We mostly work inside accounts you create and control, so the data stays in your systems and you can switch our access off at any time.
- If a security incident affects your client's data, we tell you within 24 hours of finding out. We never contact your client ourselves.
- We delete any local working copies within 30 days of handover, or of the end of a plan.
- It forms part of the Partner Agreement, and the Partner Agreement's limits on liability apply to it.
This summary helps you read the document. The full text below is what applies.
This Data Processing Addendum (“DPA”) forms part of the Partner Agreement between StudioPartner (“StudioPartner”, “we”, “us”), and the agency that signs an Order with us (the “Partner”, “you”). It applies whenever we process personal data on your behalf while providing the services. Signing an Order that refers to the Partner Agreement also signs this DPA.
Definitions
1.1 Words defined in the Partner Agreement have the same meaning here. In addition:
- “Client Personal Data” means personal data that we process on your behalf in providing the services, including personal data in the websites, stores, systems and files of your End Clients.
- “Data Protection Laws” means all laws on data protection and privacy that apply to the processing of Client Personal Data, which may include the UK GDPR and Data Protection Act 2018, the EU GDPR, the Swiss Federal Act on Data Protection, the California Consumer Privacy Act and other US state privacy laws, Canada’s PIPEDA, the Australian Privacy Act 1988, New Zealand’s Privacy Act 2020, the UAE’s Federal Decree-Law No. 45 of 2021 and India’s Digital Personal Data Protection Act, 2023.
- “End Client” means your client for whom the services are performed.
- “Partner Accounts” means the email, chat, project management, design, code, hosting, CMS, e-commerce, password manager and other accounts and systems that you or your End Client create, own or control and give our people access to.
- “Security Incident” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Client Personal Data, where it happens in systems we control or is caused by our people or our sub-processors. It does not include unsuccessful attempts that don’t compromise Client Personal Data, such as blocked log-in attempts, pings or port scans.
- “SCCs” means the standard contractual clauses approved by the European Commission in Implementing Decision (EU) 2021/914.
- “UK Addendum” means the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018.
- “sub-processor” means a third party we engage to process Client Personal Data.
- “controller”, “processor”, “data subject”, “personal data”, “processing” and “supervisory authority” have the meanings given in the Data Protection Laws. Equivalent terms in other laws (such as “business”, “service provider”, “Data Fiduciary” and “Data Processor”) are read to match.
Scope and roles
2.1 This DPA applies only to Client Personal Data. Personal data we handle for our own business, such as the contact details of your staff and our invoices to you, is covered by our Privacy Policy.
2.2 For Client Personal Data:
- where your End Client decides why and how the data is processed, the End Client is the controller, you are its processor, and we are your sub-processor. This is the usual case.
- where you decide why and how the data is processed, you are the controller and we are your processor.
2.3 You tell us in the Order if your role differs from these. If you don’t, we rely on this section.
2.4 Annex A sets out the subject matter, duration, nature and purpose of the processing, and the types of personal data and data subjects. An Order may add details for a particular project.
Your instructions
3.1 We process Client Personal Data only on your documented instructions, unless the law requires us to do otherwise. In that case we tell you before we process it, unless the law forbids us to.
3.2 Your documented instructions are the Partner Agreement, this DPA, each Order, and any further written instructions given through the project channels agreed in the Order by someone authorised to give them. You are responsible for passing on any instructions from your End Client.
3.3 An instruction that goes beyond the scope of an Order is a change, handled under change control. We may charge for it as a change.
3.4 If we believe an instruction breaks the Data Protection Laws, we’ll tell you. We may decline to follow that instruction until you confirm it in writing or change it, and doing so is not a breach of the Partner Agreement. We don’t give legal advice, and we aren’t responsible for checking whether your instructions are lawful.
Working inside your accounts
4.1 We do most of our work inside Partner Accounts: on email accounts on your domain, in your chat and project tools, in your Figma, Git and hosting accounts, and in your End Client’s systems. Code and designs live there from day one. Details are in the Partner Agreement under working under your identity.
4.2 You, or your End Client, control Partner Accounts. That means you are responsible for:
- choosing, contracting with and configuring the providers of those accounts and systems (for example Shopify, your hosting company, Google Workspace, Slack or GitHub). They are your or your End Client’s providers, not our sub-processors.
- enforcing two-factor authentication, setting permissions and reviewing access
- monitoring the accounts you give us, which our people agree to
- removing our access when you want to, including at handover
4.3 We use Partner Accounts only to provide the services. We follow the reasonable written security policies you give us for them, and don’t set up forwarding from Partner Accounts to our own systems. If a policy adds work beyond the Order, it’s handled as a change.
4.4 We keep Client Personal Data outside Partner Accounts only when a task needs it, for example a local working copy of a site or a data export for a migration. Annex B explains how we protect and delete those copies.
Our people
5.1 Only our team members who need access to perform the services can access Client Personal Data.
5.2 Everyone who does is bound by a written duty of confidentiality, or a legal one, and is trained in the security measures in Annex B.
5.3 Our team members may be employees or individual contractors who work as part of our team, under our direction, and on terms at least as protective as this DPA. They are our personnel, not sub-processors. We are responsible for their acts and omissions under this DPA as we are for our own.
Security
6.1 We apply appropriate technical and organisational measures to protect Client Personal Data, taking into account the state of the art, the cost of implementation, the nature, scope, context and purposes of the processing, and the risks to data subjects. Our current measures are in Annex B.
6.2 You agree that Annex B gives an appropriate level of security for the Client Personal Data we process, given that most processing happens in Partner Accounts that you control.
6.3 We may update our security measures from time to time, as long as the overall level of protection doesn’t go down.
6.4 We don’t claim any security certification, such as ISO 27001 or SOC 2.
Sub-processors
7.1 You give us general authorisation to use sub-processors, including those listed below.
7.2 Current sub-processors that may process Client Personal Data:
| Sub-processor | What for | Location |
|---|---|---|
| Google LLC (Google Workspace) | Our business email, calendar and file storage, if any Client Personal Data reaches our own systems | United States and other countries where Google operates |
| Bitwarden, Inc. (password manager) | Storing credentials you share with us, when you don’t share them from your own vault | United States |
| Anthropic, PBC (Claude), under commercial terms that don’t allow training on what we put in | Code assistance and QA automation, as described in the Partner Agreement under use of AI | United States |
7.3 These are not our sub-processors: the providers of Partner Accounts; providers you or your End Client choose, pay for or ask us to use; Cal.com and Cloudflare, which we use only for our own website; and Freelancer.com, which holds project funds and doesn’t process Client Personal Data.
7.4 Before a sub-processor processes Client Personal Data, we put in place a written contract that requires it to protect the data as Article 28(3) of the GDPR requires. We remain responsible to you for its performance, as the Data Protection Laws require, subject to the Liability section.
7.5 We’ll give you at least 30 days’ notice by email before we add or replace a sub-processor. If a change is urgent to keep the services secure or running, we may give shorter notice and will tell you why.
7.6 You may object to a new sub-processor on reasonable data protection grounds by writing to us within 14 days of our notice. If you do, we’ll work with you in good faith to find a solution, such as not using that sub-processor for your projects. If we can’t agree within 30 days, either of us may end the affected Order or plan by written notice. We’ll then refund any fees you have paid for services not yet performed. That refund is your only remedy for the objection. If you don’t object within 14 days, you’re treated as accepting the change.
7.7 We never pass your projects to third-party freelancers or agencies without your written consent, as set out in the Partner Agreement under our people and subcontracting.
Helping you meet your obligations
8.1 Requests from data subjects. If a data subject contacts us directly about Client Personal Data, we’ll forward the request to you within 1 business day and won’t respond to it ourselves, unless the law requires us to. Taking into account the nature of the processing, we’ll give you reasonable help to respond to requests to exercise data subjects’ rights, mostly by acting on your instructions inside Partner Accounts.
8.2 Assessments and regulators. We’ll give you reasonable help with data protection impact assessments and prior consultations with supervisory authorities, where they relate to our processing and you don’t already have the information.
8.3 Cost. Help that takes us up to 1 hour in a calendar month is included. Beyond that, we charge at the hourly rate in the Order or, if there isn’t one, our standard hourly rate at the time. We’ll tell you in advance if help will cost more than that.
8.4 Requests from authorities. If a regulator, court or law enforcement body asks us for Client Personal Data, we’ll tell you first where the law allows, redirect the request to you where possible, and disclose only what the law requires.
Security incidents
9.1 If we become aware of a Security Incident, we’ll notify you without undue delay, and in any case within 24 hours of becoming aware of it.
9.2 We’ll tell you what we know at that point and send more as we learn it, including, as far as we can:
- what happened, and when
- the types and approximate number of data subjects and records affected
- the likely consequences
- what we have done, and propose to do, to contain it and reduce harm
- a contact person on our team
9.3 We’ll take reasonable steps to contain and investigate the Security Incident, and give you the information and help you reasonably need to meet your own obligations and your End Client’s, including notifying regulators and data subjects.
9.4 We notify you, never your End Client. You decide, with your End Client, who else is told and how. We won’t notify your End Client, data subjects, regulators or the public about a Security Incident unless you ask us to in writing or the law requires us to. If the law requires it, we’ll tell you first where the law allows.
9.5 If we become aware of a security incident in Partner Accounts or your End Client’s systems that we didn’t cause, we’ll tell you within the same 24 hours so you can act. That notice is for your information, and it doesn’t make that incident a Security Incident under this DPA.
9.6 Our notice of a Security Incident is not an admission of fault or liability.
Deletion and return
10.1 Because the work and the data live in Partner Accounts, there is normally nothing to return. You keep everything when our access ends.
10.2 We delete any Client Personal Data we hold outside Partner Accounts, including local working copies, downloads and exports, within 30 days of handover. If you’re on a Plan, we delete it within 30 days of the Plan ending. You can ask us to delete it earlier, or to return a copy first, at any time.
10.3 We don’t use our own email or file storage to exchange Client Personal Data. If any reaches it, we delete it within the same 30 days.
10.4 On request, we’ll confirm deletion in writing.
10.5 We may keep Client Personal Data where the law requires it. If we do, we’ll keep protecting it under this DPA and use it only for that legal purpose.
Audits and information
11.1 We’ll make available the information you reasonably need to show that we comply with this DPA and Article 28 of the GDPR. Normally that means this DPA and Annex B, our written answers to your reasonable security questionnaire (at most once a year), and written confirmation of specific points.
11.2 If that information isn’t enough to show compliance, or a supervisory authority requires it, you may audit our processing of Client Personal Data, on these conditions:
- at most once in any 12 months, unless a supervisory authority requires it or a Security Incident we caused makes it necessary
- with at least 30 days’ written notice, and a proposed scope we agree in advance
- during our normal business hours, remotely where possible, and without unreasonably disrupting our work
- carried out by you or by an independent auditor who is not our competitor, and who has signed confidentiality terms we reasonably approve
- limited to our processing of your Client Personal Data. It never includes other partners’ data or information.
- at your cost, including our time at the rate set out in clause 8.3
11.3 Everything you learn in an audit is our confidential information under the Partner Agreement’s confidentiality terms.
11.4 Where the SCCs apply, you agree to use your audit rights under them in the way this section describes, as far as the SCCs allow.
International transfers
12.1 We may process Client Personal Data in the countries where our team members and sub-processors are located. Remote access to Partner Accounts from another country counts as processing in that country. We’ll tell you in writing, before you sign an Order, where the team members working on it are located.
12.2 From the EEA. Where processing involves a transfer of Client Personal Data from the European Economic Area to a country without an adequacy decision, the SCCs are incorporated into this DPA as follows:
- Module 2 (controller to processor) where you are the controller
- Module 3 (processor to processor) where you are a processor for your End Client
In each case you are the data exporter and we are the data importer. The options chosen and the information needed to complete the SCCs are in Annex C.
12.3 From the UK. Where processing involves a transfer from the United Kingdom, the SCCs apply as amended by the UK Addendum, completed as set out in Annex C.
12.4 From Switzerland. Where processing involves a transfer from Switzerland, the SCCs apply with the changes the Swiss Federal Act on Data Protection requires, set out in Annex C.
12.5 From other countries. Where other Data Protection Laws restrict transfers, we’ll comply with this DPA and with any transfer terms those laws require that we agree in an Order, so that Client Personal Data keeps the protection those laws require.
12.6 Onward transfers. Where a sub-processor processes Client Personal Data in another country, we’ll put in place a valid transfer mechanism with it, such as the SCCs or the EU-US Data Privacy Framework where the sub-processor is certified.
12.7 Transfer assessments. We’ll give you the information you reasonably need to assess the laws of the countries where we process Client Personal Data. We’ll tell you promptly if we can no longer comply with the SCCs, in which case you may suspend the transfer and end the affected Order.
12.8 If the SCCs or the UK Addendum require us to notify a data subject or controller directly, we’ll do so only as far as they require, and we’ll tell you first where the law allows.
Your responsibilities
13.1 You confirm, and will make sure throughout the relationship, that:
- you have the right to appoint us as your processor or sub-processor. Where your End Client is the controller, your contract with it allows you to subcontract and to use sub-processors, and contains processor terms consistent with this DPA.
- the Client Personal Data, and your instructions for processing it, comply with the Data Protection Laws. That includes having a lawful basis, giving any required notices and getting any required consents.
- you will tell us in the Order before we start if a project involves special category data, criminal records data, children’s data, health information, payment card data or any other data that needs extra protection under the Data Protection Laws. We may decline such a project or ask for extra terms.
- you will use test or anonymised data instead of real personal data wherever that’s practical.
- you will keep the Partner Accounts you give us secure, and remove access we no longer need.
13.2 We don’t handle full payment card numbers, and we build payments through the payment provider’s own secure checkout. We don’t act as a business associate under the US Health Insurance Portability and Accountability Act (HIPAA) unless we sign a separate business associate agreement. We don’t sign business associate agreements, so please don’t send us protected health information.
13.3 You are responsible for your End Client relationship, including all communication with your End Client about data protection. Your End Client has no rights against us under this DPA, except where the SCCs or the Data Protection Laws give it rights that can’t be excluded.
13.4 The Partner Agreement’s indemnities apply to claims arising from your instructions and from your breach of this section.
Region-specific terms
14.1 California and other US states. Where we process Client Personal Data that is “personal information” under the California Consumer Privacy Act, or similar data under another US state privacy law, we act as a “service provider” or “processor”. We will not:
- sell or share it, as those words are defined in those laws
- keep, use or disclose it for any purpose other than performing the services, or outside our direct business relationship with you, except as those laws allow
- combine it with personal information we receive from anyone else or collect ourselves, except as those laws allow
We’ll comply with the obligations those laws place on us, give the same level of privacy protection they require, and tell you if we can no longer meet them. You may take reasonable and appropriate steps to stop and remediate unauthorised use. We certify that we understand and will comply with these restrictions.
14.2 Australia. Where the Australian Privacy Act 1988 applies, we’ll handle Client Personal Data in line with the Australian Privacy Principles as if we were bound by them, and only for the purposes of the services.
14.3 Canada. Where PIPEDA or a Canadian provincial privacy law applies, we’ll use Client Personal Data only for the purposes you instruct, protect it with the safeguards in this DPA, and help you meet your accountability obligations.
14.4 New Zealand. Where the New Zealand Privacy Act 2020 applies, we hold Client Personal Data as your agent under section 11 of that Act, only for the purposes of the services, and don’t use or disclose it for our own purposes.
14.5 United Arab Emirates. Where the UAE’s Federal Decree-Law No. 45 of 2021, or the data protection law of the DIFC or ADGM, applies, we act as processor on your instructions and comply with the processor obligations under that law.
14.6 India. Where India’s Digital Personal Data Protection Act, 2023 applies, we act as a Data Processor under a valid contract with you, and process Client Personal Data only on your instructions and for the purposes of the services.
Liability
15.1 Each party’s liability arising out of or in connection with this DPA, whether in contract, tort (including negligence) or otherwise, is subject to the exclusions and limitations of liability in the Partner Agreement under liability.
15.2 This DPA and the Partner Agreement share one overall cap. This DPA does not create a separate or additional cap.
15.3 We are not liable for any loss to the extent it is caused by:
- our following your instructions or your End Client’s
- Partner Accounts, or the systems, providers or security of you or your End Client
- your breach of this DPA or the Data Protection Laws
15.4 Nothing in this DPA limits either party’s liability to data subjects under the SCCs, or any liability that can’t be limited by law.
Term and precedence
16.1 This DPA starts when the Partner Agreement starts, and lasts for as long as we process Client Personal Data. Clauses 10, 11, 15 and 16 survive its end.
16.2 If there’s a conflict on a data protection matter, the documents apply in this order: first the SCCs (and the UK Addendum) where they apply, then this DPA, then the Order, then the rest of the Partner Agreement. On every other matter, including liability as described in the Liability section, the Partner Agreement applies.
16.3 We may update this DPA to reflect changes in the law, a regulator’s guidance or our sub-processors. We’ll give you at least 30 days’ notice of any change that reduces your protection. The SCCs and the UK Addendum as incorporated here can only change as their own terms allow.
16.4 This DPA is governed by the law, and subject to the dispute terms, of the Partner Agreement, except where the SCCs or the Data Protection Laws require otherwise.
Annex A: Details of processing
The parties
- Data exporter: the Partner, as named in the Order. Role: controller, or processor for its End Client. Contact: as given in the Order.
- Data importer: StudioPartner, India. Role: processor, or sub-processor. Contact for data protection: privacy@studiopartner.co.
- Activities: white label web design, development and related services, as set out in the Order.
- Signature and date: signing an Order signs this DPA and its Annexes, dated the same day.
Subject matter and purpose
Providing the services under the Partner Agreement and each Order: designing, building, migrating, testing, launching, maintaining and improving websites, online stores and related systems for the Partner’s End Clients.
Duration
The term of the Partner Agreement and each Order, plus the time needed to delete Client Personal Data under clause 10.
Nature of the processing
Accessing, viewing, organising, structuring, adapting, copying for development or migration, importing and exporting, testing, storing temporarily, and deleting Client Personal Data, mostly inside Partner Accounts.
Frequency
Continuous during a project or plan, as needed to perform the services.
Types of data subjects
- the End Client’s customers, and people who buy from, sign up to or use the End Client’s website or store
- visitors to the End Client’s website
- people who submit forms, subscribe to newsletters or leave reviews or comments
- the End Client’s staff, contractors and administrators
- the Partner’s staff
Types of personal data
- contact details, such as names, email addresses, phone numbers and postal addresses
- account details, such as usernames, customer IDs and account settings (never passwords in readable form)
- order and purchase history, delivery and billing addresses, and transaction records. We don’t see full payment card numbers.
- form submissions, messages, reviews and comments
- marketing preferences and consent records
- technical data, such as IP addresses, device information and data in site logs, analytics or tag configurations
- names and work contact details of staff and administrators
Special categories of data
None expected. If an Order says a project involves special category data, the Order sets out the extra safeguards that apply, such as stricter access limits and the use of test data.
Retention
As set out in clause 10.
Transfers to sub-processors
As listed in the Sub-processors section, for the purposes stated there and for the duration of the services.
Locations of processing
The locations of our team members, as we tell you before each Order, and the locations of the sub-processors listed above.
Annex B: Security measures
Access
- We work only through named accounts you create and control. No shared log-ins.
- Two-factor authentication on every account we use, yours and ours.
- Least privilege: we ask only for the access a task needs, and give it back when the task is done.
- Credentials shared only through a password manager, ideally your vault, never by email or chat.
- Access removed at handover unless you’re on a plan. On plans, we review access with you every quarter, and confirm any removal you ask for within 1 business day.
- At offboarding, we list any keys and tokens created during the project, such as deploy keys, API keys and app passwords, so you can rotate them.
Devices
- Encrypted disks, automatic screen lock, and up-to-date operating systems and security software.
- Client Personal Data is handled only on devices that meet the standards above. It isn’t copied to phones, removable drives or personal cloud storage.
Data handling
- We process Client Personal Data inside Partner Accounts wherever possible.
- Local working copies and data exports only when a task needs them, and only for as long as it needs them.
- Test or anonymised data used in place of real data wherever practical.
- Local copies deleted within 30 days of handover, or of the end of a plan (clause 10).
- No Client Personal Data or confidential information in AI tools that train on what we put in. We use business plans with training switched off.
- No forwarding from Partner Accounts to our own systems.
Building securely
- Themes, plugins, apps and libraries only from official sources. Never nulled or pirated code.
- Dependencies kept up to date during the project and on care plans.
- Security headers configured on the sites we build, where the hosting allows.
- WordPress hardening, such as disabling file editing in the admin, protecting log-in and turning off XML-RPC unless it’s needed.
- Shopify and other apps given the minimum permissions they need.
- A backup taken before every change to a live site.
- Staging sites protected from public access and search engines.
People
- Confidentiality agreements with every team member.
- Security onboarding for everyone who works on client projects.
- Reference checks before a team member works on client projects.
- Access removed on the day someone leaves our team.
Incidents
- A documented process for finding, containing and reporting security incidents, with notice to you within 24 hours (clause 9).
Annex C: Transfer details
EU Standard Contractual Clauses
- Modules: Module 2 where the Partner is a controller. Module 3 where the Partner is a processor.
- Clause 7 (docking clause): does not apply.
- Clause 9 (sub-processors): Option 2, general written authorisation, with notice of changes as set out in clause 7.5 of this DPA.
- Clause 11 (redress): the optional independent dispute resolution wording does not apply.
- Clause 13 (supervision): the competent supervisory authority is the one that Clause 13 identifies for the data exporter.
- Clause 17 (governing law): the law of Ireland.
- Clause 18 (courts): the courts of Ireland.
- Annex I: completed by Annex A of this DPA.
- Annex II: completed by Annex B of this DPA.
- Annex III: completed by the Sub-processors section of this DPA.
UK Addendum
- Table 1 (parties): as set out in Annex A.
- Table 2 (selected SCCs, modules and clauses): the SCCs as incorporated and completed above.
- Table 3 (appendix information): as set out in Annexes A and B and the Sub-processors section.
- Table 4 (ending the Addendum when the Approved Addendum changes): neither party.
Switzerland
For transfers subject to the Swiss Federal Act on Data Protection, the SCCs apply with these changes: references to the GDPR are read as references to the Swiss Act; the competent supervisory authority is the Federal Data Protection and Information Commissioner; and “Member State” includes Switzerland, so that data subjects in Switzerland can bring claims where they habitually live.
Questions about this document? Email legal@studiopartner.co. Our guarantees in plain English are in the Trust Center.