Creation of a centralized mobile application for accessing city services

Summary#

Introduction 0838-2026, sponsored by Council Member Justin E. Sanchez, would amend the New York City Administrative Code. It would require the Department of Information Technology and Telecommunications (DoITT) to create a centralized mobile app for city services; its stated aim is to let the public access services from different agencies through one app. The bill was introduced and referred to a committee on April 16, 2026, and is not law.

  • DoITT, working with the chief privacy officer and other city agencies, would have to provide app access to all city services except services that cannot be accessed using mobile technology.
  • Where relevant, the app would have to let users schedule appointments, get reminders, and send and receive messages with the agency providing the service.
  • DoITT would have to adopt an accessibility protocol. The app would have to encrypt data exchanges with city web servers, except where another method provides at least equivalent confidentiality, data integrity, and authentication.
  • Custom software and web development created for the app would have to be open source and publicly accessible, except as department rules provide.
  • The app could not be the only way to access city services. Vendors could use or access identifying information only as needed for their service; users could request review and deletion of app information within 10 days, subject to an exception for information the agency would ordinarily retain through another access method. The app could not collect biometric identifier information.
  • The law would take effect 180 days after it becomes law.

What it means for you#

  • Residents: You could use the app to access city services, including appointment and messaging features where relevant. You would still be able to use other ways to access those services.
  • Residents using the app: You could ask to review or delete information collected or stored by the app. The 10-day deadline applies to information the agency would not ordinarily retain when providing the service another way.
  • City agencies and DoITT: Agencies would have to work with DoITT to provide app access to their services. DoITT would have to create and maintain the app and adopt an accessibility protocol.
  • Vendors: If used to create, maintain, or operate the app, a vendor could not use or access identifying information beyond what is needed for its service.

Money#

No cost information is in the available material.

  • The bill would require DoITT to create and maintain the app and take on related accessibility, privacy, and security work, but gives no staffing or cost estimate.
  • It sets no fee, fine, or appropriation.

What is unclear#

  • The bill does not give a timeline for creating the app or say how users would request review or deletion of information.
  • It does not specify how the city would decide whether a service cannot be accessed through mobile technology.
  • The open-source requirement allows exceptions through department rules, but the bill does not state what those exceptions could be.
  • The bill refers to definitions of identifying information and biometric identifier information in other code sections. Those sections and the current Administrative Code were not supplied, so their definitions and how much of the proposal would change current law could not be verified.
  • The text does not set out how agencies would handle app messages or how the accessibility protocol would be developed.

Case for#

  • The Council’s summary describes the app as a single way for the public to access services provided by different city agencies. A centralized app could make those services easier to find.
  • The bill includes appointment, reminder, and messaging features where relevant, which could make some service interactions easier to manage.
  • The bill requires an accessibility protocol, limits vendors’ access to identifying information, and bars biometric data collection through the app.
  • Keeping other access methods available would mean residents would not have to use the app to reach city services.

Case against#

  • The bill would cover all city services unless their nature makes mobile access impossible, but it does not explain how that exception would be decided.
  • A possible trade-off is that a centralized app could bring more service interactions into one system, while the bill leaves key details—such as how deletion requests work and how messages are handled—to later decisions.
  • The open-source rule has an exception for department rules, and the bill does not set limits on that exception.
  • The proposal requires app development and ongoing work but provides no cost estimate.