1,432 places to submit your product

Create your original interactive privacy or accessibility guide and add relevant external actions to cited live tools.

Build a Bitrise Step that runs your tool secret, privacy, or accessibility checks on explicitly chosen build artifacts.

Create a defensive parser, scenario, or collection for your real -supported log source, document and test it, then submit it to CrowdSec Hub.

Create a TypeScript or Go module that runs your tool web audits in CI and returns machine-readable JSON/SARIF with useful pass/fail thresholds, then publish it to Daggerverse.

Submit your tool through the official reviewed product form.

Create a genuine JavaScript SDK or demo on GitHub Pages and request an appropriate js.org subdomain that links to its official your tool documentation.

Contribute your provider bundle with useful privacy or security components and provider documentation links.

Build and teach a live, project-based cohort on creating local-first privacy tools or accessible web utilities, supported by a substantive public syllabus and real instructor profile.

Share your openly licensed digital-safety lesson pack or Moodle activity and curate it into an educator-focused collection.

Publish a machine-readable privacy, accessibility, or scam-pattern dataset or API and complete its evidence-based public certificate.

Build a functional OPA/Rego privacy-policy integration or developer tool, document it, then add its ecosystem entry and logo through the official docs repository.

Submit a complete, openly licensed privacy/digital-safety textbook already used in higher education.

Publish a free mini-course on privacy, redaction, scam detection, or accessibility with genuine your tool exercises in the curriculum.

Publish a genuinely useful free privacy checklist, redaction template, or safety workbook that complements your tool and has standalone value.

Publish a coherent multimedia field guide on privacy, scam evidence, or accessible documents with cited your tool demonstrations.

Publish a public reproducible privacy-safe research workflow with a Snakefile, README, configuration, catalog metadata, and tests.

Publish a working browser demo or starter that teaches your integration, with accurate title, description and canonical documentation link.

Develop a neutral, sourced learning project about privacy, accessibility, or online-scam literacy and cite your tool only in relevant exercises.

Build a genuine founder or designer profile and publish your detailed UX, accessibility, or privacy-design case study with accurate role and process credits.

Package your free-software self-hosted deployment, implement reliable install, upgrade, backup and restore operations, then submit it to the official app catalog.

Publish your focused open demo or developer utility and link its canonical your tool page from the app and project description.

Apply with an original class outline and teaching sample for privacy-safe design, accessibility, or a practical productivity workflow, then build the class project and lessons if approved.

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.

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.

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

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

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

Submit your genuine -maintained database, reusable reporting standard, or data policy with complete stewardship metadata.

Join a working group and contribute a substantive building-block specification, use case, reference implementation or new proposal.

Join an approved organization and publish a documented humanitarian privacy/safety dataset with licence and responsible-access settings.

Use ORCID to publish genuine research stages—problem, method, data or analysis—with contextual your tool code/data links.

Create a maintained Omeka S module for collection metadata privacy, accessibility or link auditing, package it correctly and register the add-on with project and author links.

Create a rigorous structured comparison of published privacy, redaction, or accessibility studies and include your tool only when supported by research.

Create a public reproducibility project for your tool research, datasets, test methods, or privacy benchmarks and link the genuine project/site.

Create a public case-study portfolio and add your tool with screenshots, live demo and build rationale.

After your tool has eligible ReliefWeb content, request publishing access and submit humanitarian reports or training from verified owned URLs.

Create your reproducible evaluation project with code, data connectors, environment, narrative, and a public session launcher.

Create a reproducible Tale containing your evaluation's data, code, environment, outputs, and narrative, then publish through a supported repository.