My consent log
The log answers "what was done with my consents". It shows, newest first, what Agreely recorded on your consents and acknowledgments, with keyset pagination to page through a long history. It is reached from the dashboard, and each company's detail shows the part that concerns that company.
What the log shows
Each entry is a sentence naming the company, the category of information and the purpose concerned, with the event type and its date:
- consent given;
- acknowledgment of a purpose presented for information, for which no consent was asked of you;
- check of a consent by the company, with the decision returned (allowed or denied);
- withdrawal;
- erasure: the entry keeps only the date. The company, the information and the purpose it covered no longer appear, since that link is exactly what the erasure destroyed.
Badges flag a consent signed on paper, recorded by the company (weaker evidence than a consent given with a passkey), and a purpose tied to an automated decision (décision automatisée).
What the log does not show
No entry is a consultation of your data: a check only says that the company asked whether your consent was in force. A refusal of consent does not appear, because Agreely does not link it to your account. Checks on a purpose for which no consent was asked of you do not appear either.
You see your log without exposing who you are
Agreely never persists or returns a link between a customer identifier and your DID. The log is assembled inside your own session, from only the consents your DID holds. So you see your own events without that correlation existing anywhere: unlinkability is preserved right into the log.
The same log, seen from both sides
The company sees these same events from its own side, indexed by its internal customer identifier. Both views cover the same events without ever meeting in a shared identity. On the company side, that log is a hash-chained register whose epochs are anchored on-chain: see the access log and customers.