Key takeaways
- GDPR keeps a company accountable for personal data it sends to a processor. The CCPA requires a contract that holds each recipient to the same level of privacy protection.
- Neither law names a required product. GDPR asks for security "appropriate to the risk," and the CCPA asks for "reasonable security."
- A contract tells a recipient what to do with personal data. It does not affect who can open the file.
- Self-protecting data carries its access rules, its keys, and its event record inside the file.
Where compliance work stops
Most compliance work under the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA) happens inside the company. Teams map personal data, write policies, sign vendor agreements, and tighten access to their own systems. Then a file is sent to someone else, and that responsibility stays with the company.
Both laws address that handoff. Under GDPR, the controller is responsible for data protection principles and must be able to demonstrate compliance (Article 5(2)). It stays accountable when personal data goes to a processor, and it may use only processors that provide sufficient guarantees (Article 28). The CCPA extends its own obligations to the recipient through the contract. A business that discloses personal information to a service provider, contractor, or third party must have an agreement that holds the recipient to “the same level of privacy protection.”
So the obligation reaches past the network. The protection usually does not. Self-protecting data closes that distance by putting the access rules in the file.
Where the gap opens
A payroll export goes to an insurance broker. A customer list goes to a marketing agency. In each handoff, the company still has obligations for the data and gives up the technical control.
Data is passive. It cannot act on its own behalf. The contract says what the recipient may do, and the file has no say. Once it is downloaded, forwarded, or copied to a laptop, it is protected only by whatever systems happen to surround it.
Each law has one breach provision that turns on the condition of the data itself. GDPR lifts the duty to tell affected individuals when the data was “unintelligible to any person who is not authorized to access it, such as encryption” (Article 34(3)(a)). The CCPA limits the consumer right to sue, after a breach caused by a failure of reasonable security, to “nonencrypted and nonredacted personal information” plus certain account credentials. Neither provision removes a company’s other duties.
Protection that travels with the file
Sertainty embeds the access rules, the keys, and the event record in the file itself, so the file enforces its own protection. A file protected with Sertainty technology is protected before any transport begins. When it is emailed, uploaded, or moved to network storage, the protection stays in place even if other security fails.
- The rules. The data owner sets who may open the file and under what conditions, including location, time, network, and device. The file enforces those conditions itself.
- The keys. The file uses AES-256-GCM encryption with patented proprietary techniques and internal key management. The keys are generated and stored inside the file and are never shared externally.
- The record. The file records events in a tamper-resistant log, and those events can be sent to a security information and event management (SIEM) system.
Enforcement does not depend on a network connection. The protection is part of the file, so it applies wherever the file is opened.
One file, different views
GDPR asks companies to process only the personal data each purpose needs, which it calls data protection by default (Article 25(2)). One way to meet that is to make a separate version of a file for each audience and then track every copy.
Sertainty technology allows selective decryption within a single file. Consider a claim file. The data owner could let an adjuster open the claim details and keep the bank account section closed. Each person sees only the portion the data owner allows, and one file governs access instead of several copies.
Sertainty technology enhances the security a company already has; it does not replace it. Network controls and vendor contracts govern the systems and the people. Sertainty technology covers the file after it leaves them.
Why this matters now
California has added to the work. Regulations from the California Privacy Protection Agency took effect Jan. 1, 2026. They require cybersecurity audits from businesses above set revenue and data-volume thresholds, and risk assessments before processing that presents significant risk to privacy, such as selling or sharing personal information. The first audit reports are due April 1, 2028, for businesses with more than $100 million in 2026 revenue, with later dates for smaller ones.
Personal data that has left a company’s systems is hard to account for in either exercise. That’s what self-protecting data was built for.
Talk with Sertainty
If your team shares personal data with vendors, we can walk through one of your own handoffs and show which access rules a file protected with Sertainty technology would carry. Contact Sertainty to start the conversation. You can also read what self-protecting data is and why data-level security matters.
Sources
- Regulation (EU) 2016/679 (GDPR), Articles 3, 5, 6, 25, 28, 32 and 34. EUR-Lex
- California Consumer Privacy Act, Civil Code sections 1798.100, 1798.120, 1798.140 and 1798.150, statute text effective Jan. 1, 2026. California Privacy Protection Agency
- CCPA regulations on cybersecurity audits and risk assessments, effective Jan. 1, 2026. California Privacy Protection Agency
Frequently asked questions
What is the difference between GDPR and CCPA compliance?
GDPR applies to organizations established in the European Union and to those that offer goods or services to people in the EU or monitor their behavior there. It requires one of six lawful bases before personal data is processed, and consent is only one of them. The CCPA applies to for-profit companies that do business in California and meet at least one of three thresholds based on revenue or the volume of personal information they handle. It gives consumers the right to opt out of the sale or sharing of their personal information.
Does GDPR or the CCPA require encryption?
Neither law makes encryption mandatory by name. GDPR lists "the pseudonymization and encryption of personal data" as an example of an appropriate security measure (Article 32(1)(a)). The CCPA requires "reasonable security procedures and practices" without naming a control.
What must a vendor contract include?
Under GDPR, the contract must require the processor to act only on documented instructions, keep the data confidential, apply the security measures in Article 32, and delete or return the data at the end (Article 28(3)). Under the CCPA, the agreement must limit use to specified purposes, require the same level of privacy protection, and let the business stop and remediate unauthorized use.
Does Sertainty technology make a company GDPR or CCPA compliant?
No single technology does. Compliance also covers notices, consumer rights, and contracts. Sertainty technology supports one part of the security work. It keeps access rules, keys, and an event record with the file after it leaves the network.