@Aberger Good suggestions above.
1. Rather than set to "", I would suggest
to delete a specific cookie, or delete
delete b [ k ] ;
if using @UnknownJ's approach
This removes any reference to the cookie data in the data payload sent to the collect tag.
2. It is possible to send the cookie data to the UDH (for example to use in AudienceStream), but not have it sent onwards to EventDB, EventStore or EventStream.
The relevant event attributes could be marked as restricted in UDH. They won't then be sent to EventStore unless explicitly configured to be. https://community.tealiumiq.com//t5/Universal-Data-Hub/Understanding-Restricted-Data/ta-p/17773. There is a separate checkbox to specify if the event attribute should go to EventDB, see screenshot. As for EventStream, the UI will warn you if you choose a restricted attribute to send from an EventStream.
... View more