Common Council Caucus & Regular Meeting

MINUTES OF A REGULAR MEETING MONDAY, August 3, 2020 The Common Council was convened at 7:02 p.m and was called to order by President Ellis. This meeting was held following Governor Cuomo’s executive order 202.1 and Mayor Sheehan’s emergency order 315-1b. It live streamed on Facebook using Zoom as the meeting platform. The roll being called, the following answered to their names: Anane, Balarin, Conti, Doesschate, Fahey, Farrell, Flynn, Frederick, Hoey, Igoe, Johnson, Kimbrough, Love, O’Brien, Robinson and President Ellis. Also present was the following staff: Danielle Gillespie, John-Raphael Pichardo, Brett Williams, Amy Lavine and Michele Andre. President Pro Tem Kimbrough led the Pledge of Allegiance. PUBLIC COMMENT PERIOD 1) Peter Sheehan, 32 Buckingham Drive, Albany, NY 12208 (Restrictive Covenant at 563 New Scotland Ave) 2) John Clarkson, Pine Hill Neighborhood Association (Ordinance 15.81.19) 3) John Sipos, S. Manning, Albany, NY 12209 (Restrictive Covenant at 563 New Scotland Ave) 4) Alana Klein, 29 Glenwood Street, Albany, NY (Defund Police) 5) Aerielle Morton, 37 Alexander Street, Albany, NY 12202 (The Seventy-Six Development Project on Second Avenue) 6) JoAnn Morton, 34 Alexander Street, Albany, NY 12202 (Amend Map Zoning 7) Marlon Anderson, 214 Lark Street, Albany, NY 12210 (Gun Violence) 8) Kiyonna Friday, 137 Ontario Street, Albany, NY 12206 (Dott’s Garage, members of Proud Boys) 9) Abigail Harris, 584 Madison Ave, Albany, NY 12122 (Dott’s Garage, members of Proud Boys) 10) Danielle Smith, 80 Catherine Street, Albany, NY 12202 (Dott’s Garage, members of Proud Boys) 11) Stephen Craner, 301 South Allen Street, Albany, NY 12208 (Project 563 New Scotland) 12) Najee Friday, 137 Ontario Street, Albany, NY 12206 (Dott’s Garage, members of Proud Boys) 13) Peter Sheehan, 32 Buckingham Drive, Albany, NY 12208 (Restrictive Covenant at 563 New Scotland Ave) 14) Virginia Hammer 52 S. Allen Street, Albany, NY 12208 (Support Ordinance 15.81.19 Veto) 15) Barbara Nazarewicz, 150 Jay Street, Albany, NY 12210 (Support Ordinance 15.81.19 Veto) 16) John Sipos S. Manning, Albany, NY 12209 (Restrictive Covenant at 563 New Scotland Ave) Kara Burke, 229 Davis Ave, Albany, NY 12208 (Dott’s Garage, members of Proud Boys) 17) April Purcell-Bacon, 213 Mt. Hope Drive, Albany, NY 12292 (Dott’s Garage, members of Proud Boys) There being no further speakers, the President declared the Public Comment Period closed. Approval of Minutes President Pro Tem Kimbrough made a motion to approve the minutes of July 20, 2020 meeting of the Council, which was duly seconded, and APPROVED by unanimous voice vote. CONSIDERATION OF LOCAL LAWS: President Pro Tem Kimbrough held the pending Local Laws on the pending agenda. REPORTS OF STANDING COMMITTEES: Finance, Assessment and Taxation: Council Member Farrell reported that the committee will meet on August 20, 2020 at 5:30PM to review Resolution 68.72.20R, 2020 1st quarter financial report, 2020 2nd quarter financial report, 4th quarter of 2019 financial report and discuss any budget concerns that may be associated with covid-19 with Albany City Treasurer, Darius Shahinfar and Budget Director Mike Wheeler. Planning, Economic Development and Land Use: Council Member Fahey reported that the committee will meet on August 5, 2020 at 5:30PM to review Ordinance 10.61.20, Ordinance 11.61.20, Resolution 62.71.20, Resolution 69.72.20R and Resolution 70.72.20R. General Service, Health and Environment: Council Member O’Brien reported that the committee will meet on August 24, 2020 at 5:30PM to review Ordinance 13.72.20, and Ordinance 14.72.20. CONSIDERATION OF ORDINANCES Council Member Frederick noticed Ordinance 15.81.20 as follows, which was held for further consideration: ORDINANCE 15.81.20 AN ORDINANCE AMENDING PART II OF THE CODE OF THE CITY OF ALBANY (GENERAL LEGISLATION) BY ENACTING A NEW CHAPTER 325 TITLED SURVEILLANCE TECHNOLOGY  The City of Albany, in Common Council convened, does hereby ordain and enact Section 1. Part II of the Code of the City of Albany is amended by enacting thereto a new Chapter 325 titled “SURVEILLANCE TECHOLOGY” to read as follows: Chapter 325 Surveillance Technology § 325-1 Purpose The purpose of this Chapter is to provide for the regulation of Surveillance Technology acquisition or use by the City of Albany or the use of the Surveillance Data it provides, to safeguard the right of individuals to privacy, to balance the public's right to privacy with the need to promote and ensure safety and security, to provide protocols for use of Surveillance Technology or Surveillance Data that include specific steps to mitigate potential impacts on the civil rights and liberties of any individuals, communities or groups including communities of color or other marginalized communities in the City, to balance any decision to use Surveillance Technology with an assessment of the costs and protection of privacy, civil liberties and civil rights, to allow for informed public discussion before deploying Surveillance Technology, to provide for transparency, oversight, and accountability, and to minimize the risks posed by use of Surveillance Technology in the City. §325-2 Legislative Findings. The Common Council finds that the broad application of face surveillance in public spaces is the functional equivalent of requiring every person to carry and display a personal photo identification card at all times. Face surveillance technology has been shown to be far less accurate in identifying the faces of people of color, women, and young people, and that such inaccuracies place certain persons at an elevated risk of harmful “false positive” identifications. Many of the databases to which face surveillance technology is applied are plagued by racial and other biases, which generate copycat biases in face surveillance data. The public use of face surveillance can chill the exercise of constitutionally protected free speech. The Common Council further finds that the benefits of using face surveillance, which are few and speculative, are greatly outweighed by its harms, which are substantial. §325-3 Definitions. The following definitions apply to this Chapter: (A) "Annual Surveillance Report" means a written report submitted by th Common Council on an annual basis concerning specific Surveillance Technology used by any City department during the previous year and containing the information set forth in §325-7 of this Chapter. (B) "Exigent Circumstances" means the Police Chief's or the Police Chief’s designee's good faith belief that an emergency involving danger of death, physical injury, or significant  property damage or loss requires use of the Surveillance Technology or the Surveillance Data it provides. The use of Surveillance Technology in Exigent Circumstances shall not infringe upon an individual's right to peacefully protest and exercise other lawful and protected Constitutional Rights. (C) "Identifiable Individuals" means an individual whose identity can be revealed by data, including Surveillance Data, or revealed by data when it is analyzed and/or combined with any record. (D) "Surveillance" means the act of observing or analyzing the movements, behavior, or actions of Identifiable Individuals. (E) "Surveillance Data" means any electronic data collected, captured, recorded, retained, processed, intercepted, or analyzed by Surveillance Technology acquired by the City or operated at the direction of the City. (G) "Surveillance Technology" means electronic surveillance device, hardware, or software that is capable of collecting, capturing, recording, retaining, processing, intercepting, analyzing, monitoring, or sharing audio, visual, digital, location, thermal, biometric, or similar information specifically associated with, or capable of being associated with, any Identifiable Individual or group; or any system, device, or vehicle that is equipped with an electronic surveillance device, hardware, or software. (1) "Surveillance Technology" includes : (a) Biometric Surveillance Technology, including facial, voice, iris, and gait- recognition software and databases; (b) Gunshot detection and location hardware and services; (c) X-ray vans; (d) Video and audio monitoring and/or recording technology, such as surveillance cameras and wearable body cameras; (e) Surveillance enabled or capable lightbulbs or light fixtures; (f) Tools, including software and hardware, used to gain unauthorized access to a computer, computer service, or computer network; (g) Social media monitoring software; (h) Through-the-wall radar or similar imaging technology; (i) Software designed to integrate or analyze data from Surveillance Technology, including surveillance target tracking and predictive policing software. (2) For the purposes of this Chapter, "Surveillance Technology" does not include the following devices or hardware, unless they have been equipped with, or are modified to become or include, a Surveillance Technology as defined above: (a) Routine office hardware, such as televisions, computers, and printers, that are in widespread public use and will not be used for any surveillance or surveillance-related functions; (b) Parking Ticket Devices ("PTDs") and related databases;  (c) Manually-operated, non-wearable, handheld digital cameras, audio recorders, and video recorders that are not designed to be used surreptitiously and whose functionality is used for manually capturing and manually downloading video and/or audio recordings; (d) Surveillance devices that cannot record or transmit audio or video or be remotely accessed, such as image stabilizing binoculars or night vision goggles; (e) City databases that do not and will not contain any Surveillance Data or other information collected, captured, recorded, retained, processed, intercepted, or analyzed by Surveillance Technology; (f) Manually-operated technological devices that are used primarily for internal City communications and are not designed to surreptitiously collect Surveillance Data, such as radios and email systems; (g) Parking access and revenue control systems, including proximity card readers and transponder readers at City-owned or controlled parking garages; and (h) Electronic card readers and key fobs used by City employees and other authorized persons for access to City-owned or controlled buildings and property. (H) "Surveillance Technology Impact Report" means a written report submitted by the City Departments with a request for approval of acquisition or use of Surveillance Technology, and which includes, at a minimum, the requirements set forth in Section 325-4 (I) "Surveillance Use Policy" means a policy for the City's use of Surveillance Technology, approved by the Corporation Counsel and submitted to and approved by the Common Council. The Surveillance Use Policy shall at a minimum satisfy the requirements set forth in Subsection 325-6(B). (J) "Technology-Specific Surveillance Use Policy" means a policy governing the City's use of a specific Surveillance Technology not already covered under the City's Surveillance Use Policy, approved by the Corporation Counsel and submitted to the Common Council with a Surveillance Technology Impact Report under Section 325-4(A), 325-4(B), or 325- 5 of this Chapter. §325-4 Submission to the Common Council of Surveillance Technology Impact Report and Technology-Specific Surveillance Use Policy. Commissioners, Heads of Departments, Boards, or Commissions must seek approval from the Common Council as set forth in this Section prior to the City seeking funds for, acquiring, using or entering into an agreement to acquire, share or otherwise use, Surveillance Technology as defined in this Chapter. (A) Acquisition of Surveillance Technology by City Departments Other than the Police Department. For any department other than the Police Department, for which approval under Section 325-4 of this Chapter is sought, the Department must submit to the Common Council a Surveillance Technology Impact Report, and, if necessary, a  Technology-Specific Surveillance Use Policy pertaining to the specific Surveillance Technology for which approval is sought and obtain Common Council approval before doing any of the following: (1) Seeking funds for Surveillance Technology, including but not limited to, applying for a grant, or accepting state or federal funds, or in-kind or other donations; (2) Acquiring new Surveillance Technology, including but not limited to procuring that Surveillance Technology without the exchange of monies or other consideration; (3) Using Surveillance Technology for a purpose, in a manner, or in a location not previously approved; or (4) Entering into an agreement with a non-City entity to acquire, share, or otherwise use Surveillance Technology or the Surveillance Data it provides. (B) Acquisition of Surveillance Technology by the Police Department. Other than with respect to Surveillance Technology limited to use in Exigent Circumstances in law enforcement investigations and prosecutions as specifically defined in Section 325-5 of this Chapter, the City Departments t must submit a Surveillance Technology Impact Report, and, if necessary, a Technology-Specific Surveillance Use Policy pertaining to the specific Surveillance Technology for which approval is sought to the Common Council and obtain Common Council approval, before doing any of the following: (1) Seeking funds for Surveillance Technology, including but not limited to, applying for a grant, or accepting state or federal funds, or in-kind or other donations; (2) Acquiring new Surveillance Technology, including but not limited to procuring that technology without the exchange of monies or other consideration; (3) Using Surveillance Technology for a purpose, in a manner, or in a location not previously approved; or (4) Entering into an agreement with a non-City entity to acquire, share, or otherwise use Surveillance Technology. (C) Contents of Surveillance Technology Impact Report. A Surveillance Technology Impact Report submitted pursuant to Subsections (A) or (B) above shall include all of the following: (1) Information describing the Surveillance Technology and how it works; (2) Information on the proposed purpose(s) for the Surveillance Technology; (3) The location(s) it may be deployed and when; (4) The potential impact(s) on privacy in the City; the potential impact on the civil rights and liberties of any individuals, communities or groups, including, but not limited to, communities of color or other marginalized communities in the City, and a description of whether there is a plan to address the impact(s); Examples to assess potential impact include, but are not limited to: Number of false positive results categorized by race, Number of false positive results categorized by gender, Accuracy analyses categorized by race and/or gender;  (5) The fiscal costs for the Surveillance Technology, including initial purchase, personnel and other ongoing costs, and any current or potential sources of funding; and (6) If necessary, a Technology-Specific Surveillance Use Policy. (D) Contents of Technology-Specific Surveillance Use Policy. A Technology Specific Surveillance Use Policy submitted under Subsections (A) or (B) above or Section 325-5 below shall not conflict with any provision of the City's Surveillance Use Policy. To the extent a conflict arises between the provisions of the City's Surveillance Use Policy and a Technology-Specific Surveillance Use Policy, the City's Surveillance Use Policy shall govern. A Technology-Specific Surveillance Use Policy submitted under Subsections (A) or (B) above or Section 325-5 below shall include all of the following: (1) Purpose: The specific purpose(s) for the Surveillance Technology; (2) Authorized Use: The uses that are authorized, the rules and processes required before that use, and the uses that are prohibited; (3) Data Collection: The Surveillance Data that can be collected by the Surveillance Technology; (4) Data Access: The individuals who can access or use the collected Surveillance Data, and the rules and processes required before access or use of the information; (5) Data Protection: The safeguards that protect information from unauthorized access, including, but not limited to, encryption, access-control, and access-oversight mechanisms; (6) Data Retention: The time period, if any, for which information collected by the Surveillance Technology will be routinely retained, the reason that retention period is appropriate to further the purpose(s), the process by which the information is regularly deleted after that period has elapsed, and the conditions that must be met to retain information beyond that period; (7) Public Access: If and how collected Surveillance Data can be accessed by members of the public, including criminal defendants; (8) Third-Party Data-Sharing: If and how other City or non-City entities can access or use the Surveillance Data, including any required justification and legal standard necessary to do so, and any obligation(s) imposed on the recipient of the Surveillance Data; (9) Training: The training, if any, required for any individual authorized to use the Surveillance Technology or to access information collected by the Surveillance Technology, including whether there are training materials; and (10) Oversight: The mechanisms to ensure that the Surveillance Use Policy is followed, including, but not limited to, identifying personnel assigned to ensure compliance with the policy, internal record keeping of the use of the technology or access to information collected by the Surveillance Technology, technical measures to monitor for misuse, any independent person or entity with oversight authority, and the sanctions for violations of the policy.  (E) In approving, and/or disapproving any acquisition of Surveillance Technology, the Common Council shall consider the safeguarding of individuals' right to privacy as well as the investigative and prosecutorial functions of the Police Department and promoting and ensuring the safety and security of the general public. (F) Any Surveillance Technology Impact Report, and, if necessary, Technology-Specific Surveillance Use Policy submitted to the Common Council under Section 375-4(A) or 375-4(B) shall be made publicly available no fewer than seven (7) calendar days prior to the date of the Council meeting where it shall be discussed. §325-5 - Temporary Acquisition and Use of Surveillance Technology in Exigent Circumstances. Notwithstanding the provisions of this Chapter, the Police Department may temporarily acquire or temporarily use Surveillance Technology in Exigent Circumstances for a period not to exceed 90 days without following the provisions of this Chapter before that acquisition or use. However, if the Police Department acquires or uses Surveillance Technology in Exigent Circumstances under this Section, the Police Chief must (1) report that acquisition or use to the Common Council in writing within 90 days following the end of those Exigent Circumstances; (2) submit a Surveillance Technology Impact Report, and, if necessary, a Technology-Specific Surveillance Use Policy to the Common Council regarding that Surveillance Technology within 90 days following the end of those Exigent Circumstances; and (3) include that Surveillance Technology in the Police Department's next Annual Surveillance Report to the Common Council following the end of those Exigent Circumstances. If the Police Chief is unable to meet the 90- day timeline to submit a Surveillance Technology Impact Report, and, if necessary, a Technology-Specific Surveillance Use Policy to the Common Council, the Police Chief may notify the Common Council in writing requesting to extend this period. The Common Council may grant extensions beyond the original 90-day timeline to submit a Surveillance Technology Impact Report, and, if necessary, a Technology-Specific Surveillance Use Policy. Any Surveillance Technology Impact Report, and, if necessary, Technology-Specific Surveillance Use Policy submitted to the Common Council under this Section shall be made publicly available no fewer than seven (7) calendar days prior to the date of the Council meeting where it shall be discussed. §325-6 - Submission to the Common Council of Surveillance Use Policy. (A) The Corporation Counsel shall submit to the Common Council for its review and approval a proposed Surveillance Use Policy applicable to each City department that possesses or uses Surveillance Technology before the effective date of this Chapter or for future use and acquisition of Surveillance Technology, no later than one-hundred eighty (180) days following the effective date of this Chapter, for review and approval by the Common Council. If the Corporation Counsel is unable to meet this 180-day timeline, the Corporation Counsel may notify the Common Council in writing requesting to extend this period. The Common Council may grant an extension to the Corporation Counsel to submit a proposed Surveillance Use Policy. Any Surveillance Use Policy submitted under Section 325-6 shall be made  publicly available no fewer than seven (7) calendar days prior to the date of the Council meeting where it shall be discussed. (B) A Surveillance Use Policy shall at a minimum specify the following: (1) Purpose: The specific purpose(s) for the Surveillance Technology; (2) Authorized Use: The uses that are authorized, the rules and processes required before that use, and the uses that are prohibited; (3) Data Collection: The Surveillance Data that can be collected by the Surveillance Technology; (4) Data Access: The individuals who can access or use the collected Surveillance Data, and the rules and processes required before access or use of the information; (5) Data Protection: The safeguards that protect information from unauthorized access, including, but not limited to, encryption, access-control, and access-oversight mechanisms; (6) Data Retention: The time period, if any, for which information collected by the Surveillance Technology will be routinely retained, the reason that retention period is appropriate to further the purpose(s), the process by which the information is regularly deleted after that period has elapsed, and the conditions that must be met to retain information beyond that period; (7) Public Access: If and how collected Surveillance Data can be accessed by members of the public, including criminal defendants; (8) Third-Party Data-Sharing: If and how other City or non-City entities can access or use the Surveillance Data, including any required justification and legal standard necessary to do so, and any obligation(s) imposed on the recipient of the Surveillance Data; (9) Training: The training, if any, required for any individual authorized to use the Surveillance Technology or to access information collected by the Surveillance Technology, including whether there are training materials; and (10) Oversight: The mechanisms to ensure that the Surveillance Use Policy is followed, including, but not limited to, identifying personnel assigned to ensure compliance with the policy, internal record keeping of the use of the technology or access to information collected by the Surveillance Technology, technical measures to monitor for misuse, any independent person or entity with oversight authority, and the sanctions for violations of the policy. (C) In considering the Surveillance Use Policy, the Common Council shall balance the safeguarding of individuals' right to privacy as well as the investigative and prosecutorial function of the Police Department and promoting and ensuring the safety and security of the general public. §325-7 - Submission to the Common Council of Annual Surveillance Report. (A) Within twelve (12) months of Common Council approval, and annually thereafter on or before March 1, City Departments with use of such technologies must submit an Annual  Surveillance Report pertaining to each approval for the use of Surveillance Technology or Surveillance Data has been obtained under Section 325-4 or Section 325-5 of this Chapter. Any Annual Surveillance Report submitted under this section shall be made publicly available no fewer than seven (7) calendar days prior to the date of the Council meeting where it shall be discussed. (B) The Annual Surveillance Report submitted pursuant to this Section shall include all of the following: (1) A description of how the Surveillance Technology has been used, including whether it captured images, sound, or information regarding members of the public who are not suspected of engaging in unlawful conduct; (2) Whether and how often data acquired through the use of the Surveillance Technology was shared with outside entities, the name of any recipient entity, the type(s) of data disclosed, under what legal standard(s) the information was disclosed, and the justification for the disclosure; (3) A summary of community complaints or concerns about the Surveillance Technology, if any; (4) The results of any non-privileged internal audits, any information about violations of the Surveillance Use Policy, and any actions taken in response; (5) Whether the Surveillance Technology has been effective at achieving its identified purpose; (6) Statistics on public records requests received by the City seeking documents concerning Surveillance Technology approved during the previous year; (7) Total annual costs for the Surveillance Technology, including personnel and other ongoing costs, and what source of funding will fund the technology in the coming year; and (8) Whether the civil rights and liberties of any communities or groups, including communities of color or other marginalized communities in the City are disproportionately impacted by the deployment of the Surveillance Technology. (C) Based upon information provided in the Annual Surveillance Report, the Common Council shall determine whether the benefits to the impacted City department(s) and the community of the Surveillance Technology outweigh the financial and operational costs and whether reasonable safeguards exist to address reasonable concerns regarding privacy, civil liberties, and civil rights impacted by deployment of the Surveillance Technology. (D) If questions arise from the submission of the Annual Surveillance Reports, the Chief City Auditor has the ability to perform risk assessments or audits on each City Department’s use of the surveillance technologies. Results of such risk assessments or audit shall be provide to the Common Council for consideration in a timely manner. (E) If the benefits or reasonably anticipated benefits do not outweigh the financial and/or operational costs or civil liberties or civil rights are not reasonably safeguarded, the Common Council may (1) recommend modifications to the Surveillance Use Policy that are designed to address the Common Council's concerns to the Corporation Counsel for their consideration; and/or (2) request a report back from the City Departments regarding steps taken to address the Common Council's concerns; and/or (3) disapprove further use of the Surveillance Technology. (F) No later than May 31 of each year, the Common Council shall hold a meeting to discuss the City departments' Annual Surveillance Reports, and shall publicly release a report that includes a summary of all requests for approval of Surveillance Technology Impact Reports received by the Common Council during the prior year pursuant to Section 325-4 or Section 325-5 of this Chapter, including whether the Common Council approved, disapproved, or required modifications to the Surveillance Technology Impact Report. §325-8 Exemptions and Exceptions. (A) Exemptions. For the purposes of this Chapter, the following Surveillance Technology is exempt from the requirements of this Chapter: (1) Surveillance Data acquired where the individual knowingly and voluntarily consented to provide the information, such as submitting personal information for the receipt of City services; (2) Surveillance Data acquired where the individual was presented with a clear and conspicuous opportunity to opt out of providing the information; (3) Cameras installed pursuant to state law authorization in or on any vehicle or along a public right-of-way solely to record traffic violations; (4) Cameras installed on City property solely for security purposes, including closed circuit television cameras installed by the City to monitor entryways and outdoor areas of City- owned or controlled buildings and property for the purpose of controlling access, maintaining the safety of City employees and visitors to City buildings, and protecting City property; (5) Security cameras including closed circuit television cameras installed by the City to monitor cashiers' windows and other cash-handling operations and to maintain the safety of City employees and visitors to such areas; (6) Cameras installed solely to protect the physical integrity of City infrastructure; or (7) Technology that monitors only City employees in response to complaints of wrongdoing or in order to prevent waste, fraud, or abuse of City resources. (B) Exceptions. The following situations constitute Surveillance, but are exceptions to the requirements of this Chapter: (1) Surveillance conducted pursuant to a warrant using previously approved Surveillance Technology. Surveillance conducted pursuant to a warrant using previously approved Surveillance Technology is excepted from the requirements of Section325-4(B) and  Section 325-7 where: i) the City is prohibited from publicly releasing information pertaining to the surveillance under federal or state law, or pursuant to a Court Order; or ii) the Police Chief has determined that the release of information pertaining to the surveillance would compromise public safety and security, provided that the information is released in the next Annual Surveillance Report following the Police Chief’s determination that public safety and security concerns pertaining to the release of such information no longer exist. (2) A City department head may, with the approval of the Corporation Counsel, apply a technical patch or upgrade that is necessary to mitigate threats to the City's environment. The department shall not use the new surveillance capabilities of the technology until the requirements of Section 325-4 are met, unless the Corporation Counsel determines that the use is unavoidable; in that case, the Corporation Counsel shall request Common Council approval as soon as possible. The request shall include a report to the Common Council of how the altered surveillance capabilities were used since the time of the upgrade. §325-9 Enforcement (A) Enforcement Officials. This Chapter shall be enforced by the Corporation Counsel or their designee. (B) Violation. Any person injured by a violation of this Chapter may institute proceedings for injunctive relief, declaratory relief, or a court order in a court of competent jurisdiction to enforce the provisions of this Chapter. Any action initiated under this Subsection (B) shall be brought against the City of Albany, but not against City employees. No monetary damages shall be allowed in any legal proceeding for any alleged injuries arising out of any alleged violation(s) of this Chapter. (C) Whistleblower Protections. Subject to the limitations and requirements set forth New York State Law as it may be amended from time to time, any City employee who reports an alleged violation of this Ordinance, shall be afforded protections against retaliation if applicable, as set forth in and subject to the limitations and requirements of New York State Law. (D) Nothing in this Chapter shall be construed to limit or affect any individual's rights under state or federal laws. §325-10 Severability The provisions in this Chapter are severable. If any part or provision of this Chapter, or the application of this Chapter to any person or circumstance, is held invalid by a court of competent jurisdiction, the remainder of this Chapter shall not be affected by such holding and shall continue to have full force and effect. Section 2. Effective Date. This Ordinance shall take effect 90 days after passage. President Pro Tem Kimbrough referred Ordinance 15.81.20 to the Public Safety Committee for further consideration. CONSIDERATION OF RESOLUTIONS Council Member Frederick noticed Resolution 72.81.20R as follows, which was held for further consideration: RESOLUTION NUMBER 72.81.20R RESOLUTION REGARDING THE STATE ENVIRONMENTAL QUALITY REVIEW ACT (SEQRA) REVIEW OF ORDINANCE 9.61.20 WHEREAS, Ordinance 9.61.20 by Council Member Frederick amends the zoning map of the City of Albany, changing various parcels of land in the City of Albany from Mixed-Use Neighborhood Edge (MU-NE) to Mixed-Use Campus/Institutional (MU-CI), and other parcels from Townhome (R-T) to Mixed-Use Campus/Institutional (MU-CI); and WHEREAS, South End Development, LLC (herein referred to as “Developer”) has proposed development of four (4) 6 to 8 story mixed-use modular buildings that will each have solar canopies extending over the entire building footprints. The buildings will be built into the topography of the site. Parking will be provided below-grade underneath the buildings and will be accessed via two access drives on Leonard street and once access drive on Krank Street; and WHEREAS, the zoning map amendment is a Type I action under SEQRA; and WHEREAS, on June 1, 2020, the City of Albany Common Council declared itself as the lead agent for coordinated review and contacted all involved agents of the Common Council designation of lead agent. All involved agents have until July 20, 2020, to notify the Common Council if they consent, or object, and to provide any commentary related to environmental review; and WHEREAS, ….; and NOW, THEREFORE, BE IT RESOLVED,….. President Pro Tem Kimbrough referred Resolution 72.81.20R to the Planning, Economic Development and Land Use Committee for further consideration. President Pro Tem Kimbrough made a motion, which was duly seconded, requesting Majority Consent to add Resolution 73.81.20R to the agenda. There being no discussion, the motion was adopted by voice vote. Council Member Kimbrough noticed Resolution 73.81.20R (MC) as follows, asked passage and a roll call vote thereon: Resolution Number 73.81.20R (MC) RESOLUTION OF THE COMMON COUNCIL AUTHORIZING THE EXECUTION OF AN AMENDED AND RESTATED PAYMENT-IN-LIEU-OF-TAXES (PILOT) AGREEMENT WITH LUMBER STREET APARTMENTS IV HOUSING DEVELOPMENT FUND CORP. AND IDA YARBROUGH PHASE IV LLC, AND RESCINDING RESOLUTION 63.71.20R, WHICH HAD PREVIOUSLY AUTHORIZED ENTRY INTO AN INCORRECT VERSION OF SUCH AGREEMENT  WHEREAS, the Lumber Street Apartments Housing IV Development Fund Corp. (the “HDFC”) is a corporation established pursuant to section 402 of the Not-For-Profit Corporation Law and Article XI of the Private Housing Finance Law (“PHFL”), and is controlled by or under common control with the Albany Housing Authority (the “AHA”); and WHEREAS, the HDFC is organized as a “housing development fund company” as that term is defined in section 572 of the PHFL; and WHEREAS, Ida Yarbrough Phase IV LLC (the “Company”) is a limited liability company controlled by or under common control with the AHA; and WHEREAS, the Company’s and the HDFC’s plan for the use of the property hereinafter consists of the redevelopment of approximately three hundred eighty-four (384) mixed-income affordable residential units, constitutes a “housing project” as that term is defined in Section 572 of the PHFL (the “Project”) and will be located and situated at two scattered sites located (i) at or near 252 North Pearl Street (f/k/a 260-270 North Pearl Street) (“Site 1) and (ii) at or near 41 Jennings Drive (“Site 2”), both in the City and County of Albany, State of New York (the “Property”); and WHEREAS, the HDFC is the sole managing member of the Company and is expected to be the leasehold owner of the Property as nominee of the Company; and WHEREAS, pursuant to Section 577(1) of the PHFL, the local legislative body of a municipality may exempt a project of a housing development fund company from local and municipal taxes, including school taxes, other than assessments for local improvements, to the extent of all or a part of the value of the property included in the completed project for a period of up to thirty (30) years; and WHEREAS, this Council previously authorized entry into the above-described PILOT agreement by Resolution 63.71.20R; however that resolution, and the PILOT into which it authorized the Mayor to enter both contained an error: each stated incorrectly that the Project would entail redevelopment of three hundred sixty-four (364) units, though the correct number of units is three hundred eighty-four (384); NOW, THEREFORE, BE IT RESOLVED, that Resolution 63.71.20R, duly passed with immediate effect by this Council on July 6, 2020, is hereby nullified and the approval granted in it is revoked; and BE IT FURTHER RESOLVED, that the Property and the Project shall be exempt from real property taxes to the extent described in Section 577(1) of the PHFL for a period of thirty (30) years, including city, county, and school taxes, other than assessments for local approvals, and that the Mayor of the City of Albany is hereby authorized and empowered to execute and enter into a PILOT agreement with the Company and the HDFC in a form approved by the Corporation Counsel, reflecting the correct number of units, together with such other and further forms, documents and agreements necessary to amend, renew, supplement, or effectuate the same; and  BE IT FURTHER RESOLVED, that this resolution shall take effect immediately. There being no further discussion, President Ellis called for a roll call vote thereon and the Resolution was ADOPTED: The Resolution passed by the following voice vote of all Council Members present voting in favor thereof: Affirmative – Anane, Balarin, Conti, Doesschate, Fahey, Farrell, Flynn, Frederick, Hoey, Igoe, Johnson, Kimbrough, Love, O’Brien, and Robinson Affirmative 15 Negative 0 Abstain 0 President Pro Tem Kimbrough held the pending Resolution on the agenda for further consideration. COMMON COUNCIL COMMENTS Council Member Doesschate (Ordinance 15.81.19 Council Member Hoey (Zoom Settings) Council Members Farrell (Public Comments) Council Member Balarin (Summer & Towing Company) Council Member Anane (Public Comments) Council Member O’Brien (DGS Response & Public Comments) Council Member Johnson (Public Comments) Council Member Love (Zoom Meeting & Council Member Anane’s Public Comments) Council Member Kimbrough (Public Comments & Dott’s Garage) Council President Ellis (Public Comments) ADJOURNMENT There being no further business, President Pro Tem Kimbrough made a motion to adjourn, which was duly seconded and adopted by unanimous voice vote. President Ellis declared the meeting adjourned at approximately 8:08pm. MICHELE ANDRE Senior Legislative Aide to the Council