1,432 places to submit your product

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.

Launch your properly scoped vulnerability disclosure or public bug-bounty program.

Launch your defensive vulnerability disclosure or public bug-bounty program with managed researcher access.

Publish a Canadian-ready, openly licensed privacy or digital-citizenship textbook and use Contribute → Suggest a Textbook.

Publish a polished original guide, research brief, or accessibility zine as a public document, with useful references and your relevant link inside the editorial content.

Pitch an original evidence-backed privacy, scam, or cyber advisory based on genuine your tool research.

Publish a mature open-source interoperability or public-administration solution with documentation, releases, licence, and owner metadata.

Build your free mobile mini-site with brand story, key collections, demos and contact links.

Submit an educational, non-sales session on privacy-safe tooling or accessible creator workflows when the next CFP opens.

Claim a builder profile and add your tool as a shipped project using its live public URL.

Document your real implementation of a named RDA recommendation with challenge, measurable outcome, lessons, and supporting resources.

Pitch original your tool security research, a defensible dataset or timely threat analysis.

Create a public privacy-tool research library with credible standards, papers, and references, including only genuinely relevant your tool documentation.

Package your deployable self-hosted architecture for IBM Cloud, complete Partner Center onboarding, and request public catalog approval.

Package your supported self-hosted edition or integration for RHEL or OpenShift and complete Red Hat Partner Validation for a catalog page.

Start privately, mature the process, then publish your program indexed in Intigriti's public directory.

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

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

Apply only after your tool becomes a legally registered nonprofit with software central to scalable public impact.

Publish an original benchmark or evaluation study of local-first privacy or security tooling with open code, data, and your tool implementation.

Organize the complete code, data, materials, and outputs behind your real evaluation study into a public citable box.

Publish your substantive privacy template, workbook, or creator resource with a complete description, original previews, and accurate licensing.

Author a freely licensed hands-on module for safe document sharing or privacy-first web use with relevant your tool examples.

Build a genuine Solid privacy utility that lets users choose identity providers and stores or retrieves their data from Solid Pods, then confirm the current listing handoff with maintainers.

If your component is built with or for a public body, publish a standards self-assessment and pursue stewardship/assessment.