Franklin Township Flock Data
Dear Franklin Township (Somerset),
Please accept this electronic request for public records made under OPRA and the common law right of access. I am not required to fill out an official form or use a particular software platform to submit my request per NJSA 47:1A-6(f), which states that an email from a requestor including all of the information required on the adopted form shall suffice in place of a completed form as a valid government record request.
I HAVE NOT been convicted of any indictable offense under the laws of New Jersey, any other state, or the United States.
I WILL NOT use the requested government records for a commercial purpose.
I AM NOT seeking records in connection with a legal proceeding.
Records requested:
I respectfully request access to the following records related to the Franklin Township Police Department’s Flock Safety and other automatic license plate readers (ALPRs), specifically:
1. FLOCK SAFETY INFORMATION
1.1. CONTRACTS and AGREEMENTS
1.1.a. All contracts, licenses, MOUs, MOAs, data agreements, letters of intent, Statement of Work documents, Scope of Work documents, purchase orders, and other agreement documents with Flock Safety ('Flock', and/or 'Flock Group, Inc.') that are currently or were active any time between 1/1/2020 and the date this request is processed (inclusive of those dates). This includes documentation related to the acquisition, leasing, and/or use of Flock Safety cameras or services, including associated data platforms and analytics tools.
1.2. GUIDING DOCUMENTATION and POLICIES
1.2.a. All policies, memorandums of understanding, and other guidance materials generated by the Department and/or any entity operating on its behalf regarding the acquisition and use of any data or services provided by Flock Safety ('Flock', and/or 'Flock Group, Inc.') and any representative thereof or any subdivision thereof. Responsive materials include, but are not limited to, any data-sharing agreements, retention policies, training materials, or other guidance materials.
1.2.b. All policies, records, emails, or data related to the sharing of passwords or otherwise offering access (e.g., performing searches informally by non-official request) with local, regional, or federal task forces or agents.
1.2.c. All non-email records detailing policies, SOPs, directives, training materials, and other guidance materials on when and how ALPR alerts may be utilized to initiate or justify traffic stops or detentions, requirements for independent corroboration or verification before enforcement action, documentation and/or reporting expectations for ALPR-related encounters, how hits are verified and how mismatches or false positives are handled, information on data retention and personnel access restrictions, and any policy memos explaining change history within any related documents.
1.2.d. All policies, SOPs, or other guidance materials generated by the agency detailing the required frequency of Organization Audits, Network Audits, and other audits of the Flock system and its use by personnel.
2. FLOCK SPECIFIC DATA
2.1. Organization Audit in Flock.
2.1.a. Flock-generated export report: This report should include data logged from the period of 1/1/2025, to the date this request is processed (inclusive of those dates). Per Flock's documentation, the Organization Audit is available within the Insights tab and is defined as searches done within the Department. Please include, at a minimum, the following fields: Name, Total Networks Searched, Time Frame, License Plate, Case #, Filters, Reason, and Search Date/Time.
2.2. Network Audit in Flock.
2.2.a. Flock-generated export report: This report should include data logged from the period of 1/1/2025, to the date this request is processed (inclusive of those dates). Per Flock's documentation, the Network Audit is available within the Insights tab and is defined as searches of the Department’s Flock network by any agency in the Flock System. Please include, at a minimum, the following fields: Name, Org Name, Total Networks Searched, Total Devices Searched, Time Frame, License Plate, Case #, Filters, Reason, and Search Date/Time.
2.3. List of Network Share Settings in Flock:
2.3.a. Data from Flock Platform: The names of agencies and organizations with which the Department shares ALPR data, also referred to as "Networks that I’m sharing."
2.3.b. Data from Flock Platform: The names of agencies and organizations from which the Department receives ALPR data, also referred to as "Flock networks shared with me."
2.3.c. Data from Flock Platform: The names of agencies and organizations with which the Department shares “hotlist” information, also referred to as "Hotlists that I’m sharing."
2.3.d. Data from Flock Platform: The names of agencies and organizations from which the Department receives “hotlist” information, also referred to as "Hotlists shared with me."
2.4. Hotlist Information in Flock.
2.4.a. Flock-generated export report: An exported log of hot list actions (typically "create," "update," and delete") in the Department's Flock Safety system spanning the last 6 months from the date this request is processed. This log should include fields detailing, at minimum, a timestamp, user performing the action, the event type (e.g., 'create', 'update', 'delete'), entity type, and entity details (For Entity Details, please include at minimum the fields 'hotlist name', 'reason', 'case', and 'expiry'). An example of this document may be viewed here: https://cdn.muckrock.com/foia_files/2025...
2.4.b. Documentation regarding which external Hotlists the Flock system is configured to utilize.
2.5. Information on Users with Access to the Flock System.
2.5.a. Documentation indicating users with access to the agency’s Flock deployment and the access that is enabled/disabled for each user account. The report should include: User Id, Name, Role, Identity Provider, Last login, User Mgmt, Search, Device Mgmt, and Hotlist Tool.
3. GENERAL ALPR QUESTIONS
3.1. ALPR "Hot Lists"
3.1.a. A description of all “hot lists” or “custom hot lists” currently maintained for use in Automated License Plate Reader (ALPR) systems.
3.1.b. Any policies, agreements, or data-sharing documents identifying external data sources used to populate those lists (e.g., DMV data on suspended/revoked licenses, NCIC, CLETS, Amber Alerts, stolen vehicle databases).
3.1.c. Any documentation offering guidance or specifying the criteria under which plates are added or removed from hot lists.
3.1.d. Any policies, SOPs, and/or software specification indicating how vehicles without plates or with plates that are unable to be read via automated software trigger alerts within system(s) utilized by the department.
3.2. ALPR Installation Locations.
3.2.a. Documentation detailing the location of all Flock camera and other non-mobile ALPR-capable recording device installations, both city-owned and non-city owned, that are located in Franklin Township with which the Department has access to (including via indirect access, such as the ability to query or otherwise view logged data or analytics). For each device, please include the following details: location of installation (provided with enough detail to make the location clear, either as streets at an intersection or geographic coordinates), street of which camera's field of view covers, and direction in which camera's field of view covers (using cardinal directions e.g., 'Eastbound'), device make and model, and associated owner(s) and/or third-party service provider name(s), if applicable (e.g., Flock).
3.2.b. If available, documentation including but not limited to memos or similar which indicate the selection criteria that determined placement of installed ALPR devices.
GENERAL NOTES:
***Please provide all documents in their original electronic, machine readable format. For example, please provide files as they are natively output by Flock's and other systems' export tools (e.g., as .csv) where applicable. Otherwise, please utilize .pdf, .csv, .xls, .xlsx files as appropriate.
My preferred delivery method for response(s) to this request is by E-mail as attachments. Please confirm you have received this request. If you are not the custodian of records, please forward my request to that person and provide their email address to me for future reference.
Yours faithfully,
Anonymous
══════════════════════════════════════════════════════════════════════════
Dear ANONYMOUS:
Your request has been received and is being processed. Your request was
received in this office on 12/1/2025 and given the reference number
P000810-120125 for tracking purposes.
Records Requested: I respectfully request access to the following records
related to the Franklin Township Police Department’s Flock Safety and
other automatic license plate readers (ALPRs), specifically:
1. FLOCK SAFETY INFORMATION
1.1. CONTRACTS and AGREEMENTS
1.1.a. All contracts, licenses, MOUs, MOAs, data agreements, letters of
intent, Statement of Work documents, Scope of Work documents, purchase
orders, and other agreement documents with Flock Safety ('Flock', and/or
'Flock Group, Inc.') that are currently or were active any time between
1/1/2020 and the date this request is processed (inclusive of those
dates). This includes documentation related to the acquisition, leasing,
and/or use of Flock Safety cameras or services, including associated data
platforms and analytics tools.
1.2. GUIDING DOCUMENTATION and POLICIES
1.2.a. All policies, memorandums of understanding, and other guidance
materials generated by the Department and/or any entity operating on its
behalf regarding the acquisition and use of any data or services provided
by Flock Safety ('Flock', and/or 'Flock Group, Inc.') and any
representative thereof or any subdivision thereof. Responsive materials
include, but are not limited to, any data-sharing agreements, retention
policies, training materials, or other guidance materials.
1.2.b. All policies, records, emails, or data related to the sharing of
passwords or otherwise offering access (e.g., performing searches
informally by non-official request) with local, regional, or federal task
forces or agents.
1.2.c. All non-email records detailing policies, SOPs, directives,
training materials, and other guidance materials on when and how ALPR
alerts may be utilized to initiate or justify traffic stops or detentions,
requirements for independent corroboration or verification before
enforcement action, documentation and/or reporting expectations for
ALPR-related encounters, how hits are verified and how mismatches or false
positives are handled, information on data retention and personnel access
restrictions, and any policy memos explaining change history within any
related documents.
1.2.d. All policies, SOPs, or other guidance materials generated by the
agency detailing the required frequency of Organization Audits, Network
Audits, and other audits of the Flock system and its use by personnel.
2. FLOCK SPECIFIC DATA
2.1. Organization Audit in Flock.
2.1.a. Flock-generated export report: This report should include data
logged from the period of 1/1/2025, to the date this request is processed
(inclusive of those dates). Per Flock's documentation, the Organization
Audit is available within the Insights tab and is defined as searches done
within the Department. Please include, at a minimum, the following fields:
Name, Total Networks Searched, Time Frame, License Plate, Case #, Filters,
Reason, and Search Date/Time.
2.2. Network Audit in Flock.
2.2.a. Flock-generated export report: This report should include data
logged from the period of 1/1/2025, to the date this request is processed
(inclusive of those dates). Per Flock's documentation, the Network Audit
is available within the Insights tab and is defined as searches of the
Department’s Flock network by any agency in the Flock System. Please
include, at a minimum, the following fields: Name, Org Name, Total
Networks Searched, Total Devices Searched, Time Frame, License Plate, Case
#, Filters, Reason, and Search Date/Time.
2.3. List of Network Share Settings in Flock:
2.3.a. Data from Flock Platform: The names of agencies and organizations
with which the Department shares ALPR data, also referred to as "Networks
that I’m sharing."
2.3.b. Data from Flock Platform: The names of agencies and organizations
from which the Department receives ALPR data, also referred to as "Flock
networks shared with me."
2.3.c. Data from Flock Platform: The names of agencies and organizations
with which the Department shares “hotlist” information, also referred to
as "Hotlists that I’m sharing."
2.3.d. Data from Flock Platform: The names of agencies and organizations
from which the Department receives “hotlist” information, also referred to
as "Hotlists shared with me."
2.4. Hotlist Information in Flock.
2.4.a. Flock-generated export report: An exported log of hot list actions
(typically "create," "update," and delete") in the Department's Flock
Safety system spanning the last 6 months from the date this request is
processed. This log should include fields detailing, at minimum, a
timestamp, user performing the action, the event type (e.g., 'create',
'update', 'delete'), entity type, and entity details (For Entity Details,
please include at minimum the fields 'hotlist name', 'reason', 'case', and
'expiry'). An example of this document may be viewed here:
https://cdn.muckrock.com/foia_files/2025...
2.4.b. Documentation regarding which external Hotlists the Flock system is
configured to utilize.
2.5. Information on Users with Access to the Flock System.
2.5.a. Documentation indicating users with access to the agency’s Flock
deployment and the access that is enabled/disabled for each user account.
The report should include: User Id, Name, Role, Identity Provider, Last
login, User Mgmt, Search, Device Mgmt, and Hotlist Tool.
3. GENERAL ALPR QUESTIONS
3.1. ALPR "Hot Lists"
3.1.a. A description of all “hot lists” or “custom hot lists” currently
maintained for use in Automated License Plate Reader (ALPR) systems.
3.1.b. Any policies, agreements, or data-sharing documents identifying
external data sources used to populate those lists (e.g., DMV data on
suspended/revoked licenses, NCIC, CLETS, Amber Alerts, stolen vehicle
databases).
3.1.c. Any documentation offering guidance or specifying the criteria
under which plates are added or removed from hot lists.
3.1.d. Any policies, SOPs, and/or software specification indicating how
vehicles without plates or with plates that are unable to be read via
automated software trigger alerts within system(s) utilized by the
department.
3.2. ALPR Installation Locations.
3.2.a. Documentation detailing the location of all Flock camera and other
non-mobile ALPR-capable recording device installations, both city-owned
and non-city owned, that are located in Franklin Township with which the
Department has access to (including via indirect access, such as the
ability to query or otherwise view logged data or analytics). For each
device, please include the following details: location of installation
(provided with enough detail to make the location clear, either as streets
at an intersection or geographic coordinates), street of which camera's
field of view covers, and direction in which camera's field of view covers
(using cardinal directions e.g., 'Eastbound'), device make and model, and
associated owner(s) and/or third-party service provider name(s), if
applicable (e.g., Flock).
3.2.b. If available, documentation including but not limited to memos or
similar which indicate the selection criteria that determined placement of
installed ALPR devices.
Your request will be forwarded to the relevant department(s) to locate the
information you seek and to determine the volume and any costs associated
with satisfying your request. You will be contacted about the availability
and/or provided with copies of the records in question.
You can monitor the progress of your request at the link below and you'll
receive an email when your request has been completed.
Franklin Township, Somerset County
══════════════════════════════════════════════════════════════════════════
To monitor the progress or update this request please log into the [1]OPRA
Center
[2]GovQA logo
References
Visible links
1. OPRA Center
https://u8387778.ct.sendgrid.net/ls/clic...
══════════════════════════════════════════════════════════════════════════
Dear ANONYMOUS ,
Thank you for registering with the Franklin Township, Somerset County OPRA
Center.
Your Login ID is: [OPRA #83828 email]
If you did not submit your request through the public portal but are
receiving this e-mail, an account has been created for you where you can
track and monitor the status of your request, and receive any documents in
response to your request.
If you have never used this system or cannot remember your password you
may request a temporary password here: [1]Request Temporary Password
Please login to [2]My Records Center to update your account information,
track the status of your request and receive requested records when they
become available.
══════════════════════════════════════════════════════════════════════════
This is an auto-generated email and has originated from an unmonitored
email account. Please DO NOT REPLY.
[3]GovQA logo
References
Visible links
1. Click here to Request a New Password
https://u8387778.ct.sendgrid.net/ls/clic...
2. https://u8387778.ct.sendgrid.net/ls/clic...
Attachments:
[1]Denial_Poster.pdf
--- Please respond above this line ---
══════════════════════════════════════════════════════════════════════════
RE: Police Records Request of December 01, 2025, Reference #
P000810-120125
Dear ANONYMOUS,
Franklin Township Police Department, Somerset County received a public
records request from you on December 01, 2025. Your request was for the
following record(s):
I respectfully request access to the following records related to the
Franklin Township Police Department’s Flock Safety and other automatic
license plate readers (ALPRs), specifically:
1. FLOCK SAFETY INFORMATION
1.1. CONTRACTS and AGREEMENTS
1.1.a. All contracts, licenses, MOUs, MOAs, data agreements, letters of
intent, Statement of Work documents, Scope of Work documents, purchase
orders, and other agreement documents with Flock Safety ('Flock', and/or
'Flock Group, Inc.') that are currently or were active any time between
1/1/2020 and the date this request is processed (inclusive of those
dates). This includes documentation related to the acquisition, leasing,
and/or use of Flock Safety cameras or services, including associated data
platforms and analytics tools.
1.2. GUIDING DOCUMENTATION and POLICIES
1.2.a. All policies, memorandums of understanding, and other guidance
materials generated by the Department and/or any entity operating on its
behalf regarding the acquisition and use of any data or services provided
by Flock Safety ('Flock', and/or 'Flock Group, Inc.') and any
representative thereof or any subdivision thereof. Responsive materials
include, but are not limited to, any data-sharing agreements, retention
policies, training materials, or other guidance materials.
1.2.b. All policies, records, emails, or data related to the sharing of
passwords or otherwise offering access (e.g., performing searches
informally by non-official request) with local, regional, or federal task
forces or agents.
1.2.c. All non-email records detailing policies, SOPs, directives,
training materials, and other guidance materials on when and how ALPR
alerts may be utilized to initiate or justify traffic stops or detentions,
requirements for independent corroboration or verification before
enforcement action, documentation and/or reporting expectations for
ALPR-related encounters, how hits are verified and how mismatches or false
positives are handled, information on data retention and personnel access
restrictions, and any policy memos explaining change history within any
related documents.
1.2.d. All policies, SOPs, or other guidance materials generated by the
agency detailing the required frequency of Organization Audits, Network
Audits, and other audits of the Flock system and its use by personnel.
2. FLOCK SPECIFIC DATA
2.1. Organization Audit in Flock.
2.1.a. Flock-generated export report: This report should include data
logged from the period of 1/1/2025, to the date this request is processed
(inclusive of those dates). Per Flock's documentation, the Organization
Audit is available within the Insights tab and is defined as searches done
within the Department. Please include, at a minimum, the following fields:
Name, Total Networks Searched, Time Frame, License Plate, Case #, Filters,
Reason, and Search Date/Time.
2.2. Network Audit in Flock.
2.2.a. Flock-generated export report: This report should include data
logged from the period of 1/1/2025, to the date this request is processed
(inclusive of those dates). Per Flock's documentation, the Network Audit
is available within the Insights tab and is defined as searches of the
Department’s Flock network by any agency in the Flock System. Please
include, at a minimum, the following fields: Name, Org Name, Total
Networks Searched, Total Devices Searched, Time Frame, License Plate, Case
#, Filters, Reason, and Search Date/Time.
2.3. List of Network Share Settings in Flock:
2.3.a. Data from Flock Platform: The names of agencies and organizations
with which the Department shares ALPR data, also referred to as "Networks
that I’m sharing."
2.3.b. Data from Flock Platform: The names of agencies and organizations
from which the Department receives ALPR data, also referred to as "Flock
networks shared with me."
2.3.c. Data from Flock Platform: The names of agencies and organizations
with which the Department shares “hotlist” information, also referred to
as "Hotlists that I’m sharing."
2.3.d. Data from Flock Platform: The names of agencies and organizations
from which the Department receives “hotlist” information, also referred to
as "Hotlists shared with me."
2.4. Hotlist Information in Flock.
2.4.a. Flock-generated export report: An exported log of hot list actions
(typically "create," "update," and delete") in the Department's Flock
Safety system spanning the last 6 months from the date this request is
processed. This log should include fields detailing, at minimum, a
timestamp, user performing the action, the event type (e.g., 'create',
'update', 'delete'), entity type, and entity details (For Entity Details,
please include at minimum the fields 'hotlist name', 'reason', 'case', and
'expiry'). An example of this document may be viewed here:
https://cdn.muckrock.com/foia_files/2025...
2.4.b. Documentation regarding which external Hotlists the Flock system is
configured to utilize.
2.5. Information on Users with Access to the Flock System.
2.5.a. Documentation indicating users with access to the agency’s Flock
deployment and the access that is enabled/disabled for each user account.
The report should include: User Id, Name, Role, Identity Provider, Last
login, User Mgmt, Search, Device Mgmt, and Hotlist Tool.
3. GENERAL ALPR QUESTIONS
3.1. ALPR "Hot Lists"
3.1.a. A description of all “hot lists” or “custom hot lists” currently
maintained for use in Automated License Plate Reader (ALPR) systems.
3.1.b. Any policies, agreements, or data-sharing documents identifying
external data sources used to populate those lists (e.g., DMV data on
suspended/revoked licenses, NCIC, CLETS, Amber Alerts, stolen vehicle
databases).
3.1.c. Any documentation offering guidance or specifying the criteria
under which plates are added or removed from hot lists.
3.1.d. Any policies, SOPs, and/or software specification indicating how
vehicles without plates or with plates that are unable to be read via
automated software trigger alerts within system(s) utilized by the
department.
3.2. ALPR Installation Locations.
3.2.a. Documentation detailing the location of all Flock camera and other
non-mobile ALPR-capable recording device installations, both city-owned
and non-city owned, that are located in Franklin Township with which the
Department has access to (including via indirect access, such as the
ability to query or otherwise view logged data or analytics). For each
device, please include the following details: location of installation
(provided with enough detail to make the location clear, either as streets
at an intersection or geographic coordinates), street of which camera's
field of view covers, and direction in which camera's field of view covers
(using cardinal directions e.g., 'Eastbound'), device make and model, and
associated owner(s) and/or third-party service provider name(s), if
applicable (e.g., Flock).
3.2.b. If available, documentation including but not limited to memos or
similar which indicate the selection criteria that determined placement of
installed ALPR devices.
Due to the request for all information regarding the Flock Safety and
other automatic license plate readers (ALPRs) we require a 45-business day
extension with a deadline of February 13, 2026, to respond to this
request.
For questions or additional information, please reply to this email.
Sincerely,
Jodie Scanlon
Police
══════════════════════════════════════════════════════════════════════════
To monitor the progress or update this request please log into the [2]OPRA
Center
[3]GovQA logo
References
Visible links
1. https://u8387778.ct.sendgrid.net/ls/clic...
2. OPRA Center
https://u8387778.ct.sendgrid.net/ls/clic...
--- Please respond above this line ---
══════════════════════════════════════════════════════════════════════════
RE: Police Records Request of December 01, 2025, Reference #
P000810-120125
Dear ANONYMOUS,
Franklin Township Police Department, Somerset County received a public
records request from you on December 01, 2025. Your request was for the
following record(s):
I respectfully request access to the following records related to the
Franklin Township Police Department’s Flock Safety and other automatic
license plate readers (ALPRs), specifically:
1. FLOCK SAFETY INFORMATION
1.1. CONTRACTS and AGREEMENTS
1.1.a. All contracts, licenses, MOUs, MOAs, data agreements, letters of
intent, Statement of Work documents, Scope of Work documents, purchase
orders, and other agreement documents with Flock Safety ('Flock', and/or
'Flock Group, Inc.') that are currently or were active any time between
1/1/2020 and the date this request is processed (inclusive of those
dates). This includes documentation related to the acquisition, leasing,
and/or use of Flock Safety cameras or services, including associated data
platforms and analytics tools.
1.2. GUIDING DOCUMENTATION and POLICIES
1.2.a. All policies, memorandums of understanding, and other guidance
materials generated by the Department and/or any entity operating on its
behalf regarding the acquisition and use of any data or services provided
by Flock Safety ('Flock', and/or 'Flock Group, Inc.') and any
representative thereof or any subdivision thereof. Responsive materials
include, but are not limited to, any data-sharing agreements, retention
policies, training materials, or other guidance materials.
1.2.b. All policies, records, emails, or data related to the sharing of
passwords or otherwise offering access (e.g., performing searches
informally by non-official request) with local, regional, or federal task
forces or agents.
1.2.c. All non-email records detailing policies, SOPs, directives,
training materials, and other guidance materials on when and how ALPR
alerts may be utilized to initiate or justify traffic stops or detentions,
requirements for independent corroboration or verification before
enforcement action, documentation and/or reporting expectations for
ALPR-related encounters, how hits are verified and how mismatches or false
positives are handled, information on data retention and personnel access
restrictions, and any policy memos explaining change history within any
related documents.
1.2.d. All policies, SOPs, or other guidance materials generated by the
agency detailing the required frequency of Organization Audits, Network
Audits, and other audits of the Flock system and its use by personnel.
2. FLOCK SPECIFIC DATA
2.1. Organization Audit in Flock.
2.1.a. Flock-generated export report: This report should include data
logged from the period of 1/1/2025, to the date this request is processed
(inclusive of those dates). Per Flock's documentation, the Organization
Audit is available within the Insights tab and is defined as searches done
within the Department. Please include, at a minimum, the following fields:
Name, Total Networks Searched, Time Frame, License Plate, Case #, Filters,
Reason, and Search Date/Time.
2.2. Network Audit in Flock.
2.2.a. Flock-generated export report: This report should include data
logged from the period of 1/1/2025, to the date this request is processed
(inclusive of those dates). Per Flock's documentation, the Network Audit
is available within the Insights tab and is defined as searches of the
Department’s Flock network by any agency in the Flock System. Please
include, at a minimum, the following fields: Name, Org Name, Total
Networks Searched, Total Devices Searched, Time Frame, License Plate, Case
#, Filters, Reason, and Search Date/Time.
2.3. List of Network Share Settings in Flock:
2.3.a. Data from Flock Platform: The names of agencies and organizations
with which the Department shares ALPR data, also referred to as "Networks
that I’m sharing."
2.3.b. Data from Flock Platform: The names of agencies and organizations
from which the Department receives ALPR data, also referred to as "Flock
networks shared with me."
2.3.c. Data from Flock Platform: The names of agencies and organizations
with which the Department shares “hotlist” information, also referred to
as "Hotlists that I’m sharing."
2.3.d. Data from Flock Platform: The names of agencies and organizations
from which the Department receives “hotlist” information, also referred to
as "Hotlists shared with me."
2.4. Hotlist Information in Flock.
2.4.a. Flock-generated export report: An exported log of hot list actions
(typically "create," "update," and delete") in the Department's Flock
Safety system spanning the last 6 months from the date this request is
processed. This log should include fields detailing, at minimum, a
timestamp, user performing the action, the event type (e.g., 'create',
'update', 'delete'), entity type, and entity details (For Entity Details,
please include at minimum the fields 'hotlist name', 'reason', 'case', and
'expiry'). An example of this document may be viewed here:
https://cdn.muckrock.com/foia_files/2025...
2.4.b. Documentation regarding which external Hotlists the Flock system is
configured to utilize.
2.5. Information on Users with Access to the Flock System.
2.5.a. Documentation indicating users with access to the agency’s Flock
deployment and the access that is enabled/disabled for each user account.
The report should include: User Id, Name, Role, Identity Provider, Last
login, User Mgmt, Search, Device Mgmt, and Hotlist Tool.
3. GENERAL ALPR QUESTIONS
3.1. ALPR "Hot Lists"
3.1.a. A description of all “hot lists” or “custom hot lists” currently
maintained for use in Automated License Plate Reader (ALPR) systems.
3.1.b. Any policies, agreements, or data-sharing documents identifying
external data sources used to populate those lists (e.g., DMV data on
suspended/revoked licenses, NCIC, CLETS, Amber Alerts, stolen vehicle
databases).
3.1.c. Any documentation offering guidance or specifying the criteria
under which plates are added or removed from hot lists.
3.1.d. Any policies, SOPs, and/or software specification indicating how
vehicles without plates or with plates that are unable to be read via
automated software trigger alerts within system(s) utilized by the
department.
3.2. ALPR Installation Locations.
3.2.a. Documentation detailing the location of all Flock camera and other
non-mobile ALPR-capable recording device installations, both city-owned
and non-city owned, that are located in Franklin Township with which the
Department has access to (including via indirect access, such as the
ability to query or otherwise view logged data or analytics). For each
device, please include the following details: location of installation
(provided with enough detail to make the location clear, either as streets
at an intersection or geographic coordinates), street of which camera's
field of view covers, and direction in which camera's field of view covers
(using cardinal directions e.g., 'Eastbound'), device make and model, and
associated owner(s) and/or third-party service provider name(s), if
applicable (e.g., Flock).
3.2.b. If available, documentation including but not limited to memos or
similar which indicate the selection criteria that determined placement of
installed ALPR devices.
Due to additional time needed we require a 15-business day extension with
a deadline of March 9, 2026, to respond to this request.
For questions or additional information, please reply to this email.
Sincerely,
Carissa Mueller
Police
══════════════════════════════════════════════════════════════════════════
To monitor the progress or update this request please log into the [1]OPRA
Center
[2]GovQA logo
References
Visible links
1. OPRA Center
https://u8387778.ct.sendgrid.net/ls/clic...
--- Please respond above this line ---
══════════════════════════════════════════════════════════════════════════
RE: Police Records Request of December 01, 2025, Reference #
P000810-120125
Dear ANONYMOUS,
Franklin Township Police Department, Somerset County received a public
records request from you on December 01, 2025. Your request was for the
following record(s):
I respectfully request access to the following records related to the
Franklin Township Police Department’s Flock Safety and other automatic
license plate readers (ALPRs), specifically:
1. FLOCK SAFETY INFORMATION
1.1. CONTRACTS and AGREEMENTS
1.1.a. All contracts, licenses, MOUs, MOAs, data agreements, letters of
intent, Statement of Work documents, Scope of Work documents, purchase
orders, and other agreement documents with Flock Safety ('Flock', and/or
'Flock Group, Inc.') that are currently or were active any time between
1/1/2020 and the date this request is processed (inclusive of those
dates). This includes documentation related to the acquisition, leasing,
and/or use of Flock Safety cameras or services, including associated data
platforms and analytics tools.
1.2. GUIDING DOCUMENTATION and POLICIES
1.2.a. All policies, memorandums of understanding, and other guidance
materials generated by the Department and/or any entity operating on its
behalf regarding the acquisition and use of any data or services provided
by Flock Safety ('Flock', and/or 'Flock Group, Inc.') and any
representative thereof or any subdivision thereof. Responsive materials
include, but are not limited to, any data-sharing agreements, retention
policies, training materials, or other guidance materials.
1.2.b. All policies, records, emails, or data related to the sharing of
passwords or otherwise offering access (e.g., performing searches
informally by non-official request) with local, regional, or federal task
forces or agents.
1.2.c. All non-email records detailing policies, SOPs, directives,
training materials, and other guidance materials on when and how ALPR
alerts may be utilized to initiate or justify traffic stops or detentions,
requirements for independent corroboration or verification before
enforcement action, documentation and/or reporting expectations for
ALPR-related encounters, how hits are verified and how mismatches or false
positives are handled, information on data retention and personnel access
restrictions, and any policy memos explaining change history within any
related documents.
1.2.d. All policies, SOPs, or other guidance materials generated by the
agency detailing the required frequency of Organization Audits, Network
Audits, and other audits of the Flock system and its use by personnel.
2. FLOCK SPECIFIC DATA
2.1. Organization Audit in Flock.
2.1.a. Flock-generated export report: This report should include data
logged from the period of 1/1/2025, to the date this request is processed
(inclusive of those dates). Per Flock's documentation, the Organization
Audit is available within the Insights tab and is defined as searches done
within the Department. Please include, at a minimum, the following fields:
Name, Total Networks Searched, Time Frame, License Plate, Case #, Filters,
Reason, and Search Date/Time.
2.2. Network Audit in Flock.
2.2.a. Flock-generated export report: This report should include data
logged from the period of 1/1/2025, to the date this request is processed
(inclusive of those dates). Per Flock's documentation, the Network Audit
is available within the Insights tab and is defined as searches of the
Department’s Flock network by any agency in the Flock System. Please
include, at a minimum, the following fields: Name, Org Name, Total
Networks Searched, Total Devices Searched, Time Frame, License Plate, Case
#, Filters, Reason, and Search Date/Time.
2.3. List of Network Share Settings in Flock:
2.3.a. Data from Flock Platform: The names of agencies and organizations
with which the Department shares ALPR data, also referred to as "Networks
that I’m sharing."
2.3.b. Data from Flock Platform: The names of agencies and organizations
from which the Department receives ALPR data, also referred to as "Flock
networks shared with me."
2.3.c. Data from Flock Platform: The names of agencies and organizations
with which the Department shares “hotlist” information, also referred to
as "Hotlists that I’m sharing."
2.3.d. Data from Flock Platform: The names of agencies and organizations
from which the Department receives “hotlist” information, also referred to
as "Hotlists shared with me."
2.4. Hotlist Information in Flock.
2.4.a. Flock-generated export report: An exported log of hot list actions
(typically "create," "update," and delete") in the Department's Flock
Safety system spanning the last 6 months from the date this request is
processed. This log should include fields detailing, at minimum, a
timestamp, user performing the action, the event type (e.g., 'create',
'update', 'delete'), entity type, and entity details (For Entity Details,
please include at minimum the fields 'hotlist name', 'reason', 'case', and
'expiry'). An example of this document may be viewed here:
https://cdn.muckrock.com/foia_files/2025...
2.4.b. Documentation regarding which external Hotlists the Flock system is
configured to utilize.
2.5. Information on Users with Access to the Flock System.
2.5.a. Documentation indicating users with access to the agency’s Flock
deployment and the access that is enabled/disabled for each user account.
The report should include: User Id, Name, Role, Identity Provider, Last
login, User Mgmt, Search, Device Mgmt, and Hotlist Tool.
3. GENERAL ALPR QUESTIONS
3.1. ALPR "Hot Lists"
3.1.a. A description of all “hot lists” or “custom hot lists” currently
maintained for use in Automated License Plate Reader (ALPR) systems.
3.1.b. Any policies, agreements, or data-sharing documents identifying
external data sources used to populate those lists (e.g., DMV data on
suspended/revoked licenses, NCIC, CLETS, Amber Alerts, stolen vehicle
databases).
3.1.c. Any documentation offering guidance or specifying the criteria
under which plates are added or removed from hot lists.
3.1.d. Any policies, SOPs, and/or software specification indicating how
vehicles without plates or with plates that are unable to be read via
automated software trigger alerts within system(s) utilized by the
department.
3.2. ALPR Installation Locations.
3.2.a. Documentation detailing the location of all Flock camera and other
non-mobile ALPR-capable recording device installations, both city-owned
and non-city owned, that are located in Franklin Township with which the
Department has access to (including via indirect access, such as the
ability to query or otherwise view logged data or analytics). For each
device, please include the following details: location of installation
(provided with enough detail to make the location clear, either as streets
at an intersection or geographic coordinates), street of which camera's
field of view covers, and direction in which camera's field of view covers
(using cardinal directions e.g., 'Eastbound'), device make and model, and
associated owner(s) and/or third-party service provider name(s), if
applicable (e.g., Flock).
3.2.b. If available, documentation including but not limited to memos or
similar which indicate the selection criteria that determined placement of
installed ALPR devices.
Due to additional time needed we require a 15-business day extension with
a deadline of March 31, 2026, to respond to this request.
For questions or additional information, please reply to this email.
Sincerely,
Carissa Mueller
Police
══════════════════════════════════════════════════════════════════════════
To monitor the progress or update this request please log into the [1]OPRA
Center
[2]GovQA logo
References
Visible links
1. OPRA Center
https://u8387778.ct.sendgrid.net/ls/clic...
--- Please respond above this line ---
══════════════════════════════════════════════════════════════════════════
RE: Police Records Request of December 01, 2025, Reference #
P000810-120125
Dear ANONYMOUS,
Franklin Township Police Department, Somerset County received a public
records request from you on December 01, 2025. Your request was for the
following record(s):
I respectfully request access to the following records related to the
Franklin Township Police Department’s Flock Safety and other automatic
license plate readers (ALPRs), specifically:
1. FLOCK SAFETY INFORMATION
1.1. CONTRACTS and AGREEMENTS
1.1.a. All contracts, licenses, MOUs, MOAs, data agreements, letters of
intent, Statement of Work documents, Scope of Work documents, purchase
orders, and other agreement documents with Flock Safety ('Flock', and/or
'Flock Group, Inc.') that are currently or were active any time between
1/1/2020 and the date this request is processed (inclusive of those
dates). This includes documentation related to the acquisition, leasing,
and/or use of Flock Safety cameras or services, including associated data
platforms and analytics tools.
1.2. GUIDING DOCUMENTATION and POLICIES
1.2.a. All policies, memorandums of understanding, and other guidance
materials generated by the Department and/or any entity operating on its
behalf regarding the acquisition and use of any data or services provided
by Flock Safety ('Flock', and/or 'Flock Group, Inc.') and any
representative thereof or any subdivision thereof. Responsive materials
include, but are not limited to, any data-sharing agreements, retention
policies, training materials, or other guidance materials.
1.2.b. All policies, records, emails, or data related to the sharing of
passwords or otherwise offering access (e.g., performing searches
informally by non-official request) with local, regional, or federal task
forces or agents.
1.2.c. All non-email records detailing policies, SOPs, directives,
training materials, and other guidance materials on when and how ALPR
alerts may be utilized to initiate or justify traffic stops or detentions,
requirements for independent corroboration or verification before
enforcement action, documentation and/or reporting expectations for
ALPR-related encounters, how hits are verified and how mismatches or false
positives are handled, information on data retention and personnel access
restrictions, and any policy memos explaining change history within any
related documents.
1.2.d. All policies, SOPs, or other guidance materials generated by the
agency detailing the required frequency of Organization Audits, Network
Audits, and other audits of the Flock system and its use by personnel.
2. FLOCK SPECIFIC DATA
2.1. Organization Audit in Flock.
2.1.a. Flock-generated export report: This report should include data
logged from the period of 1/1/2025, to the date this request is processed
(inclusive of those dates). Per Flock's documentation, the Organization
Audit is available within the Insights tab and is defined as searches done
within the Department. Please include, at a minimum, the following fields:
Name, Total Networks Searched, Time Frame, License Plate, Case #, Filters,
Reason, and Search Date/Time.
2.2. Network Audit in Flock.
2.2.a. Flock-generated export report: This report should include data
logged from the period of 1/1/2025, to the date this request is processed
(inclusive of those dates). Per Flock's documentation, the Network Audit
is available within the Insights tab and is defined as searches of the
Department’s Flock network by any agency in the Flock System. Please
include, at a minimum, the following fields: Name, Org Name, Total
Networks Searched, Total Devices Searched, Time Frame, License Plate, Case
#, Filters, Reason, and Search Date/Time.
2.3. List of Network Share Settings in Flock:
2.3.a. Data from Flock Platform: The names of agencies and organizations
with which the Department shares ALPR data, also referred to as "Networks
that I’m sharing."
2.3.b. Data from Flock Platform: The names of agencies and organizations
from which the Department receives ALPR data, also referred to as "Flock
networks shared with me."
2.3.c. Data from Flock Platform: The names of agencies and organizations
with which the Department shares “hotlist” information, also referred to
as "Hotlists that I’m sharing."
2.3.d. Data from Flock Platform: The names of agencies and organizations
from which the Department receives “hotlist” information, also referred to
as "Hotlists shared with me."
2.4. Hotlist Information in Flock.
2.4.a. Flock-generated export report: An exported log of hot list actions
(typically "create," "update," and delete") in the Department's Flock
Safety system spanning the last 6 months from the date this request is
processed. This log should include fields detailing, at minimum, a
timestamp, user performing the action, the event type (e.g., 'create',
'update', 'delete'), entity type, and entity details (For Entity Details,
please include at minimum the fields 'hotlist name', 'reason', 'case', and
'expiry'). An example of this document may be viewed here:
https://cdn.muckrock.com/foia_files/2025...
2.4.b. Documentation regarding which external Hotlists the Flock system is
configured to utilize.
2.5. Information on Users with Access to the Flock System.
2.5.a. Documentation indicating users with access to the agency’s Flock
deployment and the access that is enabled/disabled for each user account.
The report should include: User Id, Name, Role, Identity Provider, Last
login, User Mgmt, Search, Device Mgmt, and Hotlist Tool.
3. GENERAL ALPR QUESTIONS
3.1. ALPR "Hot Lists"
3.1.a. A description of all “hot lists” or “custom hot lists” currently
maintained for use in Automated License Plate Reader (ALPR) systems.
3.1.b. Any policies, agreements, or data-sharing documents identifying
external data sources used to populate those lists (e.g., DMV data on
suspended/revoked licenses, NCIC, CLETS, Amber Alerts, stolen vehicle
databases).
3.1.c. Any documentation offering guidance or specifying the criteria
under which plates are added or removed from hot lists.
3.1.d. Any policies, SOPs, and/or software specification indicating how
vehicles without plates or with plates that are unable to be read via
automated software trigger alerts within system(s) utilized by the
department.
3.2. ALPR Installation Locations.
3.2.a. Documentation detailing the location of all Flock camera and other
non-mobile ALPR-capable recording device installations, both city-owned
and non-city owned, that are located in Franklin Township with which the
Department has access to (including via indirect access, such as the
ability to query or otherwise view logged data or analytics). For each
device, please include the following details: location of installation
(provided with enough detail to make the location clear, either as streets
at an intersection or geographic coordinates), street of which camera's
field of view covers, and direction in which camera's field of view covers
(using cardinal directions e.g., 'Eastbound'), device make and model, and
associated owner(s) and/or third-party service provider name(s), if
applicable (e.g., Flock).
3.2.b. If available, documentation including but not limited to memos or
similar which indicate the selection criteria that determined placement of
installed ALPR devices.
Franklin Township Police Department, Somerset County has reviewed its
files and has located responsive records to your request. Please log in to
the OPRA Center at the following link to retrieve the responsive records.
[1]Police Records Request - P000810-120125
For questions or additional information, please reply to this email.
Sincerely,
Carissa Mueller
Police
══════════════════════════════════════════════════════════════════════════
To monitor the progress or update this request please log into the [2]OPRA
Center
[3]GovQA logo
References
Visible links
1. https://u8387778.ct.sendgrid.net/ls/clic...
2. OPRA Center
https://u8387778.ct.sendgrid.net/ls/clic...
Dear Franklin Township OPRA,
I appreciate your reply to my request. It seems (based on the correspondence in this thread) that I have been made an account on the OPRA Center, but I don't have access to the email to create a recovery password for my account. I would appreciate new credentials or responsive records via email.
Yours sincerely,
Anonymous
Hello!
As requested, I’m forwarding you the information for your OPRA request
that was sent through the portal.
Sincerely,
Carissa Mueller
Administrative Aide - Records
Franklin Township Police Department
495 DeMott Ln, Somerset, NJ 08873
(732)-873-5533 Ext. 2035
Fax #: (732)-873-1073
[1][email address]
[2][IMG][3][IMG][4][IMG]
NOTICE : The information contained in this message is privileged and
confidential.
This message is intended for the use of the individual(s) or entity named
above.
If the reader of this message is not the intended recipient, you are
hereby notified
that any dissemination, distribution, and/or copying of this communication
is strictly
prohibited. If you have received this message in error, please notify the
sender by
telephone immediately and permanently delete this message.
References
Visible links
1. mailto:[email address]
2. https://www.facebook.com/FranklinTwpPoli...
3. https://www.instagram.com/ftpd_somersetnj/
4. https://twitter.com/FTPDSomersetNJ?ref_s...