Privacy and consent
Agreements, participant permissions, media usage rights, expiry, and revocation held as structured records rather than remembered exceptions.
The problem this area solves
- One signature is treated as permission for the session, the website, and the ad.
- A withdrawn permission never reaches the person scheduling social posts.
- Nobody can prove what a client agreed to two years ago.
What is in this area today
Each capability is labeled with its real availability. Nothing planned is shown as if it already works.
Layered agreements
AvailableService agreement, session boundaries, and publication permission recorded separately.
Per-asset publication permission
AvailableParticipant, asset, crop, channel, campaign, expiry, and visibility on each record.
Expiry and revocation
Early accessPermissions end on a date or on request, and the change propagates.
Retention scheduling
In developmentPlanned deletion windows for archives and working files.
How client privacy is protected
- Publishing is blocked when the required permission is absent, expired, or withdrawn.
- Consent history is retained so a past state can always be explained.