rpriven
2095cb1951
- Interactive request generator with 20 state support - Quick state law lookup tool - Security-hardened input validation - Copy-paste templates for non-technical users - MIT licensed civic tech project
129 lines
4.8 KiB
Markdown
129 lines
4.8 KiB
Markdown
# Streamlined Flock Safety Public Records Request Template
|
|
|
|
## Quick Copy-Paste Version
|
|
|
|
```
|
|
[Date]
|
|
|
|
[Agency Name]
|
|
[Agency Address]
|
|
[City, State ZIP]
|
|
|
|
RE: Public Records Request - Flock Safety System
|
|
|
|
Dear Public Records Custodian:
|
|
|
|
This is a non-commercial public records request made pursuant to [Your State's Public Records Law - e.g., A.R.S. §39-121 for Arizona, C.R.S. §24-72-201 for Colorado].
|
|
|
|
I am requesting all records related to [Agency Name]'s relationship with Flock Group, Inc. (aka Flock Safety), including:
|
|
|
|
1. **Contracts & Agreements**: All contracts, amendments, intergovernmental agreements, and related documents between [Agency Name] and Flock Safety or any third parties regarding Flock products/services
|
|
|
|
2. **Financial Records**: Purchase orders, invoices, billing records, budgets, RFPs, bid responses, cost-benefit analyses, and funding sources (including grants)
|
|
|
|
3. **Policies & Procedures**: All policies, guidelines, procedures, or protocols (draft or final) regarding installation, operation, monitoring, data retention, data access, data sharing, or deletion
|
|
|
|
4. **Data Access Records**: Logs of all access requests (internal and external), data-sharing agreements, audit logs, and requests fulfilled or denied
|
|
|
|
5. **Meeting Records**: Minutes, agendas, notes, and presentations from meetings where Flock cameras or services were discussed
|
|
|
|
6. **Legal & Compliance**: Legal opinions, risk assessments, privacy impact assessments, compliance reviews, and related correspondence
|
|
|
|
7. **Technical Documentation**: System specifications, cybersecurity measures, data storage locations, interoperability documentation, and breach notifications
|
|
|
|
8. **Data Retention**: Policies on retention timeframes, deletion procedures, and actual deletion logs
|
|
|
|
9. **Training Materials**: Manuals, training materials, installation records, photographs, videos, and communications (emails, notes, etc.)
|
|
|
|
⚠️ **TIME-SENSITIVE**: Due to Flock Safety's 30-day data retention policy, I request expedited processing to preserve any relevant data that may be automatically deleted.
|
|
|
|
Please provide records in electronic format if available. If any portions are denied, please provide a written explanation citing the specific legal exemption.
|
|
|
|
I request that you respond within [timeframe based on state law - e.g., "promptly as required by A.R.S. §39-121" or "10 business days as required by C.R.S. §24-72-203(3)(b)"].
|
|
|
|
Thank you for your attention to this matter.
|
|
|
|
Sincerely,
|
|
|
|
[Your Name]
|
|
[Your Address]
|
|
[Your Email]
|
|
[Your Phone]
|
|
```
|
|
|
|
---
|
|
|
|
## State-Specific Response Time References
|
|
|
|
**No specific deadline (respond "promptly"):**
|
|
- Arizona (A.R.S. §39-121)
|
|
- Others as applicable
|
|
|
|
**3 days or less:**
|
|
- Arkansas: 3 days
|
|
- Vermont: 2 days
|
|
- Several others: 3 days
|
|
|
|
**5 days:**
|
|
- California: 10 days
|
|
- Illinois: 5 days
|
|
- Pennsylvania: 5 days
|
|
- Virginia: 5 days
|
|
- West Virginia: 5 days
|
|
|
|
**10 days:**
|
|
- Colorado: 10 business days (C.R.S. §24-72-203)
|
|
- Iowa: 10-20 days
|
|
- South Carolina: 10 days (20 if >24 months old)
|
|
|
|
**15 days:**
|
|
- Delaware: 15 days
|
|
- DC: 15 days
|
|
- Michigan: 15 days
|
|
|
|
**20 days:**
|
|
- Federal FOIA: 20 days
|
|
- Maryland: 30 days
|
|
|
|
---
|
|
|
|
## Important Notes
|
|
|
|
### Critical Timing Issue
|
|
⏱️ **Flock Safety deletes all data after 30 days** on a rolling basis. If your request is delayed or denied initially, specific footage may be permanently deleted. Request expedited processing and follow up immediately.
|
|
|
|
### What This Request Will Get You
|
|
|
|
✅ **Likely to receive:**
|
|
- Contracts and pricing
|
|
- Policies and procedures
|
|
- Meeting minutes and financial records
|
|
- Training materials and documentation
|
|
|
|
⚠️ **May require legal challenge:**
|
|
- Actual camera footage/images (courts have ruled both ways)
|
|
- Your own vehicle data (strongest legal argument)
|
|
- Data about other vehicles (usually denied on privacy grounds)
|
|
|
|
### Tips for Success
|
|
|
|
1. **Be specific about your state's law** - Don't use "FOIA" for state requests
|
|
2. **Request electronic format** - Faster and often free
|
|
3. **Follow up in writing** - Document all communications
|
|
4. **Know your state's fee structure** - Many states charge for copies
|
|
5. **Request fee waiver if applicable** - Public interest exemptions may apply
|
|
6. **Act quickly** - 30-day deletion window is real
|
|
7. **Be prepared to appeal** - Many requests require administrative appeals
|
|
|
|
### Recent Legal Wins
|
|
|
|
Courts have increasingly ruled that Flock data is subject to public records laws:
|
|
- **Virginia 2025**: Cardinal News won FOIA battle for Flock footage
|
|
- **Washington 2025**: Judge ordered police to release surveillance camera data
|
|
- **General principle**: FOIA/public records law trumps vendor contracts
|
|
|
|
### Requesting Your Own Vehicle Data
|
|
|
|
🎯 **Strongest legal argument**: Request footage of YOUR OWN vehicle for specific dates/times you traveled through areas with Flock cameras.
|
|
|
|
This approach has the highest success rate and clearest legal backing.
|