Skip to content

Glossary

Data Governance & Security

Data Privacy

Data privacy is the set of rights, rules, and practices that govern how personal information is collected, used, shared, and retained, giving people control over data about them and holding organizations accountable for handling it.

Updated · By the VIZIO AI team

What is data privacy?

Privacy asks whether an organization should use personal data in a given way; security asks whether the data is protected from those who should not have it. A company can be perfectly secure and still violate privacy, for example by using purchase history for a purpose customers never agreed to.

GDPR Article 5 sets out the core principles most laws echo: lawfulness, fairness and transparency; purpose limitation; data minimization; accuracy; storage limitation; integrity and confidentiality; and accountability. Major frameworks include the EU and UK GDPR, California's CCPA as amended by the CPRA, HIPAA for US health data and Brazil's LGPD. Turning these into daily rules is the job of data governance.

What does a privacy program include?

A working privacy program is mostly operational paperwork backed by a few technical controls.

  • Data inventory: a record of processing activities, required by GDPR Article 30 for most organizations.

  • Lawful basis and consent: one of the six bases in Article 6, plus a consent tool such as OneTrust or Cookiebot for non-essential cookies.

  • Data subject requests: access and deletion requests answered within one month under GDPR and 45 days under CCPA.

  • Impact assessments: a DPIA under Article 35 for high-risk processing such as large-scale health data.

  • Vendor contracts: data processing agreements under Article 28.

  • Retention schedule: deletion dates for each data category.

What does data privacy work look like in practice?

Most privacy work is mapping where personal data flows and making sure each flow matches what customers were told. Consider a 45-person UK e-commerce brand that starts selling to California.

  1. The team maps flows from Shopify, Klaviyo, Google Analytics 4 and its helpdesk.

  2. Counsel checks whether the business meets any CCPA threshold: annual revenue, number of California consumers, or share of revenue from selling or sharing data.

  3. Because ad pixels share data for cross-context behavioral advertising, the site adds a "Do Not Sell or Share My Personal Information" link and honors Global Privacy Control signals.

  4. A request form feeds a checklist covering every system, so a deletion request is completed across all of them, not just Shopify.

The final step is the easiest to skip: updating the privacy notice so it names the new categories of data, the purposes and the third parties now receiving it.

What are the trade-offs and common privacy mistakes?

Every privacy control costs some data, and the honest move is to plan around that loss instead of hiding it. Consent banners reduce analytics coverage; minimization limits future models; shorter retention shrinks historical comparisons.

  • Policy-pipeline mismatch: the privacy notice says one thing while the data warehouse quietly does another.

  • "Just in case" storage: keeping everything forever breaches the storage limitation principle.

  • Treating server-side tracking as an exemption: moving a tag to the server does not remove the need for consent.

  • Unreviewed AI tools: staff pasting customer data into public chatbots creates an undocumented processing activity.

How is data privacy different from data security and compliance?

Privacy defines the permitted uses, security enforces protection, and compliance proves both to regulators and auditors. Data security tools include encryption, access control and monitoring. Privacy tools manage consent, requests and data maps, and data compliance teams use their records as audit evidence: OneTrust, Transcend, DataGrail, Osano and Cookiebot are common choices.

In the data stack, privacy shows up as column-level masking policies in Snowflake or BigQuery, deletion jobs keyed on customer IDs, and pseudonymous IDs in analytics. A useful test: if a customer asked today what data you hold on them, could you answer completely within a month?

Data privacy vs data security

Data privacy

Data security

Core question

Should we use this data this way?

Is this data protected from misuse?

Key rules

GDPR, CCPA/CPRA, HIPAA, LGPD

ISO 27001, SOC 2, PCI DSS

Typical controls

Consent, notices, deletion requests

Encryption, MFA, access control

Owner

Privacy or legal lead, DPO

Security team, CISO

Failure example

Using data beyond its stated purpose

Database exposed to attackers

How does VIZIO AI handle personal data in its projects?

VIZIO AI's case studies show privacy-relevant design choices inside larger builds rather than standalone privacy programs. For a US audiology provider with clinics in seven states, our DX Studio unified patient records, device data and CRM inputs from inherited legacy systems into one warehouse, cutting duplicate and conflicting records before building predictive models. The provider reduced hearing aid return rates by 12–15% across pilot clinics.

For Found Factory, our Venture Studio added academic email verification and user role management to a co-founder matching MVP delivered in 13 weeks. Where to start: build a one-page inventory of every system that stores personal data and who can access it.

logo of Facebook
logo of X
logo of LinkedIn
logo of Reddit
logo of Telegram

Think AI-first.
Move future-fast.

Let’s build what’s next! From product ideas and intelligent workflows to data-driven systems and scalable growth operations.

Book a Strategy Call