CCPA and PDPA · For data protection officers selling into California and Singapore
One account of your processing, in California’s and Singapore’s words.
When a customer sends a privacy addendum or questionnaire under the California Consumer Privacy Act (CCPA) or Singapore’s Personal Data Protection Act (PDPA), EA drafts your answers and positions from the processing records you keep for GDPR, and marks each term your Legal Counsel needs to read. Your Data Protection Officer approves each one.
Try EA free. No card needed.
Organisations that run work on EA
The work
The same processing, described again for each law.
Each customer’s counsel writes its own
A California customer sends a service provider addendum, a Singapore customer a data intermediary schedule, each drafted by its own lawyers.
California keeps refining the rules
Its regulations set out what a service provider contract must say, down to naming each business purpose specifically, and they are updated from year to year.
Subprocessors and retention move
A new analytics tool or a change to how long tickets are kept alters answers you gave three customers ago.
Kept as one description, your processing leaves Legal Counsel only the terms that are new to each customer, not a fresh draft of the whole addendum.
What EA does
From the customer’s addendum to positions you can stand behind.
Shown on a California customer’s service provider addendum and its privacy questionnaire.
01 / 03
- EA
Reads each clause and question, and lines it up with your record of processing, your data processing agreement schedules and your subprocessor list. Knowledge Library
Your teamThe Customer Success Lead forwards the addendum, and the Information Security Manager adds the new analytics tool to the subprocessor list.
- EA
Drafts each answer and position from those records, from the specific business purposes to how consumers’ requests reach you. Where no document sets a fact, such as how long support tickets are kept, it marks “Needs evidence” and asks the owner. Terms that go beyond your standard position go to Legal Counsel. EA Agent
Your teamThe Head of Engineering sets the retention period, and Legal Counsel reads the customer’s right to check.
- EA
Brings the answers and positions to the Data Protection Officer with Legal Counsel’s note attached, and writes the approved text into the customer’s own document. If the questionnaire sits in the customer’s vendor portal, the Browser Plugin fills the fields it supports from the approved answers. Approvals Autofill Browser Plugin
Your teamThe Data Protection Officer approves, Legal Counsel settles the terms, and your team returns the addendum and submits any portal form.
See a California addendum answered from your GDPR records.
Book a demoNext customer
Next quarter’s addendum starts from this quarter’s answers.
A new subprocessor
Add it to the subprocessor list, and EA redrafts the answers that named the old list for the Data Protection Officer to check.
The next customer
A Singapore customer’s schedule is drafted from the same approved description, in the data intermediary’s three duties: protecting the data, keeping it no longer than needed, and telling the customer of a breach without undue delay.
California’s updates
Since 1 January 2026, an addendum can ask for help with the customer’s cybersecurity audit, risk assessment and automated decision-making duties. EA drafts those answers from the audit, testing and processing records you already keep. When the rules move again, your team marks the clause once and EA lists each approved answer that relied on it.
- Position
- Specific business purposes
- Source
- Record of processing, support platform
- Owner
- Data Protection Officer
- Legal note
- Attached by Legal Counsel
- Used in
- Two California addenda Current
EA’s own security
Your record of processing, open to the privacy team only.
The record of processing and your subprocessor contracts show where personal data goes, so each workspace has an access list your Data Protection Officer sets. We ran our own ISO 27001 certification on EA: read how it ran on the ISO 27001 page.
- Hosted your way
EA’s cloud in a region you choose, hybrid options or on-premises. Data never used to train the models EA runs on.
- Access
Single sign-on, which you can enforce, and an access list for each workspace.
- Support access
EA staff see your data only in a time-limited window you open.
- Testing
An independent firm runs a penetration test on EA every year.
- Security contact
EA’s security team is at security@eaglobal.ai.
FAQ
California and Singapore, from a supplier’s side.
Usually the first if you process personal information only for a California customer’s business purposes under a contract with the terms its regulations require, and the second if you process personal data on a Singapore organisation’s behalf under a contract. Your Legal Counsel decides, and EA drafts each answer to match.
Your Data Protection Officer approves each answer and position, and Legal Counsel settles any contract term beyond your standard position. EA keeps the approver and the date with each one.
EA drafts from your own records, with the source beside each answer. If the customer asks how long support tickets are kept and no document says, EA marks the answer “Needs evidence” and asks the Head of Engineering.
Yes. Your record of processing, data processing agreement schedules and subprocessor list already describe the processing, so EA starts there. Our Customer Success team helps with exports from other platforms. Plans differ by the number of autofills, the workspaces you need and the size of your knowledge library; see the pricing page.
California’s regulations list the terms. Among them: the specific business purposes; no selling or sharing; no use outside the relationship; the same level of privacy protection; the customer’s right to check, which may include assessments at least once every 12 months; notice if you can no longer comply; help with consumers’ requests; and the same terms with your subcontractors, which is why, when your subprocessor list changes, EA redrafts the answers that named it.
Your next customer’s privacy addendum, without a new programme for each law.
A California addendum, to your Data Protection Officer.
The rest of your data protection work.
Related solutions
- GDPR and data protectionA customer’s GDPR questionnaire and agreement schedules, from the same record of processing.Security and IT
- Data Protection Impact AssessmentsYour own assessment for each new system, before the processing starts.Security and IT
- Vendor security assessmentsThe security half of the same customer’s review.Security and IT
By industry
SoftwarePlatforms holding California consumers’ data for the businesses they serve.
ConsultingAdvisers holding a client’s employee data, which California’s law also covers.
Public sector and defenceSelection questionnaires, declarations and the carbon reduction plan, signed off by the right director.
Banking and building societiesThe operational resilience self-assessment and supplier reviews, attested by name.
Asset and investment managementInvestors’ DDQs, operational due diligence and the Principles for Responsible Investment report.
InsuranceBroker questionnaires, Lloyd’s confirmations and the own risk and solvency assessment.
Construction and infrastructureScheme renewals, prequalification and ISO evidence, including international engineering, procurement and construction projects.
Manufacturing and consumer goodsCustomers’ supplier questionnaires, Sedex and the conflict minerals template.
Energy and utilitiesThe CSRD statement, CDP, regulator returns and the network and information security self-assessment.
Healthcare and life sciencesPharma customers’ supplier questionnaires and the NHS data security toolkit.
Legal firmsPanel questionnaires, the professional indemnity renewal and Lexcel evidence, signed off by a partner.
Accounting firmsClients’ security questionnaires and the firm’s anti-money laundering return.

