Community
PrivacyFlow is open source — contribute, file issues, and follow the roadmap on GitHub at github.com/privacyflow-app.
PrivacyFlow is open source. The API server, the MCP server, the Agent Zero channel, and the n8n nodes are all public. Contribute, report issues, or follow the roadmap via GitHub.
Repositories
The org is at github.com/privacyflow-app. The key repos:
| Repo | Language | What it is |
|---|---|---|
privacyflow-public-backend-api | TypeScript (Deno) | The four-endpoint public API. |
privacyflow-mcp-server | TypeScript (Node) | MCP server for Claude Desktop, Cursor, OpenCode. |
privacyflow-agent-zero-channel | Python | Agent Zero plugin for bi-directional agent chat. |
n8n-nodes-privacyflow | TypeScript | n8n community node (Send + Poll Trigger). |
privacyflow-dashboard | TypeScript (Astro) | The dashboard BFF proxy. |
privacyflow-landingpage | TypeScript (Astro) | This site, including these docs. |
File a bug or request a feature
Open an issue on the relevant repo. For docs issues (typo, missing example, broken link), the landingpage repo has an Edit on GitHub link at the bottom of every page — it drops you directly into the Markdown source on the feat-comprehensive-docs branch (and on main once merged).
For API or client bugs, include:
- The endpoint or tool you called.
- The exact request (redact your API key — never paste it).
- The response status and body.
- What you expected vs. what happened.
Contribute
Pull requests are welcome. Branch naming follows the repo’s AGENTS.md (most use feat-*, fix-*, chore-*). The CI for each repo runs lint + test + build before merge.
For docs contributions specifically, every Markdown file lives in src/content/docs/<category>/<slug>.md. Frontmatter is required — see an existing file for the schema. The preview build (npm run dev) hot-reloads on save. Add the file to the sidebar by setting a unique order within its category; the sidebar sorts automatically.
Agent Zero community index
The Agent Zero channel is also published in the a0-plugins community index. The plugin uses the plugin.yaml manifest format A0 expects, and the repo’s index.yaml carries the a0-plugins metadata. If you fork the channel, keep the GitHub mirror in sync with the canonical source — the a0-plugins validator requires a GitHub-hosted repo with plugin.yaml at root.
Stay current
- Watch the repos you depend on for release notes.
- The
/llms.txtand/docs/llms-full.txtfiles at the site root are regenerated on every build — agents and humans can fetch those for a current table of contents without scraping. - For breaking changes, the API version (returned by
/api/v1/health) bumps; URL prefixes stay at/api/v1.