Trust Center
A Project Note is only useful when people can trust it.
ProjectRadar helps readers find useful projects and gives builders a fair look. That works only when coverage is honest, independent, and clear about its limits.
Publication rules
No paid editorial favors
Corrections welcomed
Why trust matters
The web has plenty of lists. Trust is the hard part.
Readers need to know what a project does, and builders deserve a fair description of their work. A useful Project Note explains the details without turning a product pitch into a promise.
Paid visibility stays separate from editorial choices, and factual corrections are free. Those are commitments readers and builders can hold us to.
Independence
How ProjectRadar stays independent
A submission is an invitation to consider a project, not a purchase order for coverage. Founders can share context, links, and access details, but publication judgment stays with ProjectRadar.
- Submitting a project does not buy coverage.
- Money does not influence project notes, optional discovery context, category eligibility, or conclusions.
- Founders cannot purchase a stronger context label or category position.
- Coverage decisions stay independent, even when a founder provides temporary access.
- Project Notes are checked against the submission and the project's public pages for factual support and clear language before publication.
Standards in practice
Facts that readers can check
Project Notes use the information a builder shares and the project's public pages. We check that factual claims have support, make important limits clear, and welcome corrections when something changes.
How Discovery Context works
Discovery Context may consider public details such as clarity, usefulness, audience fit, readiness, trust cues, design, discoverability, and project status. It does not promise traffic, search visibility, revenue, safety, quality, or success.
Submitted links may be screened
URLs may be checked for malware, phishing, spam, private-network targets, or abuse. A clean scan is not a guarantee that a site is safe.
Private details stay private
ProjectRadar uses submission notes, emails, access instructions, and private queue records for intake. They should not be copied into public notes.
Ads and labeled sponsored placements help support ProjectRadar. Paid visibility stays separate from Project Notes and Editor's Picks. Paid links use qualifiers such as rel="sponsored" or rel="nofollow" where appropriate.
What We Believe
The principles behind the notes
Readers first
A Project Note should help someone decide whether a project may be useful to them. It should not simply repeat a founder's pitch.
Builders deserve fairness
Launching is hard. We try to describe projects honestly, with enough context for readers and respect for the people building.
Useful products deserve visibility
ProjectRadar pays attention to smaller tools, apps, websites, games, and utilities that might otherwise be missed.
Transparency beats hype
We would rather explain what we know, what we checked, and what still needs a closer look than pretend every answer is certain.
Corrections should be easy
If a factual detail is wrong or outdated, founders should have a clear path to ask for a correction.
Honest context is valuable
A fair Project Note can say what stands out and point to practical next questions without becoming a takedown.
Corrections
How we handle corrections
Mistakes can happen. Products change, pages move, pricing shifts, and early launches evolve quickly. Pretending otherwise would not make ProjectRadar more trustworthy.
Founders can contact ProjectRadar when a published project note includes outdated or inaccurate factual information. Factual errors should be corrected. Products that materially change can be revisited. Independent takes may remain unchanged, but accuracy matters.
Correction path
Tell us what is wrong
Share the best source or context
We check the factual issue
We update the page when a correction is warranted
What We Do Not Do
Clear boundaries make the site easier to trust
- Sell category position
- Sell discovery context labels
- Guarantee backlinks
- Guarantee traffic
- Guarantee publication
- Accept payment for favorable notes
- Create fake founder stories
- Publish fabricated notes
Project notes may include links when those links help readers evaluate a project. That does not mean ProjectRadar guarantees backlinks, search visibility, referral traffic, customers, publication, or a favorable note.
Builders And Readers
A place for builders and curious readers
Builders can share apps, websites, tools, and other independent projects for consideration. Some projects are polished. Some are early. Some help with one small, specific job.
Launching anything online takes effort. ProjectRadar respects that effort, but the note still has to serve readers first. Honest coverage helps both sides: readers get clearer discovery, and builders get a more useful context than empty praise.
Start here
Want to see the standards in action?
Submit a project for a fair look, read the notes already live, or walk through the project note process before you send anything in.