Community Blog · Privacy
Privacy policy.
This policy covers the community blog, which has accounts. The static reference homepage and status page set no cookies, run no analytics, and collect nothing beyond standard request logs.
01What we collect
When you sign in with Discord we receive, with your consent, from Discord's OAuth2 API: your Discord user ID, username, display name, avatar, and email address. We store that data so that your posts can be attributed to your author profile.
When you use the blog we store: your posts, drafts, revisions, reports you file, and a session cookie that keeps you signed in. We may store your IP address to rate-limit abusive behaviour.
02Cookies
The blog sets one cookie, blog_session, which keeps you signed in. It is HTTP-only, secure, and expires after 30 days. We do not use advertising or tracking cookies.
03Where data lives
Account and post data is stored in a Cloudflare D1 database. The site is served by Cloudflare Pages; Cloudflare may keep standard server logs required to operate the service. Discord is the source of the profile data you authorise us to read.
04Sharing
We do not sell or rent personal data. Public information (your author profile name and display picture) is visible on your author page by design. Your email address is stored privately and is never published.
05Your choices
- You can stop signing in at any time; your posts and profile remain.
- You can delete your drafts; published posts can be unpublished from your dashboard.
- To delete your account and posts entirely, use the contact page. We will remove your data within a reasonable period.
06Children
The service requires an account age in line with Discord's own age requirement (13 or above where Discord allows). We do not knowingly collect data from children below that age.
07Changes
We may update this policy; material changes will be noted on the blog. Contact us through the contact page with privacy questions.