Verra Mobility (“we” or “us”) uses cookies on the Asset Management System website and mobile app (“AMS”). The information set out in this policy should be read alongside our privacy notice.

Cookies are small text files that are placed on your computer or mobile device by websites that you visit. They are widely used to make websites work, or work more efficiently, as well as to provide web services and functionalities for users. For example, they enable you to improve your experience on AMS and enable AMS to remember your actions and preferences (such as login, language, font size and other display preferences) over a period of time, so you don’t have to keep re-entering them whenever you come back to the Website or browse from one page to another.

You do not need to have cookies turned on to visit most of AMS. However, having cookies switched on should allow for a smoother and more tailored browsing experience, and is required for certain parts of AMS’s functionality. In the majority of cases, a cookie does not provide us with any personal information.

Types of Cookies

Cookies may be either “persistent” cookies or “session” cookies. AMS uses both persistent and session cookies.

A persistent cookie consists of a text file sent by a web server to a web browser, which allows us to collect and analyze (on an anonymous basis) traffic and use of AMS, monitor the system and improve operating performance, for example, store your preferences to enhance your subsequent visits. It will not be automatically deleted when the browser is closed but is stored by the browser and will remain valid until its set expiry date (unless deleted by the user before the expiry date).

A session cookie is essential to ensure the correct functioning of AMS and is used to manage registration/login and access to reserved features. It is stored temporarily during a browsing session will expire at the end of the user session, when the web browser is closed. AMS uses both persistent and session cookies.

A complete list of the cookies we use is set out in the table at the end of this policy. This list (together with the rest of this policy) is subject to change from time to time.

Our Use of Cookies

We do not automatically capture or store personal information from browsers to AMS, other than to log your IP address (which in certain circumstances will be your personal data) and session information such as the duration of the visit to our site and the nature of the browser used. This information is used only for administration of AMS and in the compilation of statistics which we use for analysis to improve AMS and understand in general terms who uses AMS.

Cookies may be required to allow you to access and participate in certain areas of AMS. Once you have closed your browser, this type of cookie is deactivated. Like all cookies, you can remove or block particular cookies at any time (see below).

Your Cookie Choices

Most browsers will allow you to alter the settings used for cookies and to disable and enable them as you require.

You can reject all cookies (except strictly necessary cookies) in case you prefer not to receive them, and you can have your computer warn you whenever cookies are being used. You can delete the cookies that are already on your computer and you can set your browser to prevent them from being placed. Disabling cookies may, however, prevent some web services (including on AMS) from working correctly. Please be aware that when you have set your computer to reject cookies, it can limit the functionality of AMS and it is possible then that you will not have access to some of the features on AMS.

To disable cookies, or to receive a warning whenever cookies are being used, you must adjust your browser settings. You can adjust your browser settings to delete certain cookies. Visit the “help” section of your browser for how to manage your cookie settings, or follow the links below:

Internet Explorer: http://support.microsoft.com/gp/cookies/en

Mozilla Firefox: http://support.mozilla.com/en-US/kb/Cookies

Google Chrome: http://www.google.com/support/chrome/bin/answer.py?hl=en&answer=95647

Safari: http://support.apple.com/kb/PH5042

Opera: http://www.opera.com/browser/tutorials/security/privacy/

For further general information on cookies and more detailed advice on how to disable and enable them please go to http://www.allaboutcookies.org.

Cookie List

Name Purpose Session/Persistent Type

AspNetCore.Antiforgery

This AntiForgery token cookie prevents “Cross-site request forgery” attacks. More details from Microsoft docs à https://docs.microsoft.com/en-us/aspnet/core/security/anti-request-forgery?view=aspnetcore-2.2

Session

Strictly Necessary Cookies

ARRAffinity

This is created by websites hosted in Azure and is used for making user session stick to a specific webserver in a web farm.

This is needed since AMS maintans user session states. So, switching users between server instances will make the website un-usable

Session

Strictly Necessary Cookies

.AspNetCore.Correlation.oidc We implement the Oauth 2.0 / Open Id Connect protocol for authentication and authorizing users. This cookie is related to that. Note: There could be multiple cookies of this type Persistent - Expires in less than a day Strictly Necessary Cookies
.AspNetCore.OpenIdConnect.Nonce We implement the Oauth 2.0 / Open Id Connect protocol for authentication and authorizing users. This cookie is related to that. Note: There could be multiple cookies of this type Persistent - Expires in less than a day Strictly Necessary Cookies
consent This cookie is created once the user accepts the cookie policy present at the top of the login page. The user cannot login until this policy has been accepted Persistent - Expires in 5 minutes Strictly Necessary Cookies
__cfduid (from datatables.net) Used by a Jquery Plugin that is used to display the History page in AMS Persistent - Expires in 1 month Strictly Necessary Cookies
__cfduid (from cloudfare.com) Used by a Jquery Plugin that is used to display the History page in AMS Persistent - Expires in 1 month Strictly Necessary Cookies
.AssetManagement.Session Used to store user session state Session Strictly Necessary Cookies
.AspNetCore.Cookies Used to store Identity Claims, continuation of above, now stored in new cookie chunks. Note: These cookies can be named .AspNetCore.CookiesC1 to .AspNetCore.CookiesCn where n equals any number. This means there could be multiple cookies of this type numbered appropriately. This could vary from user to user Session Strictly Necessary Cookies
.AspNetCore.CookiesC1 Used to store Identity Claims, continuation of above, now stored in new cookie chunks. Note: These cookies can be named .AspNetCore.CookiesC1 to .AspNetCore.CookiesCn where n equals any number. This means there could be multiple cookies of this type numbered appropriately. This could vary from user to user Session Strictly Necessary Cookies
.AspNetCore.CookiesC2 Used to store Identity Claims, continuation of above, now stored in new cookie chunks. Note: These cookies can be named .AspNetCore.CookiesC1 to .AspNetCore.CookiesCn where n equals any number. This means there could be multiple cookies of this type numbered appropriately. This could vary from user to user Session Strictly Necessary Cookies
LogoutMessage. Used and created by Identity Server after logout. Note: There could be multiple cookies of this type Session Strictly Necessary Cookies
idsrv Used and created by Identity Server. Note: There could be multiple cookies of this type Session Strictly Necessary Cookies
idsrv.ClientSessions. Used and created by Identity Server. Note: There could be multiple cookies of this type Session Strictly Necessary Cookies
idsrv.session Used and created by Identity Server. Note: There could be multiple cookies of this type Session Strictly Necessary Cookies