1,432 places to submit your product

Publish your privacy-checking notebook, synthetic benchmark, AI model, app, or defensive MCP server.

Create a reusable UiPath automation that invokes your documented workflow such as a local file privacy check and publish it under a verified profile.

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 test a Slicer extension for medical-image de-identification, metadata inspection or privacy validation, then add its .s4ext metadata to ExtensionIndex by pull request.

Apply only if the founder or team member has real design/engineering leadership experience and intends to provide genuine mentoring, then add an accurate personal website/profile reference.

Package your stable CLI or self-hosted helper as a tested APKBUILD, add it under Alpine testing and submit an aports merge request with accurate project metadata.

Register as your tool vendor and add its software/service profile.

Publish an original UI/UX visual case study showing your tool interaction design, accessibility states, and design process, with a contextual project URL.

Build a deployable edge privacy utility or reusable block, add balena.yml metadata, public source, configuration and multi-device tests, then publish it on balenaHub.

Package your maintained self-hosted deployment as a Juju charm with canonical documentation, source, and support links.

Build a maintained Cinnamon applet that launches or monitors your useful local privacy workflow and submit it by pull request.

Create an age-appropriate digital-citizenship or privacy FlexBook chapter with practical your tool exercises.

Answer real end-user software or privacy questions in depth and reference your specific page only when it materially completes the answer.

Create and fully test your Docker Compose service template, add metadata, logo, and documentation, then submit it to Coolify's next branch.

Apply as a designer and publish an original template, icon pack or printable that genuinely complements your workflow.

Apply with a strong portfolio and sell your original -compatible template or design kit, using permitted shop branding and product documentation.

Build a useful dbt package for privacy classification, redaction tests or data-governance macros and add it to the Hub index by pull request.

Participate as a real developer with original lessons and honest build stories; reference your tool only if a specific discussion genuinely calls for the working example.

Sign in with GitHub or Google and add your tool as a real portfolio project with tech stack.

Build a generic DHIS2 health-data de-identification or permission-audit app and submit it to App Hub for core-team review.

Use a real developer profile and contribute tested solutions on Discourse integrations, accessibility, or privacy only when the team has genuine implementation experience.

Build your Ecwid app, propose it, sign the partner agreement, and submit it for review with website and support links.

Create a structured open handbook on digital privacy or accessibility with reproducible your tool labs.

Register a substantive life-science privacy, medical-data de-identification, or research-data training resource hosted by your tool.

Create a genuinely useful package of tested security-header, HTML-meta, JSON-LD and webhook snippets with your tool validation examples, then submit it to the official Hub.

Discuss your substantive -backed research-software quality task or resource with the Editorial Board, then contribute through its approved workflow.