Predictive policing tools, including PredPol - Code, financial, policy, procurement, use, and other records (Phoenix Police Department)

Beryl Lipton filed this request with the Phoenix Police Department of Phoenix, AZ.
Multi Request Predictive policing tools, including PredPol - Code, financial, policy, procurement, use, and other records
Est. Completion None
Status
Fix Required

Communications

From: Beryl Lipton


To Whom It May Concern:

Pursuant to the Arizona Public Records Law, I hereby request the following records:

Materials and records concerning any predictive policing algorithm, program, software, or tool (including but not limited to the PredPol Predictive Policing Software), which will be referred to primarily as "the software" in this request. If this agency uses another tool that utilizes automated decision making, data analysis, or predictive analytics in the service of policing, provision of that tool's identity and corresponding responsive materials would be greatly appreciated.

Please provide as responsive materials any records related to the testing, trial, solicitation, acquisition, evaluation, and use - either actual, anticipated, past, or proposed - of "the software". Please provide responsive materials even if this agency is not currently using such "software" or if this agency did not proceed to fully adopt trial versions of the "software". I understand that this request or the quantity of responsive materials may require clarification or discussion, and if your office has any questions about this request, I invite you to send them as a response to this email or to give me a call at 617-299-1832.

Specifically, I am requesting the following records and types of records related to the aforementioned "software":

1. ALGORITHM or CODE

Any algorithm or code developed for implementation of or as part of this "software" or program. This includes any algorithm or software developed by or with, given to, used by, purchased or licensed to this agency for implementation of the above referenced program, as well as any algorithm or source code in use by this program or by which this system conducts calculations or decision making. This would include original source code, any compiled binaries (also known as executables), specification documents, spreadsheets, program scripts, and other digital materials used to calculate any data in the above program. I am particularly interested in any algorithms that may have a public policy outcome, such as providing guidance on a policy or an assessment of an individual, and if you have questions about this, I am happy to address them.

2. INPUT DATA

Any input training data for the "software" or related machine learning algorithms or programs.

For the aspects of the software that require an input (for example, to compute a value), please provide a copy of the five most recent sets of data that were used for input, as well as the five most recent outputs of the software, in whatever their native format is. If these inputs or outputs include exempt information, please provide all material save for specific information that is specifically exempted by law. Please also provide a description of input and output data fields that will aid in understanding the type of information that is submitted to the software and that is produced by the software.

3. AGREEMENTS and CONTRACTS

Any and all agreements related to the acquisition and use of the "software," algorithm, or program.

This includes (but is not limited to) all contracts (as well as associated amendments, attachments, and exhibits), data sharing agreements, insurance agreements, intergovernmental services agreements, licensing agreements, memorandums of understanding, and nondisclosure agreements regarding or relevant to this software or program.

Please provide a copy of any informal agreements, insurance agreements, liability waivers, and warranties that reference this technology or otherwise guide its use or the relationship between this agency, the provider or developer of the "software," or any other partner or entity that may use or access it.

4. BIDDING and PROCUREMENT

A copy of any available or relevant Requests for Expressions of Interest, Requests For Proposal (or equivalent calls for bids), responses to Requests for Expressions of Interest, letters of interest, responses to Requests for Proposal, sole source or limited source justification and approval documentation, documentation of selection, and other materials generated in the consideration and selection of the technology in question.

5. FINANCIAL and FUNDING MATERIALS

Any records related to the financing or funding of this "software," including a copy of any related funding opportunity announcements, grant applications, grantor status/progress reports, purchase orders, invoices, and other memoranda and documentation related to the payment or cost (or lack thereof) of the "software," related technology, personnel, equipment, or other elements concerning this "software" or program.

6. INSTRUCTIONAL MATERIALS and TRAINING

All instructional materials, presentations and presentation materials (including recorded video and audio, PowerPoint files, prepared remarks, and slides formats), and other guidance on the use of "the software."

This includes any notes taken during meetings that discussed the use of the software, any explanations (whether generated internally or externally) of how the software works, and any other document that has been used to help explain the use of "the software" to any party, including internal documentation, public relations materials, and executive summaries.

This also includes training material governing the use, sharing, or access to the "software" or any related data related to or collected by this technology, including the legal standard that is required before using the technology.

7. PRIVACY ASSESSMENTS

A copy of any data retention guidelines or policies, data security policies, data security specifications, privacy impact assessments, security audits, or other materials evaluating or guiding the security of the "software" or the privacy of the data involved.

8. USE POLICIES

Please provide a copy of any policy directives, guidance documents, memoranda, training materials, or similar records governing the use of this technology for any purpose, including all those related to data retention, permissible and impermissible use, and security standards. This would include materials that describe the application, function, and use of the "software," including advertisements, emails, handouts, usage policies, PowerPoint presentations, specification documents, or standard operating procedures.

9. AUDITS, REPORTS, and VALIDATION STUDIES

A copy of all reports concerning or mentioning the "software," including audit records, annual reports that mention the use of the "software," reports to legislative bodies, misuse reports, reports to oversight bodies.

This also includes all impact and validation studies. Please provide a copy of any validation studies conducted with respect to the program or with respect to any software or algorithms used in connection with the program. Please also provide a copy of any records pertaining to inquiries for the need of validation studies or discussion of potential or actual validation studies. A “validation study” in this context is any study designed to assess how accurate the program is in predicting what it is supposed to predict, used to assess whether the program may err in the direction of either under- or overestimating likelihoods or predicted outcomes, or intended to evaluate whether the software does or will produce any results that are biased or unexpected in any way.

10. COMMUNICATION and MARKETING MATERIALS

All communications or marketing materials relevant to or mentioning this "software" or program.

This includes any correspondence between any staff at this agency with any other organization or vendor relevant to the use of the aforementioned technology or program, including records related to meetings or follow-up actions with any vendors, companies, or other private entities marketing this technology for any use. This also includes correspondence in the form of emails, email attachments, paper letters, text message, and any other form of correspondence, as well as all marketing materials - unsolicited, requested, or otherwise - acquired from vendors of this technology.

The requested documents will be made available to the general public, and this request is not being made for commercial purposes.

In the event that there are fees, I would be grateful if you would inform me of the total charges in advance of fulfilling my request. I would prefer the request filled electronically, by e-mail attachment if available or CD-ROM if not.

Thank you in advance for your anticipated cooperation in this matter. I look forward to receiving your response to this request within 10 business days.

Sincerely,

Beryl Lipton

From: Beryl Lipton

Hi there,

I submitted this request for public records on October 15, 2019, and I haven't yet received an acknowledgement or a response. Could you please provide one and an estimated completion date?

Thank you very much for your time and help.

Best wishes,
Beryl

From: Phoenix Police Department

Good Morning,

Your request is still pending.

Thank you,

Public Records Team

Public Records and Services Unit

1717 E. Grant St. Ste #100

Phoenix, AZ 85034

Hours: Monday - Friday 8am to 4pm

Phone: 602-534-1127

From: Phoenix Police Department

Good Morning,

Your request is still pending.

Thank you,

Public Records Team

Public Records and Services Unit

1717 E. Grant St. Ste #100

Phoenix, AZ 85034

Hours: Monday - Friday 8am to 4pm

Phone: 602-534-1127

From: Phoenix Police Department

Good Morning,

Your request is still pending. You will be notified once it has been processed.

Thank you.

Public Records Team

From: Phoenix Police Department

Good morning Beryl,

Our IT staff has asked me if you could clarify what software you are referring to when you say "software". Is there a particular program or programs that you want to check for?
Thanks,

Heather

Files

There are no files associated with this request.