In an effort to be transparent and assist with questions related to GDPR, this document has been created to help explain how to view your user data within the Agilent Community, request erasure, and download your information for data portability.
- Privacy Policies
- GDPR Right to Request Erasure
- Your Profile Data
- Your Content
- Data Export of Your Information
- How Cookies Are Used
GDPR Right to Request Erasure
Deleting Your Account
You can request to have your account deleted by visiting your Profile Setting page and clicking the Delete my account link. This will begin a process that dissociates your profile data with your account and any contributions or activity you have participated in.
Your Profile Data
You can access and your profile data by clicking on the avatar in the top right and clicking the link for Profile. The resulting page will show your profile data. To change or update your profile information, please see the following help articles:
From the Browse menu at the top of the site you can access your content by clicking the Your View link. On the resulting page the Activity tab will show any activity related to your account. There are links across the other tabs next to your avatar to show a filtered view of your interactions.
Data Export of Your Information
The platform the Agilent Community uses supports a way for you to download your data. The download will be a ZIP file containing the following information:
- Conversations (note: full conversations are included, not just the messages sent by you)
- Blog posts
- Media posts
- Forum thread and replies
- Wiki pages
- Status messages
- Calendar events
- Profile data
Any files referenced within this content are included in a files/ subfolder of the export ZIP file.
To access this file, go to your Profile Settings page select the option to Export.
For related information please also reference Privacy Settings in the Agilent Community
How Cookies Are Used
The table below explains what cookies the Agilent Community platform uses and if they are required or optional:
|.CommunityServer||This cookie is an ASP.NET authentication cookie. It is used to support the login system.||Required|
|AuthorizationCookie||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.w||Stores the device width.||Required|
|Impersonator||Used when an administrator is impersonating another user.||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.|
|_returnUrl||Used to return user to the page they were viewing after logging in.||Required|
NOTE: Some additional cookies not listed above are used for feedback, analytics, and site performance evaluation.