The FMEA, FSMA, CFAE, FAEA, and MPA Online websites use cookies, but none of them store direct personal data or data that can potentially be connected or singled out to identify or track a person.


What cookies do we use?

All data stored in cookies on our sites contain closed-system identifiers to maintain application state while the user is logged in. This may include numbers or seemingly random character strings that the application uses so that it knows which user is logged in and other options the user has selected such as their school, details about the MPA event they are entering or conference they are registering for, etc. This data is internal to our closed systems and cannot be used by outside parties to identify or track a person.

Google Analytics:  We use Google Analytics to analyze our web traffic and user behavior patterns in order to improve the design and organization our website content. In compliance with Google’s terms of service, no personally identifiable data is sent to Google or stored in Google cookies.

XSRF or AntiXsrfToken: These cookies contain tokens that the server uses to prevent cross-site request forgery attacks. No user data is included.

CloudFlare: The CloudFlare content distribution network uses this cookie to identify our website as trusted web traffic. It does not correspond to any user in the web application, nor does it store any personally identifiable information.

ASP.NET_SessionId: The encrypted code in this cookie is used to tell the server which session state should be used for the current web request. Session state is stored in non-persistent memory on the server only. It internally stores various short-term application variables such as application options or features the user has selected or applied to their account. A user's session state expires from the server after 20 minutes of non-activity, and its content is never transmitted outside of the server or stored in cookies.

FLmusicApps, MPA2, FAEAApps, ASPXAUTH: These are application cookies that are set when the user is logged in. It contains encrypted or hashed tokens that the application can use internally to determine which user account is logged in and making each request.

ComponentID: A key used by MPA Online to determine which component organization the user is currently working in, so it knows which MPA events to offer and which component-specific rules and business logic to enforce.

District: A key that represents the FBA, FOA, or FVA district the user is a part of.

SchoolID: A key used by MPA Online to determine the school that the user has selected on their profile page.

FMEAID or FAEAID:  A key that represents the FMEA or FAEA member record of the currently logged-in member.

SchoolYear: Used by MPA Online to filter events to only the current school year.

RegistrationID: Used by conference or workshop registration to keep track of your specific registration details. Variations are used for various types of workshops or programs for which the user may be registering. & Used by NewRelic, a server and application monitoring service that helps us track application performance, speed, and server errors. No user data is stored, tracked, or transmitted.


For more information or clarification, please email