004. Contribute
Help write
what comes next.
You do not need to work in privacy to help shape this. First-time builders and business owners know which parts need to be clearer.
We're at the foundation stage. You can start by reading the draft, testing an assumption, or adapting this website's source.
01 / Start with the source
Take it apart. Make it better.
This website is built with Astro and TypeScript. It ships static pages, locally hosted Courier Prime, and a small local script for filtering the law library. The reading pages need no client-side JavaScript.
The website source and content are available under the Apache License 2.0. Font assets use their own included open font license.
Explore the public GitHub repository ↗
The website source is available under Apache-2.0. The privacy engine and MCP service remain planned work.
02 / Where help matters
Bring your perspective.
- First-time builders and business owners.
- Describe a real integration. Show where consent or preference handling becomes difficult in your application.
- Privacy practitioners.
- Review definitions, distinguish choices from legal bases, and identify cases the proposed contract needs to handle.
- Security engineers.
- Challenge tenant isolation, authentication boundaries, receipt handling, and access to decision evidence.
- Maintainers and technical writers.
- Improve examples, accessibility, setup instructions, and the clarity of the first specification.
03 / A useful proposal
Start with one concrete problem.
- Describe the application and the person whose data is involved.
- State the choice or permission that needs to be respected.
- Explain the expected behavior, including a change or withdrawal.
- Suggest an example or test that would prove it works.
Keep examples synthetic. Share the behavior we need to support without sharing anyone's personal data.
Bring your question or proposal to the public repository. You can open an issue without contributing code.