How to understand consent receipts

Depending on your business, you may be subject to a variety of regulations that require your website visitors to provide consent in order to interact with certain types of content. Various data privacy regulations require you to provide users with a mechanism to opt-in or opt-out of certain cookies on your website, which generates a consent receipt. If you are using Clym's wiretapping functionality on your website's live chat or AI chatbot to collect additional consent, a receipt is generated to capture the consent allowed or denied. Similarly, if you are subject to VPPA and utilizing Clym's solution to collect user consent on embedded content on your website, Clym generates a receipt with every preference configured by the user. These receipts serve as a record of each user's consent choices, helping you maintain transparency and demonstrate compliance with applicable regulations.

Within the Clym Control Center, all consent receipts are securely stored and easily accessible in one centralized location. This makes it simple to review individual consent records, monitor consent activity over time, and respond confidently to compliance audits. Additionally, users can view their consent receipts to review their choices through the Clym widget at any time. Each consent receipt includes unique identifiers, detailed records, and timestamps, making it essential to understand the information each receipt contains.

Cookies

Details

• Receipt ID - Each consent received generates a unique receipt ID that is tied to the record. For example, this may look something like RCPT_nufnZC8CFTFZhWnUAa1eqkC1pkyTmk4u.
• Receipt status - The status will be Allowed if the user accepted all cookies, Partial if the user accepted some cookies, and Denied if the user rejected all cookies.
• Receipt type - Cookie consent will always be displayed on a cookie consent receipt to indicate the user's choices with your website's cookies.
• Created on - This indicates the date and time when consent was collected and the receipt was generated.
• Data controller - Your company's name will be listed here to indicate that you are the one running these services on your website.
• Processing purposes - Depending on the types of services you are running on your website, the processing purposes will indicate why they are running, such as to provide support, deliver custom tailored ads, or to comply with legal requirements.
• Collection method - The collection method will indicate Online form to indicate that the user provided their preferences using your Clym widget.

User data

• Country - This indicates which country the user visiting your website originated from.
• Region - If applicable, this indicates which region within the country the user originated from, such as the state or province.
• Origin - This indicates the URL that the user accessed the Clym widget from and provided consent selections, such as clym.io.
• Profile ID - The profile ID is unique to each user accessing the same property. If the same user submits a DSR or other type of consent, it will contain the same profile ID. For example, this may look something like 8f35a641690d4f04b2412e1cbwvedpjh.

Wiretapping

Details

• Receipt ID - Each consent received generates a unique receipt ID that is tied to the record. For example, this may look something like RCPT_nufnZC8CFTFZhWnUAa1eqkC1pkyTmk4u.
• Receipt status - The status will be Allowed if the user accepts the terms to use the chat and Denied if the user rejects the terms and does not interact with the chat.
• Receipt type - Wiretapping will always be displayed on a wiretapping receipt to indicate the user's consent.
• Created on - This indicates the date and time when consent was collected and the receipt was generated.
• Data controller - Your company's name will be listed here to indicate that you are the one collecting consent.
• Processing purposes - This indicates the purpose of the chat widget on your website for which you are collecting wiretapping consent. For example, Online social activities.
• Collection method - The collection method will indicate Online form to indicate that the user provided their preferences using your Clym solutions on your website.

User data

• Country - This indicates which country the user visiting your website originated from.
• Region - If applicable, this indicates which region within the country the user originated from, such as the state or province.
• Origin - This indicates the URL that the user accessed the Clym wiretapping screen from and provided consent selections, such as clym.io.
• Profile ID - The profile ID is unique to each user accessing the same property. If the same user submits a DSR or other type of consent, it will contain the same profile ID. For example, this may look something like 8f35a641690d4f04b2412e1cbwvedpjh.

VPPA

Details

• Receipt ID - Each consent received generates a unique receipt ID that is tied to the record. For example, this may look something like RCPT_nufnZC8CFTFZhWnUAa1eqkC1pkyTmk4u.
• Receipt status - The status will be Allowed if the user accepts the terms to view the embedded video and Denied if the user rejects the terms and does not interact with the video.
• Receipt type - VPPA will always be displayed on a VPPA receipt to indicate the user's consent.
• Created on - This indicates the date and time when consent was collected and the receipt was generated.
• Data controller - Your company's name will be listed here to indicate that you are the one collecting consent.
• Processing purposes - This indicates the purpose of the video on your website for which you are collecting VPPA consent. For example, Display audio/video content.
• Collection method - The collection method will indicate Online form to indicate that the user provided their preferences using your Clym solutions on your website.

User data

• Country - This indicates which country the user visiting your website originated from.
• Region - If applicable, this indicates which region within the country the user originated from, such as the state or province.
• Origin - This indicates the URL that the user accessed the Clym screen from and provided consent selections, such as clym.io.
• Profile ID - The profile ID is unique to each user accessing the same property. If the same user submits a DSR or other type of consent, it will contain the same profile ID. For example, this may look something like 8f35a641690d4f04b2412e1cbwvedpjh.

If you encounter any challenges, please reach out to support@clym.io.

Updated on: 14/05/2026