Juniper Hollow Special Service District (Sample — fictional)
2026 Privacy Program Report
The approver is whoever holds the CAO role in your entity settings. In this sample: Mira Sample Quill (fictional).
- Review (step 1 of 4, current)
- Approve (step 2 of 4)
- Share (step 3 of 4)
- Done (step 4 of 4)
0 of 64 answers approved4 need a look
Showing the fictional sample's draft. Open any answer to see its source. Approving answers saves in your browser, so it needs JavaScript.
Tap any answer to see where it came from: your answer, the state's question and the PDF fields it fills. The “Demo role” switch at the top only changes who is acting; this demo has no logins.
Nothing needs a look. ✓
Needs you 1
Change the answer, or keep it and explain why.
Check 3
Look at each one. If it's right, say so.
- Section 1 · Entity informationGovernmental entity: Mailing AddressThis answer differs from the sample registry record. Does it look right, or would you like to change it?43 Sample Cloudberry Spur, Sample Pinecrest County, UT 00000…
- Section 3 · Practices2.4 Retention Schedule Proposal and ApprovalYour goal level is lower than your current level. Is that right?Implemented yes · Level 2 → 1
- Section 3 · Practices2.8 Record and Data Sharing, Selling, or PurchasingYou answered No, but chose Level 2 or higher, which means the practice is in place. Change one answer.Implemented no · Level 2 → 2
Ready to approve 60
These passed every check. Spot-check any, or approve them together.
Show 60 ready answers
- Section 1 · Entity informationGovernmental entity: NameJuniper Hollow Special Service District (Sample — fictional)
- Section 1 · Entity informationGovernmental entity: Type (Select One)Special Service District
- Section 1 · Entity informationChief Administrative Officer (CAO): NameMira Sample Quill (fictional)
- Section 1 · Entity informationChief Administrative Officer (CAO): TitleSample District Administrator
- Section 1 · Entity informationChief Administrative Officer (CAO): Emailmira.sample@
example.org - Section 1 · Entity informationChief Administrative Officer (CAO): Phone801-555-0142
- Section 1 · Entity informationFiscal year end2026-06-30
- Section 2 · Program statusHas your governmental entity initiated a privacy program?Yes
- Section 2 · Program statusHow has the governmental entity initiated a privacy program?Resolution; Policy
- Section 3 · Practices1.1 Chief Administrative Officer (CAO) DesignationImplemented yes · Level 2 → 3
- Section 3 · Practices1.2 Records Officers AppointmentImplemented yes · Level 2 → 3
- Section 3 · Practices1.3 Records Officer Training and CertificationImplemented yes · Level 2 → 3
- Section 3 · Practices1.4 Statewide Privacy TrainingImplemented yes · Level 1 → 2
- Section 3 · Practices1.5 Privacy Program ReportImplemented yes · Level 1 → 2
- Section 3 · Practices2.1 Record Series Creation and MaintenanceImplemented yes · Level 1 → 2
- Section 3 · Practices2.2 Record Series Designation and ClassificationImplemented yes · Level 1 → 2
- Section 3 · Practices2.3 Statement Filed with State ArchivistImplemented yes · Level 1 → 2
- Section 3 · Practices2.5 Record Series Privacy AnnotationImplemented no · Level 0 → 1
- Section 3 · Practices2.6 InventoryingImplemented yes · Level 1 → 2
- Section 3 · Practices2.7 Privacy Impact Assessments (PIA)Implemented no · Level 0 → 1
- Section 3 · Practices3.1 Data Subject Requests for AccessImplemented yes · Level 2 → 3
- Section 3 · Practices3.2 Data Subject Requests for Amendment or CorrectionImplemented yes · Level 1 → 2
- Section 3 · Practices3.3 Data Subject Requests for an ExplanationImplemented yes · Level 1 → 2
- Section 3 · Practices3.4 Data Subject Request by At-Risk Employees for Restricting AccessImplemented yes · Level 1 → 2
- Section 3 · Practices4.1 Privacy Notice (Notice to Provider of Information)Implemented yes · Level 1 → 2
- Section 3 · Practices4.2 Website Privacy Notice and Website Privacy PolicyImplemented yes · Level 1 → 2
- Section 3 · Practices5.1 Minimum Data NecessaryImplemented yes · Level 2 → 3
- Section 3 · Practices5.2 Retention and Disposition of Records Containing Personal DataImplemented yes · Level 1 → 2
- Section 3 · Practices5.3 Incident Response and Notification to the Cyber Center and Attorney GeneralImplemented yes · Level 1 → 2
- Section 3 · Practices5.4 Breach Notification to Affected IndividualsImplemented yes · Level 1 → 2
- Section 3 · PracticesOther privacy practice 1: nameSample quarterly access review
- Section 3 · PracticesOther privacy practice 1Implemented yes · Level 1 → 2
- Section 3 · PracticesOther privacy practice 2: nameSample portable device safeguards
- Section 3 · PracticesOther privacy practice 2Implemented yes · Level 1 → 2
- Section 3 · PracticesOther privacy practice 3: nameSample backup restore checks
- Section 3 · PracticesOther privacy practice 3Implemented yes · Level 2 → 3
- Section 4 · SharingBasic Identification & Contact InformationShare; Legal basis: Sample: limited service-contact data goes…
- Section 4 · SharingDemographic & Personal CharacteristicsN/A; Legal basis: Not provided
- Section 4 · SharingFinancial DataShare; Legal basis: Sample: payment and payroll information…
- Section 4 · SharingHealth and Medical InformationN/A; Legal basis: Not provided
- Section 4 · SharingEducation InformationN/A; Legal basis: Not provided
- Section 4 · SharingGovernment Program & Benefits DataN/A; Legal basis: Not provided
- Section 4 · SharingBiometric DataN/A; Legal basis: Not provided
- Section 4 · SharingOnline & Digital IdentifiersN/A; Legal basis: Not provided
- Section 4 · SharingCriminal or Legal InformationN/A; Legal basis: Not provided
- Section 4 · SharingVehicle & Property DataN/A; Legal basis: Not provided
- Section 4 · SharingPhotographic or Video DataN/A; Legal basis: Not provided
- Section 4 · SharingVoting & Civic DataN/A; Legal basis: Not provided
- Section 4 · SharingImmigration & Travel InformationN/A; Legal basis: Not provided
- Section 4 · SharingCommunication & Complaints DataShare; Legal basis: Sample: service correspondence may be…
- Section 4 · SharingOther data category: Other category 1N/A; Legal basis: Not provided
- Section 4 · SharingOther data category: Other category 2N/A; Legal basis: Not provided
- Section 4 · SharingOther data category: Other category 3N/A; Legal basis: Not provided
- Section 6 · Non-compliantProcessing activity 1Sample: legacy service form lacks a collection notice.
- Section 6 · Non-compliantStrategies for compliance 1Sample: CAO will add and review the notice by March 31, 2027.
- Section 6 · Non-compliantProcessing activity 2Sample: billing records lack privacy annotations.
- Section 6 · Non-compliantStrategies for compliance 2Sample: records officer will annotate the series by June 30,…
- Section 7 · High-risk useList any other processing activities the entity has identified as high-risk under the statutory definition and a brief description of the purposes and uses of each.Sample: no high-risk processing activities identified after…
- Section 8 · TrainingWhat percentage of the entity's employees who are required to complete data privacy training have completed data privacy training?75%
Approved 0
Each approved answer keeps its source. You can undo any of them from its panel until the report is approved.
Show 0 approved answers
19 optional questions left blank
Optional rows on the state form (extra activities, other categories). They are approved with the ready answers.
- Section 1 · Entity informationGovernmental entity: OtherNot answered
- Section 2 · Program statusOtherNot answered
- Section 5 · RecipientsPersonal Data Sold To:None selected
- Section 5 · RecipientsPersonal Data Purchased From:None selected
- Section 6 · Non-compliantProcessing activity 3Not answered
- Section 6 · Non-compliantStrategies for compliance 3Not answered
- Section 6 · Non-compliantProcessing activity 4Not answered
- Section 6 · Non-compliantStrategies for compliance 4Not answered
- Section 6 · Non-compliantProcessing activity 5Not answered
- Section 6 · Non-compliantStrategies for compliance 5Not answered
- Section 6 · Non-compliantProcessing activity 6Not answered
- Section 6 · Non-compliantStrategies for compliance 6Not answered
- Section 7 · High-risk useSelect all applicable high-risk processing activities the entity engages in and explain why the governmental entity engages in the high-risk processing activity.None selected
- Section 7 · High-risk useDescription of purpose: Facial recognition technologyNot answered
- Section 7 · High-risk useDescription of purpose: Automated decision makingNot answered
- Section 7 · High-risk useDescription of purpose: Profiling (e.g., behavioral or predictive analysis)Not answered
- Section 7 · High-risk useDescription of purpose: Genetic data processingNot answered
- Section 7 · High-risk useDescription of purpose: Biometric data processing (e.g., fingerprints, voice, iris scans)Not answered
- Section 7 · High-risk useDescription of purpose: Geolocation data processingNot answered