Privacy Policy
Effective .
This is a blog, so, ya know... there's not a lot happening. There's no account system, and I don't have anything for sale. BUT. Legal shit is still shit so I hope you enjoy this _thrilling_ read.
Here's everything that actually happens when you visit.
What lives in your browser
Two things, both stored on your own device and never collected otherwise:
- A
themevalue inlocalStorageso the site remembers whether you want it to use the light, dark, or system theme. - A
pendingAtprotoReactionvalue insessionStoragethat helps track if you tapped a reaction before logging in to your Atmosphere account. It just prevents you from having to tap it again, and it's cleared as soon as you log in and the reaction is created.
Analytics, about which I remain ambivalent
I run Google Analytics on the measurement ID G-901VV0CMLX. It sets two first-party cookies, _ga and one named after that ID. They both stick around for about two years, and they allow Google to process your IP address to work out roughly what country you're in. Google is the processor, and their privacy policy covers what they do with it.
Personally, I use it to see which posts people actually read. That's it. I'll never sell or give any of that data to anyone else.
Honestly, I go back and forth on whether to keep it. Running a Google tracker on a site that otherwise keeps all of your data with you feels icky. I still get value out of the analytics, but if you have recommendations for less invasive tools that provide the insights I care about, hit me up.
If you'd rather not be counted, Google's opt-out add-on works, and so does any decent content blocker. The site works exactly the same either way, and I'd rather have you block it than not visit.
Signing in with your Atmosphere account
Reactions use your Atmosphere account, so you don't need a special account just for this website. I send you over to your PDS to login. Your password is only ever sent to your PDS provider. I never see it, and there's nowhere here to store it if I did.
When you react to a post, that reaction is written into your atproto repository as a codes.trezy.reaction record. Yours, not mine. It's yours the same way your Bluesky/Blacksky/Eurosky/Whateversky posts are, which also means it's public by design, and you can delete it with any tool that can edit your repo.
Reactions and mentions on articles
Article pages use Constellation to figure out which records across the network link back to the post you're reading. That request happens from your browser, so Constellation does get to see your IP the same way any other site you visit does. It's how the mentions section figured out what to show.
Counts and previews are read back from the public Bluesky API and plc.directory for the same reason.
Embeds and diagrams
A handful of older posts embed things I don't host. The embeds include CodePen, Twitter, and YouTube. Some posts also render diagrams as an image through Kroki.
Those embeds and images are loaded directly from their respective servers, which means they can also see your IP and set their own cookies, and I have no control over what they do with either. If you're blocking third-party content, these posts may not read quite right.
Hosting
The site is static and lives on wisp.place. Like any web host, their servers log the usual request data. I don't run a server here, so they're the only ones with any record of you accessing the site files.
Affiliate links
Most of the gear links on /uses are affiliate links, so I may get a commission if you buy something. That's disclosed on the page itself as well. Following one hands you off to that retailer and their tracking, which is entirely theirs.
Things this site doesn't do
- The site has never carried an ad or a sponsor.
- There's no newsletter, so there's nothing to unsubscribe from.
- Signing in is optional, and there's no account to manage.
- Nobody has ever bought data from me, and if somebody asked I'd tell them to fuck off.
Your choices
Block the analytics, clear your site data, or delete a reaction record from your own atproto repo whenever you feel like it. You don't need my permission for any of that, so there's no form to fill in.
If you're in the EU or UK and want to exercise a right under the GDPR, or you're in California and want to exercise one under the CCPA, email me and I'll sort it out. Realistically the answer is usually that I'm not holding anything of yours, but if you ask and I'll tell you exactly what I've got.
When this changes
If I change what the site collects, I'll update this page and move the date at the top.
Getting in touch with me
Trezy.com, LLC
Charles “Trezy” Peebles
[email protected]