Privacy Lawyer for SaaS and Tech Companies
I am a privacy lawyer for SaaS and data platforms that sell across borders. I build one privacy program that answers the CCPA and CPRA in California, the GDPR in Europe and Law 25 in Quebec, written once, in terms your product team can work with.
Dual-licensed in California and Quebec. IAPP Certified: CIPP/C, CIPP/E.
A privacy program that survives a customer review
One Program, Several Laws
I map what each law asks of you and build one set of documents and practices that answers all of them.
Includes:
- CCPA and CPRA, GDPR and Quebec's Law 25
- Gap review of your current practices
- Privacy policy and notices
- Internal policies and records
- A roadmap your team can follow
Privacy in the Product
I work with product and engineering while features are designed, so a launch does not get blocked later.
Includes:
- Privacy impact assessments
- Privacy by design reviews
- AI features and customer data
- Consent and preference flows
- Data retention and deletion rules
Contracts and Data Transfers
Most privacy questions from enterprise buyers arrive as contract terms. I settle them there.
Includes:
- Data Processing Agreements (DPAs)
- Cross-border data transfer assessments
- Subprocessor list and vendor terms
- Security and breach notice terms
- Customer privacy questionnaires
Ongoing Privacy Leadership
Someone has to own privacy after the documents are written. I can hold that role from outside.
Includes:
- External privacy officer role
- Requests from individuals
- Incident response and notifications
- Staff training
- Updates when the rules change
Questions for a privacy lawyer
Usually at one of four moments. Before launch, when the privacy policy has to match what the product really does with data. When an enterprise customer sends a data processing agreement or a privacy questionnaire. When you start selling in a new place such as Quebec, California or Europe. And when something goes wrong: an incident, a complaint or a letter from a regulator.
With what you already have. Most US companies have a CCPA program of some kind. I compare it with what the GDPR and Quebec's Law 25 ask for, list the gaps in order of risk, and close them in your existing documents where possible. A separate program per country is rarely needed.
Yes, where the law allows the role to be held from outside the company. Quebec's Law 25 lets a business delegate in writing the role of the person in charge of the protection of personal information, and the GDPR allows a data protection officer to work under a service contract. I take the role under a written mandate that sets out what I handle and what stays with your team.
It depends on what the feature does with personal information and where your users are. Several laws call for an assessment in defined situations, for example certain transfers outside Quebec under Law 25 or high-risk processing under the GDPR. I look at the feature with your product team and tell you whether one is called for, then write it with them if it is.
Usually the same five things. A data processing agreement, where the data is hosted and transferred, who your subprocessors are, how fast you notify an incident, and how you handle requests from individuals. Having those answers ready in your documents shortens the review.
The same way as my other work. A defined project such as a gap review or a privacy policy can run On-Demand at US$400 / hour. Ongoing privacy leadership fits inside a recurring plan. The details are on the pricing page.
