Publication Policy

ProjectRadar helps readers discover useful projects without making discovery pay-to-play. Coverage focuses on usefulness, clarity, audience fit, trust cues, public context, and discoverability.

A good Project Note helps a reader decide whether a project is worth exploring. It also gives a builder a fair, limited view of what stands out and what could be clearer.

Project Notes may use submitted information, developer-provided descriptions, public product pages, app listings, documentation, screenshots, demos, access, and the public context a reader can reasonably see before trying the project.

A Project Note looks at what the project says it does, who it appears to serve, how clearly it explains itself, what feels useful, and what a curious reader might check next. Notes should help readers and treat builders fairly.

ProjectRadar does not invent claims to make a project sound bigger, safer, more popular, or more successful than the available evidence supports.

• Founder details
• Revenue
• Traffic
• Customer counts
• Testimonials
• Awards
• Leaderboard claims
• Performance claims
• Partnerships
• Security claims
• Search visibility claims

Anyone may submit a project. A submission helps us discover what builders are launching, but it does not guarantee coverage, publication, placement, backlink access, search visibility, traffic, customers, or positive coverage.

Projects may be listed, covered, queued, declined, or revisited later. Fit and reader value guide each decision.

• Guaranteed writeup
• Guaranteed publication
• Guaranteed placement
• Guaranteed backlinks
• Search visibility outcomes
• Guaranteed traffic
• Guaranteed customers
• Guaranteed positive coverage

Developers may provide temporary project access for paid products, apps, private betas, games, invite-only tools, SaaS products, downloadable programs, or utilities that cannot be fully evaluated from a public page.

ProjectRadar uses access only for Project Note evaluation. It does not publish private access details, promo codes, invite links, demo credentials, or test build links.

ProjectRadar's Discovery Context labels describe how clearly a project explains itself. We may consider clarity, usefulness, audience fit, product readiness, trust cues, design and UX, discoverability, and information about the founder or project.

Each label summarizes the public information available when the note was written. It is not a promise about what will happen after publication, a user rating, certification, expert audit, guarantee, safety claim, quality claim, or paid placement.

• Not a user rating
• Not a certification
• Not a guarantee
• Not paid placement
• Not a partnership endorsement
• Not a search performance claim

ProjectRadar editorial notes are not for sale. Sponsored placement buys visibility only. It does not change Project Notes, conclusions, category eligibility, or editorial picks.

• Discovery context labels
• Category position
• Hidden promotion
• Favorable coverage
• Search placement
• Undisclosed sponsored links

ProjectRadar will label sponsored links and paid visibility. Where applicable, sponsored links should use appropriate attributes, such as rel="sponsored" or rel="nofollow".

Founders and readers can request factual corrections. A helpful correction request includes the project name, project note URL, and the specific issue to check.

ProjectRadar may update Project Notes when products materially change, add important functionality, fix previously noted issues, or become meaningfully clearer for readers.

Corrections do not automatically change opinions, context labels, or conclusions. The underlying facts must support that change.