<?xml version='1.0' encoding='utf-8'?>
<baltimore-city-law heading="Subtitle 02 – Dockless Vehicles">
  <container prefix="Chapter" num="01" heading="General Provisions">
    <section prefix="Regulation" num=".01" heading="Scope.">
      <text>&lt;cite data-path="14.02.01"&gt;This chapter&lt;/cite&gt; establishes rules and regulations for the operation of dockless vehicles in Baltimore City.</text>
    </section>
    <section prefix="Regulation" num=".02" heading="Definitions.">
      <para num="A.">In &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;, the following terms have the meanings indicated.</para>
      <para num="B.">Terms Defined.<para num="(1)">Adaptive Dockless Vehicle.<para num="(a)">“Adaptive dockless vehicle” means a dockless vehicle that is accessible to people with a physical disability.</para>
          <para num="(b)">“Adaptive dockless vehicle” includes a motorized or non-motorized:<para num="(a)">Recumbent bicycle;</para>
            <para num="(b)">Tricycle; and</para>
            <para num="(c)">Hand cycle.</para>
          </para>
        </para>
        <para num="(2)">Alternative Deployment Location.<para num="(a)">“Alternative deployment location” means an area other than a public street.</para>
          <para num="(b)">“Alternative deployment location” includes:<para num="(i)">A park;</para>
            <para num="(ii)">A plaza;</para>
            <para num="(iii)">A parking lot;</para>
            <para num="(iv)">Private property; or</para>
            <para num="(v)">A transit station.</para>
          </para>
        </para>
        <para num="(3)">Applicant.<para num="(a)">“Applicant” means a person applying for an initial dockless vehicle permit.</para>
          <para num="(b)">“Applicant” does not include a permit holder applying for the renewal of a dockless vehicle permit.</para>
        </para>
        <para num="(4)">“Application Programming Interface endpoint (API)” means a protocol that enables a software application to:<para num="(a)">Communicate with another platform; or</para>
          <para num="(b)">Exchange data.</para>
        </para>
        <para num="(5)">“Beta endpoint” means an API endpoint that has been officially released in a testing mode by its regulatory authority but not formally adopted.</para>
        <para num="(6)">“Block face” means one side of a street between the intersection of two other streets, excluding an alleyway.</para>
        <para num="(7)">“Community event” means an event held by:<para num="(a)">A community organization as recognized by the City’s Online Community Association Directory; or</para>
          <para num="(b)">Another organization as deemed appropriate by the Director.</para>
        </para>
        <para num="(8)">“Compliance score” means a calculation of a permit holder’s compliance with the provisions of &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;.</para>
        <para num="(9)">“CPSC” means the U.S. Consumer Product Safety Commission.</para>
        <para num="(10)">“Department” means the Baltimore City Department of Transportation.</para>
        <para num="(11)">“Deployment” means the location where a dockless vehicle is placed by a permit holder when it is made available for rent.</para>
        <para num="(12)">“Deployment district” means a geographic area designated in the Department’s MDS Policy API for tracking the distribution of dockless vehicles.</para>
        <para num="(13)">“Director” means the Director of the Department of Transportation.</para>
        <para num="(14)">“Dockless corral” means a geographic location designated by the Department where a dockless vehicle may be parked.</para>
        <para num="(15)">“Dockless vehicle” has the meaning stated in &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-1|(b)"&gt;City Code Article 31, § 38-1(b)&lt;/cite&gt;.</para>
        <para num="(16)">“E-bike” has the meaning stated in &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-1|(d)"&gt;City Code Article 31, § 38-1(d)&lt;/cite&gt;.</para>
        <para num="(17)">"E-scooter" has the meaning stated in &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-1|(e)"&gt;City Code Article 31, § 38-1(e)&lt;/cite&gt;.</para>
        <para num="(18)">“Equitable access” means a process of making dockless vehicles available to the public by removing barriers to use including:<para num="(a)">Geography;</para>
          <para num="(b)">Income;</para>
          <para num="(c)">Banking status; or</para>
          <para num="(d)">Inclusion in a federally protected class.</para>
        </para>
        <para num="(19)">“Equity zone” means a geographic location where a dockless vehicle is deployed for equitable access as designated in the official document provided by the Department to a permit holder.</para>
        <para num="(20)">“Fleet” means the total number of dockless vehicles operated by a permit holder in Baltimore City, regardless of whether they are available for rent.</para>
        <para num="(21)">“Genetic information” means genetic markers related to a person’s medical history, including the manifestation of a:<para num="(a)">Disease; or</para>
          <para num="(b)">Disorder.</para>
        </para>
        <para num="(22)">“Geo-fencing” means a location-based service that uses GPS or cellular data to identify when a mobile device or dockless vehicle enters or exits a virtual geographic boundary.</para>
        <para num="(23)">“GitHub” means a code hosting platform.</para>
        <para num="(24)">“Low-income population” means a person whose family income is at or below 150 percent of the poverty line</para>
        <para num="(25)">“MDS” means Mobility Data Specification.</para>
        <para num="(26)">“MDS Policy API” means the Open Mobility Foundation standards and code available on GitHub for secure mobility data exchange.</para>
        <para num="(27)">“New permit holder” means a provider of dockless vehicles who has:<para num="(a)">Not previously been issued a permit to operate on a public street by the Department; or</para>
          <para num="(b)">Not held a permit in the previous year.</para>
        </para>
        <para num="(28)">Non-deployment Request.<para num="(a)">“Non-deployment request” means a request from a member of the public to prevent the deployment of a dockless vehicle in front of their property.</para>
          <para num="(b)">“Non-deployment request” includes a vehicle deployed by a dockless vehicle permit holder.</para>
          <para num="(c)">“Non-deployment request” does not include a vehicle parked by a user.</para>
        </para>
        <para num="(29)">“OMF” means Open Mobility Foundation.</para>
        <para num="(30)">“Overconcentration” means the deployment of more than 25 percent of a permit holder’s fleet in a single deployment district.</para>
        <para num="(31)">“Payment Card Industry Data Security Standards” means the set of guidelines designed to ensure companies that process credit card information maintain a secure environment.</para>
        <para num="(32)">“Parking corral” means an area designated by the Department where a dockless vehicle may be parked.</para>
        <para num="(33)">“Permit” means a dockless vehicle permit as provided in &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-8"&gt;City Code Article 31, § 38-8&lt;/cite&gt;.</para>
        <para num="(34)">“Permit agreement” means a document that is entered into between the City and a permit holder that:<para num="(a)">Stipulates required insurance coverage for a permit holder to operate in Baltimore City;</para>
          <para num="(b)">Stipulates that the permit holder is obligated to adhere to applicable laws and regulations to operate in Baltimore City; and</para>
          <para num="(c)">Outlines procedures for the cessation of operations prior to the end of a permit.</para>
        </para>
        <para num="(35)">“Permit holder” means a provider of dockless vehicles who has been issued a permit by the Department to operate on a public street.</para>
        <para num="(36)">“Permit year” means the period from July 1 to June 30 annually.</para>
        <para num="(37)">“Person” has the meaning stated in &lt;cite data-doc="Md. Code" data-path="ggp|1-107"&gt;General Provisions Article § 1-107, &lt;/cite&gt;City Code.</para>
        <para num="(38)">“Referral agency” means a government assistance program that provides services to individuals who qualify as low-income.</para>
        <para num="(39)">&lt;em&gt;“&lt;/em&gt;Remote shut down notice” means a written communication from the Department sent via e-mail to a permit holder instructing the permit holder to shut down the entirety or a portion of their fleet in Baltimore City.</para>
        <para num="(40)">Seizure.<para num="(a)">“Seizure” means the act of removing a dockless vehicle in violation of &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt; from:<para num="(i)">City property; or</para>
            <para num="(ii)">An area inaccessible to a permit holder.</para>
          </para>
          <para num="(b)">“Seizure” includes the act of:<para num="(i)">Towing;</para>
            <para num="(ii)">Impoundment; and</para>
            <para num="(iii)">Retrieval from a body of water.</para>
          </para>
        </para>
        <para num="(41)">“Speed governor” means a device that ensures the motor of a dockless vehicle is incapable of traveling at a speed in excess of a mandated speed limit on level ground.</para>
        <para num="(42)">“Street” has the meaning stated in &lt;cite data-doc="Md. Code" data-path="ggp|1-109"&gt;General Provisions Article § 1-109, &lt;/cite&gt;City Code.</para>
        <para num="(43)">“Third-party” means a person that is not the permit holder that may access data related to the operation of dockless vehicles.</para>
        <para num="(44)">“Third-party aggregator” means an organization that processes data from one or more sources for use by the City.</para>
        <para num="(45)">“Towing Division” means the Baltimore City Department of Transportation’s Towing Division.</para>
        <para num="(46)">“Tree pit” means an area of the street where a tree is planted.</para>
        <para num="(47)">“Underserved population” means a group of people that:<para num="(a)">Has limited or no access to resources; or</para>
          <para num="(b)">Is otherwise disenfranchised.</para>
        </para>
        <para num="(48)">“Vehicle model” means a vehicle of the certain type, but with different features or appearance.</para>
        <para num="(49)">“Vehicle type” means a vehicle that meets specifications in the City’s vehicle code for that vehicle.</para>
        <para num="(50)">“Web Content Accessibility Guidelines (WCAG)” means guidelines published by the World Wide Web Consortium's Web Accessibility Initiative to make web content accessible.</para>
      </para>
    </section>
    <section prefix="Regulation" num=".03" heading="Permits - Applications.">
      <para num="A.">An applicant shall submit an application for a dockless vehicle permit in accordance with the information published on the Department’s website regarding submission processes.</para>
      <para num="B.">At the time of submission, an applicant shall ensure their application contains:<para num="(1)">An operations plan that includes:<para num="(a)">Hours and days of operation, including relevant limitations;</para>
          <para num="(b)">Procedures for responding to extreme weather events;</para>
          <para num="(c)">Procedures for responding to special events;</para>
          <para num="(d)">Procedures for responding to complaints;</para>
          <para num="(e)">Procedures for ensuring availability of dockless vehicles in each deployment district; and</para>
          <para num="(f)">Procedures and avoiding overconcentration of the applicant’s fleet in a single deployment district; and</para>
        </para>
        <para num="(2)">A maintenance plan that includes:<para num="(a)">Procedures for ensuring that the applicant’s fleet is:<para num="(i)">Safe for public use; and</para>
            <para num="(ii)">Well-maintained;</para>
          </para>
          <para num="(b)">A schedule for inspection of the applicant’s fleet;</para>
          <para num="(c)">A description of the training method used for the applicant’s mechanics;</para>
          <para num="(d)">A description of the life expectancy for each component of a dockless vehicle; and</para>
          <para num="(e)">A method of long-term monitoring to ensure the condition of vehicles in the applicant’s fleet.</para>
        </para>
      </para>
      <para num="C.">An applicant shall notify the Department of a change to the noted requirements in &lt;cite data-path="14.02.01.03|B."&gt;§B of this regulation&lt;/cite&gt;.</para>
    </section>
    <section prefix="Regulation" num=".04" heading="Permits - Fees.">
      <para num="A.">A permit holder shall remit a fee for the issuance of a revocable dockless vehicle permit within 30 days of being awarded the permit.</para>
      <para num="B.">The Board of Estimates shall:<para num="(1)">Approve the cost of the fee, which will include the cost of:<para num="(a)">Issuing the permit;</para>
          <para num="(b)">Program administration;</para>
          <para num="(c)">Associated infrastructure;</para>
          <para num="(d)">Education;</para>
          <para num="(e)">Enforcement; and</para>
          <para num="(f)">Program evaluation; and</para>
        </para>
        <para num="(2)">Disclose the cost of the fee to a permit applicant before the application deadline.</para>
      </para>
      <para num="C.">If a permit holder’s permit is revoked, the Department may not refund a permitting fee paid by the permit holder for the current permit cycle.</para>
    </section>
    <section prefix="Regulation" num=".05" heading="Permits - Issuance.">
      <para num="A.">The Department may issue up to three dockless vehicle permits annually through:<para num="(1)">A renewal of an existing permit; or</para>
        <para num="(2)">A competitive application process.</para>
      </para>
      <para num="B.">Except as provided in &lt;cite data-path="14.02.01.05|C."&gt;§C of this regulation&lt;/cite&gt;, a permit holder shall maintain a daily fleet of two or more vehicle types.</para>
      <para num="C.">If a permit holder administers an adaptive vehicle program, the permit holder may maintain a fleet of a single vehicle type.</para>
      <para num="D.">If a permit holder fails to meet one or more of the standards in &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;, the Department shall:<para num="(1)">Review the performance of the permit holder under the permit issued; and</para>
        <para num="(2)">Assess the violation for a citation in accordance with &lt;cite data-path="14.02.01.26"&gt;regulation .26 of this chapter&lt;/cite&gt;.</para>
      </para>
    </section>
    <section prefix="Regulation" num=".06" heading="Permits - Renewal.">
      <para num="A.">Eligibility Requirements.
A permit holder shall be eligible to renew a permit if the permit holder:<para num="(1)">Has not had a violation in the permit year prior; and</para>
        <para num="(2)">Is in good standing to conduct business in the State of Maryland.</para>
      </para>
      <para num="B.">Renewal Process.
A permit holder may renew a permit by:<para num="(1)">Signing a renewal agreement that includes current rules and regulations; and</para>
        <para num="(2)">Remitting an annual fee in accordance with &lt;cite data-path="14.02.01.04"&gt;regulation .04 of this chapter&lt;/cite&gt;.</para>
      </para>
      <para num="C.">The Department may renew a permit if a permit holder meets the eligibility requirements in &lt;cite data-path="14.02.01.06|A."&gt;§A of this regulation&lt;/cite&gt;.</para>
    </section>
    <section prefix="Regulation" num=".07" heading="Permits - Revocation.">
      <para num="A.">The Department may revoke a permit in accordance with &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-13"&gt;City Code Article 31, § 38-13&lt;/cite&gt;.</para>
      <para num="B.">Revocation Hearing Procedures.<para num="(1)">A permit holder may request a hearing to determine whether sufficient facts exist to revoke a permit.</para>
        <para num="(2)">The Department shall:<para num="(a)">Designate a time and place for a revocation hearing;</para>
          <para num="(b)">Provide the permit holder with notice of the hearing at least ten business days before the scheduled date; and</para>
          <para num="(c)">Provide an opportunity for the permit holder to be heard at the hearing.</para>
        </para>
        <para num="(3)">A permit holder may:<para num="(a)">Waive the right to an in-person hearing for the revocation of a permit; and</para>
          <para num="(b)">Submit a written opposition to the revocation before the scheduled hearing date in accordance with &lt;cite data-path="14.02.01.07|B.|(4)"&gt;§B(4) of this regulation&lt;/cite&gt;.</para>
        </para>
        <para num="(4)">A permit holder shall submit written opposition to:</para>
        <para num="(5)">Following the hearing or the review of a written opposition, the Department shall record its findings of fact in writing.</para>
        <para num="(6)">The Director may revoke a permit if:<para num="(a)">The Department finds that sufficient grounds exist to revoke a permit; and</para>
          <para num="(b)">The Department provides at least five days’ written notice to the permit holder in advance of the revocation.</para>
        </para>
      </para>
      <para num="C.">A permit holder may appeal the revocation of a dockless vehicle permit to the Director.</para>
    </section>
    <section prefix="Regulation" num=".08" heading="Deployment.">
      <para num="A.">In General.<para num="(1)">A permit holder shall ensure that a dockless vehicle is deployed in compliance with City Code Article 31, § 38-19, Unlawful Parking.</para>
        <para num="(2)">A permit holder shall provide an account for its mobile application to the Department so that Department employees can access a dockless vehicle for free for the purposes of:<para num="(a)">Education;</para>
          <para num="(b)">A routine vehicle inspection; or</para>
          <para num="(c)">Vehicle repositioning.</para>
        </para>
        <para num="(3)">A permit holder shall apply speed geo-fencing to a dockless vehicle by using a speed governor to establish a City-wide speed limit of 15 mph except for:<para num="(a)">In a reduced speed zone as defined in the Department’s MDS Policy API where speeds are limited to eight mph; and</para>
          <para num="(b)">In a no ride zone as defined in the Department’s MDS Policy API where a dockless vehicle is limited to a speed of no more than three mph.</para>
        </para>
      </para>
      <para num="B.">Deployment District Requirements.<para num="(1)">On each day of service, a permit holder shall deploy to each deployment district:<para num="(a)">A minimum of 5 percent of their fleet; and</para>
          <para num="(b)">A maximum of 25 percent of their fleet.</para>
        </para>
        <para num="(2)">Compliance.
The Department shall:<para num="(a)">Evaluate daily compliance with the requirements in &lt;cite data-path="14.02.01.08|B.|(1)"&gt;§B(1) of this regulation&lt;/cite&gt; based on at least one hour of compliance between 5:00 a.m. and 9:0 a.m.; and</para>
          <para num="(b)">Notify a permit holder in violation of the requirements in &lt;cite data-path="14.02.01.08|B.|(1)"&gt;§B(1) of this regulation&lt;/cite&gt; via a compliance score notification.</para>
        </para>
        <para num="(3)">A permit holder shall redistribute their fleet within three hours of receipt of a compliance score notification from the Department.</para>
      </para>
      <para num="C.">Equitable Deployment Requirements.<para num="(1)">A permit holder shall deploy a minimum of three dockless vehicles per day to each equity zone.</para>
        <para num="(2)">Compliance.
The Department shall:<para num="(a)">Evaluate daily compliance based on at least one hour of compliance between 5:00 a.m. and 9:00 a.m; and</para>
          <para num="(b)">Notify a permit holder of in violation of &lt;cite data-path="14.02.01.08|C.|(1)"&gt;§C(1)&lt;/cite&gt;&lt;cite data-path="14.02.01.08|C.|(2)"&gt;-(2)&lt;/cite&gt; of &lt;cite data-path="14.02.01.08"&gt;this regulation&lt;/cite&gt; via a compliance score notification.</para>
        </para>
      </para>
      <para num="D.">Prohibitions.<para num="(1)">A permit holder may not deploy a dockless vehicle:<para num="(a)">Outside of a parking corral on a block face that contains an official parking corral designated by the Department, except as provided in &lt;cite data-path="14.02.01.08|D.|(2)"&gt;§D(2) of this regulation&lt;/cite&gt;;</para>
          <para num="(b)">In a quantity greater than ten per block face, except as allowed by the Department to accommodate a special event;</para>
          <para num="(c)">On a block face which contains the front entrance to a K-8 school;</para>
          <para num="(d)">In a tree pit or otherwise landscaped area;</para>
          <para num="(e)">In front of a property with an approved non-deployment request in accordance with &lt;cite data-path="14.02.01.08|E."&gt;§E of this regulation&lt;/cite&gt;; or</para>
          <para num="(f)">In a location the Department has notified the permit holder that they may not deploy to, beginning 48 hours after the notification.</para>
        </para>
        <para num="(2)">If a parking corral is full, a permit holder may deploy a dockless vehicle on a block face outside of the parking corral.</para>
        <para num="(3)">Unless a permit holder receives approval from the Department, a permit holder may not designate a public street in Baltimore City as a:<para num="(a)">No parking zone;</para>
          <para num="(b)">Reduced speed zone; or</para>
          <para num="(c)">No ride zone.</para>
        </para>
      </para>
      <para num="E.">Non-Deployment Requests.<para num="(1)">A property owner or manager may submit a non-deployment request in writing to the Department for an area adjacent to their property.</para>
        <para num="(2)">The Department shall notify a permit holder:<para num="(a)">Of an approved non-deployment request; and</para>
          <para num="(b)">That an approved non-deployment request will begin 48-hours after notification.</para>
        </para>
      </para>
      <para num="F.">Severe Weather and Emergencies.<para num="(1)">If 24-hour advanced notice is provided, the Department may:<para num="(a)">Suspend the requirements of &lt;cite data-path="14.02.01.08"&gt;this regulation&lt;/cite&gt;; or</para>
          <para num="(b)">Require the removal of:<para num="(i)">An entire fleet; or</para>
            <para num="(ii)">A portion of a fleet in a defined geographic location.</para>
          </para>
        </para>
        <para num="(2)">The Department may require a permit holder to remove a dockless vehicle from:<para num="(a)">An evacuation route prior to an emergency snow event; and</para>
          <para num="(b)">A low-lying area prior to an emergency flooding event.</para>
        </para>
      </para>
      <para num="G.">Special Events.
The Department may suspend the requirements of &lt;cite data-path="14.02.01.08"&gt;this regulation&lt;/cite&gt; during a special event.</para>
      <para num="H.">Temporary Exemptions from Deployment Regulations.<para num="(1)">A permit holder may apply for a temporary exemption from the deployment requirements in &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;.</para>
        <para num="(2)">A permit holder shall include a plan for communicating operational changes to affected users and the public within the application for temporary exemption.</para>
        <para num="(3)">The Department shall review applications for temporary exemption:<para num="(a)">Within 24 hours for an application based on an immediate safety concern; and</para>
          <para num="(b)">Within five business days for other exemption requests.</para>
        </para>
      </para>
      <para num="I.">Alternative Deployment Locations.<para num="(1)">A permit holder shall obtain permission to deploy a dockless vehicle to an alternative deployment location from:<para num="(a)">The Department;</para>
          <para num="(b)">A private property owner; or</para>
          <para num="(c)">Another City agency.</para>
        </para>
        <para num="(2)">A permit holder shall communicate the permission to deploy a dockless vehicle in an alternative deployment location via:<para num="(a)">Signage approved by the entity granting permission; or</para>
          <para num="(b)">A mobile or web application.</para>
        </para>
      </para>
    </section>
    <section prefix="Regulation" num=".09" heading="Equitable Dockless Vehicle Access.">
      <para num="A.">Cash Payment Plans.<para num="(1)">A permit holder shall:<para num="(a)">Provide the option to rent a dockless vehicle using a cash payment;</para>
          <para num="(b)">Offer at least one cash payment location in each deployment district;</para>
          <para num="(c)">Identify the following on its website and mobile application:<para num="(i)">The process for making a cash payment; and</para>
            <para num="(ii)">The locations where a cash payment option is available;</para>
          </para>
          <para num="(d)">Provide an instruction document to the Department that summarizes the process to sign up for a cash-payment plan; and</para>
          <para num="(e)">Inform a user of the availability of cash payment option:<para num="(i)">During initial sign-up; and</para>
            <para num="(ii)">Via email at least twice annually.</para>
          </para>
        </para>
        <para num="(2)">The Department shall post the instruction document provided for in &lt;cite data-path="14.02.01.09|A.|(1)|(d)"&gt;§A(1)(d) of this regulation&lt;/cite&gt; to the Department website.</para>
      </para>
      <para num="B.">Non-Smartphone Plans.<para num="(1)">A permit holder shall:<para num="(a)">Offer the option to rent a dockless vehicle without the use of a smartphone;</para>
          <para num="(b)">Identify the process to rent a dockless vehicle without using a smartphone on its website and mobile application;</para>
          <para num="(c)">Provide an instruction document to the Department that summarizes the process to sign up for a cash-payment plan; and</para>
          <para num="(d)">Inform a user of the availability of cash payment option:<para num="(i)">During initial sign-up; and</para>
            <para num="(ii)">Via email at least twice annually.</para>
          </para>
        </para>
        <para num="(2)">The Department shall post the instruction document provided for in &lt;cite data-path="14.02.01.09|B.|(1)|(c)"&gt;§B(1)(c) of this regulation&lt;/cite&gt; to the Department website.</para>
      </para>
      <para num="C.">Low-Income Plans.<para num="(1)">A permit holder shall offer a low-income plan to users with an income level at or below 200 percent of the federal poverty guideline.</para>
        <para num="(2)">A permit holder shall approve a low-income user by obtaining:<para num="(a)">Preapproval from a referral agency; or</para>
          <para num="(b)">Proof of assistance, including:<para num="(i)">Local assistance;</para>
            <para num="(ii)">State assistance; or</para>
            <para num="(iii)">Federal assistance.</para>
          </para>
        </para>
        <para num="(3)">A permit holder shall ensure a low-income plan:<para num="(a)">Waives an unlock fee for at least four rides per day; and</para>
          <para num="(b)">Offers a minimum 80 percent discount on rental fees for at least four rides per day.</para>
        </para>
        <para num="(4)">A permit holder shall:<para num="(a)">Describe the process to sign up for a low-income plan on the dockless vehicle:<para num="(i)">Website; and</para>
            <para num="(ii)">Mobile application;</para>
          </para>
          <para num="(b)">Notify the Department of a change to verification methods for low-income customer plans;</para>
          <para num="(c)">Provide an instruction document to the Department that summarizes the process to sign up for a low-income plan;</para>
          <para num="(d)">Inform a user of the availability of cash payment option:<para num="(i)">During initial sign-up; and</para>
            <para num="(ii)">Via email at least twice annually.</para>
          </para>
        </para>
        <para num="(5)">The Department shall post the instruction document provided for in &lt;cite data-path="14.02.01.09|C.|(4)|(c)"&gt;§C(4)(c) of this regulation&lt;/cite&gt; to the Department website.</para>
      </para>
      <para num="D.">Customer Service Phone Lines.<para num="(1)">A permit holder shall maintain a live, multilingual 24-hour customer service phone line.</para>
        <para num="(2)">If a caller is required to leave a voicemail when calling the customer service phone line, a permit holder shall respond with a call back within two hours.</para>
        <para num="(3)">A permit holder shall provide a translation or call back within four hours when a message is left by a customer in:<para num="(a)">Spanish;</para>
          <para num="(b)">French;</para>
          <para num="(c)">Mandarin Chinese; or</para>
          <para num="(d)">Korean.</para>
        </para>
      </para>
      <para num="E.">Web Accessibility.
Within 120 days of receiving a permit, a permit holder shall ensure that its software application used for vehicle rental and website are accessible to visually impaired individuals consistent with the latest WCAG standards.</para>
    </section>
    <section prefix="Regulation" num=".10" heading="Compliance.">
      <para num="A.">Compliance Scores – Calculation and Reporting.
The Department shall:<para num="(1)">Calculate a compliance score to determine compliance for:<para num="(a)">Equitable distribution of a dockless vehicle fleet; and</para>
          <para num="(b)">Parking of a dockless vehicle fleet; and</para>
        </para>
        <para num="(2)">Report compliance scores to a permit holder twice per calendar month.</para>
      </para>
      <para num="B.">Compliance Requirements – Distribution.<para num="(1)">To remain compliant with the distribution requirements of &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;, a permit holder shall ensure a minimum compliance score of 85 percent for each reporting period in:<para num="(a)">A deployment district; and</para>
          <para num="(b)">An equity zone.</para>
        </para>
      </para>
      <para num="C.">Compliance Requirements – Fleet Parking.
To remain compliant with fleet parking requirements, a permit holder shall ensure:<para num="(1)">No more than 5 percent of a dockless vehicle fleet remains parked for longer than 5 days for the period from April 1 through November 30; and</para>
        <para num="(2)">No more than 10 percent of a dockless vehicle fleet remains parked for longer than 5 days for the period from December 1 through March 31.</para>
      </para>
      <para num="D.">Eligibility for Fleet Cap Increase.
To be eligible for a fleet cap increase, a permit holder shall score a minimum of 90 percent compliance for each reporting period in<para num="(1)">A deployment district; and</para>
        <para num="(2)">An equity zone.</para>
      </para>
      <para num="E.">Winter Weather Compliance Exemptions.
On days for which the Baltimore City Public School System implements a modified schedule due to inclement weather, the Department shall grant compliance exemptions for violations of:<para num="(1)">Distribution;</para>
        <para num="(2)">Equity; and</para>
        <para num="(3)">Five-day parking.</para>
      </para>
      <para num="F.">Remote Shut Down Notice Exemptions.
When the Department has issued a remote shutdown notice to a permit holder, the Department shall grant compliance exemptions for violations of:<para num="(1)">Distribution;</para>
        <para num="(2)">Equity; and</para>
        <para num="(3)">Five-day parking.</para>
      </para>
    </section>
    <section prefix="Regulation" num=".11" heading="Vehicle Standards.">
      <para num="A.">Vehicle Approval.<para num="(1)">A permit holder shall ensure a dockless vehicle model intended for deployment on a public street has been approved by the Director prior to its deployment on the public street.</para>
        <para num="(2)">To deploy a new vehicle model or vehicle type, a permit holder shall submit the following to the Department at least two weeks prior to intended deployment:<para num="(a)">Vehicle specifications;</para>
          <para num="(b)">A safety certificate;</para>
          <para num="(c)">A deployment plan;</para>
          <para num="(d)">A change to an operations plan, if any; and</para>
          <para num="(e)">A change to a maintenance plan, if any.</para>
        </para>
        <para num="(3)">A permit holder may not deploy a new vehicle model or type until receiving written approval from the Department.</para>
      </para>
      <para num="B.">Required Features – In General.
A permit holder shall ensure a dockless vehicle deployed on a public street:<para num="(1)">Weighs no more than 100 pounds;</para>
        <para num="(2)">Is equipped with an operational structural feature that allows the vehicle to be stably parked upright without needing to lean on another object;</para>
        <para num="(3)">Is equipped with built-in front and back lights that:<para num="(a)">Illuminate while the dockless vehicle is in use; and</para>
          <para num="(b)">Are visible from a distance of at least 500 feet under normal atmospheric conditions at night;</para>
        </para>
        <para num="(4)">Is equipped with a bell or noise emitting device;</para>
        <para num="(5)">Has tires with a diameter of at least nine inches;</para>
        <para num="(6)">Has tactile identification which:<para num="(a)">Meets State requirements; and</para>
          <para num="(b)">Is located on the stem near the handlebars if handlebars are present; and</para>
        </para>
        <para num="(7)">Has legible decals listing:<para num="(a)">The name of the permit holder displayed in a minimum of 16-point font;</para>
          <para num="(b)">The following contact information for a permit holder displayed in a minimum of 16-point font:<para num="(i)">A toll-free telephone number;</para>
            <para num="(ii)">An e-mail address; and</para>
            <para num="(iii)">A website address; and</para>
          </para>
          <para num="(c)">A unique identification number displayed in:<para num="(i)">A minimum of 48-point font; or</para>
            <para num="(ii)">Font that is at least 1 inch in height.</para>
          </para>
        </para>
      </para>
      <para num="C.">Required Features – E-scooters.
A permit holder shall ensure that an e-scooter deployed on a public street:<para num="(1)">Has a speedometer that is legible; and</para>
        <para num="(2)">Is equipped with a speed governor capable of throttling speeds to specific speed limits in geographical areas designated in the MDS Policy API.</para>
      </para>
      <para num="D.">Data and Information.
A permit holder shall ensure a dockless vehicle and its associated apps do not provide false information, including:<para num="(1)">An inaccurate speedometer reading; and</para>
        <para num="(2)">An alarm that announces that a vehicle can notify the police.</para>
      </para>
      <para num="E.">Additional Requirements.<para num="(1)">A permit holder shall certify that its deployed vehicles meet:<para num="(a)">Applicable federal laws;</para>
          <para num="(b)">Applicable State laws;</para>
          <para num="(c)">Applicable provisions of City Code;</para>
          <para num="(d)">CPSC Safety Standards: ISO 43.150 for Pedal Bicycles; and</para>
          <para num="(e)">CPSC Public Law 107-319 for E-Scooters and E-Bicycles.</para>
        </para>
        <para num="(2)">A permit holder shall certify that each dockless vehicle they deploy in the City are:<para num="(a)">Free of defects in materials;</para>
          <para num="(b)">Free of defects in construction; and</para>
          <para num="(c)">Safe for members of the public to use in the ordinary course of usage.</para>
        </para>
      </para>
    </section>
    <section prefix="Regulation" num=".12" heading="Vehicle Standards - Inspections and Notification.">
      <para num="A.">The Department shall:<para num="(1)">Perform regular vehicle inspections to ensure that a rentable dockless vehicle deployed on a public street is:<para num="(a)">Functioning safely; and</para>
          <para num="(b)">Properly equipped; and</para>
        </para>
        <para num="(2)">Provide advance notice to a permit holder about the details of an inspection to be performed.</para>
      </para>
      <para num="B.">For vehicles found to be in violation of &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;, the Department shall notify a permit holder within 24 hours of inspection.</para>
    </section>
    <section prefix="Regulation" num=".13" heading="Vehicle Standards – Timeline for Compliance.">
      <text>Upon notification of a violation in accordance with &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;, the Department shall calculate a timeline for compliance that is:</text>
      <para num="A.">Based on the extent of changes required to a permit holder’s fleet;</para>
      <para num="B.">No fewer than 60 days; and</para>
      <para num="C.">No more than 6 months.</para>
    </section>
    <section prefix="Regulation" num=".14" heading="Remote Shutdown.">
      <para num="A.">User Reported Safety Issue.<para num="(1)">Upon the first report of a safety issue by a user, a permit holder shall remotely shut down the dockless vehicle so that it cannot be operated until repaired.</para>
        <para num="(2)">If a reported safety issue is due to an equipment malfunction which could be present in additional dockless vehicles, the permit holder shall:<para num="(a)">Remove their entire fleet of vehicles from the street within 24 hours; and</para>
          <para num="(b)">Ensure the fleet remains off the street until:<para num="(i)">Further investigation is completed; and</para>
            <para num="(ii)">Relaunch is approved by the City.</para>
          </para>
        </para>
      </para>
      <para num="B.">Remote Shut Down Notice.<para num="(1)">The Department may issue a remote shutdown notice if it is deemed necessary to protect:<para num="(a)">The safety of a dockless vehicle user; or</para>
          <para num="(b)">Public safety.</para>
        </para>
        <para num="(2)">The Department shall ensure a remote shutdown notice includes:<para num="(a)">The duration of the shutdown period;</para>
          <para num="(b)">The reasoning behind the shutdown;</para>
          <para num="(c)">Which vehicle type the permit holder is instructed to shut down; and</para>
          <para num="(d)">The geographic area within Baltimore City in which the vehicles should be shut down.</para>
        </para>
        <para num="(3)">Within two hours of receipt of a remote shutdown notice from the Department, a permit holder shall remotely shut down:<para num="(a)">Part of their fleet, as specified in the notice; or</para>
          <para num="(b)">Their entire fleet, as specified in the notice.</para>
        </para>
      </para>
    </section>
    <section prefix="Regulation" num=".15" heading="Fleet Size.">
      <para num="A.">Minimum and Maximum Fleet Sizes.<para num="(1)">For each permitted vehicle type, a permit holder may initially operate a fleet consisting of:<para num="(a)">A minimum of 150 dockless vehicles; and</para>
          <para num="(b)">A maximum of 1500 dockless vehicles.</para>
        </para>
        <para num="(2)">A permit holder’s total fleet may include a combination of vehicle types allowed by their permit if there is a minimum of 150 vehicles of each type.</para>
      </para>
      <para num="B.">Adaptive Vehicle Exemptions.<para num="(1)">The Department may exempt a permit holder that includes adaptive dockless vehicles in their fleet from:<para num="(a)">The requirement to maintain a minimum of 150 vehicles for adaptive dockless vehicles; and</para>
          <para num="(b)">The requirement to maintain a minimum of 150 vehicles for other permitted dockless vehicle types.</para>
        </para>
        <para num="(2)">A permit holder that includes an adaptive dockless vehicle in their fleet shall ensure the adaptive dockless vehicle:<para num="(a)">Is officially approved by the Director; and</para>
          <para num="(b)">Is not included in the count for the maximum number of vehicles allowed in a permit holder’s fleet.</para>
        </para>
      </para>
      <para num="C.">Timelines for Reaching Minimum Fleet Size.<para num="(1)">A permit holder permitted in the previous year shall reach the minimum fleet size per vehicle type within 20 days of permit issuance.</para>
        <para num="(2)">A new permit holder shall reach the minimum fleet size within 60 days of permit issuance.</para>
        <para num="(3)">A permit holder who introduces a new vehicle type shall reach the minimum fleet size within 60 days of receiving approval of the new vehicle type from the Department.</para>
      </para>
      <para num="D.">Fleet Increases.<para num="(1)">Each quarter, a permit holder may request a fleet increase of up to 250 vehicles in excess of the limits established in &lt;cite data-path="14.02.01.15|A."&gt;§A of this Regulation&lt;/cite&gt;.</para>
        <para num="(2)">In reviewing a fleet increase request, the Department shall assess:<para num="(a)">Performance during the period prior to the evaluation; and</para>
          <para num="(b)">Projections for the subsequent quarter.</para>
        </para>
        <para num="(3)">The Department may:<para num="(a)">Set an overall fleet cap; and</para>
          <para num="(b)">Revoke a fleet increase.</para>
        </para>
      </para>
    </section>
    <section prefix="Regulation" num=".16" heading="Parking and Operation.">
      <para num="A.">In General.<para num="(1)">A permit holder shall instruct users to:<para num="(a)">Park a dockless vehicle in compliance with &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-19"&gt;City Code Article 31, § 38-19&lt;/cite&gt;;</para>
          <para num="(b)">Operate a dockless vehicle in compliance with &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-18"&gt;City Code Article 31, § 38-18&lt;/cite&gt;; and</para>
          <para num="(c)">Provide end of trip pictures that show:<para num="(i)">The location a vehicle was parked; and</para>
            <para num="(ii)">The manner in which a vehicle was parked.</para>
          </para>
        </para>
        <para num="(2)">A permit holder shall use end of trip pictures:<para num="(i)">When a parking violation is reported by the Department; and</para>
          <para num="(ii)">To disable a user account when three or more end of trip pictures fail to provide the information required by &lt;cite data-path="14.02.01.16|A.|(1)|(c)"&gt;§A(1)(c) of this regulation&lt;/cite&gt;.</para>
        </para>
      </para>
      <para num="B.">Notice and Response.<para num="(1)">Upon notification that a dockless vehicle is improperly parked, a permit holder shall reposition or remove the vehicle within:<para num="(a)">Three hours of notification by the Department; and</para>
          <para num="(b)">Six hours of notification by a member of the public.</para>
        </para>
        <para num="(2)">The Department may perform a check of parking complaint response times, during which the Department may:<para num="(a)">Report an illegally parked vehicle officially; or</para>
          <para num="(b)">Anonymously report an illegally parked vehicle as a member of the public.</para>
        </para>
      </para>
      <para num="C.">Abandoned Vehicles.
If a dockless vehicle has been parked at the same location and not ridden for five consecutive days, a permit holder shall:<para num="(1)">Perform a mechanical check of the dockless vehicle; and</para>
        <para num="(2)">Relocate the dockless vehicle to another block face.</para>
      </para>
      <para num="D.">Mobile Application Requirements.
A permit holder shall:<para num="(1)">Ensure a dockless vehicle mobile application displays:<para num="(a)">Applicable operating laws within four menu selections from the home screen; and</para>
          <para num="(b)">The location of parking corrals installed by the Department; and</para>
        </para>
        <para num="(2)">Provide a discount through the mobile application to a user who ends their trip by parking a dockless vehicle in a parking corral installed by the Department.</para>
        <para num="(3)">Upload the location of parking corrals installed by the Department to a dockless vehicle mobile application within 10 days of notification from the Department.</para>
      </para>
      <para num="E.">No Parking Zones.<para num="(1)">The Department may establish a no parking zone on the public street in accordance with &lt;cite data-path="14.02.01.16|E.|(2)"&gt;§E(2) of this regulation&lt;/cite&gt;.</para>
        <para num="(2)">For a no parking zone established in accordance with &lt;cite data-path="14.02.01.16"&gt;this regulation&lt;/cite&gt;, the Department shall:<para num="(a)">Identify the no parking zone in the MDS Policy API; and</para>
          <para num="(b)">Notify a permit holder of the no parking zone through the MDS Policy API.</para>
        </para>
        <para num="(3)">Within 72 hours of notification from the Department, a permit holder shall prohibit a user from ending a trip in a no parking zone.</para>
      </para>
      <para num="F.">No Operation Zones.<para num="(1)">The Department may establish a no operation zone on the public street in accordance with &lt;cite data-path="14.02.01.16|F.|(2)"&gt;§F(2) of this regulation&lt;/cite&gt;.</para>
        <para num="(2)">For a no operation zone established in accordance with &lt;cite data-path="14.02.01.16"&gt;this regulation&lt;/cite&gt;, the Department shall:<para num="(a)">Identify the no operation zone in the MDS Policy API; and</para>
          <para num="(b)">Notify a permit holder of the no operation zone through the MDS Policy API.</para>
        </para>
        <para num="(3)">The Department shall ensure compliance with a no operation zone via testing of vehicles.</para>
        <para num="(4)">Within 72 hours of notification from the Department, a permit holder shall ensure their vehicles lose electric assistance or drive when a user rides into a no operation zone.</para>
      </para>
      <para num="G.">Reduced Speed Zones.<para num="(1)">The Department may establish a reduced speed zone on a public street in accordance with &lt;cite data-path="14.02.01.16|G.|(2)"&gt;§G(2) of this regulation&lt;/cite&gt;.</para>
        <para num="(2)">For a reduced speed zone established in accordance with &lt;cite data-path="14.02.01.16"&gt;this regulation&lt;/cite&gt;, the Department shall:<para num="(a)">Identify the reduced speed zone in the MDS Policy API; and</para>
          <para num="(b)">Notify a permit holder of the reduced speed zone through the MDS Policy API.</para>
        </para>
        <para num="(3)">The Department shall ensure compliance with a reduced speed zone via testing of vehicles.</para>
        <para num="(4)">Within 72 hours of notification from the Department, a permit holder shall ensure their vehicles are limited to eight miles per hour when a user rides into a reduced speed zone.</para>
      </para>
      <para num="H.">A permit holder will be subject to the compliance inspection process in &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;, including the issuance of a warning or citation, if a violation of the provisions of &lt;cite data-path="14.02.01.16"&gt;this regulation&lt;/cite&gt; occurs.</para>
    </section>
    <section prefix="Regulation" num=".17" heading="Seizure and Recovery.">
      <para num="A.">The Department may seize a dockless vehicle if:<para num="(1)">A permit holder fails to comply with a request to reposition or remove a vehicle in accordance with &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;; or</para>
        <para num="(2)">A dockless vehicle is in a location where it cannot be accessed by a permit holder.</para>
      </para>
      <para num="B.">At the time of seizure, the Department shall:<para num="(1)">Notify the permit holder in accordance with &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-24"&gt;City Code Article 31, § 38-24&lt;/cite&gt;;</para>
        <para num="(2)">Take pictures that indicate that the dockless vehicle is in violation of &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;;</para>
        <para num="(3)">Record the identification number of the dockless vehicle; and</para>
        <para num="(4)">Record the property number assigned to the dockless vehicle by the Towing Division.</para>
      </para>
      <para num="C.">If the Department seizes a dockless vehicle, the Department shall charge a permit holder the following fees from the refundable performance bond:<para num="(1)">$220.00, for five or fewer e- scooters seized at the same time;</para>
        <para num="(2)">$220.00, for more than five e-scooters seized at the same time, plus $44.00 per each e-scooter beyond the fifth;</para>
        <para num="(3)">$220.00, for three or fewer bicycles or e-bicycles seized at the same time; and</para>
        <para num="(4)">$220.00, for more than three bicycles or e-bicycles seized at the same time, plus $73.33 per bicycle or e-bicycle beyond the third.</para>
      </para>
      <para num="D.">After the first 48 hours from the initial seizure date, the Department may charge a permit holder $15.00 for each 24-hour period for each group of:<para num="(1)">Up to five e-scooters; or</para>
        <para num="(2)">Up to three bicycles or e-bicycles.</para>
      </para>
      <para num="E.">Recovery of Seized Vehicles.<para num="(1)">A permit holder shall retrieve a seized dockless vehicle from:</para>
        <para num="(2)">A permit holder shall notify the Towing Division of the person who will retrieve a seized vehicle by calling 410-396-9958 or 410-545-3417.</para>
      </para>
    </section>
    <section prefix="Regulation" num=".18" heading="User Education.">
      <para num="A.">A permit holder shall provide in-app user education on proper operation of a dockless vehicle by:<para num="(1)">Developing an in-app quiz for new users that:<para num="(a)">Contains a minimum of five questions approved by the Department pertaining to:<para num="(i)">Parking;</para>
            <para num="(ii)">Operations; or</para>
            <para num="(iii)">General safety; and</para>
          </para>
          <para num="(b)">Requires a score of at least 80 percent before the third rental of a dockless vehicle by a user; and</para>
        </para>
        <para num="(2)">Displaying a banner on the app home screen for up to one week of each month that highlights relevant information determined by the Department.</para>
      </para>
      <para num="B.">A permit holder shall provide in-person user education on proper operation of a dockless vehicle by:<para num="(1)">Hosting or participating in a minimum of one community event per deployment district annually to display safety information;</para>
        <para num="(2)">Attending a minimum of two community events annually between November and February; and</para>
        <para num="(3)">Attending a minimum of four public meetings upon invitation by the Department.</para>
      </para>
      <para num="C.">Access to Additional User Data.<para num="(1)">A permit holder may request that users “opt in” to provide access to:<para num="(a)">Location services; or</para>
          <para num="(b)">Files on a user’s phone.</para>
        </para>
        <para num="(2)">A permit holder may not prevent use of a dockless vehicle based on a user’s decision to grant or deny the data noted in &lt;cite data-path="14.02.01.18|C.|(1)"&gt;§C(1) of this regulation&lt;/cite&gt;.</para>
      </para>
      <para num="D.">Departmental Survey.
Within 10 days of notification by the Department, a permit holder shall:<para num="(1)">Include a clickable link to a yearly Department survey in the mobile application; and</para>
        <para num="(2)">Send the survey link to active users via e-mail.</para>
      </para>
    </section>
    <section prefix="Regulation" num=".19" heading="Special Events.">
      <para num="A.">The Department may require a permit holder to provide staffing for special events expecting over 5,000 attendants in accordance with &lt;cite data-path="14.02.01.19"&gt;this regulation&lt;/cite&gt;.</para>
      <para num="B.">Upon notification from the Department, a permit holder shall be required to:<para num="(1)">Designate an individual as a staff contact for event organizers;</para>
        <para num="(2)">For events expecting 5,000-9,999 people in attendance, provide up to two staffers for:<para num="(a)">Up to one hour before the event;</para>
          <para num="(b)">During the event; and</para>
          <para num="(c)">Up to one hour after the conclusion of the event;</para>
        </para>
        <para num="(3)">For events expecting over 10,000 people in attendance, provide up to three staffers for:<para num="(a)">Up to one hour before the event;</para>
          <para num="(b)">During the event; and</para>
          <para num="(c)">Up to one hour after the conclusion of the event.</para>
        </para>
      </para>
    </section>
    <section prefix="Regulation" num=".20" heading="Pricing.">
      <para num="A.">Except as provided in &lt;cite data-path="14.02.01.20|B."&gt;§B of this regulation&lt;/cite&gt;, a permit holder may not:<para num="(1)">Set a higher price for the use of a dockless vehicle in a certain part of the City; or</para>
        <para num="(2)">Base pricing on a users’:<para num="(a)">Inclusion in a federally protected class;</para>
          <para num="(b)">Genetic information; or</para>
          <para num="(c)">Citizenship.</para>
        </para>
      </para>
      <para num="B.">A permit holder may use a pricing variation to:<para num="(1)">Incentivize proper operation of a dockless vehicle; or</para>
        <para num="(2)">Increase usership among underserved or low-income populations.</para>
      </para>
    </section>
    <section prefix="Regulation" num=".21" heading="Advertising and User Engagement.">
      <para num="A.">A permit holder shall ensure that user engagement, including participation at required community events, is inclusive of:<para num="(1)">Underserved populations; and</para>
        <para num="(2)">Low-income populations.</para>
      </para>
      <para num="B.">A permit holder may not:<para num="(1)">Use the name of a City agency, including the Department, without prior written approval;</para>
        <para num="(2)">Use the logo of a City agency, including the Department, without prior written approval’ and</para>
        <para num="(3)">Use the following to display third-party advertising:<para num="(a)">A dockless vehicle;</para>
          <para num="(b)">A mobile application;</para>
          <para num="(c)">A kiosk;</para>
          <para num="(d)">Related physical infrastructure; or</para>
          <para num="(e)">Related web-based infrastructure.</para>
        </para>
      </para>
    </section>
    <section prefix="Regulation" num=".22" heading="Data and Reporting.">
      <para num="A.">GPS.
A permit holder shall ensure each dockless vehicle in their fleet is equipped with on-board GPS technology that does not rely on a user’s mobile device to obtain spatial information.</para>
      <para num="B.">Publicly Accessible Application Program Interface (API).<para num="(1)">The permit holder shall provide a publicly accessible API.</para>
        <para num="(2)">The permit holder shall ensure that:<para num="(a)">The public API is in a gbfs.json file format;</para>
          <para num="(b)">There are no “stations” in the parlance of GBFS, therefore both station_status.json and station_information.json should return an empty list;</para>
          <para num="(c)">FreE-Bicycle-status.json is required;</para>
          <para num="(d)">The field “vehicle_type” is added to the public API to describe the vehicle type, which may be:<para num="(i)">“Bicycle”;</para>
            <para num="(ii)">“E-Bicycle”;</para>
            <para num="(iii)">“Scooter”; or</para>
            <para num="(iv)">Another type of specified permitted vehicle;</para>
          </para>
          <para num="(e)">The Department is instructed on how to request authentication, if the public API requires authentication;</para>
          <para num="(f)">The location of the public API is provided to the Department; and</para>
          <para num="(g)">A smart phone-based application used to rent dockless vehicles is not considered the public API program interface required by &lt;cite data-path="14.02.01.22|B.|(1)"&gt;§B(1) of this regulation&lt;/cite&gt;.</para>
        </para>
        <para num="(3)">The permit holder shall provide access to at least 50 requests per hour.</para>
        <para num="(4)">The Department shall post the location of the public API to the Department’s website.</para>
      </para>
      <para num="C.">Mobility Data Specification (MDS) Policy API.<para num="(1)">A permit holder shall:<para num="(a)">Provide an MDS Policy API to the Department for a dockless vehicle trip in Baltimore City, including trips which:<para num="(i)">Start in Baltimore City;</para>
            <para num="(ii)">End in Baltimore City; or</para>
            <para num="(iii)">Pass through Baltimore City;</para>
          </para>
          <para num="(b)">Adhere to an MDS of 1.0 or newer, as set by the OMF;</para>
          <para num="(c)">Post the MDS Policy API on GitHub under the OMF Mobility Data specification;</para>
          <para num="(d)">Provide API endpoints, including:<para num="(i)">A trip;</para>
            <para num="(ii)">A status change;</para>
            <para num="(iii)">A vehicle; and</para>
            <para num="(iv)">Real-time data;</para>
          </para>
          <para num="(e)">Update or add endpoints to the MDS Policy API within:<para num="(i)">Sixty days of notification from the Department for required published endpoints; and</para>
            <para num="(ii)">Ninety days for beta endpoints;</para>
          </para>
          <para num="(f)">Change vehicle status to ‘Unknown’ if a vehicle is suspected to be:<para num="(i)">Vandalized; or</para>
            <para num="(ii)">Missing for five or more days;</para>
          </para>
          <para num="(g)">Ensure GPS data are transmitted from a dockless vehicle on-trip at a minimum frequency of once per 30 seconds;</para>
          <para num="(h)">Develop and maintain a working Wi-Fi connection to ingest MDS Policy API endpoints provided by the Department; and</para>
          <para num="(i)">Share current data through the MDS Policy API at least once per 24 hours.</para>
        </para>
        <para num="(2)">The Department may require additional or updated endpoints published by OMF.</para>
        <para num="(3)">The Department may share the MDS Policy API with a third-party aggregator in accordance with &lt;cite data-path="14.02.01.22|C.|(4)"&gt;§C(4) of this regulation&lt;/cite&gt; for the purpose of:<para num="(a)">Secure data storage; and</para>
          <para num="(b)">Analysis.</para>
        </para>
        <para num="(4)">To share data with a third-party aggregator in accordance with &lt;cite data-path="14.02.01.22|C.|(3)"&gt;§C(3) of this regulation&lt;/cite&gt;, the Department shall enter into a memorandum of understanding with a third-party aggregator that:<para num="(a)">Includes a provision governing the public release of data by a third-party aggregator; and</para>
          <para num="(b)">Is made available for a permit holder to review prior to being finalized.</para>
        </para>
      </para>
      <para num="D.">Reporting.<para num="(1)">Time Sensitive Reports.
A permit holder shall report the following to the Department within 24 hours of notice:<para num="(a)">Non-deployment request at a location by an adjacent property owner for verification by the Department;</para>
          <para num="(b)">A vehicle that is in a location where the permit holder cannot retrieve it, including a body of water; and</para>
          <para num="(c)">An issue that could affect public safety, including:<para num="(i)">A report of criminal activity involving a dockless vehicle;</para>
            <para num="(ii)">A report of a crash involving a dockless vehicle;</para>
            <para num="(iii)">Contact with the Baltimore City Police Department;</para>
            <para num="(iv)">Contact with the Baltimore City Fire Department; or</para>
            <para num="(v)">A defect in equipment.</para>
          </para>
        </para>
        <para num="(2)">Monthly Reports.
A permit holder shall provide the Department with a monthly report by the tenth business day following the final day of the month which:<para num="(a)">Uses the Department’s reporting template;</para>
          <para num="(b)">Is in Excel or CSV format;</para>
          <para num="(c)">Includes:<para num="(i)">A report of each dockless vehicle lost due to theft or vandalism;</para>
            <para num="(ii)">Aggregated repair information on a permit holder’s dockless vehicle fleet by model of vehicle and type of repair;</para>
            <para num="(iii)">Each illegal parking request from the public;</para>
            <para num="(iv)">Each customer complaint received with response time noted;</para>
            <para num="(v)">A record of attendance at a City meeting;</para>
            <para num="(vi)">The number of people in attendance at a community event;</para>
            <para num="(vii)">A summary of marketing efforts;</para>
            <para num="(viii)">The number of users that took a trip on a dockless vehicle during the reporting period;</para>
            <para num="(ix)">The number of rides by low-income pass users during the reporting period;</para>
            <para num="(x)">The number of rides by cash users during the reporting period;</para>
            <para num="(xi)">The number of rides by non-smart phone users during the reporting period;</para>
            <para num="(xii)">The number of users provided for in &lt;cite data-path="14.02.01.22|D.|(2)|(c)|(ix)"&gt;§(2)(c)(ix)&lt;/cite&gt;&lt;cite data-path="14.02.01.22|D.|(2)|(c)|(xi)"&gt;-(xi)&lt;/cite&gt; of &lt;cite data-path="14.02.01.22"&gt;this regulation&lt;/cite&gt; disaggregated by the type of plan and user home zip code;</para>
            <para num="(xiii)">The number of users of the low-income pass; and</para>
            <para num="(xiv)">An update to maintenance or operational plan.</para>
          </para>
        </para>
        <para num="(3)">Software Issues and Hacking Events.
A permit holder shall:<para num="(a)">Notify the Department of a change to a data portal, including a response to a notification from the Department regarding:<para num="(i)">A software glitch;</para>
            <para num="(ii)">An issue with hacking; or</para>
            <para num="(iii)">A data portal;</para>
          </para>
          <para num="(b)">Acknowledge a notification from the Department about data and reporting within 24 hours;</para>
          <para num="(c)">Provide the Department with a plan for addressing an identified problem;</para>
          <para num="(d)">Provide a progress update to the Department once per 48 hours while the problem persists; and</para>
          <para num="(e)">Permanently fix an issues within 60 days of receiving notice of the problem.</para>
        </para>
        <para num="(4)">User Privacy.
A permit holder shall protect user privacy by:<para num="(a)">Complying with Payment Card Industry Data Security Standards for an electronic payment;</para>
          <para num="(b)">Notifying a user of a mobile device feature that the mobile application accesses; and</para>
          <para num="(c)">Not releasing personal user data to an entity:<para num="(i)">Unrelated to operations; or</para>
            <para num="(ii)">That intends to use the data in a commercial sale to a third party.</para>
          </para>
        </para>
      </para>
    </section>
    <section prefix="Regulation" num=".23" heading="Security Bond.">
      <para num="A.">Security Bond.<para num="(1)">A permit holder shall provide a security for performance in the amount of $10,000 to the Department.</para>
        <para num="(2)">A permit holder shall ensure the security is in the form of:<para num="(a)">A performance bond;</para>
          <para num="(b)">A refundable bond; or</para>
          <para num="(c)">Another security acceptable to the City.</para>
        </para>
      </para>
      <para num="B.">Rental Taxes.<para num="(1)">A permit holder shall remit a rental tax to the Department of Finance twice annually in accordance with &lt;cite data-path="14.02.01.23"&gt;this section&lt;/cite&gt;.</para>
        <para num="(2)">January – June.<para num="(a)">The Department shall invoice a permit holder by July 15 for the tax provided for in &lt;cite data-path="14.02.01.23|B.|(2)|(b)|(i)"&gt;§B(2)(b)(i) of this regulation&lt;/cite&gt;.</para>
          <para num="(b)">The permit holder shall:<para num="(i)">Pay a tax of $0.10 per rental for dockless vehicle rentals between January 1 and June 30 annually; and</para>
            <para num="(ii)">Remit the tax within one calendar month after receiving an invoice from the Department.</para>
          </para>
        </para>
        <para num="(3)">July – December.<para num="(a)">The Department shall invoice a permit holder by January 15 for the tax provided for in &lt;cite data-path="14.02.01.23|B.|(3)|(b)|(i)"&gt;§B(3)(b)(i) of this regulation&lt;/cite&gt;.</para>
          <para num="(b)">The permit holder shall:<para num="(i)">Pay a tax of $0.10 per rental for dockless vehicle rentals between July 1 and December 31 annually; and</para>
            <para num="(ii)">Remit the tax within one calendar month after receiving an invoice from the Department.</para>
          </para>
        </para>
        <para num="(4)">A permit holder shall submit the following to the Department with each remitment of the annual tax:<para num="(a)">A list of the total number of transactions during the reporting period; and</para>
          <para num="(b)">A digital copy of:<para num="(i)">Payments during the reporting period; and</para>
            <para num="(ii)">Transactions during the reporting period.</para>
          </para>
        </para>
      </para>
    </section>
    <section prefix="Regulation" num=".24" heading="Procedures for Claims Against Security Bond.">
      <para num="A.">Authorization to Draw Against Security.
The City may deduct from the security provided by a permit holder to recover incurred costs if:<para num="(1)">A permit holder fails to remove from the public street a dockless vehicle that is:<para num="(a)">Unsafe;</para>
          <para num="(b)">Unpermitted; or</para>
          <para num="(c)">Abandoned;</para>
        </para>
        <para num="(2)">The Department seizes a dockless vehicles due to a violation of these regulations; or</para>
        <para num="(3)">A permit holder’s dockless vehicle causes damage to public property.</para>
      </para>
      <para num="B.">Notification.
If the City intends to deduct from a permit holder’s security as provided in &lt;cite data-path="14.02.01.24|A."&gt;§A of this regulation&lt;/cite&gt; the Department shall provide written notice to a permit holder prior to the deduction which states:<para num="(1)">The reason for the deduction;</para>
        <para num="(2)">The amount of the deduction;</para>
        <para num="(3)">Information on submission of an objection to a deduction in accordance with &lt;cite data-path="14.02.01.24|C."&gt;§C of this regulation&lt;/cite&gt;.</para>
      </para>
      <para num="C.">Objection Submission.
A permit holder may submit an objection to a planned deduction to their security bond:<para num="(1)">In writing; and</para>
        <para num="(2)">Within 7 days of the date of the written notice.</para>
      </para>
      <para num="D.">Notification of Outcome.<para num="(1)">The Department shall provide a permit holder with written notification of a decision rendered regarding their objection which:<para num="(a)">Provides the reason for denying the objection; or</para>
          <para num="(b)">Confirms acceptance of the objection.</para>
        </para>
        <para num="(2)">The Department shall send the notification to the permit holder three days before a deduction is made.</para>
      </para>
    </section>
    <section prefix="Regulation" num=".25" heading="Insurance.">
      <para num="A.">Required Insurance.
A permit holder shall procure and maintain the coverage required in the permit agreement during:<para num="(1)">The term of an initial dockless vehicle permit; or</para>
        <para num="(2)">The renewal of a dockless vehicle permit:</para>
      </para>
      <para num="B.">A permit holder shall name The Mayor and City Council of Baltimore as an additional insured on the permit holder’s:<para num="(1)">Commercial general liability insurance; and</para>
        <para num="(2)">Commercial automobile liability policies.</para>
      </para>
      <para num="C.">A permit holder shall indemnify the Mayor and City Council of Baltimore from liability relating to:<para num="(1)">The issuance of a dockless vehicle; or</para>
        <para num="(2)">The provision of services under a dockless vehicle permit.</para>
      </para>
      <para num="D.">The City shall notify a permit holder before resolution or settlement of claims for which the City will seek indemnification.</para>
    </section>
    <section prefix="Regulation" num=".26" heading="Citations.">
      <para num="A.">The Department may:<para num="(1)">Issue a citation under &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|1|§40-14"&gt;City Code Article 1, § 40-14&lt;/cite&gt; to a permit holder found to be in violation of:<para num="(a)">&lt;cite data-path="14.02.01"&gt;This chapter&lt;/cite&gt;; or</para>
          <para num="(b)">&lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31"&gt;City Code Article 31&lt;/cite&gt;, Subtitle 38; or</para>
        </para>
        <para num="(2)">Issue a citation under &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|1|§41-14"&gt;City Code Article 1, § 41-14&lt;/cite&gt; to a permit holder found to be in violation of:<para num="(a)">&lt;cite data-path="14.02.01"&gt;This chapter&lt;/cite&gt;; or</para>
          <para num="(b)">&lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31"&gt;City Code Article 31&lt;/cite&gt;, Subtitle 38.</para>
        </para>
      </para>
      <para num="B.">Notification of Violation.
If a permit holder is found to be in violation during a compliance inspection, the Department shall:<para num="(1)">Issue a first warning to the permit holder noting the violation;</para>
        <para num="(2)">Issue a second warning to a permit holder if the violation recurs within 60 days of the first warning; and</para>
        <para num="(3)">Issue a citation if the violation recurs within 60 days of the second warning.</para>
      </para>
      <para num="C.">Abatement Period.
The Department shall:<para num="(1)">Grant an abatement period to a permit holder to fix a violation; and</para>
        <para num="(2)">Issue an additional citation to a permit holder who commits an additional violation within 60 days of a granted abatement period.</para>
      </para>
      <para num="D.">Appeals<para num="(1)">A permit holder may appeal:<para num="(a)">A civil citation to the District Court of Baltimore City; or</para>
          <para num="(b)">An environmental citation to Environmental Control Board.</para>
        </para>
        <para num="(2)">For a citation issued in accordance with &lt;cite data-path="14.02.01.26|D.|(1)|(b)"&gt;§ D(1)(b) of this regulation&lt;/cite&gt;, a permit holder may appeal a decision rendered by the Environmental Control Board to the Circuit Court.</para>
      </para>
    </section>
  </container>
</baltimore-city-law>
