Privacy Policy

Privacy policy of fullmetalbrackets.com

Last updated on

This privacy policy will advise of what information, if any, is collected when you use this website and for what purpose. The policy may change in the future, at which time this page will be updated. Check back from time to time and note that date the Privacy Policy was last updated.

Data collection

This website does not use cookies. There is no account or newsletter to sign up for, no way for a user to submit information, nor for any user-submitted information to even be stored. You can verify with The Markup’s Blacklight scanner.

[warning]

Under certain circumstances, Cloudflare may issue a “challenge” to confirm that a visitor is not a bot or other malicious actor. If (and only if) a challenge is presented and passed, Cloudflare uses a cf_clearance cookie to preserve the challenge state across cross-site requests. For more information, see this section of the Cloudflare documentation.

This website only collects three temporary pieces of data, and only under specific circumstances:

  1. When you use the theme toggle on the site header to change between light/dark theme, a text string with the choice (light or dark) is saved in your browser’s local storage. This allows the choice of theme to persist across browser sessions.

  2. When you use any of the filters on the Lifestream page and Wiki articles, booleans representing their states are saved in your browser’s session storage. This allows the active/inactive filters to persist across page navigations, but the stored data is cleared when the tab is closed.

  3. At the bottom of all blog posts is a Giscus comment component. When you login to Github through this component to comment on a blog post, a session token is saved in your browser’s local storage. This allows you to remain logged in across browser sessions. (More details about Giscus comments below.)

Besides what is noted above, no other data is collected by this website.

Analytics

This website uses Umami, a Google Analytics alternative which is GDPR-compliant and collects only anonymized traffic data. You can see the stats yourself right here. Data collected through Umami includes visitors’ referrers (what website they came from), country and region, and when certain internal and external links are clicked. This data is anonymized and cannot be used to identify you.

Additionally, because this website is hosted on Cloudflare Workers, by default Cloudflare’s own Web Analytics tracks all HTTP requests, bandwidth usage and unique visitor metrics when visiting this website. This data is anonymized and cannot be used to identify you. For more information, please see Cloudflare Web Analytics.

Comments

Certain pages, as well as all blog posts and wiki articles, use Giscus for commenting which collects no data. However, that any information you put into your comments are publically displayed for all to see at the bottom of any page on site this that you are commenting on.

Please be aware a GitHub account is required to leave comments, and by commenting you will actually be participating in GitHub Discussions on this website’s public GitHub repository. Because the repo is public, any information you put into a comment is publically available via GitHub as well.

Webmentions

This website supports Webmentions for blog posts, wiki articles and various pages.

By supporting Webmentions on your website, you explicitly signal your wish for linked websites to process and publish your public replies to their content. You can at any time request the removal of one or all Webmentions originating from your website.

An incoming Webmention request is by design a request for publishing a comment from elsewhere on the web; this is what the protocol was designed for and why it is active on your website. Commonly, received Webmentions are displayed as comments on a web page. This means that a copy of your content is displayed on the website you link to in your own post.

Brid.gy is used for backfeed, and all of my blog posts are syndicated to both Mastodon and Bluesky. (I do not syndicate or cross-post anywhere else.) Interacting with these syndicated posts on either Mastodon or Bluesky — including replying, re-posting, boosting or liking — will appear on this site below those blog posts.

Likewise, linking to or otherwise interacting with pages on this website from Mastodon, Bluesky or your own website will have it appear below that post or page. If this happens and you’d like for me to delete it from my website, please email me about it and I will do so at my earliest opportunity.

The personal data being processed and published from social media through Brid.gy might include:

  • Your website or profile’s public display name
  • The profile picture from your website or Mastodon/Bluesky account
  • The URL of your website or Mastodon/Bluesky account
  • Any personal information you include in your post

Legal Basis: The publishing of incoming Webmentions is based on the legitimate interest to enable interaction with the readers of this website (Art. 6(1) lit. f GDPR), following the design intention of the Webmention protocol.

This website maintains a list of links to external websites, tools and applications, a blogroll of followed blogs and personal sites, and a postroll of recommended posts or articles. Blog posts or wiki articles on this site may also contain external links to additional resources, official documentation, informative third-party sources, attributions, etc.

I always try to link to reputable sources, but it is up to you to review those websites’ own privacy policies. I cannot accept any responsibility for your privacy once you have left this website.

Contributing

Every blog post has a Suggest edits link at the bottom which leads to the source page on GitHub. If you notice an error or outdated information, or even a typo or other minor thing that’s bugging you, feel free to click the link and fork the repo, make your changes, then submit a pull request. A GitHub account is required.

Alternately you can simply send me an email with any corrections or fixes you’d like to suggest.

Questions and concerns

If you have any concerns about this privacy policy, or any questions about the website or for me specifically, feel free to contact me via email.