Responsible Technology and Data Privacy
Technology can improve communication, maintenance, registration, safety, and public access—but only when its purpose is clear, its risks are understood, and residents' rights are protected.
This campaign policy does not approve a vendor, surveillance system, software platform, artificial-intelligence product, or data-sharing agreement.
- ›Define the Public Purpose
- ›Collect Less Data
- ›Keep People Accountable
- ›Review Results and Risks
2026 FRRPD Campaign Research Brief
Useful Technology with Clear Limits
I support practical technology when it helps the district serve residents more effectively. That could include accessible registration, maintenance reporting, public project dashboards, emergency communication, facility scheduling, energy management, or carefully governed safety tools.
Technology should never be adopted simply because it is new. Before collecting data or automating a decision, the district should explain the problem, compare alternatives, understand the complete cost, evaluate privacy and cybersecurity, establish human responsibility, and determine how success will be measured.
Residents should know what information is collected, why it is needed, who can access it, how long it is kept, and how they can ask questions or report concerns.
A Responsible Review Process
A consistent process keeps technology purposeful and accountable.
Define the Problem
Explain the specific problem technology is meant to solve.
Consider Nontechnical Alternatives
Evaluate whether a non-technical solution would work as well or better.
Identify Data and System Requirements
Determine what data and systems are actually necessary.
Complete Required Reviews
Conduct privacy, accessibility, security, legal, and financial review.
Establish Contract Protections
Build procurement and contract safeguards before adoption.
Test Through a Pilot
Pilot the system on a limited basis when appropriate.
Require Human Oversight
Ensure trained human oversight of consequential decisions.
Publish and Reconsider
Publish results, incidents, changes, and renewal decisions.
Where Technology Could Help
These are categories to evaluate—not systems that currently exist unless verified.
- ›Registration and payments
- ›Facility scheduling
- ›Maintenance requests and asset management
- ›Public notices and emergency communication
- ›Websites and accessible digital services
- ›Project and financial dashboards
- ›Energy, irrigation, and facility controls
- ›Public Wi-Fi
- ›Safety technology
- ›Cameras and sensors
- ›Artificial intelligence and analytics
- ›Mobile applications
- ›Digital records and communications
These systems should not be claimed to currently exist unless verified.
Resident Data Belongs to Residents
Clear privacy principles protect trust before any system is adopted.
- ✓Collect only what is necessary.
- ✓Use data only for the disclosed purpose.
- ✓Limit access by role.
- ✓Establish documented retention and deletion.
- ✓Protect children and vulnerable users.
- ✓Do not sell personal information.
- ✓Do not use resident data for campaign purposes.
- ✓Disclose third-party sharing.
- ✓Provide a way to ask questions and report concerns.
- ✓Review privacy before renewal or expansion.
Coordinate Without Duplicating
This policy coordinates with the existing Smart Park Safety policy.
- ✓Cameras or analytics do not replace human judgment.
- ✓AI-generated alerts require trained human review before consequential action whenever practicable.
- ✓No system should be described as preventing all crime or emergencies.
- ✓Facial recognition, biometric identification, or broad person-tracking must not be added by implication.
- ✓Any such capability would require separate public, legal, privacy, accuracy, civil-rights, and security review before consideration.
- ✓Safety footage must not be reused for campaign content.
- ✓Access and retention must be governed and audited.
AI Needs Human Accountability
AI can help—but only with clear limits, testing, and human responsibility.
- ›Defined use case
- ›Human responsibility
- ›Accuracy testing
- ›Bias and error review
- ›Data-quality review
- ›Documentation
- ›Appeal or correction process where decisions affect a person
- ›Vendor transparency
- ›Security
- ›Accessibility
- ›Incident reporting
- ›Regular reevaluation
- ›Ability to stop use
AI recommendations or ratings should not be described as objective facts without disclosed methodology and human review.
Protect the Most Sensitive Information
Participant and especially children's data requires the strongest protections.
Protect
- ✓Names and contact information
- ✓Birth dates
- ✓Schools
- ✓Medical and accommodation information
- ✓Emergency contacts
- ✓Photographs and videos
- ✓Program registration
- ✓Payment data
- ✓Attendance and location information
- ✓Background-check information
Require access controls, purpose limits, secure storage, appropriate consent, and minimal retention.
Security Is Part of the Contract
Cybersecurity expectations belong in procurement and contracts—not as afterthoughts.
- ›Authentication
- ›Least-privilege access
- ›Encryption
- ›Backups
- ›Software updates
- ›Incident response
- ›Breach notification
- ›Vendor subcontractors
- ›Data location
- ›Data export
- ›Contract termination
- ›Secure deletion
- ›Service continuity
- ›Insurance
- ›Security testing
- ›Public-record obligations
A system should not be claimed as secure merely because a vendor says so.
Technology Must Not Leave People Behind
Digital services must include residents who cannot or choose not to use them.
- ✓WCAG-compatible services
- ✓Keyboard access
- ✓Screen-reader support
- ✓Clear error messages
- ✓Accessible documents
- ✓Language assistance where practical
- ✓Telephone or in-person alternatives for essential services
- ✓No exclusion of residents who lack devices, internet, banking, or technical skills
Show Residents What the District Uses
A public register builds transparency about the technology the district adopts.
For Each Entry
- ›System name
- ›Public purpose
- ›Department use
- ›Data categories
- ›Vendor
- ›Contract term
- ›Cost
- ›Retention
- ›Third-party sharing
- ›Security review
- ›Accessibility review
- ›Date last evaluated
- ›Contact for questions
This is an empty framework—no fabricated entries should be created.
A Practical Path Forward
Responsible technology develops in practical phases.
Inventory Systems and Data
- ›Catalog current systems
- ›Identify data collected
- ›Document vendors and contracts
- ›Map access and retention
Establish Standards
- ›Adopt privacy standards
- ›Adopt cybersecurity standards
- ›Set AI and accessibility rules
- ›Strengthen procurement protections
Review and Test
- ›Review high-risk systems
- ›Responsibly test improvements
- ›Confirm human oversight
- ›Document findings
Publish and Repeat
- ›Publish oversight information
- ›Report incidents and changes
- ›Renew, modify, or discontinue systems
- ›Repeat reviews regularly
Track Oversight, Not Just Adoption
Progress should be measured by responsible oversight—not by how much technology is installed.
- ✓Systems inventoried
- ✓Privacy reviews
- ✓Security reviews
- ✓Accessibility issues corrected
- ✓Data incidents
- ✓Response time
- ✓Staff training
- ✓Unnecessary data collection eliminated
- ✓Contracts with exit and deletion protections
- ✓Resident questions and complaints resolved
- ✓Pilot results
- ✓Systems renewed, modified, or discontinued
Connected Plans
“Technology should help the district serve people—not make decisions less understandable, collect information without purpose, or weaken public accountability.”
Dacoda E. Quinn
Candidate for Feather River Recreation and Park District Board of Directors · November 3, 2026
