What cookies does Community use?

The following Cookie Compliance FAQ has been prepared concerning cookies' use of user information in a user-owned device.

1. Does any part of Telligent Community Server make use of cookies or similar techniques for storing information on the client's browser?
   
   Yes. Community (and Reporting, if in use) store cookies on the client's browser.
   
   
2. What are the cookies, what are they used for, and what information is stored in them?
   
   The cookies are listed and described in the following table. All cookies are purely for technical functionality and user experience. (Updates from previous versions noted in bold)
   
   

   Cookie	Description	Required/Optional
   .te.auth (versions > 12.1)	Used for authentication.	Required
   .te.csrf (versions > 12.1)	Used for security purposes - Cross-site request forgery (CSRF) prevention.	Required
   .CommunityServer (versions < 12.1)	ASP.NET authentication cookie. It is used to support the login system.	Required
   AuthorizationCookie (versions < 12.1)	A Globally Unique Identifier (GUID, e.g., 80FC959D-E916-4C1D-9054-C058450DB32D), used for security purposes.	Required
   Telligent.Evolution-UI	Default cookie used for storing values from widgets. This stores the user's view preferences for blog post lists and forum thread lists. Can be disabled via widget code (BlogPostList and ForumThreadList)	Optional
   tzoffset	Determines a user's time zone offset for use when creating an account. Can be disabled via widget code. (User - Login and Create)	Optional
   tzid	Determines a user's time zone offset for use when creating an account. Can be disabled via widget code. (User - Login and Create)	Optional
   .te.dpr	Stores the device pixel ratio.  Used when providing resized images to the clients to ensure that users get properly resized images on high-resolution displays	Required
   .te.js	Set if the client supports JavaScript. Used to optimize how the platform builds out some pages or alternatively degrade gracefully (ex. search bot).
   .te.w	Stores the device width.	Required
   .te.u	Used when an administrator is impersonating another user. (Previously: Impersonator)	Required
   ThemeConfigration	Used when a user with theme management permissions is previewing theme changes before making them live.	Required
   Telligent.Evolution-MediaGallery	Saves a user’s preference for display of a media gallery file list.	Required
   enable_theme_staging	Used when staged theme changes are being previewed.	Required and set only when previewing is enabled.
   _templates	Client side UI templates used to render content. Does not contain any user data.	Required
   _cwpcr	(C)ross (W)indow (P)resent (C)ontent (R)egistrar  This is part of the infrastructure supporting content presence. Multiple tabs/windows are all tracking what a user is "present" to in their current scrolled segment of their viewport and storing it in a common location (_cwpcr) for the tab that has the actual socket connection to consolidate and send back the server on regular intervals. NOTE: The information in this value is not actually stored anywhere. It's ephemeral and just used to deliver targeted updates to things users are looking at.	Required
   AWSALB	Set by our hosting provider, Amazon AWS, for load balancing purposes.(Only applies when running within our SaaS environment)	Required
   AWSALBCORS	Set by our hosting provider, Amazon AWS, for load balancing purposes.(Only applies when running within our SaaS environment)	Required

3. Are the cookies strictly necessary for the customer or user experience, and if so, why?
   
   With the exception of cookies that can be disabled or turned off, all of these cookies are required for proper site functioning. 
   
   
4. Are any of the cookies used in the processing of personal data? 
   
   No.