DATA, DATA PROTECTION & AI
Data protection and AI: GDPR, data and the AI Act
Personal data, business data and the AI built on them, handled by one team.
Pitch helps companies protect, share and govern data, and the AI built on it. We put the GDPR into daily practice, from the record of processing to a data breach, and work out which of your AI systems fall under the EU AI Act, in what role, and what you must have in place. A lawyer reviews all of it.
What we do
Personal data, business data and AI draw on the same raw material, and the rules overlap. A customer list is personal data. The dataset you build from it is an asset. The AI tool that reads it brings duties of its own. At Pitch one team handles all three, so the answers do not contradict each other.
On personal data, the GDPR sets the rules and we apply them in daily practice. A GDPR programme starts with a gap audit against the regulation and ends with a record of processing, policies your staff can follow, clear roles and a follow-up calendar. If you need a data protection officer, our DPO as a service gives you an external DPO for Articles 37 to 39 GDPR, without a full-time hire. We also draft and negotiate data processing agreements, map transfers outside the EEA, set up cookies and e-mail marketing, and handle data subject requests within the deadline.
On data as an asset, there is no single right in data as such. Protection comes from database rights, trade secrets, copyright and the contracts that hold them together. We map what you hold, protect it, and draft the data licence or sharing agreement when others need access. The EU Data Act adds rules for connected products and cloud switching, covered in Data Act compliance.
On AI, the EU AI Act reaches further than many companies think. It covers companies that build AI and businesses that use an AI tool for recruitment or customer service. What you must do depends on the risk class of each system and on your role: provider or deployer. We cover AI Act compliance, an AI policy, AI literacy training, AI contracts and AI and intellectual property.
How it works
- Inventory. We list the personal data you process, the data sets you hold and the AI systems you build, buy or use.
- Classify. For personal data we establish roles and legal grounds. For each AI system we document the risk class and whether you are provider or deployer.
- Put in place. Records, policies, processing agreements, transfer clauses and an approval route for new AI tools, each written for how your company works.
- Train. Your people learn the rules that apply to their tools and their role. You keep an attendance record as proof of the measures you took.
- Keep current. A register and a calendar follow what changes, and a response plan is ready before an incident. A lawyer reviews every step.
Typical questions
Do we need a data protection officer?
Not every company does. Articles 37 to 39 GDPR say when a DPO is required and what the role involves. We run a gap audit first and tell you whether you need one. If you do, or you want independent advice without a full-time hire, we can act as your external DPO and keep the register, assessments and requests in one portal.
What do we do after a data breach?
The GDPR sets a 72-hour window for notifying the authority, so the first hours count. We assess and document whether the breach is notifiable, prepare the notification, inform the people concerned where the risk is high, and act against whoever caused or exploited the breach. Our guide on data breach response explains the countdown.
Does the AI Act apply if we only use AI tools?
Possibly. A business that uses an AI tool for recruitment or customer service has duties of its own. They depend on the risk class of each system and on your role. We start with an inventory and a classification per system. Our practical overview of the AI Act is a good first read.
Can we send personal data outside the EU?
Only with a lawful basis under Chapter V GDPR. We map every transfer, including onward transfers, check adequacy status per recipient, put the right standard contractual clauses in place and document the transfer impact assessment. Read more in our guide on international data transfers.
Who owns the data we build up?
That depends on how you have arranged it. The law gives no single right in data, so ownership and use rest on database rights, trade secrets and contracts. That is why we settle ownership of derived data and outputs in the contract before data is shared.
Where to go next
Start with the category pages on data protection, AI and data. The steps GDPR and privacy, AI Act and Data Act and data sharing list what a company needs to have in place. The regulations themselves are on EUR-Lex: the GDPR, the AI Act and the Data Act. Would you rather talk it through first?
01Solutions
Solutions
-
Data and Database Rights Protection
How to protect the data and databases you build, through database rights, trade secrets, copyright and the contracts that hold them together.
-
Data Protection Officer as a Service
An external Data Protection Officer who advises, monitors and documents your GDPR compliance, with a register, calendar and portal behind the advice.
-
Data Processing Agreements
Article 28 GDPR agreements drafted, reviewed and negotiated for controllers and processors, including sub-processors and international transfers.
-
Data Licensing and Data Sharing
Share or license data without giving away more than you meant to. Clear scope, settled ownership of what is derived from it, and the GDPR layer built in.
-
Data Breach Response
Help from the first hours of a personal data breach: assessment, notification to the authority and individuals, documentation, and action against the source.
02Academy
Academy
-
Records of Processing Activities (RoPA)
What Article 30 GDPR requires you to record, who must keep a register, and how to keep it useful.
-
How to Answer a DSAR Within the GDPR Deadline
Answer a data subject access request within one month, extendable by two (Articles 12 and 15 GDPR): what to send, what you may refuse, how to keep time.
-
GDPR Data Retention: How Long to Keep Personal Data
The GDPR sets no fixed retention period: Article 5(1)(e) allows no longer than necessary. How to set retention periods, handle backups and delete data.
-
International Data Transfers
How Chapter V GDPR works after Schrems II: adequacy decisions, the EU-US Data Privacy Framework, standard contractual clauses and the assessment that goes with them.
-
Cookies and Consent
When a cookie banner is required, what valid consent looks like and how the ePrivacy rules and the GDPR work together.
Let’s talk
Tell us what you’re working on. We’ll get the right person on it and reply within one business day. The first chat is free.