<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>ConsentVeil Journal</title><link>https://consentveil.com/blog/</link><description>Practical notes on website consent.</description><item><title>A cookie banner is not a test of what happens behind it.</title><link>https://consentveil.com/blog/01-a-banner-is-not-a-test/</link><guid>https://consentveil.com/blog/01-a-banner-is-not-a-test/</guid><description>Why the visible consent interface is only the beginning of a technical review.</description></item><item><title>Where consent checks fit into website maintenance.</title><link>https://consentveil.com/blog/02-consent-checks-after-updates/</link><guid>https://consentveil.com/blog/02-consent-checks-after-updates/</guid><description>A practical way to connect website changes with independent technical checks.</description></item><item><title>How to read a consent report without overreading the score.</title><link>https://consentveil.com/blog/03-reading-a-consent-report/</link><guid>https://consentveil.com/blog/03-reading-a-consent-report/</guid><description>Coverage, confidence and inconclusive results matter as much as the headline number.</description></item></channel></rss>