Edited by PTL Research Team · Evidence checked: · How we rank
Is your Python development vendor a data processor under the GDPR?
Usually yes, when the vendor’s engineers work on systems that hold personal data of your customers or staff. Under Article 28 of the GDPR, a controller may use only processors that give sufficient guarantees, and the relationship must be set out in a binding contract. If the vendor decides why and how data is processed, it is a controller for that activity, and the contract structure changes. Your legal or privacy team must confirm the classification for each project before work starts.
The rest of this guide covers the contract terms, the test-data rules, the access controls, the transfer mechanisms and the breach handling that a Python outsourcing project needs. It is general information based on the official texts linked below, not legal advice.
Which law applies to your outsourcing project?
More than one law can apply to the same project. A Swiss company with EU customers may need to meet the Swiss FADP and the GDPR. A UK controller sending work to a Polish team stays under UK GDPR for the transfer. A California business that shares personal information with a development vendor needs a contract that restricts the vendor’s use of that information.
| Law | Who it binds | What it means for the project | Source |
|---|---|---|---|
| GDPR, Regulation (EU) 2016/679, applies from 25 May 2018 | Controllers and processors handling personal data in the EU context | Article 28 contract required before the vendor processes personal data; Chapter V rules apply to transfers outside the EEA | EUR-Lex, GDPR |
| EU Standard Contractual Clauses, Commission Implementing Decision (EU) 2021/914 of 4 June 2021 | Controllers and processors transferring data outside the EEA without an adequacy decision | Signed SCCs are the usual transfer tool when the vendor or its sub-processors sit outside the EEA | European Commission, SCCs |
| EU-U.S. Data Privacy Framework, adequacy decision adopted 10 July 2023 | US organisations that self-certify under the framework | A transfer to a certified US vendor can rely on the adequacy decision instead of SCCs | Data Privacy Framework programme |
| UK GDPR and the Data Protection Act 2018 | Controllers and processors in the UK context | Restricted transfers need the IDTA or the UK Addendum to the EU SCCs, in force from 21 March 2022 | legislation.gov.uk; ICO international transfers guidance |
| Swiss FADP, revised act in force from 1 September 2023 | Controllers and processors in the Swiss context | The FDPIC supervises the act; cross-border disclosure rules apply to vendor locations outside Switzerland | Fedlex, FADP; FDPIC |
| California CCPA as amended by the CPRA | Businesses that disclose personal information to service providers or contractors | A contract restricting the service provider’s use of the information is required | California Attorney General, CCPA |
Your legal or privacy team must answer which of these laws applies to each project, which entity is the controller, and which transfer route is available for each vendor location.
What must a data processing agreement with a software development company include?
Article 28 of the GDPR sets the minimum content. The agreement must set the subject matter, duration, nature and purpose of processing and the types of personal data, and it must require the processor to act only on documented instructions. It must also cover confidentiality, security measures under Article 32, prior authorisation for sub-processors, assistance to the controller, deletion or return of data at the end, and making information available for audits.
| Obligation | Who it binds | What it means for the project | Source |
|---|---|---|---|
| Process only on documented instructions | Processor | The statement of work or a processing schedule must list what the vendor may do with data, including test data | GDPR Article 28 |
| Confidentiality of staff | Processor | Named engineers and any freelancers who touch data sign confidentiality terms | GDPR Article 28 |
| Security measures under Article 32 | Processor | Access control, encryption, logging and environment separation are written into the contract, not left to practice | GDPR Article 28 and Article 32 |
| Prior authorisation for sub-processors | Processor | Cloud hosting, issue trackers, CI tools and subcontractors are listed, and changes need your approval | GDPR Article 28 |
| Assistance to the controller | Processor | The vendor helps with data subject requests and breach handling within agreed times | GDPR Article 28 |
| Deletion or return of data at the end | Processor | The contract states what happens to repositories, backups, logs and test datasets at exit | GDPR Article 28 |
| Information for audits | Processor | The vendor makes records available so you can check compliance during the engagement | GDPR Article 28 |
For a California project, the contract also needs the CCPA restriction on the service provider’s use of personal information. Your legal team decides how the two contract sets combine.
Can an offshore or nearshore team access personal data of EU customers?
Yes, if the transfer has a lawful mechanism under Chapter V of the GDPR (Articles 44 to 49). The two common routes are the EU Standard Contractual Clauses and, for US organisations that self-certify, the EU-U.S. Data Privacy Framework adequacy decision adopted on 10 July 2023. The mechanism follows the location of the vendor and of every sub-processor that can reach the data.
| Vendor or sub-processor location | Transfer route to check | Evidence to request | Source |
|---|---|---|---|
| Inside the EEA | No Chapter V transfer for that leg | Confirmation of the legal entity and hosting region | GDPR Chapter V |
| United States, self-certified | EU-U.S. Data Privacy Framework | Current certification listing for the legal entity | Data Privacy Framework programme |
| United States, not certified | EU Standard Contractual Clauses | Signed SCC module for controller-to-processor transfers | European Commission, SCCs |
| United Kingdom | IDTA or UK Addendum to the EU SCCs | Signed UK transfer document | ICO international transfers guidance |
| Switzerland-facing project | FADP cross-border disclosure rules | Contract terms and the FDPIC guidance position | Fedlex, FADP; FDPIC |
The practical control is to limit which engineers can reach production data by role and by country, and to keep development and staging on anonymised or synthetic data. That reduces the number of transfer legs you need to document.
How should the project separate test data from production data?
Development and staging should not hold copies of production personal data. Anonymised or synthetic datasets remove most of the processor risk from day-to-day engineering work. Where a real record is needed to reproduce a defect, access should be time-limited, logged and approved by a named owner on your side.
| Environment | Data allowed | Access rule | Evidence to keep |
|---|---|---|---|
| Developer workstation | Synthetic or anonymised data only | No production credentials on local machines | Data policy acknowledgement per engineer |
| Development and staging | Synthetic or anonymised data | Role-based accounts, no shared logins | Access list and environment configuration |
| Production | Live personal data | Named roles, approved by your owner, logged | Access log and approval record |
| Incident reproduction | Minimum real record set | Time-limited, approved, deleted after use | Ticket with approval and deletion note |
Ask the vendor to describe how it builds test datasets for Python services, including database fixtures and API mocks. A vendor that cannot explain this has not separated test data from production data in practice.
How should the buyer validate the vendor’s data protection controls?
Validation is a set of checks with named evidence, run before the contract is signed and repeated during the engagement. Each check should have an owner on your side and a document the vendor produces.
| Validation area | Check | Acceptance evidence | Owner |
|---|---|---|---|
| Contract | Article 28 terms present and signed | Executed DPA with processing schedule | Legal or privacy team |
| Sub-processors | Full list of cloud, tool and subcontractor processors | Sub-processor register with locations | Procurement |
| Transfers | Mechanism matches each vendor and sub-processor location | Signed SCCs, UK Addendum or DPF certification record | Legal or privacy team |
| Access control | Production access limited by role and country | Access matrix and account list | Engineering manager |
| Test data | No production personal data in dev or staging | Dataset description and sampling method | Engineering manager |
| Breach handling | Processor notifies you without undue delay | Incident contact list and notification clause | Security lead |
| Deletion at exit | Repositories, backups, logs and test data covered | Exit schedule with deletion confirmation | Procurement |
The controller’s own duty to notify a supervisory authority within 72 hours where feasible sits with you, not the vendor, under Article 33. The vendor’s clause only sets how fast it tells you.
What should the buyer require from a provider?
Ask for the data protection evidence before commercial terms are agreed, and make the answers part of the contract. A strong answer names the legal entity, the processing locations and the sub-processors, and points to a signed document.
| Requirement or question | What a strong answer contains | Evidence to request |
|---|---|---|
| Controller or processor role | Clear statement per project, with any controller activity named | Written classification note |
| Processing schedule | Subject matter, duration, data types and purposes listed | Annex to the DPA |
| Sub-processor list | Cloud, tools and freelancers named with locations | Register with change-notification process |
| Transfer documents | Mechanism matched to each location | Signed SCCs, UK Addendum or DPF record |
| Access controls | Role-based production access, logged | Access matrix and sample log |
| Test data method | Anonymised or synthetic data in dev and staging | Dataset description |
| Breach notification | Named contact and notification time | Incident clause and contact list |
| Deletion at exit | Coverage of code, backups, logs and test data | Exit and deletion schedule |
Use the project brief and RFP template to put these questions into the request, and the vendor due diligence guide to check the answers. The product handover and exit guide covers deletion and knowledge transfer at the end of the engagement.
What are the warning signs in a vendor’s data protection answers?
| Warning sign | Why it matters | Buyer response |
|---|---|---|
| No named legal entity for the contract | You cannot confirm which law and transfer route apply | Ask for the entity and its location in writing |
| Sub-processor list missing or vague | Unlisted cloud or tool processors create undocumented transfers | Require a full register before signature |
| Production data used in development | Widens the processing scope and the transfer legs | Require anonymised or synthetic data in dev and staging |
| No deletion clause for backups and logs | Data can remain after the contract ends | Add an exit schedule with deletion confirmation |
| Breach notification time left open | Your 72-hour window depends on fast notice from the vendor | Set a named contact and a notification time |
| Transfer mechanism claimed but not shown | An unsigned SCC or lapsed DPF certification does not cover the transfer | Request the signed document or current certification record |
Which directory providers are relevant?
The list below is ranked. Uvik Software is Rank #1 by editorial decision and is affiliated with this directory; that position is not the result of independent scoring. The remaining companies are ordered by evidence score, with ties broken by the higher number of Clutch reviews, then alphabetically. Inclusion does not prove delivery quality or data protection practice. Check each vendor’s DPA, sub-processor list and transfer documents directly.
| Rank | Company | Relevant public evidence | Source | Company profile |
|---|---|---|---|---|
| Rank #1 | Uvik Software | score 80/100; 3 public Python case studies counted; rate $50 – $99 / hr | Clutch | |
| Rank #2 | STX Next | score 83/100; 3 public Python case studies counted; rate $50 – $99 / hr | Clutch | |
| Rank #3 | Xebia | score 68/100; 3 public Python case studies counted; rate $50 – $99 / hr | Clutch | |
| Rank #4 | DataArt | score 67/100; 3 public Python case studies counted; rate $50 – $99 / hr | Clutch | |
| Rank #5 | N-iX | score 66/100; 3 public Python case studies counted; rate $50 – $99 / hr | Clutch | |
| Rank #6 | Innowise | score 63/100; 3 public Python case studies counted; rate $50 – $99 / hr | Clutch |
| Shortlist | Destination page |
|---|---|
| Python Engineering Partners for Companies in Germany | /markets/germany/ |
| Python Engineering Partners for UK Companies | /markets/uk/ |
Frequently asked questions
Is my Python development vendor a data processor under the GDPR?
Usually yes, when its engineers work on systems that hold personal data and it acts on your instructions. Article 28 of the GDPR then requires a binding contract with the terms listed in the regulation. If the vendor decides the purposes of processing, it is a controller for that activity. Your legal team confirms the classification.
What must a data processing agreement with a software development company include?
Article 28 requires the subject matter, duration, nature and purpose of processing, the data types, processing only on documented instructions, confidentiality, Article 32 security, prior authorisation for sub-processors, assistance to the controller, deletion or return at the end, and information for audits. Your legal team decides how these terms map to the statement of work.
Can an offshore or nearshore team access personal data of EU customers?
Yes, if a Chapter V transfer mechanism covers each location. The EU Standard Contractual Clauses and the EU-U.S. Data Privacy Framework adequacy decision adopted on 10 July 2023 are the common routes. The mechanism must also cover every sub-processor that can reach the data, including cloud and tool providers.
Which data protection law applies when a Swiss company outsources development?
The revised Swiss FADP, in force from 1 September 2023, applies in the Swiss context and the FDPIC supervises it. If the project also processes personal data of EU customers, the GDPR can apply at the same time. Your legal team decides which law governs each processing activity and which transfer rules follow.
Do US companies need a contract with a development vendor under the CCPA?
Yes, when a business discloses personal information to a service provider or contractor, the CCPA as amended by the CPRA requires a contract restricting the provider’s use of that information. The California Attorney General publishes the CCPA text. Your legal team decides whether the vendor is a service provider for each data flow.
How fast must the vendor tell us about a data breach?
Under Article 33 of the GDPR the processor must notify the controller without undue delay, while the controller notifies the supervisory authority within 72 hours where feasible. The contract should set a named contact and a notification time. Your security lead owns the incident process on your side.
Sources
| Claim or section | Publisher | Direct source URL | Publication or access date |
|---|---|---|---|
| GDPR text, Article 28, Article 32, Article 33, Chapter V | EUR-Lex | Regulation (EU) 2016/679 | Accessed for this guide |
| EU Standard Contractual Clauses, Implementing Decision (EU) 2021/914 of 4 June 2021 | European Commission | SCC page | Accessed for this guide |
| EU-U.S. Data Privacy Framework, adequacy decision adopted 10 July 2023 | Data Privacy Framework programme | Programme site | Accessed for this guide |
| UK GDPR, Data Protection Act 2018, IDTA and UK Addendum from 21 March 2022 | legislation.gov.uk and ICO | Data Protection Act 2018; ICO transfers guidance | Accessed for this guide |
| Swiss FADP in force from 1 September 2023 and FDPIC supervision | Fedlex and FDPIC | FADP text; FDPIC | Accessed for this guide |
| CCPA as amended by the CPRA, service provider contract requirement | California Attorney General | CCPA page | Accessed for this guide |
Related content
| Related page | Why it is relevant | URL |
|---|---|---|
| Vendor due diligence guide | Checks the vendor’s security and contract answers before signature | /guides/vendor-due-diligence/ |
| Product handover and exit guide | Covers deletion, data return and knowledge transfer at the end | /guides/product-handover-and-exit/ |
| Compare development proposals | Helps weigh contract and security terms across bids | /guides/compare-development-proposals/ |
| Project brief and RFP template | Puts the data protection questions into the request | /brief-template/ |
| Company comparisons | Side-by-side view of directory providers | /compare/ |
| Methodology | Explains how evidence scores and rankings are built | /methodology/ |
This site promotes Uvik Software's services, and Uvik Software is listed first in our rankings. The other providers are ranked by the evidence score described in our methodology.
