HomeProductsAIServicesIntegrationsCompany
PrivacyOS One Global · California

California privacy, on the engine you already run

The CCPA, as amended by the CPRA, gives Californians rights over their data and sets duties for the businesses that hold it. Purplecop handles those rights on the same engine as your other privacy laws, so California is one more jurisdiction, not one more tool.

See how we work
The difference

From a California project to one more jurisdiction

What changes for a US business on Purplecop.

Why Purplecop

What only Purplecop brings to the CCPA

California handled on the same engine as every other privacy law you hold.

Policies already tagged for CCPA

Privacy policies in the AI Policy Builder carry CCPA tags, so the policy set starts mapped.

AI Policy Builder

Requests on the strictest clock

Rights requests run on the strictest deadline among the laws that apply.

PrivacyOS One Global

The CCPA built into the platform

The CCPA is not a ready-made framework in the library yet. Our practitioners author its clauses in the platform and map them to the controls you already run, so you start from existing work.

Framework authoring + services

One control, many frameworks

A control shared across frameworks is created once in the library, not rebuilt for each one. The work you do for the CCPA counts toward everything else you hold.

Map once, satisfy many

Exceptions that expire

A policy exception carries a justification, risk tier, compensating control and expiry date, so a temporary waiver cannot become permanent by accident.

Policies

Auditors read-only, can still flag a gap

External auditors get read-only access enforced on the server, across four roles from Lead Auditor to Observer — with one exception: they can raise a correction request when a requirement is not met.

Audit management
What you get

Built on one platform, with people who use it

Platform

PrivacyOS One Global

PrivacyOS One Global covers GDPR, CCPA/CPRA and the cross-border duties between them on one records-and-rights engine.

PoliciesRights requestsFramework authoringControls
Services

Practitioners beside the platform

The team that runs your engagement works inside the same system, so the work they do stays with you.

Also on the platform

TPRM

Onboard, assess, score and continuously monitor every vendor in one workflow.

Third-party risk

Asset Intelligence

Asset discovery, network monitoring and the audit log in one module, so every asset’s data lives in one place.

Asset Intelligence

Phishing Simulation

Live phishing campaigns with per-user risk scores, run entirely in-house.

Human layer

LMS

Role-based security awareness training for every employee, tracked to completion.

Human layer

People

A directory of the people in scope for training, policy sign-off and access reviews.

People

RBAC

Role-based access control with granular permissions, on a least-privilege model.

Access control
Questions

What teams ask us about the CCPA and CPRA

What changed with the CPRA?

The CPRA amended the CCPA, adding rights such as correction and limits on sensitive personal information, and created a dedicated enforcement agency.

Is CCPA in the control library?

Policy templates are tagged for CCPA; the requirements themselves are authored into your controls by our practitioners.

Do we need a separate tool for US privacy?

No. California runs on the same engine as your other privacy laws.

How much faster is it?

It scales with how much you integrate: the more connectors you turn on, the more evidence is collected automatically, saving up to 70% of the time you used to spend preparing for each consumer request.

See it against your own scope

We will walk the product against your scope and show you what runs on day one and what needs configuring.

See all solutions