Site policies

• No paid placement. Nobody can buy a listing, a ranking or an editor's pick, and the directory carries no affiliate links.
• Every dossier states what a tool is for, who it suits and — in the warning field — the trap people hit with it.
• Claims are grounded in the vendor's own documentation or in first-hand builder experience, and we link out so you can check.
• Pricing and limits are summarised for orientation only. The vendor's page is always the source of truth.

Anyone with a confirmed account can submit a tool. Each submission is screened automatically before a human sees it:

• Duplicate detection against every entry already in the directory, by domain and by name.
• A reachability and domain check on the URL you provide.
• An automated usefulness grade against our editorial standards.

Clear, verifiable entries can publish immediately; everything else waits for a moderator. Submissions that are spam, dead, thinly disguised marketing or a duplicate are rejected. Being rejected is not a judgement of you — resubmit with better evidence and it will be reconsidered.

Kbaise runs an automated editorial pipeline. It watches vendor pages and model documentation for changes, drafts corrections and summaries, and keeps guides in step with upstream docs. We say this plainly rather than hiding it:

• Automated drafts are checked against the source page before publishing, and high-risk changes are held for a human moderator.
• Freshness stamps on tool dossiers and guides show when a link was last checked and when the content was last verified.
• Community notes are written by people, never generated.
• If you find something wrong, report it and we will correct or retract it.

Contribute the way you would want a stranger to contribute for you.

• Write from experience and say what actually happened, including what went wrong.
• Disclose any commercial connection to a tool you are recommending.
• No harassment, hate speech, personal attacks or outing of private information.
• No vote manipulation, sockpuppet accounts or coordinated promotion.
• No malware, phishing links or content that is unlawful where we operate.

Breaches lead to content removal, and repeated or serious breaches to account suspension.

Moderators review reported content, the submission queue and flagged automated drafts. If something of yours is removed and you think that was wrong, reply through the in-page report tool or email legal@kbaise.com with a link and a short explanation. We aim to answer appeals within a few working days.

Kbaise uses browser storage for exactly two things: an authentication cookie that keeps you signed in, and local preferences such as your comparison tray and dismissed prompts. Both are strictly necessary or purely functional.

There are no advertising cookies and no cross-site tracking, which is why you see no consent wall. Details of everything we store are in the privacy notice.

We describe third-party products and quote short excerpts from public documentation for identification and commentary, always with a link back to the source. If you own material that appears here and want it removed, email legal@kbaise.com with:

• The exact URL on kbaise.com and the material in question.
• The original work and proof you hold the rights, or authority to act for the owner.
• Your contact details and a statement that the use is not authorised.

We remove or amend valid claims promptly and tell the contributor why. Vendors can also ask us to correct or delist their own entry.

If you find a vulnerability, report it privately to security@kbaise.com before disclosing it anywhere else. Include the steps to reproduce it and what you were able to reach.

• Test only against your own account and data.
• No denial-of-service, spam, social engineering or physical attacks.
• Do not access, modify or retain other people's data — stop as soon as you have proof.

We will acknowledge good-faith reports, keep you updated while we fix the issue, and credit you if you would like that. There is no paid bounty programme.

Anything on this site can be wrong. Signed-in builders can right-click any page to file a correction with the exact element attached, or use the feedback queue. Corrections that change a factual claim update the entry's verification date so readers can see it was rechecked.