INDEPENDENT · SOURCE-BACKED · ADULTS 18+

Check the feature.
Keep the limits.

A practical evidence desk for checking AI companion chat, memory, voice, images, video, customization and user controls without turning product claims into promises.

Sponsored links may earn us a commission. The methods and source labels stay the same whether you click or not.

Illustrated feature-check console showing claim, access, method, result and limitations
THE EVIDENCE CONSOLE

A feature claim is the start of a check, not the result.

Copy the claim, identify the plan and device, use a harmless repeatable action, record only what happened, and preserve anything still unknown. This keeps a limited rollout, paid boundary or missing disclosure visible.

CLAIM

Quote before interpreting

Keep vendor-stated capability separate from observed behavior.

ACCESS

Name the boundary

Record plan, credits, region, device and account conditions.

METHOD

Use a fixed script

Change one harmless variable at a time and keep prompts fictional.

LIMITS

Leave unknowns visible

Do not infer a missing feature or turn one observation into a guarantee.

25 DISTINCT FEATURE-CHECK INTENTS

One capability. One method. One honest boundary.

The homepage owns the overall verification method. Each guide below answers one narrower question and links to its evidence and adjacent controls.

Feature Testing8 focused checks
Safety Controls6 focused checks
Compare Features4 focused checks
Evidence Method6 focused checks
FOUNDATION SOURCES

Methods before rankings.

Government, standards and independent guidance establish the evidence frame. Vendor pages are visibly labeled and never presented as independent verification.

SPONSORED CASE STUDY

See the current Candy AI experience, then apply the same checklist.

Candy AI is one commercial case study. Features, plans and policies can change; confirm the current account and checkout for yourself.

Open Candy AI — sponsored