1,432 places to submit your product

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

Submit your valid public podcast feed and keep website and episode-link metadata accurate.

Make your real public repository REUSE-compliant, register its Git URL, and link the resulting compliance page from project docs.

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.

Host or claim your genuine show, verify the RSS email, and publish accurate episode notes with relevant HTTPS resources.

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

Publish your real OpenAPI definition publicly with an accurate description and external documentation URL.

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.

Run AI Verify on your real AI use case, then submit accurate results, version, experience, lessons and company logo.

Pitch a practical, outcome-based tutorial on client-side privacy, accessible UI, or web safety using original examples and an honest author identity.

Submit a formal publication, case study, educational resource or on-demand training linking digital resilience to disaster-risk reduction.

Publish a genuine browser or desktop your tool utility with screenshots, documentation and an official-site link.

Document a real participatory public-decision deployment as a Case, Method or Organization entry with evaluations and project URL.

Build a ProcessWire admin module for external URL, metadata, accessibility or security audits, register as a module author and submit it to the official directory.

List your legitimate documented API in the relevant developer category using the normal or Pro review queue.

Register a stable, genuinely research-used your tool software, service, or database with accurate maintainer and version metadata.

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.

After releasing your real CLI or native app, submit a tested formula or cask with its canonical homepage.

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

After your tool has a stable, commonly used JSON or YAML configuration format, contribute its accurate schema and test fixtures so editors can provide validation, completion, and tooltips.

Apply with your concrete privacy, security or user-autonomy FOSS work package, milestones, budget and public repository.

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.

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