Home / Services / Security & Compliance / GDPR & Data Privacy Compliance
GDPR & DATA PRIVACY SERVICES
GDPR and privacy compliance that lets you sell anywhere, safely.
Data mapping, records of processing, DPIAs, privacy notices, data subject requests and cross-border transfers, covering GDPR, UK GDPR and US state laws like CCPA.
Free 30-minute call · Written proposal in 48 hours · NDA before we talk
GDPR IN SHORT
What is GDPR compliance?
GDPR compliance means handling personal data of people in the EU the way the General Data Protection Regulation requires: a lawful basis for every use, transparency, data minimization, security, respect for individual rights and safeguards for transfers. It applies to companies outside the EU that offer services to, or monitor, people in the EU.
WHO MUST COMPLY
SaaS with EU or UK users
eCommerce selling to Europe
Ad tech & analytics
HR & recruiting platforms
Health & fintech apps
AI companies training on personal data
Key facts
REACH
Applies outside the EU when you offer goods or services to, or monitor, people in the EU (Article 3).
MAXIMUM FINES
Up to €20 million or 4% of worldwide annual turnover, whichever is higher.
BREACH NOTICE
To the supervisory authority within 72 hours of becoming aware, where required.
RIGHTS REQUESTS
Answer access, deletion and other requests within one month.
US TRANSFERS
Possible through the EU-US Data Privacy Framework or standard contractual clauses.
THE CORE REQUIREMENTS
What GDPR actually requires you to do
Six practical work streams cover most of what regulators and enterprise buyers will check.
ARTICLE 30
Records of processing
A living record of what personal data you process, why, where it goes and how long you keep it.
Start here: everything else builds on it
ARTICLE 6
Lawful basis for every use
Consent, contract, legal obligation, vital interests, public task or legitimate interests, documented per purpose.
Watch out: consent is not always the right basis
ARTICLE 35
Data protection impact assessments
Required before high-risk processing, such as large-scale profiling, sensitive data or new technologies like AI.
Expect: DPIAs for most AI features
ARTICLES 15–22
Data subject rights
Access, correction, deletion, portability, objection and restriction, answered within one month.
Build: a repeatable request workflow
ARTICLE 32
Security of processing
Appropriate technical and organizational measures, such as encryption, access control and testing.
Reuse: your SOC 2 or ISO 27001 controls
CHAPTER V
International transfers
Adequacy decisions, the EU-US Data Privacy Framework or standard contractual clauses with a transfer assessment.
Check: every vendor outside the EU
GDPR VS US PRIVACY LAWS
GDPR vs CCPA/CPRA: what changes for US companies?
If you already work toward GDPR, most of the CCPA work is done. The differences are in consent, notices and the right to opt out.
GDPR (EU and UK)
CCPA / CPRA (California)
Who it protects
People in the EU or UK
California residents
Default model
You need a lawful basis before processing
You may process, but people can opt out of sale or sharing
Key notices
Privacy notice at collection
Notice at collection and a "Do Not Sell or Share" link
Rights response time
One month, extendable
45 days, extendable
Penalties
Up to €20M or 4% of global turnover
Per-violation administrative fines
OUR ADVICE
Build one privacy program on the stricter GDPR model, then add CCPA-specific notices and opt-out handling. It is faster than running two separate programs.
DELIVERY TIMELINE
How a GDPR program comes together
Most companies reach a solid, documented GDPR program in 6 to 12 weeks, then keep it current as products change.
01
Discover
Interviews and system review to find every personal-data flow. Typical: 1–2 weeks.
02
Data map
Records of processing and data-flow diagrams across systems and vendors. Typical: 2–3 weeks.
03
Assess
Lawful bases, DPIAs, retention and transfer assessments. Typical: 2–3 weeks.
04
Remediate
Privacy notices, consent, retention rules and vendor DPAs updated. Typical: 2–4 weeks.
05
Operationalize
Rights-request workflow, breach procedure and team training. Typical: 1–2 weeks.
06
Maintain
Privacy by design reviews for new features, and a yearly refresh.
DELIVERY TIMELINE
Typical total: 6–12 weeks to a documented program
01
Discover
1–2 weeks
02
Data map
2–3 weeks
03
Assess
2–3 weeks
04
Remediate
2–4 weeks
05
Operationalize
1–2 weeks
06
Maintain
Ongoing
THROUGHOUT THE PROJECT
You always know where you stand
Weekly status updates
Progress, owners and dates
One accountable lead
A single point of contact, start to finish
Legal-ready documents
Clear drafts your counsel can approve
WHAT'S INCLUDED
Everything you need for a defensible privacy program
Practical documents and workflows that hold up with regulators and enterprise buyers.
✓
Data mapping & RoPA
Every system, purpose and data flow, kept current.
✓
Lawful basis review
The right basis for each purpose, documented.
✓
DPIAs
Impact assessments for high-risk and AI-driven processing.
✓
Privacy notices & cookies
Clear notices and a consent setup that matches how your site really works.
✓
Vendor DPAs & transfers
Data processing agreements, SCCs and transfer assessments for every vendor.
✓
Rights request workflow
A repeatable process to answer access and deletion requests on time.
✓
Breach response procedure
72-hour assessment and notification steps, tested.
✓
Team training
Short, role-based privacy training with completion records.
You own every record, assessment and policy. No lock-in, ever.
EXPERT INSIGHTS
What most GDPR guides won't tell you
Lessons from privacy programs that actually work in fast-moving product teams.
01
Consent is often the wrong basis.
Consent can be withdrawn at any time. For core product processing, contract or legitimate interests are usually more stable and more honest.
02
Your data map is never finished.
Every new feature, vendor or AI model changes it. Tie updates to your release process, not a yearly scramble.
03
Cookie banners are not compliance.
A banner that loads trackers before consent creates risk. Test what actually fires on page load.
04
AI features usually need a DPIA.
Training or running models on personal data is typically high-risk processing. Do the assessment before launch.
05
Vendors are your biggest blind spot.
Analytics, support and AI tools often process personal data outside the EU. Each needs a DPA and a transfer mechanism.
06
Security work counts twice.
Your SOC 2 or ISO 27001 controls are strong evidence for GDPR Article 32. Reuse them.
TOOLS & FRAMEWORK MAPPING
Privacy tools that fit your stack
We work with the privacy and consent platforms you already use, or help you choose the right one.
PRIVACY MANAGEMENT
OneTrust
TrustArc
Osano
CONSENT
Cookiebot
OneTrust CMP
Google Consent Mode
DATA DISCOVERY
BigID
Microsoft Purview
AWS Macie
REQUESTS & TICKETS
Jira
Zendesk
Intercom
SECURITY EVIDENCE
Vanta
Drata
Secureframe
ONE PROGRAM, MAPPED TO
UK GDPR
CCPA / CPRA
ISO 27701
India DPDP Act
PIPEDA
PROOF
Use cases for GDPR & Data Privacy Compliance
Real problems, the services we combined, and the results.
All use cases →
ECOMMERCE
PCI DSS 4.0
SOC
PCI DSS 4.0 and unified compliance for multi-market retailers
THE CHALLENGE
Stores, a growing online channel and PCI DSS 4.0 requirements that are now mandatory.
OUR APPROACH
Checkout script control plus one unified control framework across every market.
WHAT SUCCESS LOOKS LIKE
One set of controls and evidence for PCI DSS, ISO 27001, SOC 2 and privacy audits.
5
frameworks mapped to one control set
Read the story →
1 / 3
RELATED INDUSTRIES
Built for your industry
GDPR & Data Privacy Compliance adapted to the rules, systems and customers of your industry.
All industries →
BLOG & RESOURCES
Insights on security, compliance and privacy
Practical guides for founders and technology leaders. No jargon.
View all resources →
PRIVACY
GDPR for US and Canadian companies: when it applies
A plain-English checklist for teams with European users.
Akash Soni, Founder & CEO · 8 min read
MEDIA & AI
Generative AI on your catalog, with consent and rights intact
A 6-step plan for labels, publishers and broadcasters.
Akash Soni, Founder & CEO · 9 min read
AI FOR SAAS
AI features for SaaS: what enterprise buyers now expect
Guardrails, evaluation and data-use terms that pass review.
Akash Soni, Founder & CEO · 8 min read
FAQ
GDPR and privacy questions, answered
Straight answers for companies outside Europe. If yours isn't here, ask us directly.
Still unsure? Talk to a security expert. 30 minutes, no pitch.
Book a free consultation
Does GDPR apply to US companies?
Yes. GDPR applies to US and Canadian companies that offer goods or services to people in the EU or monitor their behaviour, even without an EU office. That includes SaaS platforms with EU users, online stores shipping to Europe and apps using tracking or analytics on EU visitors.
What are the GDPR fines?
GDPR fines can reach €20 million or 4% of global annual turnover, whichever is higher, for the most serious violations. Lesser violations can reach €10 million or 2%. Regulators also order processing to stop, which can hurt a business more than the fine itself.
Do we need a Data Protection Officer?
You need a Data Protection Officer if your core activities involve large-scale, regular monitoring of people or large-scale processing of sensitive data, such as health data, or if you are a public authority. Many other companies appoint a privacy lead voluntarily. Non-EU companies also usually need an EU representative.
What is a DPIA and when do we need one?
A data protection impact assessment (DPIA) is a documented review of the privacy risks of a new processing activity and how you will reduce them. GDPR requires one for high-risk processing, such as large-scale profiling, new technologies like AI, tracking or processing sensitive data.
How fast must we report a data breach?
Under GDPR you must notify the supervisory authority within 72 hours of becoming aware of a personal data breach, unless it is unlikely to risk people's rights. If the risk is high, you must also inform affected individuals without undue delay. Document every breach, even ones you don't report.
How do we transfer EU data to the US?
US companies can receive EU personal data under the EU-US Data Privacy Framework if they self-certify, or by using Standard Contractual Clauses with a transfer impact assessment. Encryption, minimization and clear vendor contracts strengthen any transfer mechanism you choose.
How long does GDPR compliance take?
A practical GDPR program for a small or mid-size company usually takes 6 to 12 weeks. That includes data mapping, records of processing, lawful bases, privacy notices, data processing agreements, consent and cookie management, DPIAs and a breach response process. Ongoing compliance then needs regular reviews.
Is GDPR the same as CCPA?
No. GDPR is an EU law requiring a lawful basis for all processing of personal data. The CCPA, as amended by the CPRA, is a California law focused on transparency and consumers' rights to know, delete, correct and opt out of the sale or sharing of data. One privacy program can cover both.
RELATED SERVICES
SOC 2 Compliance & Audit Readiness →
Add the Privacy criterion to your SOC 2
ISO 27001 Certification Consulting →
Add ISO 27701 privacy on top of your ISMS
AI Governance & ISO 42001 →
Govern AI that uses personal data
Data Engineering & Data Pipelines →
Build privacy into your data platform
Find out where your privacy risks are, in one free call.
Book a free 30-minute call. You'll leave with your highest-risk data flows and clear next steps, whether or not we work together.
Your highest-risk data flows
Clear next steps
NDA before we talk