What this policy covers
This Privacy Policy describes how the current site and AI Product Tools implementation handle information when you browse the site, use the tools, or use AI Handoff exports.
It is based on the behavior visible in this codebase. It does not describe data practices that are not implemented here.
Current site behavior
The current site code does not implement user accounts, logins, paid subscriptions, contact-form submissions, advertising trackers, or a first-party analytics platform.
Most tool interactions happen in your browser. Some tools save state in browser storage so your work persists between visits. Certain AI Handoff formats send tool state to a public same-site endpoint so formatted exports can be returned.
Browser storage and on-device tool state
Several tools use local browser storage (`localStorage`) and session storage (`sessionStorage`) to preserve your progress, settings, stack selections, dismissed insights, or calculator inputs on your device.
Examples in the current implementation include saved measurement stacks, wizard answers, calculator assumptions, accessibility and debt settings, UX methods state, process-builder state, and similar tool-specific working data.
- Local storage generally remains in your browser until you clear it, reset a tool, or remove it manually.
- Session storage is shorter lived and may clear when your browser tab or session ends.
- This browser storage is not the same as a server-side user account database.
AI Handoff, prompts, and tool payloads
Some AI Handoff views are generated entirely in the browser. In the current implementation, Markdown and MCP export formats send the current tool payload to `/api/ai-handoff/:tool/:format` so the site can return a formatted response.
The current AI Handoff worker code is public, unauthenticated, and does not write requests to an application database. The payload is processed to return the requested output format.
If you use AI Handoff, do not include confidential, regulated, or personal data unless you are comfortable sending it through that endpoint as part of your own use of the site.
Forms, uploads, and email links
The current site does not provide a hosted contact form for you to submit information directly through the site.
Current tools do not ask you to upload files, documents, or images to the site.
If you click an email link such as me@mathew-lincoln.com, your message is handled by your own email application or provider, not by a site form handler.
Third-party services and infrastructure
The site loads some third-party assets in the current implementation, including Google Fonts and stylesheet or library resources served through public CDNs such as cdnjs and jsDelivr. Those providers may receive ordinary request information such as IP address, browser metadata, and the fact that your browser requested the asset.
The site may also rely on hosting, edge, or CDN infrastructure to deliver pages and the AI Handoff endpoint. Ordinary operational or request logs may be created by that infrastructure even where the site code itself does not create a user database.
Cookies and analytics
The current site code does not implement first-party analytics, advertising pixels, or marketing-cookie logic.
The tools do use browser storage, as described above. Third-party asset providers or hosting infrastructure may use their own technical cookies or logging mechanisms under their own policies.
How information is used and whether it is shared
Information processed by the site is used to render pages, preserve local tool state in your browser, and return requested AI Handoff outputs.
The site does not sell personal information. The current implementation shares data only with technical providers needed to deliver the site, serve third-party assets, or process the AI Handoff request path you choose to use.
Retention
Browser storage remains on your device until you clear it, reset the relevant tool, or your browser removes it.
The current AI Handoff worker code does not implement application-level persistent storage. Ordinary infrastructure or request logs may still exist under the retention settings of the deployment or provider environment.
Because there are no user accounts in the current implementation, the site does not maintain a long-term user profile database through the application layer.
Your choices
- You can clear browser storage through your browser settings or by using reset controls provided in individual tools.
- You can avoid sending tool payloads to the AI Handoff endpoint by not using those export formats.
- You can avoid email disclosure through the site by not using mailto links.
Contact and updates
For privacy questions, contact me@mathew-lincoln.com.
This policy may be updated as the tools and site evolve. Material changes should be reflected by updating the date on this page.