Privacy Policy
Last updated October 7, 2026.
Who we are
Lockamy Studios (Cary, North Carolina) runs this website, lockamystudios.com. You can reach us at support@lockamystudios.com.
This website
This is a static website. It has no accounts, no sign-in, no forms, no comments, no advertising, and no analytics. It does not set cookies and does not use your browser's local storage.
Two third parties still see your visit, because of how the web works:
- GitHub Pages hosts the site. GitHub receives your IP address and browser details when you load a page, as described in GitHub's privacy statement. We do not run our own server logs.
- Google Fonts supplies the site's typefaces. Your browser requests them from Google, which receives your IP address and browser details, as described in Google's privacy policy.
Links on this site lead to other sites (GitHub, Quickring, SlashBuilder and others). Their own privacy policies apply once you leave this site.
If you email us
If you write to support@lockamystudios.com, we use your message and email address only to reply to you. We keep the conversation for as long as it is useful and we do not sell it or share it with anyone else. Ask us to delete it and we will.
Our LinkedIn app
Lockamy Studios operates a small LinkedIn app, dlockamy_blog_github. Its only job is to share new posts from Douglas Lockamy's own blog (dlockamy.com) to his own LinkedIn profile, so he does not have to copy them over by hand.
- Who uses it: only its owner, Douglas Lockamy. No other LinkedIn member is ever asked to sign in to it, and it is not offered to anyone else.
- What it does: after he authorizes it, it publishes a link and a short summary of a newly published blog post to his profile.
- What LinkedIn data it touches: his LinkedIn member identifier and name, which LinkedIn requires in order to post as him, and the permission to post on his behalf. It does not read his connections, messages, feed, or anyone else's profile, and it collects nothing about people who visit the blog or this site.
- How it is stored: the access token LinkedIn issues is kept as an encrypted secret in a private GitHub Actions configuration. It expires after about 60 days and is then replaced. It is not sold, shared, or used for any other purpose.
- Taking it back: the authorization can be revoked at any time in LinkedIn under Settings → Data privacy → Permitted services, which immediately stops the app from posting.
Children
This site and our apps are not directed at children under 13, and we do not knowingly collect their information.
Changes
If this policy changes, we will update the date at the top of this page. If you have a question about it, write to support@lockamystudios.com.