Corrections policy

Report an attribution, classification, price or calculation error

Sign in, open the relevant channel profile, select the analysis and post in its comments section. For an asset price, trader call or an issue without a relevant analysis, open the affected asset’s discussion (Chat) and include the page URL. These existing public discussions are the reporting intake; comments allow up to 1,000 characters and asset messages up to 500. Check that your post appears after submitting. This does not create a private support ticket or send an email to staff, and there is no promised review or response time. Do not include private contact details or sensitive information.

• Find a channel and analysis
• Find an asset discussion
• Sign in to post

What to include

Identify the page URL, channel or trader, video URL, asset ticker and buy/sell call. State whether the problem is attribution, classification, price or calculation, what is shown and what you believe it should be. For attribution or classification, include the source timestamp, exact quote and enough surrounding context to explain the difference. For prices, include the provider or source URL, currency, price date, entry/latest values and whether the source adjusts for splits or dividends. For calculations, show the inputs, formula and expected result. Split a longer explanation into concise follow-up posts if needed; posting a report does not itself change a score.

Creator responses and disputes

A signed-in user with a verified claim to the channel can add, edit or remove a creator note under that channel’s recommendation and mark it disputed. Start the claim process from the channel profile; it checks channel control with a token in the YouTube channel description. A note or dispute provides public context; it does not change the extracted call, its prices, its score or ranking eligibility. Other signed-in users can comment and reply on analyses. A verified channel claim is not proof of a person’s legal identity.

What can actually be corrected

Administrators have controls to refetch a transcript, requeue extraction, backfill missing recommendation entry prices and recalculate video performance, plus channel performance/portfolio recalculation and asset-data editing. A backfill fills missing entries; it does not overwrite an existing disputed price. Re-extraction rebuilds recommendation rows and can change attribution or classification, but does not guarantee a different or correct answer. Creator notes belong to recommendation rows and can be removed when those rows are replaced. Scheduled price updates and the split-repair heuristic described in the methodology can also change results. There is no dedicated public per-call edit, resolution-status tracker or published correction history in the current application.

Limits of the reporting process

Reports are stored as public discussion posts, not automatically routed to a reviewer, and they do not trigger recalculation. The application does not establish a staffed review process, response deadline, notification of resolution or appeal procedure. An issue without an affected public analysis or asset has no dedicated intake destination here. A private or general support channel would require the operator to provide and monitor an external destination; none is designated by this policy. Until data changes and dependent calculations refresh, affected figures may remain unchanged.