Privacy Policy

1. Data Controller

The data controller for ducksource.blog is Chris Coveyduck, UK-based. For any data-related enquiries, please contact chris@ducksource.blog.

2. What Data Is Collected

ducksource.blog is a personal/professional blog. We collect minimal data:

• Analytics: We may use basic, privacy-respecting analytics to understand which articles are read. This may include page view counts, referring sources, and approximate geography. No personally identifiable information is stored for analytics purposes.
• Comments (Giscus): If you leave a comment on an article, this is powered by Giscus, which uses GitHub Discussions. To comment, you authenticate via GitHub OAuth. Your GitHub username, avatar, and comment content are stored by GitHub, not directly by this site. Please refer to GitHub's Privacy Policy for details.
• Contact: If you email chris@ducksource.blog directly, your email address and message content are retained only as long as necessary to respond.

3. Legal Basis for Processing

Under UK GDPR, processing is carried out on the following bases:

• Legitimate interests — basic site analytics to understand what content is useful, without infringing on visitor privacy.
• Consent — for Giscus comments, you initiate the GitHub OAuth flow voluntarily.
• Contractual necessity — for email enquiries, processing your message to respond is necessary to fulfil the communication you initiated.

4. Cookies

We may use cookies for analytics purposes and to support site functionality. The Cloudflare CDN (see section 5) may set its own cookies for security and performance. Giscus/GitHub may set cookies when you interact with the comment system. We do not use cookies for advertising or cross-site tracking.

5. Third-Party Services

• Cloudflare: This site is hosted and served via Cloudflare, which provides CDN, DDoS protection, and performance optimisation. Cloudflare may process visitor IP addresses and request metadata as part of its service. See Cloudflare's Privacy Policy.
• GitHub / Giscus: Comments are powered by Giscus, which stores discussion data in a GitHub repository. GitHub is the data processor for comment data. See GitHub's Privacy Statement.

6. Data Retention

Personal data is not retained indefinitely. Email correspondence is kept only as long as reasonably necessary. Analytics data, where collected, is retained in aggregate form without linking to individual identities. Comment data stored by GitHub is subject to GitHub's own retention policies.

7. Your Rights Under UK GDPR

You have the following rights regarding any personal data we hold about you:

• Right of access — you may request a copy of any personal data held about you.
• Right to rectification — you may request correction of inaccurate data.
• Right to erasure ("right to be forgotten") — you may request deletion of your data where there is no legitimate reason to continue processing it.
• Right to data portability — you may request your data in a structured, commonly used format.
• Right to object — you may object to processing carried out on the basis of legitimate interests.

To exercise any of these rights, please contact chris@ducksource.blog. We will respond within 30 days.

8. ICO Registration

Individuals and sole traders running personal blogs in the UK may be exempt from mandatory ICO registration, depending on the nature of data processed. ducksource.blog processes minimal personal data and does not process data for commercial gain. We monitor the applicable thresholds and will register with the ICO if required. For more information, see ico.org.uk.

9. Changes to This Policy

This policy may be updated from time to time. The effective date at the top of this page reflects the most recent revision. Continued use of the site after changes are posted constitutes acceptance of the updated policy.

10. Contact

For any privacy-related questions or to exercise your rights, contact: chris@ducksource.blog