storing "data transparency" in consent records

[Rod Widdowson]

> So it's with these thoughts that I'm pondering how best to treat these
> two intercepts *right* *now* (with GDPR coming into effect today):
> * Use RDBMS storage for consent and localStorage for inform?
>   (But then if you have RDBMS storage to make consent Just Work across
>   devices why bother with device-specific localStorage for the
>   "inform" nag screens?)
> * Use separate RDBMS tables for consent vs. inform (somehow)?
> * Don't bother about this and let people "revoke" "consent", explaining
>   in The Fine Local Documentation that this also covers "re-activating
>   those friendly information screens" for R&S and CoCo services?

I'm taking this as read that this cannot be pushed back to the IDM?  It seems to fit the "admin-writes, user-reads" paradigm...