GRC · Service

GDPR and CCPA compliance

Sell into the EU and California without privacy holding up the deal.

What it covers

Records of processingContracts and transfersNoticesRights handling

What GDPR and CCPA compliance involves

The GDPR is the European Union's data protection law, and the CCPA is California's privacy law. Both reach companies outside their borders: the GDPR when you offer goods or services to people in the EU or monitor them there, the CCPA when you do business in California above its thresholds. Both also reach you through contracts when you process data for a customer they cover.

Compliance means a record of what you process and why, contracts that pass the right duties to and from your vendors, notices that match what you do, and a process for answering people's requests. EU and US customers check these in due diligence before they sign, and regulators such as the California Privacy Protection Agency ask for them when they investigate.

You need it when

  • An EU customer sends a data processing agreement and a privacy questionnaire before it will sign.
  • You launch to users in the EU, ship to EU addresses or track EU visitors, which brings you under Art. 3(2) GDPR as a controller.
  • A US customer adds a CCPA service provider addendum to your contract.
  • Your company crosses a CCPA threshold, such as annual gross revenue above US$26,625,000.

What you get

The scope is agreed on the first call and written down before the work starts.

  • Records of processing and a lawful basis for each purpose under the GDPR.
  • Data processing agreements and transfer safeguards, such as Standard Contractual Clauses.
  • Privacy notices and rights handling for GDPR data subjects and CCPA consumers.
  • Answers to the privacy questions in your customers' security reviews.

Deliverables

What you hold at the end of the engagement, and who each document is for.

DocumentWhat it holdsWho it is for
Record of processingEach processing activity with its purpose, lawful basis, people and data, recipients, transfers, retention and security measures, as Art. 30 GDPR requires.Privacy lead and regulators
Contract packData processing agreements under Art. 28, Standard Contractual Clauses with a transfer impact assessment for each flow from the EU to India, and the CCPA service provider terms.Legal and customers
Privacy noticesA GDPR notice under Arts. 13 and 14, and a CCPA privacy policy and notice at collection, all written from the record of processing.Users and customers
Rights procedureHow requests come in, how identity is checked, who answers, and the clocks: one month under the GDPR, 45 days under the CCPA, plus the opt-out of sale or sharing.Support and privacy teams
Due-diligence answer setAnswers to the privacy questions customers ask in security reviews, each pointing to the document that backs it.Sales and account teams

How the work runs

Weeks 1 to 2

Roles and reach

For each product and customer, whether you are a controller or processor under the GDPR and a business or service provider under the CCPA, and whether you need an EU representative (Art. 27) or a DPO (Art. 37).

Weeks 2 to 4

Record of processing

Interviews with the teams that handle personal data, and the Art. 30 record built from them, with a lawful basis for each purpose.

Weeks 4 to 7

Contracts and transfers

Data processing agreements, Standard Contractual Clauses with a transfer impact assessment for each flow from the EU to India, and the CCPA service provider terms, passed down to your own sub-processors.

Weeks 6 to 9

Notices and rights

Notices published, and the request process set up and tested with a sample request, including the opt-out links and the browser opt-out signal where the CCPA needs them.

Week 10

Answers and handover

The answer set for customer security reviews, a review date for each activity in the record, and your team shown how to keep it current.

A row from a record of processing

The record lists each processing activity against the fields in Art. 30(1) GDPR; the controller's name and contact details, and those of its EU representative and DPO, sit at the top. This entry was written for this page; it does not come from a client.

Processing activityCustomer accounts in the web app: sign-up, sign-in, support and billing
Purposes and lawful basis (Art. 30(1)(b))Open and run customer accounts, give support and bill for the subscription. Art. 6(1)(b), contract; invoices also Art. 6(1)(c), legal obligation.
People and data (Art. 30(1)(c))Users of customer accounts. Name, work email, company, hashed password, billing address, sign-in IP addresses. No special-category data.
Recipients (Art. 30(1)(d))Cloud host, payment processor, email delivery service and support desk software, each under an Art. 28 agreement.
Transfers outside the EU (Art. 30(1)(e))To India, where the support and engineering teams work. Standard Contractual Clauses under Art. 46(2)(c), with a transfer impact assessment.
Retention (Art. 30(1)(f))Account data deleted 90 days after the subscription ends. Invoices kept for as long as tax law requires.
Security measures (Art. 30(1)(g))Encryption in transit and at rest, single sign-on with multi-factor authentication for staff, role-based access, logs reviewed every week (Art. 32(1)).
California (CCPA)Identifiers and commercial information of California consumers. Not sold or shared. The vendors are service providers, with the s. 1798.140(ag) terms in each contract.

Where it usually goes wrong

A privacy notice copied from a template

A notice that lists purposes or vendors you do not have, or misses ones you do, is a misstatement a regulator or a customer can hold against you. Infofacility writes notices from the record of processing, so each line matches something you do.

Signing the customer's DPA unread

Customer DPAs often carry breach notice windows, audit rights and sub-processor approvals your teams cannot meet. Infofacility checks each clause against how you actually work and marks the ones to negotiate, so your lawyers raise them before you sign.

A record of processing built once and left

Products, vendors and countries change, and the next customer questionnaire shows the record is out of date. Infofacility gives each activity in the record an owner and a review date, and shows your team how to update it at handover.

The requirements it answers

The frameworks, laws and regulators whose requirements this work gives you evidence for.

Art. 28 GDPRArt. 30 GDPRArt. 46 GDPRCCPA
Read What is the GDPR? in the library

Pricing

GDPR and CCPA compliance

Price on request

Scope sets the price. Book a scoping call for a written quote, in US dollars or rupees.

Request a callback

What sets the price

  • The number of products and processing activities in scope.
  • Whether you act as controller, processor or both under the GDPR, and as a business or service provider under the CCPA.
  • The number of customer and vendor contracts to review, and of data flows out of the EU.
  • Whether any processing needs a data protection impact assessment under Art. 35 GDPR.

What Infofacility needs from you

  • A privacy or legal contact who can decide on roles, lawful bases and contract positions.
  • Time with the people who run product, engineering, support, marketing and HR, for the data mapping interviews.
  • Your customer and vendor contracts, current privacy notices and recent customer questionnaires.
  • A list of your vendors and sub-processors, and what each one receives.

Questions

Does the GDPR apply to a company outside the EU?

Yes, in two ways. Directly under Art. 3(2), when you offer goods or services to people in the EU, paid or free, or monitor their behaviour there. Through contract under Art. 28, when you process personal data for an EU customer as its processor. Most Indian companies meet it the second way, through a data processing agreement and a customer questionnaire.

What is a record of processing activities?

The written list Art. 30 GDPR requires of each processing activity: its purposes, the people and data involved, the recipients, transfers outside the EU, retention periods and security measures. Organisations with fewer than 250 employees are exempt only when the processing is occasional, unlikely to result in a risk and involves no special-category or criminal-offence data. Processing customer data every day is not occasional, so most software companies need one.

Do we need Standard Contractual Clauses to receive EU personal data in India?

Yes, in most cases. The European Commission has not adopted an adequacy decision for India, so each transfer from the EU to India needs a Chapter V safeguard. The usual one is the Commission's Standard Contractual Clauses under Art. 46(2)(c), with a transfer impact assessment. Binding corporate rules (Art. 47) are the alternative for transfers within a group.

Does the CCPA apply to a company outside California?

It can. It applies to a for-profit business that does business in California and has annual gross revenue above US$26,625,000, buys, sells or shares the personal information of 100,000 or more consumers or households, or earns half its revenue from selling or sharing it. More often a company outside the US meets it as a service provider, through the terms its US customers put in the contract.

How is the CCPA different from the GDPR?

The GDPR needs a lawful basis before you process personal data. The CCPA lets you process it after a notice at collection, and gives consumers the right to know, delete, correct and opt out of sale or sharing. The GDPR has no size threshold; the CCPA covers only businesses above its thresholds, and their service providers. Requests are answered within one month under the GDPR and 45 days under the CCPA.

Is there a GDPR certificate?

None is required. Art. 42 GDPR allows certification schemes approved by a supervisory authority or the EDPB, and an ISO 27001 or ISO 27701 certificate is not one of them, though EU customers often ask for one as evidence of security. Infofacility issues no certificates; it builds the records, contracts and processes that customers and authorities check.

Keep reading

The library pages behind this work, written and reviewed by the same people.

Request a callback

Tell Infofacility what you need and by when. A consultant calls you back to agree the scope and send a quote.

Request a callback

Tell us what you need. A consultant replies to set up a short scoping call.

Your details are used only to answer this request, as the Privacy Policy sets out.