Withdrawal & preferences

People may change their minds about optional purposes. Operationally, you need a record of the new choice without erasing what happened before.

How Erasure models this

• A receipt is append-only.
• Preference updates create a new receipt for the same project, still tied to the relevant published config.
• Erasure does not “edit” an old receipt in place.

What you implement

1. Keep a published consent version live.
2. Use the SDK preference / update flows as the product and SDK support.
3. Inspect Receipts in the console when auditing.

TODO: Expand with exact SDK preference APIs once public SDK docs section is fully expanded — see SDKs. Do not invent method names beyond documented Anumati.init + consent post.

What this is not

• Not automatic deletion of data when someone withdraws optional analytics (that is a rights / systems problem if you choose to treat it as erasure)
• Not legal determination of which purposes are withdrawable