How this site is sourced and checked

Every claim on the main Chub AI page should trace back to one of the categories below. If it cannot, it does not get published.

Sources, heaviest to lightest

1. Direct observation of the public product. A free account plus the public site, used to confirm the sign-in flow, character search, the Lorebook and creation tools, and how the NSFW toggle presents. What sits behind a paid tier is reported from documented sources, not dressed up as first-hand paid access.
2. Primary materials. chub.ai and venus.chub.ai, docs.chub.ai, the CharHubAI repositories, status.chub.ai, and the app-store record for the removed Google Play and iOS builds.
3. Independent research and reporting. Independent write-ups, outage post-mortems, and pricing breakdowns from third parties, each named inline where it carries a claim.
4. Community signal. The r/Chub_AI subreddit and the official Discord, used for outage timing and user-side workarounds, treated as reports rather than fact.
5. Aggregated coverage. Read only to cross-check dates and prices, never the sole basis for anything.

Verified versus cited

Fast-moving details (tier prices, model line-ups, NSFW handling, app availability, whether the site is up) are checked against the live public product before publishing. Long-run claims that need data no single writer can produce are attributed to their source and named as such. The line between the two is deliberate.

What happens when sources disagree

Conflicts are not smoothed over, they are printed. The clearest example is the app: some community sources point to a self-distributed Android APK on charhub.io, while other 2026 reviews say there is no maintained mobile app at all. Rather than pick the tidier answer, the main page names the disagreement and tells you to treat mobile as unreliable. That is the house rule for every contested fact.

Freshness

The main page is checked on a rolling basis, and any material change to Chub’s pricing, model list, app situation or regional access triggers an out-of-cycle update. When a page changes, its dateModified stamp moves; datePublished is left alone so the first-publish record survives.

Corrections

A factual fix beats defending the original wording every time. Send the claim, the correction and a source through LinkedIn. Verified corrections are applied to the page, noted under the editorial policy, and reflected in schema. The independence and money rules that sit alongside this are on that same editorial policy page, and the site’s remit is described on the about page.

What this is not

This site does not run paid infrastructure checks it cannot fund, does not invent numbers to fill a gap, and does not give financial, legal or medical advice, which is spelled out in the terms of service, while the privacy policy covers the little data the site holds. Age and content positions are handled separately on the age verification and § 2257 pages.

Last updated: July 12, 2026 · by Melissa Blake