consent-and-preferences

This skill answers one question: on what basis may the program write to this person at all, in this channel, for this purpose; what did the person say afterward; how far does that reach and how fast; and which uses of their data besides sending rest on which basis and stop on which request.

What sets this work apart from the rest of the library opens references/consent-vocabulary.md.

Three units, named apart. The basis record is one person, one channel, one purpose, with what the permission rests on, where it came from, the wording version, the proof and the lifetime. It is the unit of references/lawful-basis-and-collection.md. The instruction is one recorded choice by the person after that: a type on or off, a frequency, a channel, a pause, or a withdrawal, each with a scope and a deadline by which it takes effect everywhere. It is the unit of references/preference-center-and-unsubscribe.md. The purpose is one reason the program holds or uses personal data other than to send a message, with the data it needs, its basis, its retention line and the route by which the person stops it. It is the unit of references/processing-beyond-sending.md. Mixing the first two is the argument about whether an unsubscribe "counts" for the other brand; mixing the first and the third is the argument about whether consent to a newsletter covers a churn model.