Policy
Not legal terms — those live on the Terms & Privacy page, and our broader mission and principles live on About. This page gets specific about a few commitments that matter most in practice.
On this page
Open source licensing
Every project we publish carries an explicit open source license (typically MIT) from its first commit. We don't run a "source available, but not really open" model, and we don't plan to relicense a project to close it off after people have started depending on it. If a project's license ever needs to change, we'll explain why, publicly, before it happens. This site's own code follows the same rule — see its LICENSE.
Use of AI in our work
We use AI tools, including for parts of this website, as part of how we build — the same way we use any other development tool. Where it matters for trust or safety, we say so plainly rather than let it go unstated. A few specifics:
- Code generated with AI assistance goes through the same review as any other code before it ships in a project.
- We don't use AI to generate fake testimonials, fabricated user numbers, or misleading claims about adoption — content on this site describing traction or usage is accurate as of when it was written, or clearly marked as aspirational.
- We don't train AI models on data submitted through our projects (contact forms, issue reports, etc.) without saying so explicitly first.
Accessibility
We aim for our own site and projects to meet WCAG 2.1 AA as a baseline — keyboard navigable, screen-reader friendly, sufficient color contrast, visible focus states. We won't always get this perfectly right on the first try, especially on newer, less-tested projects, but we treat accessibility bugs as real bugs, not optional polish, and we welcome reports when we miss something.
Data minimalism
We collect the minimum data we need to do what we say we're doing, and we default to not collecting things we don't have an immediate use for. See the Privacy Policy for the specifics of what that means on this site today.
How this page changes
As Link with iQ grows past being mostly one person, these positions may need more structure behind them (an actual accessibility audit process, a formal AI-use policy document, etc.). We'll update this page as that happens rather than let it drift out of date.
Tell us where we're falling short
If something we build doesn't live up to a position on this page, we want to know about it.