C.L.O.C.K. Accountability · Source Documents
Flock in Appling County: Source Documents
Redacted correspondence reading copies, audit provenance, calculations, source locators, and research limits supporting the article. Agency statements are distinguished from requester statements and independent research.
Requests and correspondence
August 19–September 18, 2026 · Redacted reading copies retained from the September 26 source package.
These reading copies omit personal contact information, technical routing headers, and repeated quoted chains. Original email evidence remains preserved privately. Requester statements and official responses are distinguished by their source captions.
S1 · August 19, 2026, 07:44:05 AM EDT · Georgia Open Records Request — ALPR / Flock Acquisition, Procurement, and Implementation Records
To the Open Records Officer / Custodian of Records:
Pursuant to the Georgia Open Records Act, O.C.G.A. §§ 50-18-70 et seq., I request electronic copies of the following existing records maintained by or on behalf of the Appling County Sheriff’s Office concerning automated license plate reader or license plate recognition technology (“ALPR/LPR”), including Flock Safety/Flock Group systems.
Date range: January 1, 2023 through the date of this request.
This request seeks:
1. Vendor solicitation and acquisition records, including proposals, quotes and quotations, estimates, bids, sales proposals, order forms, purchase orders, contracts, agreements, statements of work, amendments, addenda, renewal documents, and cancellation or termination documents.
2. Invoices and payment-related records maintained by the Sheriff’s Office, including vendor invoices, receipts, payment requests, purchase requisitions, documentation identifying the account or funding source from which an ALPR/LPR expenditure was to be paid, and records reflecting recurring subscription, service, maintenance, connectivity, hosting, or licensing costs.
3. Funding records, including existing records identifying whether ALPR/LPR equipment or services were funded in whole or in part through county appropriations, Sheriff’s Office funds, state or federal grants, asset forfeiture funds, donations, private funding, intergovernmental funding, or any other funding source. This includes grant applications, grant awards, reimbursement requests, award notices, or other existing records specifically concerning funding for ALPR/LPR equipment or services.
4. Approval and authorization records, including existing records reflecting approval or authorization to acquire, purchase, lease, subscribe to, install, deploy, or renew ALPR/LPR equipment or services.
5. Installation and deployment records, including installation work orders, deployment records, installation completion records, records identifying the number of ALPR/LPR units acquired or deployed, records identifying installation or activation dates, and permits, approvals, applications, or correspondence with the Georgia Department of Transportation concerning installation of ALPR/LPR equipment.
6. Vendor agreements governing the service or data, including terms of service, master service agreements, data ownership provisions, data retention provisions, data-sharing provisions, agency-access agreements, network or nationwide-search participation agreements, and agreements permitting another governmental entity to access Appling County Sheriff’s Office ALPR/LPR data or permitting the Sheriff’s Office to access another entity’s ALPR/LPR data.
7. Records sufficient to identify the ALPR/LPR system currently operated or available for use by the Appling County Sheriff’s Office, including vendor, product or service, number of units, original acquisition or activation date, current contract or subscription term, and current recurring cost.
For purposes of identifying responsive records, relevant terms may include, but are not limited to: “ALPR,” “LPR,” “automated license plate reader,” “automatic license plate reader,” “automated license plate recognition,” “license plate reader,” “license plate recognition,” “Flock,” “Flock Safety,” and “Flock Group.”
This request seeks existing records only and does not request that the Sheriff’s Office create a new report, compilation, or analysis.
FORMAT AND COST
Electronic copies are preferred in their native electronic format where practicable. There is no need to print records that already exist electronically.
If responsive records are already organized by vendor, contract, purchase order, invoice, grant, or similar file structure, please produce those existing records rather than conducting a broader search than necessary.
If fulfilling this request is expected to result in charges, please provide a written itemized estimate before incurring costs exceeding $25.00, identifying the anticipated search, retrieval, redaction, or production work and the hourly rate to be charged.
If narrowing or clarifying a particular portion of this request would materially reduce the anticipated cost, please identify that portion before undertaking substantial search or retrieval work so that I may consider narrowing it.
If any responsive record or portion of a record is withheld or redacted, please identify the specific statutory authority, including Code section, subsection, and paragraph, relied upon for the withholding or redaction, and produce all reasonably segregable non-exempt portions.
If responsive records are maintained by a private vendor or other entity on behalf of the Sheriff’s Office, please include those records to the extent they constitute public records under Georgia law.
If no responsive records exist for a particular numbered category above, please state that no responsive records were located for that category.
Thank you,
[requester name redacted]
S2 · August 19, 2026, 07:46:49 AM EDT · Georgia Open Records Request — ALPR / Flock Policies, Procedures, Training, and Governance
To the Open Records Officer / Custodian of Records:
Pursuant to the Georgia Open Records Act, O.C.G.A. §§ 50-18-70 et seq., I request electronic copies of existing policies, procedures, rules, directives, training materials, and governance records maintained by or on behalf of the Appling County Sheriff’s Office concerning automated license plate reader or license plate recognition technology (“ALPR/LPR”), including Flock Safety/Flock Group systems.
For policies and similar governance documents, this request seeks the current version and any prior or superseded version maintained by the agency that was in effect at any time from January 1, 2023 through the date of this request.
In particular, please include any policy, procedure, general order, directive, or other written governance document that was in effect when the Appling County Sheriff’s Office first began operating or using ALPR/LPR technology, if such a record exists.
Specifically, I request:
1. ALPR/LPR policies and procedures, including any policies; standard operating procedures (SOPs); general orders; special orders; directives; rules; written protocols; manuals; or written instructions governing ALPR/LPR use.
2. Authorized-use rules, including existing records addressing permissible purposes for ALPR/LPR searches; prohibited uses; requirements to establish or document a law-enforcement purpose; restrictions on personal or non-law-enforcement use; investigative-use requirements; and approval required before conducting particular types of searches.
3. User access and account controls, including policies or procedures governing who may access the ALPR/LPR system; creation or approval of user accounts; user permission levels; account termination; authentication requirements; supervisory access; and access by persons outside the Appling County Sheriff’s Office.
4. Search and query procedures, including policies, procedures, or instructions concerning plate-number searches; vehicle searches; location or geographic searches; historical searches; investigative queries; search justification or reason codes; documentation of search purposes; and restrictions governing searches involving persons who are not suspects in criminal investigations.
5. Hot lists, watch lists, alerts, and notifications, including policies or procedures governing entry of vehicles or license plates into hot lists or watch lists; criteria required for entry; approval requirements; expiration or removal; alert recipients; response to an ALPR/LPR alert; verification of an alert before enforcement action; and documentation associated with alerts.
6. Data retention and deletion, including policies or procedures establishing retention periods; automatic deletion periods; preservation of data for investigations; extension of retention periods; downloading or exporting ALPR/LPR data; and destruction or deletion of exported data.
7. Data sharing and external access, including policies, procedures, or agreements governing sharing ALPR/LPR data with another law-enforcement agency; sharing with federal, state, local, or out-of-state agencies; access through regional, statewide, or nationwide ALPR networks; requests from other agencies; approval of external agency access; revocation of shared access; and restrictions on redisclosure.
8. Audit, accountability, and supervisory review, including policies or procedures concerning logging of user activity; search or query audit logs; periodic audits; supervisory review; compliance reviews; detection of unauthorized use; investigation of suspected misuse; and documentation or reporting of policy violations.
9. Training requirements and materials, including ALPR/LPR training policies; training presentations; training manuals; written training materials; vendor-provided training materials maintained by the Sheriff’s Office; user certification requirements; written acknowledgments required before receiving access; and refresher-training requirements.
10. Misuse and disciplinary provisions, including policies, procedures, directives, or written rules addressing unauthorized searches; personal use; improper disclosure; unauthorized sharing; credential sharing; policy violations; and suspension or revocation of ALPR/LPR access.
11. Vendor-provided governance requirements maintained or used by the Sheriff’s Office, including acceptable-use policies; user agreements; agency agreements; search-use requirements; privacy or data-use rules; data-sharing controls; audit requirements; and other vendor rules Sheriff’s Office personnel are expected or required to follow when using the ALPR/LPR system.
12. Records reflecting adoption or revision of ALPR/LPR governance, including existing approval pages; effective-date pages; revision histories; policy-change notices; directives implementing or modifying ALPR/LPR procedures; and records identifying the effective date of a current or superseded ALPR/LPR policy.
13. Records sufficient to establish the governance timeline, specifically the effective date of the first written ALPR/LPR policy, procedure, general order, directive, or equivalent governance document; any subsequent effective or revision dates; and any existing record identifying when ALPR/LPR users were first required to acknowledge, receive training on, or comply with such policies.
For purposes of identifying responsive records, relevant terms may include, but are not limited to: “ALPR,” “LPR,” “automated license plate reader,” “automatic license plate reader,” “automated license plate recognition,” “license plate reader,” “license plate recognition,” “Flock,” “Flock Safety,” and “Flock Group.”
This request seeks existing records only. It does not request that the Sheriff’s Office create a policy, report, explanation, summary, compilation, or analysis that does not presently exist.
If ALPR/LPR operation is governed wholly or partly by a broader Sheriff’s Office policy—for example, a criminal-intelligence, investigative-database, information-security, records-retention, data-sharing, surveillance-technology, or law-enforcement-database policy—please produce the responsive existing policy or responsive portions thereof.
FORMAT AND COST
Electronic copies are preferred in their native electronic format where practicable. There is no need to print records that already exist electronically.
If fulfilling this request is expected to result in charges, please provide a written itemized estimate before incurring costs exceeding $25.00, identifying the anticipated search, retrieval, redaction, or production work and the hourly rate to be charged.
If narrowing or clarifying a particular portion of this request would materially reduce the anticipated cost, please identify that portion before undertaking substantial search or retrieval work so that I may consider narrowing it.
If any responsive record or portion of a record is withheld or redacted, please identify the specific statutory authority, including Code section, subsection, and paragraph, relied upon for the withholding or redaction, and produce all reasonably segregable non-exempt portions.
If responsive governance records are maintained by a private vendor on behalf of the Sheriff’s Office or are vendor-created records received and maintained by the Sheriff’s Office in connection with operation of the system, please include those responsive records to the extent they constitute public records under Georgia law.
If no responsive records exist for a particular numbered category above, please state that no responsive records were located for that category.
Thank you,
[requester name redacted]
S3 · August 20, 2026, 03:46:17 PM EDT · Open Records Request
We have received the attached request and we are working on providing you with all available information.
Thank You!
S4 · August 25, 2026, 02:24:46 PM EDT · Flock Camera ORR
[requester name redacted],
Please find attached a copy of the FLOCK policy.
In response to your request:
1. This would be covered by the copy of our FLOCK Policy
2. This would also be covered by the copy of our Flock Policy
3. N/A this is determined by the flock admin staff on who has access to our system.
4. See policy.
5. N/A
6. Retention is set by the FLOCK system, original retention is only 30 days and via updates is being changed to 7 days unless the information is tagged for evidence and would be on a case by case basis.
7. N/A
8. N/A we have had no suspected or known misuse or policy violations to date. Periodic review of Flock is done Monthly by an administrator.
9. Training was conducted by webinar for staff by FLOCK staff. I do not have the dates and times on this.
10. See Policy, also we have had no misuse to date
11. N/A
12. N/A
13. N/A
If you have any further questions or concerns, you can contact our office.
Thank You!
Appling County Sheriff’s Office
912-367-8120
S5 · August 25, 2026, 02:33:19 PM EDT · Flock Camera ORR
Please find attached the FLOCK policy. The one sent in the previous response did not have both sides of that policy.
S6 · August 31, 2026, 08:07:38 AM EDT · Deficiency Notice and Request for Completion — August 19, 2026 ALPR / Flock Open Records Requests
Open Records Officer,
I have now had time to carefully compare my two August 19 Flock/ALPR requests with the Sheriff’s Office’s August 20 acknowledgment, the August 25 response, the policy that was first sent, and the corrected two-page policy that followed.
After doing that comparison, there are several things I need the Sheriff’s Office to clear up and several portions of the original requests that still appear to be unresolved.
For reference, I sent two separate requests on August 19:
[Intervening text omitted; access-controls paragraph follows]
The response says access is determined by “flock admin staff.” The News-Banner article separately attributes to Sheriff Melton a written policy concerning who may enter information into the system and reports that eight people were then authorized, with that number being reduced by two.
S7 · August 31, 2026, 01:37:47 PM EDT · RE: Deficiency Notice and Request for Completion — August 19, 2026 ALPR / Flock Open Records Requests
Originally I, the Open Records Custodian, had not received Request 1 about “ALPR / Flock Acquisition, Procurement, and Implementation Records”.
This request has now been received and I will work on providing that information to you; as well as working on addressing your concerns with Request 2 “ALPR / Flock Policies, Procedures, Training, and Governance”.
S8 · September 14, 2026, 09:27:12 AM EDT · RE: Deficiency Notice and Request for Completion — August 19, 2026 ALPR / Flock Open Records Requests
Open Records Officer,
I am following up regarding my two August 19, 2026 Georgia Open Records Act requests concerning the Appling County Sheriff’s Office’s Flock/ALPR system and my August 31, 2026 Deficiency Notice and Request for Completion.
On August 31, you responded:
“Originally I, the Open Records Custodian, had not received Request 1 about ‘ALPR / Flock Acquisition, Procurement, and Implementation Records’.
This request has now been received and I will work on providing that information to you; as well as working on addressing your concerns with Request 2 ‘ALPR / Flock Policies, Procedures, Training, and Governance’.”
I appreciate that acknowledgment. However, I have received no subsequent production, production schedule, fee estimate, exemption notice, or other disposition of the outstanding portions of either request.
O.C.G.A. § 50-18-71(b)(1)(A) requires responsive records to be produced within three business days after receipt where they are available. Where responsive records exist but are not available for production within three business days, the Act requires the agency, within that period, to provide a description of the records and a timeline for when they will be available, and thereafter to provide the records or access to them as soon as practicable.
Request 1 was expressly acknowledged as received by the Open Records Custodian on August 31. Your same response expressly stated that the Sheriff’s Office would work on addressing the outstanding matters concerning Request 2.
Fourteen calendar days have now elapsed since that acknowledgment. I have received neither the outstanding responsive records nor a description and production timeline for responsive records that could not be produced within the statutory period.
My August 31 correspondence already identified in detail what remained unresolved under both requests. I will not repeat those categories here. This follow-up does not expand, modify, replace, or restart either original request or my August 31 deficiency/completion notice.
Please complete the outstanding response in accordance with the Georgia Open Records Act.
For each outstanding category, please either produce the responsive existing records; clearly state that no responsive records were located; identify or describe responsive records that require additional production time and provide the applicable production timeline; or, for any records or portions of records being withheld, identify the specific statutory authority supporting the withholding.
My prior authorization for charges up to $25.00 remains unchanged.
If the estimated cost of fulfilling either request exceeds $25.00, please provide the written estimate required by O.C.G.A. § 50-18-71(d) before undertaking chargeable work exceeding that authorization.
Any such estimate should clearly identify the statutory basis for the charges and provide sufficient itemization for me to determine how the estimate was calculated, including, as applicable, the estimated administrative time, hourly rate used, applicable no-charge period, copying or production charges, and any other component included in the estimated total. If charges are attributed to search, retrieval, redaction, copying, or other administrative work, please identify the applicable statutory basis for those charges.
I am not authorizing charges exceeding $25.00 unless and until I receive and approve the required estimate.
Electronic production remains preferred in native electronic format where practicable.
Please treat this correspondence solely as a request for completion of the two existing August 19 requests and the outstanding matters identified in my August 31 correspondence. It is not a new Open Records Act request and does not reset the dates associated with the existing requests.
Thank you,
[requester name redacted]
S9 · September 15, 2026, 01:20:51 PM EDT · RE: Deficiency Notice and Request for Completion — August 19, 2026 ALPR / Flock Open Records Requests
[requester name redacted],
Please find the attached documents as a revised response to your request “ALPR/Flock Policies, Training, Governance”. I have also attached our Policies and Procedures Cover Page, Index, and Policy Statement #28.
Please note for any additional information regarding the webinars, those records are maintained by FLOCK and you can request dates and times through them; our office does not maintain those records.
Thank You!
S11 · September 18, 2026, 09:48:26 AM EDT · RE: Deficiency Notice and Request for Completion — August 19, 2026 ALPR / Flock Open Records Requests
Open Records Officer,
I am following up on the September 15, 2026 revised response to my August 19 request, “ALPR / Flock Policies, Procedures, Training, and Governance.”
Your revised response materially clarified one point: ACSO states that “We did not have a policy set in place until July 28, 2026. There were no prior policies before this date in regards to the FLOCK Cameras.” I will preserve that as ACSO’s representation concerning the absence of a prior Flock-specific policy. It does not, however, establish when the Flock system first became operational or when ACSO first began using it.
That distinction matters. My existing requests seek records sufficient to establish the governance and implementation timeline, including when the system was acquired, installed, activated, accessed, searched, used for alerts, or otherwise placed into operational use. Please produce the existing responsive records that establish the earliest operational/activation date. If no such records are maintained by ACSO, please state that clearly. This is a request for completion of the existing August 19 requests, not a new request.
I also need to address the statement in your September 15 email that webinar records “are maintained by FLOCK” and that I can request dates and times through Flock because ACSO does not maintain those records.
That does not resolve the existing request. O.C.G.A. § 50-18-71(a)(2)(B) expressly requires a custodian responding to an Open Records Act request to retrieve qualifying public records prepared and maintained or received by a private person or private entity in the performance of a service or function for or on behalf of the agency. O.C.G.A. § 50-18-71(h) further requires an agency that contracts with a private vendor to collect or maintain public records to ensure that the arrangement does not limit public access or permit the vendor to impede access.
Accordingly, please do not direct me to submit a separate request to Flock Safety for qualifying records maintained by Flock for or on behalf of ACSO. Please retrieve and produce those responsive records through ACSO’s response.
This applies not merely to webinar dates and times, but to qualifying existing records within the scope of the August 19 governance request that are maintained by Flock for or on behalf of ACSO, including, as applicable, training/course and completion records; account, role, permission, access-control and account-change records; retention configuration and change records; alert/watch-list procedures or configuration records; sharing/network-participation and access-revocation records; and audit/review logs, reports, or related records.
I am not requesting Flock Safety’s unrelated proprietary or internal corporate records, nor am I asking ACSO to create a new report or compilation.
For each remaining category, please produce the responsive records; state clearly that no responsive records were located after the required search and retrieval, including qualifying contractor-held records; provide the applicable production timeline if responsive records exist but are not yet available; or identify the specific statutory authority for any withholding.
The existing $25.00 authorization remains unchanged. If ACSO will seek costs exceeding $25.00, please provide the estimate required by O.C.G.A. § 50-18-71(d) before undertaking chargeable work beyond that authorization.
Thank you,
[requester name redacted]
S12 · September 18, 2026, 09:48:50 AM EDT · Outstanding Request 1 — ALPR / Flock Acquisition, Procurement, and Implementation Records
Open Records Officer,
I am writing separately to address the still-outstanding August 19, 2026 request titled “ALPR / Flock Acquisition, Procurement, and Implementation Records.”
On August 31, 2026, you expressly stated that you had not originally received this request, that it had then been received, and that you would work on providing the requested information. My September 14 follow-up again identified Request 1 as outstanding.
The September 15 production expressly identified itself as a revised response to the separate “ALPR/Flock Policies, Training, Governance” request. I have located no substantive production, no-record determination, exemption notice, fee estimate, or production schedule disposing of the acquisition/procurement/implementation request.
Please complete Request 1.
That request contains seven existing-record categories concerning the acquisition and implementation of the Flock system, including vendor acquisition records; invoices and recurring costs; funding source(s); approval and authorization records; installation/deployment records; vendor, service, subscription, and data agreements; and records sufficient to identify the system, number of units, acquisition or activation dates, current contract/subscription term, and recurring cost.
The operational timeline is now particularly material because ACSO’s September 15 revised governance response states that no Flock-camera policy existed before July 28, 2026. That statement establishes ACSO’s position concerning its policy history; it does not establish when the system was first installed, activated, accessed, or used. The acquisition/implementation records should establish that timeline without requiring ACSO to create a new narrative.
O.C.G.A. § 50-18-71(b)(1)(A) requires responsive records to be produced within a reasonable time not exceeding three business days after receipt when available. Where responsive records exist but are unavailable within that period, the agency must provide a description of the records and a timeline for availability within the statutory response period, and then provide the records or access as soon as practicable.
Please provide a complete disposition of each of the seven categories: produce the responsive existing records; state clearly where no responsive records were located; identify responsive records that remain to be produced and provide the production timeline; or identify the specific statutory authority for any withholding.
My authorization for charges up to $25.00 remains unchanged. If ACSO will seek costs exceeding $25.00, please provide the written estimate required by O.C.G.A. § 50-18-71(d) before undertaking chargeable work beyond that authorization. The estimate should identify the statutory basis for the charges and provide sufficient itemization to show how the total was calculated, including, as applicable, estimated administrative time, hourly rate, the no-charge first quarter hour, copying or production charges, and any other component of the estimate.
I am not authorizing charges exceeding $25.00 unless and until I receive and approve that estimate.
This correspondence seeks completion of the existing August 19 request. It does not expand, replace, or restart that request.
Thank you,
[requester name redacted]
S13 · September 18, 2026, 03:59:36 PM EDT · RE: Outstanding Request 1 — ALPR / Flock Acquisition, Procurement, and Implementation Records
We have not finished gathering information for this request, we will send back a response once all 7 categories have been completed.
Two separate completion demands
October 3, 2026 · Sent copies verified.
Request 1: completion demand sent October 3, 6:42 p.m. Eastern
Request 1 — Demand for rolling production and a definite completion schedule — August 19 Flock acquisition request
Sent separately to the Sheriff’s Office records address and Sheriff Melton. This is a reading copy of the approved outgoing text. The retained send record documents review of the Gmail sent copy and recipient headers. Sent status does not establish delivery, reading, or acknowledgment.
Sheriff Melton and Sara Taylor, This email concerns my August 19, 2026 request titled “ALPR / Flock Acquisition, Procurement, and Implementation Records,” consisting of seven numbered categories. Please respond separately to this request so its disposition is clear. You acknowledged receipt on August 31. I followed up on September 14 and again on September 18, requesting production and a timeline for any responsive records that remained unavailable. Your September 18 reply stated: “We have not finished gathering information for this request, we will send back a response once all 7 categories have been completed.” That statement supplies neither a description of the remaining records nor a production timeline. “Once all 7 categories have been completed” identifies no dates and leaves the request open-ended. It does not satisfy the timeline requirement in O.C.G.A. § 50-18-71(b)(1)(A). The same provision requires release of records that can be located and produced within the response period even when others remain unavailable. Please produce available responsive records now and continue rolling production as additional records become available. Do not hold available records until all seven categories are finished. Your office has had repeated opportunities to provide the required production timeline. Despite my follow-ups, that timeline remains missing. Because your office has failed to provide it, I am now forced to set out specific dates for resolving this request. I am demanding the following schedule: 1. By 5:00 p.m. Eastern on Wednesday, October 7, 2026: produce all responsive records currently available and provide a separate disposition for each of the seven original categories. 2. By 5:00 p.m. Eastern on Friday, October 9, 2026: complete production of the remaining responsive records. 3. If you contend that particular records cannot be produced by October 9, identify them in the October 7 response, explain the specific obstacle, and provide a firm calendar date for production of each remaining category or batch. Continue rolling production in the meantime. For each category, identify the records produced and those remaining. Clearly state where no responsive records were located. For withheld or redacted material, identify the exemption by Code section, subsection, and paragraph, and produce the non-exempt portions. Your office is a law-enforcement agency. The public should be able to expect it to follow Georgia’s public-records law without repeated demands for a basic production schedule. This prolonged absence of a definite timeline undermines transparency and public confidence. These demanded dates do not extend the statutory obligations, restart the August 19 request, or expand its scope. Electronic production remains preferred in native format where practicable. My existing $25 fee authorization remains unchanged; obtain my approval before exceeding it. Another statement that information is still being gathered, without records and a definite schedule, will not resolve this request. Please reply in the acquisition-request thread with the production and category-by-category disposition. [requester name redacted] C.L.O.C.K. Accountability
Request 2: completion demand sent October 3, 6:44 p.m. Eastern
Request 2 — Demand for completion, contractor-held records, and rolling production — August 19 Flock governance request
Sent separately to the Sheriff’s Office records address and Sheriff Melton. This is a reading copy of the approved outgoing text. The retained send record documents review of the Gmail sent copy and recipient headers. Sent status does not establish delivery, reading, or acknowledgment.
Sheriff Melton and Sara Taylor, This email concerns my August 19, 2026 request titled “ALPR / Flock Policies, Procedures, Training, and Governance,” consisting of thirteen numbered categories. Please respond separately to this request so its disposition is clear. Your revised response delivered September 15 supplied a policy and other documents, but did not resolve the outstanding matters identified in my completion correspondence. My September 18 follow-up specifically addressed those deficiencies and retrieval of qualifying records maintained by Flock on the office’s behalf. I have located no subsequent response to that follow-up. I requested production and a timeline in my September 14 correspondence and again in the September 18 governance follow-up. Your office has had repeated opportunities to identify any remaining responsive records and provide a definite production schedule. The outstanding matters still require a complete disposition. Please complete the search and retrieval within the original thirteen categories, including the unresolved matters concerning access controls, training, retention, sharing, audits and reviews, and the governance timeline. Your revised response states that no Flock camera policy was in place before July 28, 2026. It also describes webinar training, monthly reviews, and retention changing from thirty days to seven days while reporting that supporting records or written documentation were not located for those matters. Please complete the response concerning responsive existing records supporting those statements and any broader agency policies that governed earlier use, as requested originally. Your September 15 email said that webinar records were maintained by Flock and that I could request dates and times from the company because your office did not maintain them. That referral does not resolve the agency’s retrieval obligation for qualifying public records. O.C.G.A. § 50-18-71(a)(2)(B) requires retrieval of qualifying private-entity-held public records, subject to its retention provisions. Section 50-18-71(h) requires vendor arrangements to preserve public access. Please obtain and produce responsive records Flock maintains for or on behalf of your office within the existing request’s scope. For any responsive existing records that remain unavailable, § 50-18-71(b)(1)(A) requires a description and production timeline. Available records should be released while the remainder is pending. I expressly request rolling production as additional responsive records become available. Because the outstanding matters remain unresolved despite repeated follow-ups, I am now forced to set out specific dates for completing this request: 1. By 5:00 p.m. Eastern on Wednesday, October 7, 2026: produce available outstanding records and provide a disposition for every unresolved original category, including the status of qualifying contractor-held records. 2. By 5:00 p.m. Eastern on Friday, October 9, 2026: complete production of the remaining responsive records. 3. If you contend that particular records cannot be produced by October 9, identify them in the October 7 response, explain the specific obstacle, and provide a firm calendar date for each remaining category or batch. Continue rolling production in the meantime. Clearly identify records produced and still pending. Where no responsive records were located, state that after completing the required search and retrieval. For withheld or redacted material, identify the exemption by Code section, subsection, and paragraph, and produce the non-exempt portions. A law-enforcement agency should set an example of compliance with state law. Having to repeatedly pursue basic records, vendor retrieval, and a production schedule raises serious concerns about the office’s transparency. This seeks completion of the existing request and does not expand or restart it. The demanded dates do not extend the statutory obligations. Electronic production remains preferred in native format where practicable. My existing $25 fee authorization remains unchanged; obtain my approval before exceeding it. Please provide a substantive completion response in the governance-request thread. Another referral to Flock or open-ended assurance that work is continuing will not resolve the outstanding request. [requester name redacted] C.L.O.C.K. Accountability
Independent network-audit source
C.L.O.C.K. source notes, rechecked September 26, 2026. This material was obtained independently, not produced by Appling in response to these requests.
Source: MuckRock request 186694, source listing; file listed May 27, 2025: full network-audit CSV.
SHA-256 of the preserved full CSV: fdd7b470d27e99983aebe024736bd5b97d656d17213dc1472b1d717ccb646aae. A fingerprint identifies the file checked, not the truth or completeness of its contents.
The full file contains four records naming Appling County GA SO. Download the derived four-row extract. Record numbers count the header as record 1; embedded line breaks mean these are not physical text-line numbers.
| CSV record | Search Time (UTC) | Recorded reason |
|---|---|---|
| 245726 | April 22, 2025, 15:44:15 | Investigation |
| 267690 | April 22, 2025, 15:59:12 | Investigation |
| 57839 | April 22, 2025, 17:21:15 | Investigation |
| 281092 | April 23, 2025, 21:06:08 | Drug+Arrest |
The earliest Search Time is April 22, 2025, at 15:44:15 UTC = 11:44:15 a.m. EDT (UTC minus four hours). July 28, 2026 minus April 22, 2025 = 462 elapsed calendar days. The April 15 beginning of a Time Frame field is the period searched, not proof of activity on April 15.
These records support attribution to the named agency, not an independent identification of the operator. They do not establish camera activation, first-ever use, continuous use, successful detections, case outcomes or misuse. No complete lifetime search count is asserted.
Have I Been Flocked was the discovery route. See the October 3 statistics snapshot and research limits, the live statistics page, and the audit-log explanation.
SOURCE VERIFICATION AND REVIEW LIMITS — OCTOBER 3, 2026
Research notes supporting this article; not native evidence or a complete live-system audit. Have I Been Flocked: https://haveibeenflocked.com/pd/7116-appling-county-ga-so/stats Live browser statistics displayed 768 unique searches, earliest April 22, 2025, latest July 20, 2026; 538 no-case-number searches; last statistics update October 3, 12:20 p.m. EDT. The page displayed: Data import started Oct 3, 8:01 PM is in progress. Some data may be incomplete until the import finishes. The notice itself did not state a time zone. https://haveibeenflocked.com/pd/7116-appling-county-ga-so/audit The agency audit explanation identifies searches performed BY Appling, most recent agency-record import August 8, 2026, generally nationwide searches seen in records released by other agencies. It does not purport to be a complete local/statewide/lifetime history. The earlier review read blank date filters. Current refresh again displayed July 20 as latest activity. 768 is a dated snapshot, not a settled current or lifetime total. 538 / 768 * 100 = 70.0520833333 percent, rounded to one decimal = 70.1 percent. The available audit row count (775) includes display/repeat distinctions and is not equated with unique searches. Account totals were not used. Institute for Justice: https://ij.org/the-ij-database-of-alpr-abuse/ Live visible State combobox set to Georgia; Type set to All types; 82 incidents shown. Counted the camera field in the filtered visible incident list: Flock 81; Unspecified 1; sum 82. Incidents are not a statewide count of arrests, unique officers, convictions, or independently adjudicated cases. The displayed Georgia incident list was used for this count. No current complete official count of 73 Georgia officers arrested and charged was confirmed. Correspondence: Bounded October 3 Gmail review used in:anywhere (including Spam and Trash), Flock/ALPR/name/domain searches and the two request threads. No later agency Flock response was located in those searches. This does not certify other accounts, channels, unknown senders, or messages outside the queries. Search methods and original review notes remain privately retained. The two approved October 3 demands were sent separately at 6:42 and 6:44 p.m. Eastern. Gmail sent-copy headers, bodies, and the two-conversation sent-folder result were checked. Those checks do not prove recipient delivery or acknowledgment. Private mailbox URLs, personal email addresses, and confirmation screenshots are excluded from this public source collection. Preserved source records: The revised governance letter is dated August 31 and was delivered September 15. Policy Statement #28 is dated July 28. Initial no-misuse assurance is August 25, not the revised letter date or delivery date. Existing four-row derived audit extract was re-read; the previous source review recorded full original-file reconciliation on September 26. This review did not re-acquire or independently reconcile every row underlying the live aggregate. Original source filename: Mount_Prospect_IL_PD_Network_Audit_4_16_2025_5_1_2025.csv. Source record 245726 counts the header as record 1. Org Name Appling County GA SO, April 22, 2025 at 15:44:15 UTC; scope 6,248 networks and 80,271 devices. Scope is not detections, query results, or proof of misuse. Legal and publication limits: Code reproductions and cited judicial opinions were checked in this review. Analysis of the missing timeline is a source-based compliance assessment, not a court ruling. No criminal guilt, intent to conceal, local Flock misuse, first-public-disclosure date, or absence of all broader policies is established. Current requests sought existing records; the governance access category did not expressly demand a named user roster. Questions asking for additional public explanations are distinguished from the scope of the original records requests. Capability revision — sources checked October 3, 2026: R17: https://www.flocksafety.com/blog/does-flock-enable-mass-surveillance Locator: introduction; Key Points; Claim/Fact tracking discussion. Vendor source. R18: https://www.fox8live.com/2026/06/15/flock-says-its-cameras-dont-track-people-its-own-training-videos-say-otherwise/ Locator: training videos; Condor demonstration; company interview. Firsthand InvestigateTV reporting. R19: https://www.wired.com/story/hackers-flock-camera-data-shows-how-system-works/ Locator: software tests and company response. Firsthand joint research. R20: https://www.wired.com/story/flock-safety-os-investigate/ Locator: reconstructed interface and development-status response. Firsthand interface research. No extracted firmware, camera footage, or sensitive leaked dataset was downloaded in this revision. Claims remain attributed to the investigators; this article did not independently repeat their technical tests. Hardware examination, observed operation, public statements, and interface evidence are distinguished. Local configuration remains unconfirmed. Public-trust revision — October 3, 2026: Re-read the agency's policy-history statement on revised-response page 2 and the September 18 acquisition reply. Refreshed the cited judicial opinions on sheriff independence and the policy/timeline statutory text. No new mailbox review was performed in this revision. The author clarified that he has no firsthand or documentary source proving that no advance resident consultation or County Commission notification occurred; his concern rests on the earlier searches yielding no located public mention. Those universal absence claims are not presented as established facts. The newspaper's report of several months of community discussion does not itself establish advance consultation, official notice, or their absence. The policy interval is from a documented agency-attributed search to the stated policy date. It is not a verified date when all residents first learned of the system, the local installation date, or proof of continuous local-camera operation throughout the interval. The missing production timeline is a source-based statutory-compliance assessment, not a court judgment or a finding of willful intent. Repeat public-notice search — October 3, 2026: See Public_Notice_Search_2026-10-03.txt for source URLs, exact locators, searched documents, terms, and limitations. Twenty-four linked county meeting PDFs (113 pages) under August 2024 through July 2026 were rendered and OCR searched, with four targeted visual checks. No Flock/ALPR/plate-reader/surveillance mention was located in the OCR text. This is not a complete manual visual review, complete newspaper/social archive search, or review of private communications. The search verified a contrary public-record lead: the Georgia DOT native approval workbook released May 22, 2025 reports an Appling entry approved October 2, 2024 for two cameras, Tab 1 A89:F89. That entry does not identify the vendor, prove activation or installation, or establish resident consultation or commission notification. No first-public-disclosure date is established. No new mailbox search or external write occurred. Policy and training clarification — October 3, 2026: Rechecked O.C.G.A. 35-1-22(e): the statute imposes a mandatory use-and-operation policy duty on deploying agencies, including policies for officer training in use of captured plate data consistent with the statute. The text does not literally say prior to activation and supplies no post-deployment grace period. Requiring applicable policies during deployment and operation is the article's textual interpretation, not a new court holding. The office's statement that no Flock-camera policies existed before July 28 is distinguished from proof that no broader agency policy could apply. Visually re-read revised-response page 1, item 9: Flock webinar training reported; no dates or times located. Re-read the September 15 delivery email, S9: the office says it does not maintain those records and the requester can seek dates and times from Flock. These establish a documentation gap, not proof that no training occurred or that the office can never produce any training record. Request S2, items 9 and 13, covers training requirements/materials and governance-timeline records; it does not expressly demand every individual's attendance roster. Subsection (e) expressly requires training policies; it does not expressly prescribe webinar attendance-record creation. A separate statutory violation for missing attendance records has not been confirmed. Additional sources checked: https://rules.sos.ga.gov/gac/464-5 ; https://www.georgiaarchives.org/records/localgov_print_all ; https://www.georgiaarchives.org/records/local_government/schedules/44/P80 ; https://law.justia.com/codes/georgia/title-50/chapter-18/article-5/section-50-18-99/ . The general continuing-education schedule LG-16-041 expressly excludes law enforcement; public-safety schedules include field-training files (LG-19-089) and lesson plans (LG-19-091). These do not, without classifying the actual records and applicable local schedule, establish a universal duty to create webinar attendance records. No destruction or noncompliant retention is established. Existing qualifying vendor-held public records remain subject to the separately cited Open Records Act retrieval provisions.
OCTOBER 4 TRUST AND GEORGIA MISUSE SOURCE NOTES
Scope: public-source research checked October 4. Local correspondence findings remain bounded to the October 3 review. The September 18 office response in correspondence source S13 states that information is still being gathered and a response will be sent once all seven categories have been completed. It supplies no production dates. The September 14 S8 and September 18 S12 follow-ups explicitly identify the timeline requirement. The statutory comparison is to O.C.G.A. 50-18-71(b)(1)(A). This supports the source-based finding of failure to supply the required timeline; motive, knowing-and-willful findings, and criminal guilt are not established. Statutory text rechecked: https://law.justia.com/codes/georgia/title-50/chapter-18/article-4/section-50-18-71/ ALPR policy duty rechecked: https://law.justia.com/codes/georgia/title-35/chapter-1/section-35-1-22/ GBI announcements rechecked October 4: July 6 - five former Albany officers; reported internal-audit finding https://gbi.georgia.gov/press-releases/2026-07-06/gbi-arrests-five-former-albany-police-department-officers-misuse-license September 2 - Clayton County deputy; preliminary information https://gbi.georgia.gov/press-releases/2026-09-02/gbi-arrests-clayton-county-sheriffs-office-deputy-misuse-license-plate September 14 - former Colquitt County deputy; preliminary information https://gbi.georgia.gov/press-releases/2026-09-14/gbi-arrests-former-colquitt-county-deputy-misuse-license-plate-reader September 30 - former Hall County investigator; audit and preliminary information https://gbi.georgia.gov/press-releases/2026-09-30/gbi-arrests-former-hall-county-sheriffs-office-investigator-misuse The Albany release reports an internal-audit finding of repeated non-law-enforcement use. The other three describe preliminary information. All announce arrests and charges. No conviction is inferred. These selected cases are not a complete statewide count and do not establish Appling misuse. The Institute for Justice figure remains the article's dated October 3 incident snapshot, not an updated arrest count. The mandatory-policy duty remains distinguished from an exact statutory pre-activation phrase and from a separately unconfirmed webinar-attendance-record creation duty. The office's response concerning earlier Flock policies is reported accurately; applicability of broader earlier policies remains unresolved.
OCTOBER 4 CAPABILITY, KYLE, AND SEARCH-LOG SOURCE NOTES
Scope: public-source research checked October 4. Local correspondence findings remain bounded to the October 3 review. R19 sources: https://www.wired.com/story/hackers-flock-camera-data-shows-how-system-works/ Locators: analysis of recovered files; extracted-model tests and media; facial-recognition limitation; final company response. https://www.flocksafety.com/blog/gunshot-detection-and-license-plate-reader-security-alert Locator: Ongoing Security Reinforcements, paragraph about physical device access and footage. The page presents different date fields; this review cites the passage as live text read October 4 rather than asserting a single publication date. Vendor media FAQ rechecked: https://www.flocksafety.com/press-center Locator: Media FAQ, What do Flock LPR cameras capture and how do they work? R22 primary source: https://storage.courtlistener.com/recap/gov.uscourts.oknd.76981/gov.uscourts.oknd.76981.62.0.pdf Native PDF acquired October 4, 2026 via a direct HTTPS read of the public CourtListener RECAP URL. File: United_States_v_Kyle_ECF62_2026-10-01.pdf. Bytes: 691722. Pages: 38. SHA256: A16E8BFE0662BEA57A31CD8C465E1495C288557C739C9FC7BF858CBBB147C802 The hash verifies the preserved bytes; it does not certify the archive or the truth of every statement in the opinion. Court-header identification: United States v. Melisa Susan Kyle, Northern District of Oklahoma, No. 4:26-cr-00189-SEH, ECF 62, filed October 1, 2026, Judge Sara E. Hill. Printed-page locators: 2-4; 10-11; 25-30; 34; 37-38. Court findings, government contentions, and hypothetical discussion are distinguished in the article. The order itself supplies the findings used in the article; the news story is secondary context. Supplied secondary report: https://www.lawcommentary.com/articles/flock-license-plate-search-unconstitutional-fourth-amendment-oklahoma No later docket disposition or filed appeal was confirmed. The source entry identifies that procedural limit. R23 original reporting: https://theintercept.com/2026/09/09/flock-cameras-police-loitering-curfew-surveillance/ Sam Biddle, September 9, 2026. Correction September 10, 2026, 2:46 p.m. Eastern. Native publisher HTML read October 4 using a direct HTTPS read from the original publisher. Locators: Plano deputy-chief clarification; Norcross example; LaGrange examples; case-number discussion; final correction. The full underlying log set was not independently reconciled. Article statements are attributed to the reporter. The correction is retained; search totals and scopes are not converted into people, cameras, successful matches, or a population percentage. Supplied secondary coverage: https://cybernews.com/privacy/flock-camera-logs-show-police-tracking-people-who-just-hang-around/ Do not rely on its uncorrected phrasing or its search-to-population comparison to count people surveilled. R24 dated contract comparison: https://www.aclu.org/news/privacy-technology/tracking-alpr-cameras/flocks-terms-and-conditions Jay Stanley, ACLU, April 16, 2026. This is attributed advocacy analysis, not a judicial ruling. https://footnote4a.org/blog/terms-feb2026/feb-2026-terms.pdf Third-party archived standard terms marked February 16, 2026. Native PDF acquired October 4 by direct HTTPS read. File: Flock_Standard_Terms_2026-02-16_Third_Party_Archive.pdf. Bytes: 257760. Pages: 15. SHA256: 27B7BFA8025FEBB79F04B8ECEF1AA8E75C75248DEC536FD9236D23FFF1E41B55. Locators: section 4.1 on printed PDF page 5; section 5 on page 6. Hash records the acquired bytes, not certification of archive authenticity or local applicability. https://www.flocksafety.com/legal/terms-and-conditions Live page marked Last Updated August 21, 2026; read October 4. Locators: sections 4.1 and 5. Do not treat the ACLU April description as unchanged current text. Do not treat a perpetual license alone as proof that every captured image is retained forever. The vendor historical-versions help page returned 403 during this review; the February text is identified as a third-party archive. Neither online version nor the ACLU analysis establishes Appling's executed terms, amendments, or renewals. These remain a local records question.
PUBLIC NOTICE AND COMMISSION-RECORD SEARCH — OCTOBER 3, 2026
Research notes supporting this article. Not an agency certification or an exhaustive public-records audit. RESULT No documentation of advance resident consultation or advance County Commission notification was located in the public sources searched. This is an absence-of-located-documentation finding. I cannot confirm that residents were never consulted or commissioners were never notified. An earlier public record WAS located: the Georgia DOT approval list released on MuckRock May 22, 2025 lists an Appling County Sheriff's Office entry approved October 2, 2024 for two cameras. This entry establishes what the approval list reports. It does not identify Flock as vendor, establish installation/activation dates, establish notice to residents or commissioners, or prove that this was the first public disclosure. PRIMARY SOURCE: GEORGIA DOT APPROVAL LIST Request page: https://www.muckrock.com/foi/georgia-230/applications-to-install-license-plate-readers-185539/#comm-2004505 May 22, 2025 GDOT response: releases the attached responsive document; tracking number 19370. Native attachment: https://cdn.muckrock.com/foia_files/2025/05/22/ALPR_Approved_List_Rev_5_7_2025.xlsx Locator: worksheet 'Tab 1'; A1:F1 headers; A89:F89 Appling entry. A89 Permit Number: ALPR-001-000001-5 B89 Agency: Appling County Sheriff's Office C89 County: Appling D89 Number of Cameras: 2 E89 Maintenance Agreement Contract CATS Number: blank F89 Date Approved: October 2, 2024 (underlying date value 2024-10-02 00:00:00). Native XLSX SHA-256: 586729c189fe2bfac9c715b36c6b3380a266e6615e655a2d316be1b485048351 Read only; the source workbook was not edited or re-exported. COUNTY MEETING DOCUMENTS Official index: https://applingcountyga.org/?page_id=98 Scope: 24 linked PDF documents under the archive entries August 2024 through July 2026. This is a review of the linked documents, not certification that every meeting, attachment, or discussion is represented. All 113 PDF pages were rendered and processed with Windows OCR. OCR text was searched for Flock (including common letter substitutions), ALPR, license plate, plate reader, surveillance, camera, Sheriff, and Melton. No Flock/ALPR/plate-reader/surveillance mention was located. Generic camera hits concerned meeting live-stream equipment; Sheriff hits concerned other matters. Targeted visual checks: August 2024 linked minutes page 4; October 2024 combined minutes page 3; November 2024 combined minutes page 2; April 2025 minutes page 1. Those checks confirmed the respective Sheriff-report, fencing, and live-stream contexts. They do not amount to a manual visual review of all 113 pages. Calculation: 24 documents = the 24 PDF entries listed below; 113 pages = the sum of their page counts. No page had a no-text-recognized placeholder. OCR can still omit or misread words. PDF DOCUMENTS SEARCHED — source filenames retained in the URLs; labels identify archive entries August_2024_Minutes.pdf | 5 pages https://applingcountyga.org/wp-content/uploads/2024/10/0824-Minutes-combined.pdf SHA-256: 7104dd6cb51d7220a2c5557e7c823859cec4b8a36318488bc510ea125e700f98 September_2024_Minutes.pdf | 3 pages https://applingcountyga.org/wp-content/uploads/2024/10/Appling-Co-BOC-Regular-Meeting-Minutes-September-10-2024.pdf SHA-256: 840d52d8a609140789fd751c6e9ae543567a78413fbf0e10c7c678bcfce2e79c October_2024_Minutes.pdf | 11 pages https://applingcountyga.org/wp-content/uploads/2024/12/1024-Combined-Minutes.pdf SHA-256: cc8a24bf3ec725b0a6ed2235877a2ea487d666296fa770522c2e44080689202c November_2024_Minutes.pdf | 5 pages https://applingcountyga.org/wp-content/uploads/2025/03/1124-Minutes-Combined.pdf SHA-256: fc3ff2391820f00e5e5e01064b806eeb53d0a8777976b025f3c1b16c075435c0 December_2024_Minutes.pdf | 4 pages https://applingcountyga.org/wp-content/uploads/2025/03/1224-Minutes-Combined.pdf SHA-256: 99310c5a17f49d05524792ea58866a1802f17adb4be412078b1d946961c336aa January_2025_Minutes.pdf | 6 pages https://applingcountyga.org/wp-content/uploads/2025/03/0125-Minutes-Combined.pdf SHA-256: 5909e90729bdd06bc47e799f200cb3024e69270f059fa70015049f557909d47b February_2025_Minutes.pdf | 10 pages https://applingcountyga.org/wp-content/uploads/2025/04/02-2025-Combined-Minutes.pdf SHA-256: aba7f1f1b1596480933ce5decbf0e5ca6adb801b522450522166bca9f0357b42 March_2025_Minutes.pdf | 6 pages https://applingcountyga.org/wp-content/uploads/2025/04/03-25-Minutes.pdf SHA-256: 876238305596261a4344a2d431d2208670eabbb5e64bd33e127b6f93b7a67cb0 April_2025_Minutes.pdf | 4 pages https://applingcountyga.org/wp-content/uploads/2025/05/04-2025-Minutes.pdf SHA-256: 0cae66187ce82eadcdfcdc0e74e597012e434c1e586c0621ba5da868a076e365 May_2025_Minutes.pdf | 4 pages https://applingcountyga.org/wp-content/uploads/2025/10/Appling-Co-BOC-Regular-Meeting-Minutes-May-8-2025.pdf SHA-256: 9355ee28f987a5f90bb07c9c09a4fb128b8c28008f7abf19052aa8200723d267 June_2025_Minutes.pdf | 5 pages https://applingcountyga.org/wp-content/uploads/2025/07/06-2025-Combined-June-1.pdf SHA-256: d8706c07d9d356b4e20406f90bbe32a1e379797ba99832161f89dfd6c2dd54ba July_2025_Minutes.pdf | 3 pages https://applingcountyga.org/wp-content/uploads/2025/09/Appling-BOC-Regular-Meeting-Minutes-July-8-2025.pdf SHA-256: fe71d57aa7a246112efb6bf6c73a41d75e4439908310b672e20d6bb5db84f0e4 August_2025_Minutes.pdf | 3 pages https://applingcountyga.org/wp-content/uploads/2025/09/Appling-BOC-Regular-Meeting-Minutes-August-5-2025.pdf SHA-256: 42a59f359d355265277053b1f93231faaf2549d48fe872c67d6027bc8a06bb99 September_2025_Minutes.pdf | 5 pages https://applingcountyga.org/wp-content/uploads/2026/01/Minutes%20Combo%2009%202025.pdf SHA-256: 0c675e5b9ad7763739725db8f2063624af0fd96fae26399332052be68e806587 October_2025_Minutes.pdf | 3 pages https://applingcountyga.org/wp-content/uploads/2026/01/Appling-BOC-Regular-Meeting-Minutes-October-7-2025.pdf SHA-256: 09e3c83355e26e9045eabc11a8f943e7247d795ab95f35548161b8149aaebcbc November_2025_Minutes.pdf | 6 pages https://applingcountyga.org/wp-content/uploads/2026/01/Combo-Minutes-11025.pdf SHA-256: 413c67a302679bf3bfa23de32eee75a68be96306f80c338e288f04324d24ad7d December_2025_Minutes.pdf | 3 pages https://applingcountyga.org/wp-content/uploads/2026/01/Appling-BOC-Regular-Meeting-Minutes-December-2-2025-1.pdf SHA-256: adca08beb2af32064c8aa4c7676bcf1263d5a042c59ad7717568192acc5b3d0e January_2026_Minutes.pdf | 6 pages https://applingcountyga.org/wp-content/uploads/2026/02/01-26-Minutes-Combined.pdf SHA-256: 6489df52cd86b67533399ddf9c23f0e76c1c8c9588d95ec89468ba6eff97417f February_2026_Minutes.pdf | 3 pages https://applingcountyga.org/wp-content/uploads/2026/03/Appling-Co-Board-of-Commissioners-Regular-Meeting-February-3-2026.pdf SHA-256: eb1d523372f4f6611a76f4c725ea122999da2f2217c72a799df10b9041809b18 March_2026_Minutes.pdf | 2 pages https://applingcountyga.org/wp-content/uploads/2026/05/03-03-26-Minutes.pdf SHA-256: 749328a0024d26315ed592bdab63f2053168e7a7b79481c7ca1377b424809a09 April_2026_Minutes.pdf | 5 pages https://applingcountyga.org/wp-content/uploads/2026/06/04-26-Combined.pdf SHA-256: dd413c62cf972eb129b9d2bf3518a04a3b995696a61896358258bc1fd3553442 May_2026_Archive_Link.pdf | 5 pages https://applingcountyga.org/wp-content/uploads/2026/07/051226-Combined.pdf SHA-256: 94f94425b058c2af741d4acc819cc9f6cf846acd052f4e8fffaa80ced4f496fd June_2026_Minutes.pdf | 3 pages https://applingcountyga.org/wp-content/uploads/2026/08/Appling-Co-Board-of-Commissioners-Regular-Meeting-June-2-2026.pdf SHA-256: 4b6616cbc4302d2a9297416695b011af06301ef74b9b82c2ac1de975066cf494 July_2026_Archive_Link.pdf | 3 pages https://applingcountyga.org/wp-content/uploads/2026/08/2026-07-21-Minutes.pdf SHA-256: e042ae97acaa56e4c5bdf2e7626080a6aba115f8d5addccd13f1b364490d4021 TARGETED WEB SEARCHES Search terms combined Appling County, Baxley, Sheriff, Flock, ALPR, license plate readers, commission, meeting, notice, and camera. Site restrictions included applingcountyga.org and applingcountysheriffsoffice.com. Date-restricted searches used before:2025-05-01 and before:2026-08-19. Representative exact queries: site:applingcountyga.org ("Flock" OR "ALPR" OR "license plate") site:applingcountysheriffsoffice.com ("Flock" OR "ALPR" OR "license plate") "Appling County" "Flock" before:2025-05-01 "Appling County" "Flock" ("commission" OR "meeting" OR "notice") before:2026-08-19 "Appling" "Flock" "Baxley" before:2026-08-19 "Appling County" "ALPR" "2024" Georgia Department Transportation No advance resident-consultation or commission-notification document was identified in returned results. Search-engine date filters and indexing do not certify historical publication dates or completeness. Discovery lead: https://areyouflocked.com/georgia/baxley (EFF Atlas record AOS013826) linked to the native GDOT release. The underlying entry was checked directly rather than relying on the derivative summary. Some results concern Appling, Georgia IN COLUMBIA COUNTY. Those were excluded; they do not establish Appling County practices. OTHER REVIEWED CONTEXT AND LIMITS The saved Baxley News-Banner August 19, 2026 article by Jamie Gardner describes several months of community discussion and quotes County Manager Reid Lovett on the cameras. It establishes his awareness by that report, not whether commissioners received advance notification or residents were consulted before implementation. The web fetcher could not open the MuckRock request page, but the browser displayed its correspondence and the native attachment was downloaded from the observed link. No CAPTCHA was solved. This review did not watch all meeting videos, inspect every possible attachment or archive year, search a complete newspaper archive, review private discussions or all social posts, or make a new Gmail search. The criticism of undisclosed or unexplained deployment is a transparency and public-trust issue. No separate consultation or County Commission approval requirement is established by this search.