Cities Index.
View Exhibit A

Oakland City Council
June 4, 2024

Document
View Exhibit A
Meeting
June 4, 2024
Body
Oakland City Council
Original file
251 KB
Text extracted from the city's file for reading and search. Open the original on oakland.legistar1.com. That file is the official record.

DRAFT

CITY DATA ADDENDUM
Mobile Parking Payment Systems for
Parking Management and Enforcement

Michael P . Ford
Parking & Mobility Division
Department of Transporta�on
City of Oakland
August 23, 2023

This City Data Addendum [” Addendum”] is Exhibit 1 to the Professional Services Agreement between the City of Oakland [“City”] and Contractor Name [“Contractor”] to provide Mobile Parking Payment Services [“Agreement”] as is set forth with specificity therein and is incorporated into the Agreement by this reference. In the event of a conflict between the terms and condi�ons of this Addendum and the Agreement, the terms of this Addendum shall prevail but only with respect to the maters stated herein.

1. Background
DRAFT
As is set forth with specificity in the Agreement’s Statement of Work [Exhibit D], Contractor avers and covenants to develop, implement and operate a mobile parking payment system [“System”] that, at a minimum, will enable customers to remotely pay for parking sessions by using mobile phones or mobile devices to provide Contractor payment informa�on which Contractor will collect and store for City on Contractor’s mobile so�ware applica�on, website, and/or phone number for City-controlled paid parking [“Services”]. Contractor’s Services may also support daily or monthly permits by zone merchant valida�on Given the sensi�ve nature of the informa�on Contractor will collect and store for City, Contractor further avers and covenants that its System and Services will meet the City’s key goal of enhancing user data protec�ons by complying with: (1) the City’s Surveillance Technology Ordinance (Oakland Municipal Code Chapter 9.64); (2) the City’s Surveillance Impact Report [Exhibit B]; and, (3) the City’s Mobile Parking Payment Use Policy [Exhibit C], all of which are incorporated herein by this reference.

2. Scope and Ownership of Information to be Collected
The Agreement will require Contractor to collect from the users of its System, a broad range of personal and sensitive information. The California Consumer Privacy Act [CCPA]1 and Consumer Privacy Rights Act [“CPRA”] 2 definitions for “personal information”3 and “sensitive personal information”4 are incorporated herein by this reference and shall apply to the information Contractor collects.

1 Cal. Civ. Code Sec�on 1798 et. seq.
2 The CPRA is more accurately described as an amendment of the CCPA. The CPRA specifically states that it “amends” exis�ng provisions of Title 1.81.5 of the California Civil Code (currently known as the CCPA) and “adds” new provisions (related to the establishment of the California Privacy Protec�on Agency). 3 It identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular consumer or household. 4 It contains some or all of the following;
• social security, driver’s license, state iden�fica�on card, or passport number • account log-in, financial account, debit card, or credit card number in combina�on with any required security or access code, password, or creden�als allowing access to an account.

DRAFT
With the exception of that information which is publicly known or available as set forth in Section 5 [“Confidential Information”] of the Agreement, City data [“Data”] shall consist of any and all data disclosed or provided by the City to Contractor, including but not limited to, all data, files, documentation, information, communications, media, whether intangible or tangible, whether provided directly or indirectly by Contractor to provide its Services, together with any and all results of Contractor’s providing of its Services, including all data Contractor accesses, collects, modifies, develops as work product, or otherwise generates while providing its Services to City under this Agreement, whether pursuant or incidental to the purposes of the Agreement and whether or not delivered to the City, shall be the exclusive property of, and all ownership rights therein shall vest in, the City (collectively “City Data”).

To the extent necessary, Contractor hereby assigns to the City, the rights to City Data which arise out of, or are developed in connec�on with or are the results of, Contractor’s Services.

3. Use of City Data

3.1 By Contractor

Contractor avers and covenants to:

• Comply with the terms of the City’s Surveillance Technology Ordinance [OMC 9.64] • Comply with
o the City’s Surveillance Impact Report [Exhibit B];
o the City’s Mobile Parking Payment Use Policy [Exhibit C], • Anonymize the City Data and take such other steps as may be required to assure that personally iden�fiable or personally sensi�ve informa�on are not visible to City staff at any �me for any reason;
DRAFT
• Not sell, rent, release, disclose, disseminate, make available, transfer, or otherwise communicate orally, in wri�ng, or by electronic or other means, City Data, to another business or a third party for monetary or other valuable considera�on; • Only share City Data with third par�es as permited by City’s Mobile Parking Payment Use Policy [Exhibit C; Sec�on 8 “Third-Party Data-Sharing”]; • Only use City Data to fulfill its obliga�ons to City under the Agreement; • Comply with the terms of the Agreement;
• Implement security safeguards;
• Not combine City Data with personal informa�on received from others; • No�fy City when it uses subcontractors;
• Pass through the Agreement’s terms and condi�ons to any subcontractors it uses; .

N otwithstanding any other law or provision of this Agreement, Contractor shall, during its provision of Services to City as called for hereunder, take all steps necessary to assure that all Data resul�ng from its Services is kept confiden�al and disclosed: (1) only to Contractor’s personnel, agents or subcontractors with an absolute need to have access to the Data, who have executed a Confiden�ality Agreement with Contractor sufficient to enable Contractor to comply with the requirements of this Sec�on 4, with Contractor remaining liable for any breach of this Sec�on 4 by its personnel, agents or subcontractors; and (2) to the City Project Manager for such dissemina�on as the City Project Manager, in its sole discre�on, determines should be made; or (3) as required by law

Contractor shall fully indemnify City for any third-party claims against City resul�ng from Contractor’s use of City Data in viola�on of this Addendum’s provisions.

3.2 By City
City’s access to City Data shall be limited to authorized staff and used only as permitted by City’s Surveillance Use Policy [Exhibit B] and as required by City’s parking enforcement responsibilities [Resolution 84664 C.M.S.] which include but, are not limited to, shaping parking DRAFT
policies and practices to better support the City’s Parking Principles and developing a more equitable mobility system. In this regard, only designated DOT and Finance Department staff will have access through unique portal credentials to the following anonymized City Data Contractor stores:
• Estimating parking demand, occupancy, and revenues;
• Evaluating parking payment options;
• Monitoring demand-responsive parking areas and compliance; • Reconciling payment transactions with total parking revenues received; • Promoting compliance and enforcing parking restrictions, permits, and payment; • Reviewing contested parking citations;
• Remitting user transaction fees to Providers via invoices;

4. Contractor’s System Security

This Agreement requires Contractor to store City Data in Contractor’s certified data center[s] which are external to the City’s premises and administered by Contractor for the purposes of this Agreement [“System”]. City’s Data is highly sensitive, confidential and is of paramount importance to the City because unauthorized disclosures of the Data could seriously harm the City and possibly third parties.

Contractor acknowledges that City, in entering into this Agreement with Contractor, is relying upon Contractor’s professional expertise, know-how, judgment, experience and its representations in its System Security Plan that the integrity of the security, availability and processing of its System protects and preserves the confidentiality and privacy of the City Data. Contractor warrants that its System has been accredited under industry recognized standards [e.g., SOC 2] and that, at all times, Contractor will maintain and ensure that the Data remains secure and does not through any of Contractor’s actions or lack of action thereof become vulnerable to unauthorized access by third parties.

DRAFT
Contractor avers and covenants to con�nue to take all technical and organiza�onal measures necessary to protect the informa�on technology systems and data used in connec�on with the opera�on of the Contractor’s business. Without limi�ng the foregoing, Contractor will con�nue to use reasonable efforts to establish and maintain, implement and comply with, reasonable inf orma�on technology, informa�on security, cyber security and data protec�on controls, policies and procedures, including oversight, access controls, encryp�on, technological and physical safeguards and business con�nuity/disaster recovery and security plans that are designed to protect against and prevent breach, destruc�on, loss, unauthorized distribu�on, use, access, disablement, misappropria�on or modifica�on, or other compromise or misuse of or rela�ng to any informa�on technology system or da ta used in connec�on with the opera�on of Contractor’s business.

Contractor agrees to maintain the City Data and to not disclose such information except as required to perform hereunder or as required by law. Contractor shall maintain network risk and cyber liability coverage (including coverage for unauthorized access, failure of security, breach of privacy perils, as well at no�fica�on costs and regulatory defense) as required by the City’s Schedule Q. Such insurance shall be maintained in force at all �mes during the term of this Agreement.

Notwithstanding as may be otherwise provided in either this Addendum or this Agreement and, with the exception of those instances for which the City is responsible, Contractor avers and covenants to be solely responsible for restoring and correcting any corruption to City’s Data that occur by reason of Contractor’s actions or lack thereof, including ransomware attacks upon Contractor and to fully indemnify the City for any claims against City and injury to City resulting from corruptions of the City Data.

5. DATA INCIDENTS

DRAFT
a. Contractor shall implement and maintain a program for managing unauthorized disclosures of, access to, or use of City Data however they may occur (“Data Incident”). In case of a Data Incident, or if Contractor knows or reasonably suspects a Data Incident has occurred, Contractor shall:
(i) Promptly, and in any case in a manner to ensure no�ce within 24 hours, no�fy City’s Director of Informa�on Technology/Chief Informa�on Office and Chief Security Officer, or their designees of the Data Incident or suspected Data Incident; (ii) Cooperate with City and law enforcement agencies, where applicable, to inves�gate and resolve the Data Incident, including without limita�on by providing reasonable assistance to City in no�fying injured third par�es; and (iii) Otherwise comply with applicable laws governing data breach no�fica�on and response.

b. In case of a Data Incident or reasonably suspected Data Incident, Contractor shall, upon request by City:
(i) immediately conduct a reasonable inves�ga�on of the reasons for and circumstances surrounding such Data Incident or reasonably suspected Data Incident; (ii) use best efforts and take all necessary ac�ons to prevent, contain, and mi�gate the impact of, such Data Incident or reasonably suspected Data Incident; (iii) collect and preserve all evidence concerning the discovery, cause, vulnerability, remedial ac�ons and impact related to such Data Incident or reasonably suspected Data Incident, which shall meet reasonable expecta�ons of forensic admissibility; and
(iv) document the incident response and remedial ac�ons taken in detail, which shall meet reasonable expecta�ons of forensic admissibility.

c. In addi�on, if the Data Incident results from Contractor’s breach of this Agreement or negligent or unauthorized act or omission, including without limita�on those of its subcontractors or other agents, Contractor shall:

DRAFT

(i) Indemnify City for any reasonable expense related to no�fica�on of consumers;

(ii) Provide 2 years of credit monitoring service to any affected individual.

(iii) Contractor shall give City prompt access to such records related to a Data Incident as City may reasonably request. City will treat such records as Contractor’s Confiden�al Informa�on pursuant to Sec�on 122 below [“Proprietary or Confiden�al Informa�on]. Contractor is not required to give City access to records that might compromise the security of Contractor’s other customers.

City will coordinate with Contractor on the content of any intended public statements or required notices for the affected individuals and/or notices to the relevant authorities regarding the Data Incident.

6. Termination of the Agreement
Within ten (10) days of the date of termina�on of the Agreement for any reason, Contractor shall send all City Data to City in a format acceptable to the City and which protects and preserves the sensi�ve nature of the City Data. Contractor may not keep copies of the City Data. For the purposes of this provision, Contractor’s Assignment of the Agreement under Sec�on 10 [“Assignment”] or Bankruptcy under Sec�on 33 [“Bankruptcy”] of the Agreement or cessa�on of business shall be considered a Termina�on of the Agreement.

← All documents from this meeting