Termination Time in Consent Receipt

[ShanChathusanda93]

Hi,

There is a termination time in each purpose in a consent receipt. When a user upload a consent receipt to an organization, the organization can process that user's consents. My question is, from when the organization have to terminate each purpose? Is it from the consentTImestamp which is delivered by the consent receipt or from the time that the organization got the consent receipt.

Thanks.

[dturnerx]

@ShanChathusanda93 - It depends :-)

The challenge is the very large number of variations of termination conditions. You've identified two. Another could be x days after the user unsubscribes from the service or y days following the user's last use of the service. This is why we left the field as a string.

As adoption grows, our hope is that standardized term and conditions, or at least consistent ones, will be defined by industry groups or domains.

[ShanChathusanda93]

Hi @dturnerx
In the specification the termination time is a string describing when the consent expired. Can we provide the exact date and time the consent is expired in the consent receipt? or should it be a string in the specification?

Regards.

[dturnerx]

@ShanChathusanda93
Termination is not a time, it's a set of conditions, which could be just a specific time and date. Hence my previous comment. The WG decided the problem was too hard to solve in v1.1.

4.5.9. Termination
REQUIRED: Conditions for the termination of consent. Link to policy defining how consent or purpose is terminated.
JSON: termination, type: string