Searches for race-bias messages (Palo Alto Police Department)

Brandon Smith filed this request with the Palo Alto Police Department of Palo Alto, CA.
Tracking #

W001705-040119

Multi Request Searches for race-bias messages
Status
Completed

Communications

From: Brandon Smith


To Whom It May Concern:

Pursuant to the California Public Records Act, I hereby request the following records:

1. Documents that show what kind of a database your agency's email is stored in (such as Microsoft Access; Oracle; Microsoft Sharepoint; SQL; or Microsoft Exchange).

2a. Documents sufficient to show any FOIA management software or email search software (not including the client one uses to read and reply to email) in use by your agency. These documents could include purchase orders, contracts for use of a service, or—if and only if neither of those are available—some departmental communication portraying the name of the system.

2b. Any vendor-provided manuals or instructions or software documentation for software used by the agency to search emails

2c. Complete copies of any rules, guidelines, instructions, or best practices in use by your agency for searching emails and texts in response to FOIA requests

3. Documents that show all of, and represent the entirety of each of, your agency’s contracts with cell/mobile service providers (sometimes called carriers). Also we request any documents that describe a deletion schedule for text messages sent to/from the devices on your agency's provider contract. For this purpose, "deletion schedule" means a number of days before messages are regularly deleted from the carrier's data repositories. Such a schedule would also specify whether that date is a rolling daily deletion after that many days, or rather periodical, where the number of days represents the period.

4a. Keyword searches of all SMS ("text") records sent to and received by all sworn officers on agency-issued mobile devices

4b. Keyword searches of all emails sent to and received by sworn officers on agency email accounts.

- For the keywords on 4a and 4b, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *email or SMS* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identifier. (An example of unique sender/recipient identification would be an email address or a phone number, depending on the type of record.)

5a. Documents that show what, if any, text-based messaging clients or platforms (you might call them software-based “systems” for messaging, or “instant messaging”) are available for use on computers in your patrol cars. Also we request documents that show what public body maintains or is responsible for each of those clients/platforms. For instance, sometimes a messaging system is maintained and offered by a state agency like highway patrol; other systems are built or contracted-for locally, by your jurisdiction itself. We request the above-described documents on any and all messaging systems deployed on a computer in a police vehicle in your jurisdiction.

If your jurisdiction maintains/provides its own software on in-car computers for "instant messaging”—and therefore is the keeper of records associated with the system, including historic message logs—I request:

5b. Documents sufficient to show what kind of a database that messages crossing the in-car messaging system are stored in. (Examples might be Microsoft Access; Oracle; SQL or similar). The file extension of the message logs will suffice.

5d. Keyword searches of databases containing messages sent and received over the in-car computers' instant messaging system. For the keywords that requester(s) would like searched, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *in-car IM* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identification. An example of unique sender/recipient identification would, in the case of a car-to-car instant message, be some kind of username corresponding to an officer, or, if and only if an officer identifier is not extant, an identifier for a particular computer or patrol car.

6. Documents that provide evidence of any search your jurisdiction that either the department itself or the public body of which it’s a part has undertaken, in the five years prior to the date of this request, for racist, race-biased, or white supremacist terminology. This would include any searches undertaken of text messages, emails, or instant messages, for example, those IMs to and from in-car computers. It need not include an internal investigation of any single officer. Rather, we seek documents that show a search of communications to/from groups of officers, ranging up to the entire department. We seek documents that show the date of the search; the rationale or reason for the search; the search terms used; the name of the public official who requested the search; the total number of officers whose communications were searched (and if a subset of a department, the reason for choosing that subset); the type of communications searched; and any summary of the result(s) of any search. If no document exists that can be construed as a summary of search results, we request the full results of any search.

Please take under advisement:

Communications that contain these terms, if in use by a law enforcement officer, are public and not personal records. Police officers interact directly with a diverse public and any expressions of potentially prejudicial or biased sentiments relate directly to an officer’s job responsibilities and performance. They are undoubtedly subject to disclosure. In the event you cite an ongoing investigation as a reason for withholding a particular record, we ask, as a part of this records request, for a document that shows the date (nothing more) of the last internal communication in the investigation.

Nearly every state, yours included, defines a public record as any record that a public body is in “control” of, not just in the “possession” of. This provides for situations where records are stored in the care of a third-party storage facility, or some kind of technology vendor that provides data storage or communications services to the public body in question. To the extent a technology vendor is in possession of the records sought herein, this request, barring justified exemption, compels the public body to seek the requested documents from its technology vendor.

Should a FOIA officer have one or more questions about the request, please contact Brandon Smith via phone (740-505-0038) or the email address this request was sent from. Mr. Smith would be happy to hear from you.

It is not Mr. Smith’s wish to overburden your office. An email or phone call is probably in order soon to discuss your office’s standard for how much estimated time—say, for review toward redaction—constitutes an unduly burdensome request. That said, we believe the list of search terms contained herein is sufficiently culled to produce only a reasonably number of responsive records.

Rarely does caselaw on what is and is not overly burdensome specify which type of employee is required for processing; the only relevant factor is estimated time by *a* staff member. In other words, if a search would be impossible or overly burdensome for a FOIA staffer, but an IT staffer can do it in ten minutes, then the law requires the public body to request an IT staffer complete the job. This is our purpose in asking for documents showing what type of database each record is stored in: the type of file determines what type of search is possible by a qualified IT staffer.

This request is being made on behalf of Brandon Smith and on behalf of ProPublica.

Search terms list:

nigger
spic
coon
monkey
white power
white genocide
1488
14/88
14 words
fourteen words
mud people
boot party
Curb job
hammerskin
hammer skin
Vinlanders 
Blood & Honour
Blood & Honor
Blood and honor
Gab
mein
heil
Reich
Muslim problem
White genocide
White civil rights
Knights
Filthy jew
Aryan
Confederate flag
Dixie
Diversity is a code word
Globalist
fashy
Chimp out
Chimpout
Goy
Kek
shekels
Kike
TRS
Shills
Identitarian
Stormfront
Daily Stormer
Identity Evropa 
Identity Europa 
Cultural marxist 
Anti-white 
White identity  
Jewish Question 
JQ 
ZOG
Klansman
White pride
WPWW
Rahowa
Ghost skin

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 calendar days, as the statute requires.

Sincerely,

Brandon Smith

From: Palo Alto Police Department

04/01/2019

Dear Brandon :

The City of Palo Alto is dedicated and responsive to our community.  Your request has been received and is being processed.  Your request was given the reference number W001705-040119 for tracking purposes.

Records Requested: To Whom It May Concern:Pursuant to the California Public Records Act, I hereby request the following records:1. Documents that show what kind of a database your agency's email is stored in (such as Microsoft Access; Oracle; Microsoft Sharepoint; SQL; or Microsoft Exchange).2a. Documents sufficient to show any FOIA management software or email search software (not including the client one uses to read and reply to email) in use by your agency. These documents could include purchase orders, contracts for use of a service, or—if and only if neither of those are available—some departmental communication portraying the name of the system.2b. Any vendor-provided manuals or instructions or software documentation for software used by the agency to search emails2c. Complete copies of any rules, guidelines, instructions, or best practices in use by your agency for searching emails and texts in response to FOIA requests3. Documents that show all of, and represent the entirety of each of, your agency’s contracts with cell/mobile service providers (sometimes called carriers). Also we request any documents that describe a deletion schedule for text messages sent to/from the devices on your agency's provider contract. For this purpose, "deletion schedule" means a number of days before messages are regularly deleted from the carrier's data repositories. Such a schedule would also specify whether that date is a rolling daily deletion after that many days, or rather periodical, where the number of days represents the period.4a. Keyword searches of all SMS ("text") records sent to and received by all sworn officers on agency-issued mobile devices4b. Keyword searches of all emails sent to and received by sworn officers on agency email accounts.- For the keywords on 4a and 4b, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.- For each returned *email or SMS* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identifier. (An example of unique sender/recipient identification would be an email address or a phone number, depending on the type of record.)5a. Documents that show what, if any, text-based messaging clients or platforms (you might call them software-based “systems” for messaging, or “instant messaging”) are available for use on computers in your patrol cars. Also we request documents that show what public body maintains or is responsible for each of those clients/platforms. For instance, sometimes a messaging system is maintained and offered by a state agency like highway patrol; other systems are built or contracted-for locally, by your jurisdiction itself. We request the above-described documents on any and all messaging systems deployed on a computer in a police vehicle in your jurisdiction.If your jurisdiction maintains/provides its own software on in-car computers for "instant messaging”—and therefore is the keeper of records associated with the system, including historic message logs—I request:5b. Documents sufficient to show what kind of a database that messages crossing the in-car messaging system are stored in. (Examples might be Microsoft Access; Oracle; SQL or similar). The file extension of the message logs will suffice.5d. Keyword searches of databases containing messages sent and received over the in-car computers' instant messaging system. For the keywords that requester(s) would like searched, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.- For each returned *in-car IM* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identification. An example of unique sender/recipient identification would, in the case of a car-to-car instant message, be some kind of username corresponding to an officer, or, if and only if an officer identifier is not extant, an identifier for a particular computer or patrol car.6. Documents that provide evidence of any search your jurisdiction that either the department itself or the public body of which it’s a part has undertaken, in the five years prior to the date of this request, for racist, race-biased, or white supremacist terminology. This would include any searches undertaken of text messages, emails, or instant messages, for example, those IMs to and from in-car computers. It need not include an internal investigation of any single officer. Rather, we seek documents that show a search of communications to/from groups of officers, ranging up to the entire department. We seek documents that show the date of the search; the rationale or reason for the search; the search terms used; the name of the public official who requested the search; the total number of officers whose communications were searched (and if a subset of a department, the reason for choosing that subset); the type of communications searched; and any summary of the result(s) of any search. If no document exists that can be construed as a summary of search results, we request the full results of any search.Please take under advisement:Communications that contain these terms, if in use by a law enforcement officer, are public and not personal records. Police officers interact directly with a diverse public and any expressions of potentially prejudicial or biased sentiments relate directly to an officer’s job responsibilities and performance. They are undoubtedly subject to disclosure. In the event you cite an ongoing investigation as a reason for withholding a particular record, we ask, as a part of this records request, for a document that shows the date (nothing more) of the last internal communication in the investigation.Nearly every state, yours included, defines a public record as any record that a public body is in “control” of, not just in the “possession” of. This provides for situations where records are stored in the care of a third-party storage facility, or some kind of technology vendor that provides data storage or communications services to the public body in question. To the extent a technology vendor is in possession of the records sought herein, this request, barring justified exemption, compels the public body to seek the requested documents from its technology vendor.Should a FOIA officer have one or more questions about the request, please contact Brandon Smith via phone (740-505-0038) or the email address this request was sent from. Mr. Smith would be happy to hear from you.It is not Mr. Smith’s wish to overburden your office. An email or phone call is probably in order soon to discuss your office’s standard for how much estimated time—say, for review toward redaction—constitutes an unduly burdensome request. That said, we believe the list of search terms contained herein is sufficiently culled to produce only a reasonably number of responsive records.Rarely does caselaw on what is and is not overly burdensome specify which type of employee is required for processing; the only relevant factor is estimated time by *a* staff member. In other words, if a search would be impossible or overly burdensome for a FOIA staffer, but an IT staffer can do it in ten minutes, then the law requires the public body to request an IT staffer complete the job. This is our purpose in asking for documents showing what type of database each record is stored in: the type of file determines what type of search is possible by a qualified IT staffer.This request is being made on behalf of Brandon Smith and on behalf of ProPublica.Search terms list:niggerspiccoonmonkeywhite powerwhite genocide148814/8814 wordsfourteen wordsmud peopleboot partyCurb jobhammerskinhammer skinVinlanders Blood & HonourBlood & HonorBlood and honorGabmeinheilReichMuslim problemWhite genocideWhite civil rightsKnightsFilthy jewAryanConfederate flagDixieDiversity is a code wordGlobalistfashyChimp outChimpoutGoyKekshekelsKikeTRSShillsIdentitarianStormfrontDaily StormerIdentity Evropa Identity Europa Cultural marxist Anti-white White identity Jewish Question JQ ZOGKlansmanWhite prideWPWWRahowaGhost skinThe 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 calendar days, as the statute requires.Sincerely,Brandon SmithUpload documents directly: https://https://www.muckrock.comhttps://accounts.muckrock.com/accounts/login/?url_auth_token=AAAdGnflSbxYB2gXIt04NuwDSx0%3A1hBBTA%3AUj0t2icB9MCXGk94GMRHOaQ82hc&next=https%3A%2F%2Fwww.muckrock.com%2Faccounts%2Flogin%2F%3Femail%3Ddacia.tavares%2540cityofpaloalto.org%26next%3D%252Faccounts%252Fagency_login%252Fpalo-alto-police-department-404%252Fsearches-for-race-bias-messages-palo-alto-police-department-71025%252F#agency-reply

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'll receive an email when your request has been completed.

Thank you.

City of Palo Alto

From: Palo Alto Police Department

--- Please respond above this line ---



04/12/2019


RE: PUBLIC RECORDS REQUEST of April 01, 2019, Reference # W001705-040119
Dear Brandon ,
I am writing in response to your requests for documents under the California Public Records Act (Govt. Code § 6250 et seq.) received by the City on 4/1/2019.
Your request mentioned: To Whom It May Concern:

Pursuant to the California Public Records Act, I hereby request the following records:

1. Documents that show what kind of a database your agency's email is stored in (such as Microsoft Access; Oracle; Microsoft Sharepoint; SQL; or Microsoft Exchange).

2a. Documents sufficient to show any FOIA management software or email search software (not including the client one uses to read and reply to email) in use by your agency. These documents could include purchase orders, contracts for use of a service, or—if and only if neither of those are available—some departmental communication portraying the name of the system.

2b. Any vendor-provided manuals or instructions or software documentation for software used by the agency to search emails

2c. Complete copies of any rules, guidelines, instructions, or best practices in use by your agency for searching emails and texts in response to FOIA requests

3. Documents that show all of, and represent the entirety of each of, your agency’s contracts with cell/mobile service providers (sometimes called carriers). Also we request any documents that describe a deletion schedule for text messages sent to/from the devices on your agency's provider contract. For this purpose, "deletion schedule" means a number of days before messages are regularly deleted from the carrier's data repositories. Such a schedule would also specify whether that date is a rolling daily deletion after that many days, or rather periodical, where the number of days represents the period.

4a. Keyword searches of all SMS ("text") records sent to and received by all sworn officers on agency-issued mobile devices

4b. Keyword searches of all emails sent to and received by sworn officers on agency email accounts.

- For the keywords on 4a and 4b, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *email or SMS* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identifier. (An example of unique sender/recipient identification would be an email address or a phone number, depending on the type of record.)

5a. Documents that show what, if any, text-based messaging clients or platforms (you might call them software-based “systems” for messaging, or “instant messaging”) are available for use on computers in your patrol cars. Also we request documents that show what public body maintains or is responsible for each of those clients/platforms. For instance, sometimes a messaging system is maintained and offered by a state agency like highway patrol; other systems are built or contracted-for locally, by your jurisdiction itself. We request the above-described documents on any and all messaging systems deployed on a computer in a police vehicle in your jurisdiction.

If your jurisdiction maintains/provides its own software on in-car computers for "instant messaging”—and therefore is the keeper of records associated with the system, including historic message logs—I request:

5b. Documents sufficient to show what kind of a database that messages crossing the in-car messaging system are stored in. (Examples might be Microsoft Access; Oracle; SQL or similar). The file extension of the message logs will suffice.

5d. Keyword searches of databases containing messages sent and received over the in-car computers' instant messaging system. For the keywords that requester(s) would like searched, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *in-car IM* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identification. An example of unique sender/recipient identification would, in the case of a car-to-car instant message, be some kind of username corresponding to an officer, or, if and only if an officer identifier is not extant, an identifier for a particular computer or patrol car.

6. Documents that provide evidence of any search your jurisdiction that either the department itself or the public body of which it’s a part has undertaken, in the five years prior to the date of this request, for racist, race-biased, or white supremacist terminology. This would include any searches undertaken of text messages, emails, or instant messages, for example, those IMs to and from in-car computers. It need not include an internal investigation of any single officer. Rather, we seek documents that show a search of communications to/from groups of officers, ranging up to the entire department. We seek documents that show the date of the search; the rationale or reason for the search; the search terms used; the name of the public official who requested the search; the total number of officers whose communications were searched (and if a subset of a department, the reason for choosing that subset); the type of communications searched; and any summary of the result(s) of any search. If no document exists that can be construed as a summary of search results, we request the full results of any search.

Please take under advisement:

Communications that contain these terms, if in use by a law enforcement officer, are public and not personal records. Police officers interact directly with a diverse public and any expressions of potentially prejudicial or biased sentiments relate directly to an officer’s job responsibilities and performance. They are undoubtedly subject to disclosure. In the event you cite an ongoing investigation as a reason for withholding a particular record, we ask, as a part of this records request, for a document that shows the date (nothing more) of the last internal communication in the investigation.

Nearly every state, yours included, defines a public record as any record that a public body is in “control” of, not just in the “possession” of. This provides for situations where records are stored in the care of a third-party storage facility, or some kind of technology vendor that provides data storage or communications services to the public body in question. To the extent a technology vendor is in possession of the records sought herein, this request, barring justified exemption, compels the public body to seek the requested documents from its technology vendor.

Should a FOIA officer have one or more questions about the request, please contact Brandon Smith via phone (740-505-0038) or the email address this request was sent from. Mr. Smith would be happy to hear from you.

It is not Mr. Smith’s wish to overburden your office. An email or phone call is probably in order soon to discuss your office’s standard for how much estimated time—say, for review toward redaction—constitutes an unduly burdensome request. That said, we believe the list of search terms contained herein is sufficiently culled to produce only a reasonably number of responsive records.

Rarely does caselaw on what is and is not overly burdensome specify which type of employee is required for processing; the only relevant factor is estimated time by *a* staff member. In other words, if a search would be impossible or overly burdensome for a FOIA staffer, but an IT staffer can do it in ten minutes, then the law requires the public body to request an IT staffer complete the job. This is our purpose in asking for documents showing what type of database each record is stored in: the type of file determines what type of search is possible by a qualified IT staffer.

This request is being made on behalf of Brandon Smith and on behalf of ProPublica.

Search terms list:

nigger
spic
coon
monkey
white power
white genocide
1488
14/88
14 words
fourteen words
mud people
boot party
Curb job
hammerskin
hammer skin
Vinlanders
Blood & Honour
Blood & Honor
Blood and honor
Gab
mein
heil
Reich
Muslim problem
White genocide
White civil rights
Knights
Filthy jew
Aryan
Confederate flag
Dixie
Diversity is a code word
Globalist
fashy
Chimp out
Chimpout
Goy
Kek
shekels
Kike
TRS
Shills
Identitarian
Stormfront
Daily Stormer
Identity Evropa
Identity Europa
Cultural marxist
Anti-white
White identity
Jewish Question
JQ
ZOG
Klansman
White pride
WPWW
Rahowa
Ghost skin

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 calendar days, as the statute requires.

Sincerely,

Brandon Smith

This letter is to clarify what information that you are seeking from the City.  Please confirm if you are looking for key words in a derogatory manner, or any time used.  For example, are you looking for every time the company "Survey Monkey" is listed, the NHL Hockey Team Las Vegas Golden Knights, or White when it refers to the last name of a person, a color of a vehicle, color of a building/house, or name of a Business/Corporation?  If not, and you are willing to narrow your request to emails that are the Key Word phrases you provided, then this should allow us to have a more focused search.   Please respond to my request for clarification so that we may proceed.
Sincerely, Lisa Scheff Public Safety Program Manager/Records Police Department

From: Palo Alto Police Department

--- Please respond above this line ---



04/12/2019


RE: PUBLIC RECORDS REQUEST of April 01, 2019, Reference # W001705-040119
Dear Brandon ,
I am writing in response to your requests for documents under the California Public Records Act (Govt. Code § 6250 et seq.) received by the City on 4/1/2019.
Your request mentioned: To Whom It May Concern:

Pursuant to the California Public Records Act, I hereby request the following records:

1. Documents that show what kind of a database your agency's email is stored in (such as Microsoft Access; Oracle; Microsoft Sharepoint; SQL; or Microsoft Exchange).

2a. Documents sufficient to show any FOIA management software or email search software (not including the client one uses to read and reply to email) in use by your agency. These documents could include purchase orders, contracts for use of a service, or—if and only if neither of those are available—some departmental communication portraying the name of the system.

2b. Any vendor-provided manuals or instructions or software documentation for software used by the agency to search emails

2c. Complete copies of any rules, guidelines, instructions, or best practices in use by your agency for searching emails and texts in response to FOIA requests

3. Documents that show all of, and represent the entirety of each of, your agency’s contracts with cell/mobile service providers (sometimes called carriers). Also we request any documents that describe a deletion schedule for text messages sent to/from the devices on your agency's provider contract. For this purpose, "deletion schedule" means a number of days before messages are regularly deleted from the carrier's data repositories. Such a schedule would also specify whether that date is a rolling daily deletion after that many days, or rather periodical, where the number of days represents the period.

4a. Keyword searches of all SMS ("text") records sent to and received by all sworn officers on agency-issued mobile devices

4b. Keyword searches of all emails sent to and received by sworn officers on agency email accounts.

- For the keywords on 4a and 4b, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *email or SMS* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identifier. (An example of unique sender/recipient identification would be an email address or a phone number, depending on the type of record.)

5a. Documents that show what, if any, text-based messaging clients or platforms (you might call them software-based “systems” for messaging, or “instant messaging”) are available for use on computers in your patrol cars. Also we request documents that show what public body maintains or is responsible for each of those clients/platforms. For instance, sometimes a messaging system is maintained and offered by a state agency like highway patrol; other systems are built or contracted-for locally, by your jurisdiction itself. We request the above-described documents on any and all messaging systems deployed on a computer in a police vehicle in your jurisdiction.

If your jurisdiction maintains/provides its own software on in-car computers for "instant messaging”—and therefore is the keeper of records associated with the system, including historic message logs—I request:

5b. Documents sufficient to show what kind of a database that messages crossing the in-car messaging system are stored in. (Examples might be Microsoft Access; Oracle; SQL or similar). The file extension of the message logs will suffice.

5d. Keyword searches of databases containing messages sent and received over the in-car computers' instant messaging system. For the keywords that requester(s) would like searched, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *in-car IM* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identification. An example of unique sender/recipient identification would, in the case of a car-to-car instant message, be some kind of username corresponding to an officer, or, if and only if an officer identifier is not extant, an identifier for a particular computer or patrol car.

6. Documents that provide evidence of any search your jurisdiction that either the department itself or the public body of which it’s a part has undertaken, in the five years prior to the date of this request, for racist, race-biased, or white supremacist terminology. This would include any searches undertaken of text messages, emails, or instant messages, for example, those IMs to and from in-car computers. It need not include an internal investigation of any single officer. Rather, we seek documents that show a search of communications to/from groups of officers, ranging up to the entire department. We seek documents that show the date of the search; the rationale or reason for the search; the search terms used; the name of the public official who requested the search; the total number of officers whose communications were searched (and if a subset of a department, the reason for choosing that subset); the type of communications searched; and any summary of the result(s) of any search. If no document exists that can be construed as a summary of search results, we request the full results of any search.

Please take under advisement:

Communications that contain these terms, if in use by a law enforcement officer, are public and not personal records. Police officers interact directly with a diverse public and any expressions of potentially prejudicial or biased sentiments relate directly to an officer’s job responsibilities and performance. They are undoubtedly subject to disclosure. In the event you cite an ongoing investigation as a reason for withholding a particular record, we ask, as a part of this records request, for a document that shows the date (nothing more) of the last internal communication in the investigation.

Nearly every state, yours included, defines a public record as any record that a public body is in “control” of, not just in the “possession” of. This provides for situations where records are stored in the care of a third-party storage facility, or some kind of technology vendor that provides data storage or communications services to the public body in question. To the extent a technology vendor is in possession of the records sought herein, this request, barring justified exemption, compels the public body to seek the requested documents from its technology vendor.

Should a FOIA officer have one or more questions about the request, please contact Brandon Smith via phone (740-505-0038) or the email address this request was sent from. Mr. Smith would be happy to hear from you.

It is not Mr. Smith’s wish to overburden your office. An email or phone call is probably in order soon to discuss your office’s standard for how much estimated time—say, for review toward redaction—constitutes an unduly burdensome request. That said, we believe the list of search terms contained herein is sufficiently culled to produce only a reasonably number of responsive records.

Rarely does caselaw on what is and is not overly burdensome specify which type of employee is required for processing; the only relevant factor is estimated time by *a* staff member. In other words, if a search would be impossible or overly burdensome for a FOIA staffer, but an IT staffer can do it in ten minutes, then the law requires the public body to request an IT staffer complete the job. This is our purpose in asking for documents showing what type of database each record is stored in: the type of file determines what type of search is possible by a qualified IT staffer.

This request is being made on behalf of Brandon Smith and on behalf of ProPublica.

Search terms list:

nigger
spic
coon
monkey
white power
white genocide
1488
14/88
14 words
fourteen words
mud people
boot party
Curb job
hammerskin
hammer skin
Vinlanders
Blood & Honour
Blood & Honor
Blood and honor
Gab
mein
heil
Reich
Muslim problem
White genocide
White civil rights
Knights
Filthy jew
Aryan
Confederate flag
Dixie
Diversity is a code word
Globalist
fashy
Chimp out
Chimpout
Goy
Kek
shekels
Kike
TRS
Shills
Identitarian
Stormfront
Daily Stormer
Identity Evropa
Identity Europa
Cultural marxist
Anti-white
White identity
Jewish Question
JQ
ZOG
Klansman
White pride
WPWW
Rahowa
Ghost skin

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 calendar days, as the statute requires.

Sincerely,

Brandon Smith

This letter is to clarify what information that you are seeking from the City.  Please confirm if you are looking for key words in a derogatory manner, or any time used.  For example, are you looking for every time the company "Survey Monkey" is listed, the NHL Hockey Team Las Vegas Golden Knights, or White when it refers to the last name of a person, a color of a vehicle, color of a building/house, or name of a Business/Corporation?  If not, and you are willing to narrow your request to emails that are the Key Word phrases you provided, then this should allow us to have a more focused search.   Please respond to my request for clarification so that we may proceed.
Sincerely, Lisa Scheff Public Safety Program Manager/Records Police Department

From:

Hello Mr. Smith,

I received word that you had contacted the Palo Alto City Manager's office today to make an inquiry regarding your California Public Records Act Ref: W001705-0411019. I just tried calling you directly and left you a voicemail message. In that message, I said that I would try to send you an email to the address us used via Muckrock. Below is a snip of the communication I sent via the Gov.QA portal on 4/12/2019:

This letter is to clarify what information that you are seeking from the City. Please confirm if you are looking for key words in a derogatory manner, or any time used. For example, are you looking for every time the company "Survey Monkey" is listed, the NHL Hockey Team Las Vegas Golden Knights, or White when it refers to the last name of a person, a color of a vehicle, color of a building/house, or name of a Business/Corporation? If not, and you are willing to narrow your request to emails that are the Key Word phrases you provided, then this should allow us to have a more focused search. Please respond to my request for clarification so that we may proceed.

Please feel free to contact me directly so that I may know how you want to proceed.

Thank you,

[cid:image001.png@01D4FC51.68049BB0]

From: Palo Alto Police Department

--- Please respond above this line ---



05/02/2019


RE: PUBLIC RECORDS REQUEST of April 01, 2019, Reference # W001705-040119
Dear Brandon ,
I am writing in response to your requests for documents under the California Public Records Act (Govt. Code § 6250 et seq.) received by the City on 4/1/2019.
Your request mentioned: To Whom It May Concern:

Pursuant to the California Public Records Act, I hereby request the following records:

1. Documents that show what kind of a database your agency's email is stored in (such as Microsoft Access; Oracle; Microsoft Sharepoint; SQL; or Microsoft Exchange).

2a. Documents sufficient to show any FOIA management software or email search software (not including the client one uses to read and reply to email) in use by your agency. These documents could include purchase orders, contracts for use of a service, or—if and only if neither of those are available—some departmental communication portraying the name of the system.

2b. Any vendor-provided manuals or instructions or software documentation for software used by the agency to search emails

2c. Complete copies of any rules, guidelines, instructions, or best practices in use by your agency for searching emails and texts in response to FOIA requests

3. Documents that show all of, and represent the entirety of each of, your agency’s contracts with cell/mobile service providers (sometimes called carriers). Also we request any documents that describe a deletion schedule for text messages sent to/from the devices on your agency's provider contract. For this purpose, "deletion schedule" means a number of days before messages are regularly deleted from the carrier's data repositories. Such a schedule would also specify whether that date is a rolling daily deletion after that many days, or rather periodical, where the number of days represents the period.

4a. Keyword searches of all SMS ("text") records sent to and received by all sworn officers on agency-issued mobile devices

4b. Keyword searches of all emails sent to and received by sworn officers on agency email accounts.

- For the keywords on 4a and 4b, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *email or SMS* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identifier. (An example of unique sender/recipient identification would be an email address or a phone number, depending on the type of record.)

5a. Documents that show what, if any, text-based messaging clients or platforms (you might call them software-based “systems” for messaging, or “instant messaging”) are available for use on computers in your patrol cars. Also we request documents that show what public body maintains or is responsible for each of those clients/platforms. For instance, sometimes a messaging system is maintained and offered by a state agency like highway patrol; other systems are built or contracted-for locally, by your jurisdiction itself. We request the above-described documents on any and all messaging systems deployed on a computer in a police vehicle in your jurisdiction.

If your jurisdiction maintains/provides its own software on in-car computers for "instant messaging”—and therefore is the keeper of records associated with the system, including historic message logs—I request:

5b. Documents sufficient to show what kind of a database that messages crossing the in-car messaging system are stored in. (Examples might be Microsoft Access; Oracle; SQL or similar). The file extension of the message logs will suffice.

5d. Keyword searches of databases containing messages sent and received over the in-car computers' instant messaging system. For the keywords that requester(s) would like searched, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *in-car IM* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identification. An example of unique sender/recipient identification would, in the case of a car-to-car instant message, be some kind of username corresponding to an officer, or, if and only if an officer identifier is not extant, an identifier for a particular computer or patrol car.

6. Documents that provide evidence of any search your jurisdiction that either the department itself or the public body of which it’s a part has undertaken, in the five years prior to the date of this request, for racist, race-biased, or white supremacist terminology. This would include any searches undertaken of text messages, emails, or instant messages, for example, those IMs to and from in-car computers. It need not include an internal investigation of any single officer. Rather, we seek documents that show a search of communications to/from groups of officers, ranging up to the entire department. We seek documents that show the date of the search; the rationale or reason for the search; the search terms used; the name of the public official who requested the search; the total number of officers whose communications were searched (and if a subset of a department, the reason for choosing that subset); the type of communications searched; and any summary of the result(s) of any search. If no document exists that can be construed as a summary of search results, we request the full results of any search.

Please take under advisement:

Communications that contain these terms, if in use by a law enforcement officer, are public and not personal records. Police officers interact directly with a diverse public and any expressions of potentially prejudicial or biased sentiments relate directly to an officer’s job responsibilities and performance. They are undoubtedly subject to disclosure. In the event you cite an ongoing investigation as a reason for withholding a particular record, we ask, as a part of this records request, for a document that shows the date (nothing more) of the last internal communication in the investigation.

Nearly every state, yours included, defines a public record as any record that a public body is in “control” of, not just in the “possession” of. This provides for situations where records are stored in the care of a third-party storage facility, or some kind of technology vendor that provides data storage or communications services to the public body in question. To the extent a technology vendor is in possession of the records sought herein, this request, barring justified exemption, compels the public body to seek the requested documents from its technology vendor.

Should a FOIA officer have one or more questions about the request, please contact Brandon Smith via phone (740-505-0038) or the email address this request was sent from. Mr. Smith would be happy to hear from you.

It is not Mr. Smith’s wish to overburden your office. An email or phone call is probably in order soon to discuss your office’s standard for how much estimated time—say, for review toward redaction—constitutes an unduly burdensome request. That said, we believe the list of search terms contained herein is sufficiently culled to produce only a reasonably number of responsive records.

Rarely does caselaw on what is and is not overly burdensome specify which type of employee is required for processing; the only relevant factor is estimated time by *a* staff member. In other words, if a search would be impossible or overly burdensome for a FOIA staffer, but an IT staffer can do it in ten minutes, then the law requires the public body to request an IT staffer complete the job. This is our purpose in asking for documents showing what type of database each record is stored in: the type of file determines what type of search is possible by a qualified IT staffer.

This request is being made on behalf of Brandon Smith and on behalf of ProPublica.

Search terms list:

nigger
spic
coon
monkey
white power
white genocide
1488
14/88
14 words
fourteen words
mud people
boot party
Curb job
hammerskin
hammer skin
Vinlanders
Blood & Honour
Blood & Honor
Blood and honor
Gab
mein
heil
Reich
Muslim problem
White genocide
White civil rights
Knights
Filthy jew
Aryan
Confederate flag
Dixie
Diversity is a code word
Globalist
fashy
Chimp out
Chimpout
Goy
Kek
shekels
Kike
TRS
Shills
Identitarian
Stormfront
Daily Stormer
Identity Evropa
Identity Europa
Cultural marxist
Anti-white
White identity
Jewish Question
JQ
ZOG
Klansman
White pride
WPWW
Rahowa
Ghost skin

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 calendar days, as the statute requires.

Sincerely,

Brandon Smith

Mr. Smith, This letter is to clarify what information that you are seeking from the City.
CLARIFICATIONS:  You have requested a voluminous amount of records from the City.  I have tried to contact you on April 12th and on April 26th both by phone voicemail and via email to assist in processing your request. If you would like for the City to proceed with your Public Records Act request, please respond in writing to the City to re-open your request with the clarifications requested.
Thank you, Lisa Scheff Public Safety Program Manager/Records Police Department

From: Palo Alto Police Department

--- Please respond above this line ---



05/02/2019


RE: PUBLIC RECORDS REQUEST of April 01, 2019, Reference # W001705-040119
Dear Brandon ,
I am writing in response to your requests for documents under the California Public Records Act (Govt. Code § 6250 et seq.) received by the City on 4/1/2019.
Your request mentioned: To Whom It May Concern:

Pursuant to the California Public Records Act, I hereby request the following records:

1. Documents that show what kind of a database your agency's email is stored in (such as Microsoft Access; Oracle; Microsoft Sharepoint; SQL; or Microsoft Exchange).

2a. Documents sufficient to show any FOIA management software or email search software (not including the client one uses to read and reply to email) in use by your agency. These documents could include purchase orders, contracts for use of a service, or—if and only if neither of those are available—some departmental communication portraying the name of the system.

2b. Any vendor-provided manuals or instructions or software documentation for software used by the agency to search emails

2c. Complete copies of any rules, guidelines, instructions, or best practices in use by your agency for searching emails and texts in response to FOIA requests

3. Documents that show all of, and represent the entirety of each of, your agency’s contracts with cell/mobile service providers (sometimes called carriers). Also we request any documents that describe a deletion schedule for text messages sent to/from the devices on your agency's provider contract. For this purpose, "deletion schedule" means a number of days before messages are regularly deleted from the carrier's data repositories. Such a schedule would also specify whether that date is a rolling daily deletion after that many days, or rather periodical, where the number of days represents the period.

4a. Keyword searches of all SMS ("text") records sent to and received by all sworn officers on agency-issued mobile devices

4b. Keyword searches of all emails sent to and received by sworn officers on agency email accounts.

- For the keywords on 4a and 4b, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *email or SMS* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identifier. (An example of unique sender/recipient identification would be an email address or a phone number, depending on the type of record.)

5a. Documents that show what, if any, text-based messaging clients or platforms (you might call them software-based “systems” for messaging, or “instant messaging”) are available for use on computers in your patrol cars. Also we request documents that show what public body maintains or is responsible for each of those clients/platforms. For instance, sometimes a messaging system is maintained and offered by a state agency like highway patrol; other systems are built or contracted-for locally, by your jurisdiction itself. We request the above-described documents on any and all messaging systems deployed on a computer in a police vehicle in your jurisdiction.

If your jurisdiction maintains/provides its own software on in-car computers for "instant messaging”—and therefore is the keeper of records associated with the system, including historic message logs—I request:

5b. Documents sufficient to show what kind of a database that messages crossing the in-car messaging system are stored in. (Examples might be Microsoft Access; Oracle; SQL or similar). The file extension of the message logs will suffice.

5d. Keyword searches of databases containing messages sent and received over the in-car computers' instant messaging system. For the keywords that requester(s) would like searched, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *in-car IM* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identification. An example of unique sender/recipient identification would, in the case of a car-to-car instant message, be some kind of username corresponding to an officer, or, if and only if an officer identifier is not extant, an identifier for a particular computer or patrol car.

6. Documents that provide evidence of any search your jurisdiction that either the department itself or the public body of which it’s a part has undertaken, in the five years prior to the date of this request, for racist, race-biased, or white supremacist terminology. This would include any searches undertaken of text messages, emails, or instant messages, for example, those IMs to and from in-car computers. It need not include an internal investigation of any single officer. Rather, we seek documents that show a search of communications to/from groups of officers, ranging up to the entire department. We seek documents that show the date of the search; the rationale or reason for the search; the search terms used; the name of the public official who requested the search; the total number of officers whose communications were searched (and if a subset of a department, the reason for choosing that subset); the type of communications searched; and any summary of the result(s) of any search. If no document exists that can be construed as a summary of search results, we request the full results of any search.

Please take under advisement:

Communications that contain these terms, if in use by a law enforcement officer, are public and not personal records. Police officers interact directly with a diverse public and any expressions of potentially prejudicial or biased sentiments relate directly to an officer’s job responsibilities and performance. They are undoubtedly subject to disclosure. In the event you cite an ongoing investigation as a reason for withholding a particular record, we ask, as a part of this records request, for a document that shows the date (nothing more) of the last internal communication in the investigation.

Nearly every state, yours included, defines a public record as any record that a public body is in “control” of, not just in the “possession” of. This provides for situations where records are stored in the care of a third-party storage facility, or some kind of technology vendor that provides data storage or communications services to the public body in question. To the extent a technology vendor is in possession of the records sought herein, this request, barring justified exemption, compels the public body to seek the requested documents from its technology vendor.

Should a FOIA officer have one or more questions about the request, please contact Brandon Smith via phone (740-505-0038) or the email address this request was sent from. Mr. Smith would be happy to hear from you.

It is not Mr. Smith’s wish to overburden your office. An email or phone call is probably in order soon to discuss your office’s standard for how much estimated time—say, for review toward redaction—constitutes an unduly burdensome request. That said, we believe the list of search terms contained herein is sufficiently culled to produce only a reasonably number of responsive records.

Rarely does caselaw on what is and is not overly burdensome specify which type of employee is required for processing; the only relevant factor is estimated time by *a* staff member. In other words, if a search would be impossible or overly burdensome for a FOIA staffer, but an IT staffer can do it in ten minutes, then the law requires the public body to request an IT staffer complete the job. This is our purpose in asking for documents showing what type of database each record is stored in: the type of file determines what type of search is possible by a qualified IT staffer.

This request is being made on behalf of Brandon Smith and on behalf of ProPublica.

Search terms list:

nigger
spic
coon
monkey
white power
white genocide
1488
14/88
14 words
fourteen words
mud people
boot party
Curb job
hammerskin
hammer skin
Vinlanders
Blood & Honour
Blood & Honor
Blood and honor
Gab
mein
heil
Reich
Muslim problem
White genocide
White civil rights
Knights
Filthy jew
Aryan
Confederate flag
Dixie
Diversity is a code word
Globalist
fashy
Chimp out
Chimpout
Goy
Kek
shekels
Kike
TRS
Shills
Identitarian
Stormfront
Daily Stormer
Identity Evropa
Identity Europa
Cultural marxist
Anti-white
White identity
Jewish Question
JQ
ZOG
Klansman
White pride
WPWW
Rahowa
Ghost skin

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 calendar days, as the statute requires.

Sincerely,

Brandon Smith

Mr. Smith, This letter is to clarify what information that you are seeking from the City.
CLARIFICATIONS:  You have requested a voluminous amount of records from the City.  I have tried to contact you on April 12th and on April 26th both by phone voicemail and via email to assist in processing your request. If you would like for the City to proceed with your Public Records Act request, please respond in writing to the City to re-open your request with the clarifications requested.
Thank you, Lisa Scheff Public Safety Program Manager/Records Police Department

From: Brandon Smith

Hi Lisa. Thank you for following up.

In response to your message on 5-7, I would like the terms searched in their entirety. That is, if a term (defined as a word, words, or characters, on a single *line* of my aforementioned list) contains two words with a space, there is no need to search just one of the words. That will likely, as you have mentioned, result in a false positive result. (It seems as though you're able to discern what I'm actually looking for.) Instead, please search only for the full term that is on a single line of my list, including any spaces, if present. Also, as I believe i mentioned in my request, please ensure you search for all combinations of capital and lowercase letters. I may ask for proof that that happened upon the completion of my request.

My apologies if I had missed your call. Any voicemails left in the future should be returned more promptly.

Thank you for your attention to the request.

Best regards,
Brandon Smith

From: Brandon Smith

Hi, Lisa. Can you confirm you received my message dated 5-20-19? I had asked for the terms to be searched as stated in the original request--that is, regardless of intent of use.

Best,
Brandon

From: Palo Alto Police Department

--- Please respond above this line ---

June 17, 2019
Hi Brandon,
Yes, I did receive your response.  I tried calling you right back, but it went to voicemail.  My response to you is under review and I hope to have it to you no later than Thursday, June 20, 2019.
Thank you,
Lisa

From: Palo Alto Police Department

--- Please respond above this line ---



06/20/2019


RE: PUBLIC RECORDS REQUEST of April 01, 2019, Reference # W001705-040119
Dear Brandon ,
I am writing in response to your requests for documents under the California Public Records Act (Govt. Code § 6250 et seq.) received by the City on 4/1/2019.
Your request mentioned: To Whom It May Concern:

Pursuant to the California Public Records Act, I hereby request the following records:

1. Documents that show what kind of a database your agency's email is stored in (such as Microsoft Access; Oracle; Microsoft Sharepoint; SQL; or Microsoft Exchange).

2a. Documents sufficient to show any FOIA management software or email search software (not including the client one uses to read and reply to email) in use by your agency. These documents could include purchase orders, contracts for use of a service, or—if and only if neither of those are available—some departmental communication portraying the name of the system.

2b. Any vendor-provided manuals or instructions or software documentation for software used by the agency to search emails

2c. Complete copies of any rules, guidelines, instructions, or best practices in use by your agency for searching emails and texts in response to FOIA requests

3. Documents that show all of, and represent the entirety of each of, your agency’s contracts with cell/mobile service providers (sometimes called carriers). Also we request any documents that describe a deletion schedule for text messages sent to/from the devices on your agency's provider contract. For this purpose, "deletion schedule" means a number of days before messages are regularly deleted from the carrier's data repositories. Such a schedule would also specify whether that date is a rolling daily deletion after that many days, or rather periodical, where the number of days represents the period.

4a. Keyword searches of all SMS ("text") records sent to and received by all sworn officers on agency-issued mobile devices

4b. Keyword searches of all emails sent to and received by sworn officers on agency email accounts.

- For the keywords on 4a and 4b, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *email or SMS* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identifier. (An example of unique sender/recipient identification would be an email address or a phone number, depending on the type of record.)

5a. Documents that show what, if any, text-based messaging clients or platforms (you might call them software-based “systems” for messaging, or “instant messaging”) are available for use on computers in your patrol cars. Also we request documents that show what public body maintains or is responsible for each of those clients/platforms. For instance, sometimes a messaging system is maintained and offered by a state agency like highway patrol; other systems are built or contracted-for locally, by your jurisdiction itself. We request the above-described documents on any and all messaging systems deployed on a computer in a police vehicle in your jurisdiction.

If your jurisdiction maintains/provides its own software on in-car computers for "instant messaging”—and therefore is the keeper of records associated with the system, including historic message logs—I request:

5b. Documents sufficient to show what kind of a database that messages crossing the in-car messaging system are stored in. (Examples might be Microsoft Access; Oracle; SQL or similar). The file extension of the message logs will suffice.

5d. Keyword searches of databases containing messages sent and received over the in-car computers' instant messaging system. For the keywords that requester(s) would like searched, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *in-car IM* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identification. An example of unique sender/recipient identification would, in the case of a car-to-car instant message, be some kind of username corresponding to an officer, or, if and only if an officer identifier is not extant, an identifier for a particular computer or patrol car.

6. Documents that provide evidence of any search your jurisdiction that either the department itself or the public body of which it’s a part has undertaken, in the five years prior to the date of this request, for racist, race-biased, or white supremacist terminology. This would include any searches undertaken of text messages, emails, or instant messages, for example, those IMs to and from in-car computers. It need not include an internal investigation of any single officer. Rather, we seek documents that show a search of communications to/from groups of officers, ranging up to the entire department. We seek documents that show the date of the search; the rationale or reason for the search; the search terms used; the name of the public official who requested the search; the total number of officers whose communications were searched (and if a subset of a department, the reason for choosing that subset); the type of communications searched; and any summary of the result(s) of any search. If no document exists that can be construed as a summary of search results, we request the full results of any search.

Please take under advisement:

Communications that contain these terms, if in use by a law enforcement officer, are public and not personal records. Police officers interact directly with a diverse public and any expressions of potentially prejudicial or biased sentiments relate directly to an officer’s job responsibilities and performance. They are undoubtedly subject to disclosure. In the event you cite an ongoing investigation as a reason for withholding a particular record, we ask, as a part of this records request, for a document that shows the date (nothing more) of the last internal communication in the investigation.

Nearly every state, yours included, defines a public record as any record that a public body is in “control” of, not just in the “possession” of. This provides for situations where records are stored in the care of a third-party storage facility, or some kind of technology vendor that provides data storage or communications services to the public body in question. To the extent a technology vendor is in possession of the records sought herein, this request, barring justified exemption, compels the public body to seek the requested documents from its technology vendor.

Should a FOIA officer have one or more questions about the request, please contact Brandon Smith via phone (740-505-0038) or the email address this request was sent from. Mr. Smith would be happy to hear from you.

It is not Mr. Smith’s wish to overburden your office. An email or phone call is probably in order soon to discuss your office’s standard for how much estimated time—say, for review toward redaction—constitutes an unduly burdensome request. That said, we believe the list of search terms contained herein is sufficiently culled to produce only a reasonably number of responsive records.

Rarely does caselaw on what is and is not overly burdensome specify which type of employee is required for processing; the only relevant factor is estimated time by *a* staff member. In other words, if a search would be impossible or overly burdensome for a FOIA staffer, but an IT staffer can do it in ten minutes, then the law requires the public body to request an IT staffer complete the job. This is our purpose in asking for documents showing what type of database each record is stored in: the type of file determines what type of search is possible by a qualified IT staffer.

This request is being made on behalf of Brandon Smith and on behalf of ProPublica.

Search terms list:

nigger
spic
coon
monkey
white power
white genocide
1488
14/88
14 words
fourteen words
mud people
boot party
Curb job
hammerskin
hammer skin
Vinlanders
Blood & Honour
Blood & Honor
Blood and honor
Gab
mein
heil
Reich
Muslim problem
White genocide
White civil rights
Knights
Filthy jew
Aryan
Confederate flag
Dixie
Diversity is a code word
Globalist
fashy
Chimp out
Chimpout
Goy
Kek
shekels
Kike
TRS
Shills
Identitarian
Stormfront
Daily Stormer
Identity Evropa
Identity Europa
Cultural marxist
Anti-white
White identity
Jewish Question
JQ
ZOG
Klansman
White pride
WPWW
Rahowa
Ghost skin

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 calendar days, as the statute requires.

Sincerely,

Brandon Smith

From: Palo Alto Police Department

Attachments:

See files attached.

From: Palo Alto Police Department

--- Please respond above this line ---



08/13/2019


RE: PUBLIC RECORDS REQUEST of April 01, 2019, Reference # W001705-040119
Dear Brandon ,
I am writing in response to your requests for documents under the California Public Records Act (Govt. Code § 6250 et seq.) received by the City on 4/1/2019.
Your request mentioned: To Whom It May Concern:

Pursuant to the California Public Records Act, I hereby request the following records:

1. Documents that show what kind of a database your agency's email is stored in (such as Microsoft Access; Oracle; Microsoft Sharepoint; SQL; or Microsoft Exchange).

2a. Documents sufficient to show any FOIA management software or email search software (not including the client one uses to read and reply to email) in use by your agency. These documents could include purchase orders, contracts for use of a service, or—if and only if neither of those are available—some departmental communication portraying the name of the system.

2b. Any vendor-provided manuals or instructions or software documentation for software used by the agency to search emails

2c. Complete copies of any rules, guidelines, instructions, or best practices in use by your agency for searching emails and texts in response to FOIA requests

3. Documents that show all of, and represent the entirety of each of, your agency’s contracts with cell/mobile service providers (sometimes called carriers). Also we request any documents that describe a deletion schedule for text messages sent to/from the devices on your agency's provider contract. For this purpose, "deletion schedule" means a number of days before messages are regularly deleted from the carrier's data repositories. Such a schedule would also specify whether that date is a rolling daily deletion after that many days, or rather periodical, where the number of days represents the period.

4a. Keyword searches of all SMS ("text") records sent to and received by all sworn officers on agency-issued mobile devices

4b. Keyword searches of all emails sent to and received by sworn officers on agency email accounts.

- For the keywords on 4a and 4b, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *email or SMS* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identifier. (An example of unique sender/recipient identification would be an email address or a phone number, depending on the type of record.)

5a. Documents that show what, if any, text-based messaging clients or platforms (you might call them software-based “systems” for messaging, or “instant messaging”) are available for use on computers in your patrol cars. Also we request documents that show what public body maintains or is responsible for each of those clients/platforms. For instance, sometimes a messaging system is maintained and offered by a state agency like highway patrol; other systems are built or contracted-for locally, by your jurisdiction itself. We request the above-described documents on any and all messaging systems deployed on a computer in a police vehicle in your jurisdiction.

If your jurisdiction maintains/provides its own software on in-car computers for "instant messaging”—and therefore is the keeper of records associated with the system, including historic message logs—I request:

5b. Documents sufficient to show what kind of a database that messages crossing the in-car messaging system are stored in. (Examples might be Microsoft Access; Oracle; SQL or similar). The file extension of the message logs will suffice.

5d. Keyword searches of databases containing messages sent and received over the in-car computers' instant messaging system. For the keywords that requester(s) would like searched, please refer to the list at the bottom of this request. Date range is four months prior to the date of the request until the date of the request. Please provide the requesters evidence that your search was agnostic toward capital and lowercase letters throughout each searched character string.

- For each returned *in-car IM* result, please include the following metadata: unique sender identification; unique recipient identification; date and time of transmission; and document(s) sufficient to show the full name of the officer associated with the unique identification. An example of unique sender/recipient identification would, in the case of a car-to-car instant message, be some kind of username corresponding to an officer, or, if and only if an officer identifier is not extant, an identifier for a particular computer or patrol car.

6. Documents that provide evidence of any search your jurisdiction that either the department itself or the public body of which it’s a part has undertaken, in the five years prior to the date of this request, for racist, race-biased, or white supremacist terminology. This would include any searches undertaken of text messages, emails, or instant messages, for example, those IMs to and from in-car computers. It need not include an internal investigation of any single officer. Rather, we seek documents that show a search of communications to/from groups of officers, ranging up to the entire department. We seek documents that show the date of the search; the rationale or reason for the search; the search terms used; the name of the public official who requested the search; the total number of officers whose communications were searched (and if a subset of a department, the reason for choosing that subset); the type of communications searched; and any summary of the result(s) of any search. If no document exists that can be construed as a summary of search results, we request the full results of any search.

Please take under advisement:

Communications that contain these terms, if in use by a law enforcement officer, are public and not personal records. Police officers interact directly with a diverse public and any expressions of potentially prejudicial or biased sentiments relate directly to an officer’s job responsibilities and performance. They are undoubtedly subject to disclosure. In the event you cite an ongoing investigation as a reason for withholding a particular record, we ask, as a part of this records request, for a document that shows the date (nothing more) of the last internal communication in the investigation.

Nearly every state, yours included, defines a public record as any record that a public body is in “control” of, not just in the “possession” of. This provides for situations where records are stored in the care of a third-party storage facility, or some kind of technology vendor that provides data storage or communications services to the public body in question. To the extent a technology vendor is in possession of the records sought herein, this request, barring justified exemption, compels the public body to seek the requested documents from its technology vendor.

Should a FOIA officer have one or more questions about the request, please contact Brandon Smith via phone (740-505-0038) or the email address this request was sent from. Mr. Smith would be happy to hear from you.

It is not Mr. Smith’s wish to overburden your office. An email or phone call is probably in order soon to discuss your office’s standard for how much estimated time—say, for review toward redaction—constitutes an unduly burdensome request. That said, we believe the list of search terms contained herein is sufficiently culled to produce only a reasonably number of responsive records.

Rarely does caselaw on what is and is not overly burdensome specify which type of employee is required for processing; the only relevant factor is estimated time by *a* staff member. In other words, if a search would be impossible or overly burdensome for a FOIA staffer, but an IT staffer can do it in ten minutes, then the law requires the public body to request an IT staffer complete the job. This is our purpose in asking for documents showing what type of database each record is stored in: the type of file determines what type of search is possible by a qualified IT staffer.

This request is being made on behalf of Brandon Smith and on behalf of ProPublica.

Search terms list:

nigger
spic
coon
monkey
white power
white genocide
1488
14/88
14 words
fourteen words
mud people
boot party
Curb job
hammerskin
hammer skin
Vinlanders
Blood & Honour
Blood & Honor
Blood and honor
Gab
mein
heil
Reich
Muslim problem
White genocide
White civil rights
Knights
Filthy jew
Aryan
Confederate flag
Dixie
Diversity is a code word
Globalist
fashy
Chimp out
Chimpout
Goy
Kek
shekels
Kike
TRS
Shills
Identitarian
Stormfront
Daily Stormer
Identity Evropa
Identity Europa
Cultural marxist
Anti-white
White identity
Jewish Question
JQ
ZOG
Klansman
White pride
WPWW
Rahowa
Ghost skin

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 calendar days, as the statute requires.

Sincerely,

Brandon Smith

Response:
1. Documents that show what kind of a database your agency's email is stored in (such as Microsoft Access; Oracle; Microsoft Sharepoint; SQL; or Microsoft Exchange). The City of Palo Alto uses Office 365 / Exchange Online for all Email related data transactions. All City mailboxes are stored within a separate Government tenant located in North America and hosted by Microsoft Corporation. 2a. Documents sufficient to show any FOIA management software or email search software (not including the client one uses to read and reply to email) in use by your agency. These documents could include purchase orders, contracts for use of a service, or—if and only if neither of those are available—some departmental communication portraying the name of the system. . The City of Palo Alto uses the “native” E-Discovery tool available within the Microsoft Office 365 /Security and Compliance Center Government tenant subscription

2b. Any vendor-provided manuals or instructions or software documentation for software used by the agency to search emails The Microsoft eDiscovery documentation can be found online at . https://docs.microsoft.com/en-us/office365/securitycompliance/ediscovery-cases?redirectSourcePath=%252farticle%252fediscovery-cases-in-the-office-365-security-compliance-center-8dd335ab-29d0-41c3-8dd8-9f7c7481e60c (https://u8387795.ct.sendgrid.net/wf/click?upn=Ow1KccipsoIsnXbuEgm-2FN-2BPUx7cPd3hpSFuYyPSGLTvClQUnWyP2vUR-2BxY6BVhz5rMG7AjGuDqkyc6MKwvcQZ3DdG3mesLy3sa7oX3q28REpgIx15XkZ0q8fYh42bEfO-2FSLKiXZzcmT7vVJoa2YCzUr8SyKwT5seCXMzg0Re1CfS0-2FhWc65ZA6M27BlMTLnQc8-2F6ozmD6IMQrLCoAYLNavAs82HWoq1gdVXX-2FyaFPt534awTeQEiixzNECmZfB1ccXmpEYfKdv9LA2fl9NHRBIpkFEdBnwrUmF739rKs1TE-3D_Wdegw-2FrR-2BplQ7bFn03P4NkDrsgfptwEJRbfOjmqG119808xt-2BrPyP2xSs04yCjXlGFN9Pv9D1G-2F8p7P5lYTeQ-2FQIjnZyObt-2FAretL6f0q2diDd1LVLpgSC5s7G1I8YasDSnm5L7YILbfUeMAKdkgDJ28XbGObtDizt8S87yIWD6I7QKvgJOUF2r-2FBkNsNQYR3cIbGMb-2BH-2BBaIJtGowmSLIHRAqPWNXgcnMS2La85t2SqdHGaL47XMP0hoXvMVH59kdpM7Ycr6IUAAMGOa3qTEFnpjeXfLLEAhB3YErNpHvoccj5o-2FSg3BXip3JpAbpRmugVTffURi7InHj1nEMS5uNSG-2BhDGOdaU0rTkpAbXQTsRpN4yJAYkfoYmeKAFTPFTt2EdMC6quO1YaxW48uB0KA-3D-3D)

Sincerely,
Tim Shimizu City of Palo Alto

Files

pages

Close