Privacy policy

Last updated: August 23, 2026. This policy covers buildwithbaker.io and the free tools listed on the Tools page.

The site itself

buildwithbaker.io is a static website hosted on GitHub Pages. There is no database, no login, no cookies set by me, and no analytics or advertising scripts. The site runs a strict content-security policy that blocks third-party scripts, and it self-hosts its typeface rather than pulling one from a font service.

Because the site is a set of static files, some of the tools save small things in your browser's own local storage so they remember what you were doing. That is not a cookie and it is not sent anywhere - it sits on your device until you clear your browser's site data. Across the site that amounts to: your light or dark theme choice, and, per tool, the small handful of settings listed under each tool below. Nothing in it identifies you, and I cannot read any of it.

Because the site is served by GitHub, GitHub's own infrastructure may log standard request data (such as your IP address and browser type) for security and operational purposes. That happens at the hosting layer for every site on GitHub Pages and is governed by GitHub's privacy statement. I do not have access to those logs and do not collect or store them myself.

The contact form

When you send a message through the contact form, it is delivered to me by Formspree, a form-handling service. The information you type - your name, email address, and message - is transmitted to Formspree and then to my inbox so I can reply.

I use that information only to respond to you and any follow-up about your inquiry. I do not add you to a mailing list, and I do not sell or share it. Formspree's handling of submissions is governed by Formspree's privacy policy. If you'd rather not use the form, you can email me directly at adam@buildwithbaker.io.

The tools

Every tool published under Build with Baker is built to keep your data with you. Here is how each one handles it:

UniStyle

UniStyle (the web app at unistyle.io and the Chrome extension) converts the text you type into Unicode styles entirely inside your browser. Your text is not sent to any Build with Baker server. The Chrome extension requests only the permissions it needs to operate and does not collect browsing history or personal data.

Your favorite styles and your recent conversions are kept in your browser's local storage so they are still there next time. They stay on your device.

Wren

Wren is a local-first notes app. It ships in three forms - an installable web app, a Chrome extension, and a Windows desktop app - and all three behave the same way. Your notes are saved as plain Markdown files in a folder you pick on your own device. They stay on your disk, not on my servers, and I never receive or store them.

Two things worth knowing about that folder. Wren also writes a small index alongside your notes (.wren-index.json, _index.md and README-for-AI.md) so the folder is readable by other tools; those are yours and stay local like everything else. And if you install the optional Wren MCP server, an AI assistant running on your own machine can read and write notes in that folder. That is a local connection between two programs on your computer, not a service I run.

Cloud sync is optional and off unless you turn it on. It works through the Google Drive API: you sign in to your own Google account, Wren is granted access only to the files it creates, and your notes go to a folder in your Drive. Signing in means your browser talks to Google's servers. Your notes still never touch mine.

Pinion.md

Pinion.md reads and writes Markdown files directly on your device through the File System Access API. Files open and save locally; nothing is uploaded to a server. There is no account and no data collection. It does load its typefaces from Google Fonts, so your browser makes a request to Google's font servers when the page opens.

Home Affordability Calculator

The calculator runs entirely in your browser. The numbers you enter are never transmitted anywhere - there is no server call at any point.

They are, however, remembered on your own device. The calculator saves your income, target price, down-payment percent and interest rate to your browser's local storage so the page is already filled in when you come back. That data never leaves your machine and I have no way to see it. Clearing your browser's site data for buildwithbaker.io removes it, and the calculator has a reset control that clears it too.

The AI Receipt

The AI Receipt estimates what an AI task would cost. Everything is computed in your browser from a price table shipped with the page - your task description, the slider values, and the receipt you download are never sent anywhere. It makes no network requests at all once the page has loaded.

Baker's Recipe List

Baker's Recipe List has no login and no account. It does make one kind of outbound request: when it shows nutrition estimates for a recipe, it looks the ingredients up against USDA FoodData Central, a US Department of Agriculture database. The ingredient terms for the recipe you are viewing are sent to that API. Nothing about you is - no account, no identifier, no history.

Recipes you pin, your shopping list, and your cook log are saved in your browser's local storage on your own device. They are not sent to me.

Northwoods Area Events

The events tracker is a single static page. The event list is baked into the page itself, so nothing you do on it is transmitted - no searching, no filtering, no clicks. Your chosen view and light or dark preference are saved in your browser's local storage. The page loads its typeface from Google Fonts, which means your browser makes a request to Google's font servers when it opens.

Links to other sites

Some pages link out to third parties - Ko-fi for tips, GitHub for source code, X for posts, and the Chrome Web Store for extensions. Once you follow one of those links, that service's own privacy policy applies. I don't control and am not responsible for how those sites handle your data.

Children's privacy

These tools are general-purpose utilities and are not directed at children under 13, and I do not knowingly collect personal information from them.

Changes to this policy

If I add anything that changes what is collected - for example, traffic analytics or an email newsletter - I'll update this page and change the "last updated" date above before it goes live.

Questions

Anything here unclear, or want your contact-form message deleted? Email adam@buildwithbaker.io and I'll take care of it.