1,432 places to submit your product

Publish useful browser extension linking your tool.

Package your commercetools Connector and request certification and public Marketplace listing.

After publishing a mature security policy and VDP, contact the Secretariat to apply as a signatory to all four principles.

Submit a working AI feature with accurate categorization, pricing, description, and screenshots for quality review.

Apply as an eligible Member or Partner and contribute resources or expertise to real cyber-capacity-building working groups.

Build a Homey app only if your tool adds a genuine IoT privacy or local-device workflow; package, test, validate, and submit it for certification.

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

Publish a Max package for media metadata inspection, audio privacy, or accessibility analysis.

Create a founder blog that shares compact product lessons and full tutorials linking to your relevant page when useful.

Build a working Miro app for board accessibility, privacy, or export auditing; establish real users and demand before applying through the partner route.

Host your maintained open-source component with complete README, homepage/source metadata, releases and optional pages.sr.ht docs.

Submit only your specific AI tool with the official site and contact email, not the platform as a generic tools directory.

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

Submit your qualified AI utility with authorized branding, logo, category, pricing model and fully accurate product information.

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

Build your useful iOS or macOS app and submit complete support, privacy, accessibility and marketing metadata through App Store Connect.

Build an OAuth app that audits merchant exports or product assets for privacy issues, then submit tested listing assets through the Developer Portal.

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.

Build a production Contentful app for your tool privacy or content checks and apply through the Marketplace submission flow.

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.

Submit your tool best landing or tools page with a strong screenshot, accurate categories, and creator details.

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.

Create a portfolio for genuine your tool product/design work and use each project's external URL field for the matching live page.

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 founder or product-design portfolio with your original case study and add the canonical site as an external menu link.

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.

Create a legitimate free or paid your tool resource or software product and publish it on a branded hosted storefront.

Apply only with a validated open-source privacy or anti-surveillance project that directly helps users facing repressive censorship or surveillance.

Apply as a General Member only if your tool will meaningfully contribute engineering or resources to open-source security.

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

Submit the production PWA URL only after its manifest, service worker, installability, icons, and offline flow pass validation.

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

Publish your genuine Android app with accurate support/privacy URLs, data-safety declarations, assets and compatible binary.

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.