1,432 places to submit your product

Submit one released evaluator such as WCAG Quick Auditor with accurate standards, scope, license, release date, and accessibility-statement details.

Submit only your tool tools with a clear civic or public-interest use case, using the official project name, URL, one-sentence description, accurate category, and contact email.

Sponsor your frontend, accessibility, CSS, or developer utility with a useful demo and audience-specific copy.

Publish a documented synthetic privacy, redaction, accessibility, or scam-detection benchmark dataset.

Promote a privacy-respecting or thoughtfully designed your tool utility through a classified or main sponsor slot.

Submit your tool strongest AI-powered utilities with a polished listing.

Build a Freshdesk or Freshservice app that deliberately sends selected ticket text to your PII or scam check and returns a transparent report.

Publish an Inkscape extension for SVG metadata cleanup, privacy inspection, or accessible-export checks.

Build a Mendix connector or module that invokes your tool on user-selected records or files and displays structured reports.

After becoming a genuine member, submit your tool as a completed web project with a plain factual description in MetaFilter Projects only.

Build an OBS privacy guard that detects exposed secrets or sensitive screen regions before streaming.

Build an ONLYOFFICE plugin for document redaction, metadata cleanup, or secret scanning.

Build a Sentry integration that detects PII or credentials before issue data is exported or shared.

Create a substantive privacy, security, or accessibility lesson using your tool exercises and propose it through the Incubator.

Create a Zendesk app or marketing-only integration for selected-ticket PII and scam checks with your tool support and pricing links.

Build a Zoho extension for document privacy, text cleanup, or data-export checks and submit its support, policy, guide, and website links.

Build and document a real Adalo component library for your workflow and apply for marketplace publication.

Offer your tool as a documented SaaS or BYOL deployment for Alibaba Cloud customers with clear privacy controls and support.

Sponsor your tool’s strongest browser or JavaScript-based developer utility with copy tailored to working JS developers.

Run a clearly disclosed campaign for your tool’s developer and security tools across relevant Changelog podcasts or newsletters.

Use a real writer or designer identity, add authored your tool work as a properly credited clip or case study, and include the personal website link in the profile.

Publish a reusable Defold privacy-safe logging, security, or build-audit tool.

After your tool has a genuinely open-source, well-documented public-interest component, complete the eligibility assessment and nominate that specific component.

Build a genuine FIWARE-powered privacy, consent, data-space, or civic-safety solution, document its architecture and data models, then submit it for expert validation.

Create a GDevelop extension for safe local storage, consent UX, or secret-free analytics configuration.

Build your public OAuth integration, gain qualifying installs, then submit setup docs plus support, privacy, and terms URLs.

Open-source your reusable research-focused component, archive it with a persistent identifier, and submit a software metapaper with project/code links.

Obtain senior approval, submit the signed endorsement materials, implement the Principles and share a real case study.

Build a genuine Salesforce package or API solution for selected-record privacy or document checks and complete its company and listing profile.

Submit a mature macOS, iOS, or web companion app that provides your privacy workflow and links to its official product documentation.

Build a Shopware admin extension for privacy and accessibility checks on selected catalog content, media, and exports.

Build a SketchUp extension for model metadata sanitization or accessibility-ready export checks.

Build a Stripe app that sends selected non-sensitive invoice or export data to your clearly scoped audit and publish complete documentation.

Place your targeted campaign in TLDR Dev, InfoSec, AI, Tech, Product, or Founders with a focused landing page.

Build your VTEX IO storefront or admin privacy utility, define billing, and submit it for homologation.

Publish a secure one-click self-hosted your tool image or cloud-init deployment with documentation and support.

Apply only with a meaningful open agent-security or MCP-governance contribution and an ongoing participation plan.

Apply only after operating a real civil-society digital-security help desk and meeting network operations and vetting requirements.

Apply only after your tool operates a genuine OA scholarly-book publishing program, then submit peer-reviewed privacy-tech books.

Join only when your tool will fund and actively contribute to open-source AI or data work.