What Is the Purpose of a Privacy Impact Assessment in Texas?
A privacy impact assessment shows whether your organization needs the personal data it holds and what protections that data requires. This guide covers its purpose, the Texas requirements and how to build one from live system evidence.
A privacy impact assessment (PIA) determines whether your organization needs the personal data it holds and what protections that data requires. It follows the data through your systems, documents the risks to people, and records who owns the safeguards. The purpose is a defensible decision, not a completed questionnaire.
For a Texas firm facing a customer’s PIA request, start with the requirement behind it. The Texas Data Privacy and Security Act (TDPSA) calls this work a data protection assessment. Small businesses are generally exempt, but a customer contract can still require an assessment.
What is a privacy impact assessment actually for?
The Centers for Medicare & Medicaid Services describes a PIA as an analysis of how personally identifiable information is handled throughout its life cycle. Its guidance, reviewed January 30, 2025, treats the assessment as a process for identifying privacy risks and building protections into systems, not a form to file afterward.
A security assessment asks whether you can protect the data. A PIA also asks whether you need it in the first place. Encryption does not justify collecting information your service does not need, and access controls do not justify keeping it indefinitely.
What requirement triggers your PIA?
Identify the requirement behind the request before gathering evidence. Each can set a different scope.
The federal requirement comes from Section 208 of the E-Government Act of 2002. It applies when a federal agency develops or procures new information technology involving identifiable information. That federal agency obligation is not a blanket requirement for private Texas firms.
Texas has a separate framework. The TDPSA requires data protection assessments for certain processing activities by covered businesses. Coverage and exemptions need review before you conclude that a statutory assessment is required.
A customer can also make a PIA a condition of onboarding. Find the clause or questionnaire that requests it. Your size does not cancel a contractual requirement, and a statutory exemption does not answer the customer’s questions.
Does the Texas Data Privacy and Security Act reach your firm?
Check coverage before assuming either that the law applies or that your firm is too small. Fasthoff Law Firm’s July 6, 2026, explanation describes a broad coverage test without a revenue or consumer-count threshold.
- Do you conduct business in Texas or produce a product or service consumed by Texas residents? This is the geographic part of the coverage test.
- Do you process or sell personal data? Evaluate this alongside the geographic test and the applicable exemptions.
- Do you qualify as a small business under SBA standards? The standard depends on your industry. Some use employee headcount; others use annual receipts.
- Does an exemption apply? Review entity and data exemptions with counsel. Even generally exempt small businesses must obtain prior consumer consent before selling sensitive personal data.
Coverage alone does not mean every processing activity requires an assessment. Have counsel identify the applicable assessment obligation, then compare it with the customer’s contractual scope.
Which of your data counts under the TDPSA?
A TDPSA “consumer” is a Texas resident acting in an individual or household context. The definition excludes employment and commercial contexts. Employee records and business-contact information therefore need a different scope analysis from consumer records.
A customer’s review may reach beyond those statutory boundaries. It can ask about employee access to customer systems even where employment-context data falls outside the consumer definition. State which data categories the assessment covers and why.
Sensitive data needs counsel’s attention. Examples include health diagnoses, identifying biometric data and personal data collected from a known child. Texas also includes precise geolocation, defined using a 1,750-foot radius. Healthcare firms should check the entity exemption for HIPAA-covered entities and business associates rather than assume only particular patient records are exempt.
How do you map data flows from the systems themselves?
Build the map from live settings. An interview can identify a system; it cannot prove that system deletes records on schedule.
Pull the evidence before drawing anything
Collect the records that show where the data actually goes:
- The data inventory, including spreadsheets that hold information in scope.
- The integration and API list, including scheduled synchronization jobs.
- Dated exports or screenshots of retention and sharing settings from each SaaS admin console.
- Vendor subprocessor lists and the relevant contract terms.
Record who can access each system and how access is granted. Check those permissions against the stated purpose for holding the data.
Walk each flow end to end
Trace each data category from collection through deletion. Show where it is stored and how long it is kept in a simple diagram. Pay particular attention to handoffs: a spreadsheet export can leave the source system’s controls behind.
Check each connection against the settings and vendor records. If you cannot verify a flow, record an open item. Do not turn an assumption into an attestation.
How do you decide the risk of each flow?
Write down your evaluation criteria before assessing individual flows. Have counsel confirm the applicable legal requirements; the operational team should document how it evaluates harm and applies the method consistently.
For each flow, ask whether the collection is necessary, what harm exposure or misuse could cause, and which safeguard reduces that harm. Record the remaining risk and who has authority to accept it.
A numerical score is useful only if you can explain its calculation. “High risk” without a stated reason gives an executive no basis for deciding what to fix first.
When should you stop and bring in counsel?
Operations can establish what the systems do. Counsel should determine what the law requires. Bring counsel in when:
- The assessment involves sensitive personal data.
- A customer requests an attestation covering data you cannot yet describe.
- An incident or disclosure may already have triggered a notice obligation.
Do not sign while the underlying facts remain unknown. A PIA does not replace a breach-notification analysis.
What does a defensible PIA report contain?
The report must let someone outside your team trace a conclusion back to evidence. Confirm any required format with the customer or counsel, then include:
- The data map, including handoffs between systems.
- Dated evidence supporting each entry.
- Risk decisions and the criteria behind them.
- Safeguards with accountable owners and due dates.
- Remaining risk and its acceptance.
- Executive sign-off.
Complete the review before onboarding or deployment so its findings can change the design. Revisit it when a system or vendor changes. A report describing last year’s settings cannot support an attestation about today’s environment.
How does one assessment serve your Q4 audits, insurers and vendor reviews?
If your insurance renewal and vendor reviews fall in Q4, use the same verified data map for both. The insurer may ask where sensitive records sit; the customer may ask about retention and subprocessors. Board reporting needs the resulting exposure and remediation decisions.
One evidence set can support those reviews, but the deliverables may differ. Check each requirement rather than assume a customer questionnaire satisfies a statutory assessment. Do not sign a privacy attestation until someone has verified retention and sharing settings in the live systems.
We run security programs at Total 360 Security. To discuss the ownership your assessment needs, bring the requesting contract clause, your system list and exported settings to a 30-minute risk discussion. Our virtual CISO services provide cybersecurity leadership and compliance program ownership.
Frequently asked questions
What is the purpose of a Privacy Impact Assessment (PIA)?
A PIA determines whether personal data is needed and what safeguards its use requires. It documents data flows, risks to people and the decisions made to reduce those risks. The result should be supported by system evidence, not questionnaire answers alone.
What is a data protection assessment under the Texas Data Privacy and Security Act?
A data protection assessment is the TDPSA’s assessment of certain personal-data processing activities. It is not automatically required for every business or every use of personal data. Counsel should confirm coverage and exemptions before you set the scope.
Does a small business need to conduct a Privacy Impact Assessment in Texas?
Businesses qualifying as small under the applicable SBA industry standard are generally exempt from the TDPSA. Even exempt small businesses must obtain prior consent before selling sensitive personal data. A customer contract can independently require a PIA regardless of that exemption.
What is the difference between a privacy impact assessment and a security assessment?
A security assessment evaluates whether safeguards protect data against threats. A PIA also examines whether collecting or keeping that data is justified and what harm its use could cause people. A system can have strong security controls and still hold unnecessary personal information.
How often should a Privacy Impact Assessment be updated?
Review the PIA when a system or vendor changes, and check any contractual review schedule. Update the evidence and risk decisions when those changes affect the assessment. An old sign-off does not cover a new data flow.
Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.
Serving Texas, California, Nevada, New Mexico.
More from the blog
10 min read
Identity Access Management Software: What to Govern First
A practical order for identity access management software: define privileged access, name an owner, inventory raw exports and review each quarter before buying a tool.
Read article7 min read
SOC 2 Audit: What Type II Requires and Who Owns Each Control
A SOC 2 audit is an independent CPA examination of your controls against the AICPA criteria. Here is what a Type II report requires, who owns each control and what evidence to keep.
Read article7 min read
Compliance Monitoring: What to Check Monthly and Quarterly
Compliance monitoring is the ongoing check that your operations follow the rules that apply to you. This guide sets a monthly evidence set, a quarterly sampling routine and clear ownership for every exception.
Read article