Crypto Signal Provider Pricing and Commercial Terms Audit

What each commercial status means

The status is assigned to the offer row, not to the provider as a whole. A provider can therefore have current and conflicted rows at the same time. Status does not measure quality, profitability, safety, service availability, or legal compliance. It records how the reviewed evidence fit together at the cohort capture.

The four rows reconcile to all 64 offer records. 5 providers have only current rows, but that still does not establish today’s checkout price or terms. The remaining dossiers contain at least one conflicted, unresolved, or historical row and should be checked at the exact route and checkout shown to the buyer.

Offer-row depth varies by dossier

A dossier contains between 2 and 7 offer rows, with a median of 4. More rows can mean that a provider exposes more products, more access routes, more plan variants, or more unresolved name collisions. It does not mean that the provider is larger, better, riskier, or more thoroughly verified.

Alphabetical provider status matrix

This matrix is alphabetical, not ranked. It shows the count of authored offer rows and their evidence states. The source column is the number of source assignments used in that dossier; it is not a score and should not be added to a trust model. A row with several current offers can still have unresolved operator identity, refund treatment, performance proof, or execution risk.

The largest dossiers contain seven rows; the smallest contain two. The matrix keeps conflicting and unresolved commercial records visible instead of collapsing every plan into one headline price. That matters when a public post, legacy page, checkout, Telegram promotion, referral path, or same-name website may describe a different product or contracting route.

Paid and free labels overlap

All 16 dossiers carry a free-access flag, while 15 also carry a paid-access flag. 15 are therefore mixed, 0 are paid-only, and 1 is free-only in the frozen files. These are dossier-level access labels, not counts of free or paid products. They describe whether the reviewed footprint included each access type.

Free is not the same as zero economic cost. A free public feed may lead into a paid room, exchange-referral route, minimum deposit, copy-trading fee, spread, funding cost, token purchase, custody relationship, account registration, API connection, or performance-fee proposal. Conversely, a paid flag does not prove that a current checkout is available or that the captured price still applies. Before treating access as free or paid, record the complete path from public route to final account, payment recipient, and trade-execution layer.

Refund, cancellation, and renewal language is sparse and uneven

The audit searches only the reviewer-authored billing field for three literal word families. It finds refund wording in 23 rows across 10 providers, cancellation wording in 8 rows across 7 providers, and renewal wording in 8 rows across 6 providers.

This is a lexical visibility test, not a contract analysis. The absence of a word can mean the reviewed offer omitted the term, used different language, placed it in another document, or required account access. Its presence can describe a restriction rather than a benefit. A buyer should save the controlling terms, checkout, invoice, renewal screen, cancellation confirmation, and access-removal evidence together.

Operator and team evidence remain unsettled

No dossier in this cohort carries a confirmed operator status. 9 operators are unresolved and 7 are conflicted. Team evidence is different: 7 dossiers are pseudonymous, 5 unresolved, 3 provider-claimed, and 1 confirmed. These fields should not be merged into one identity score.

An operator status asks whether the contracting or operating entity was reconciled. A team status asks how named or pseudonymous people were evidenced. A confirmed person does not automatically confirm the merchant, and an unresolved or pseudonymous state does not prove wrongdoing. The practical checkout question is narrower: who contracts, who receives payment, which law and terms govern, and which support route can correct a billing or access failure?

The source trail is broad, but publication timing is often unresolved

The cohort uses 152 source assignments, 148 unique URLs, and 42 hostnames. Each dossier has between 7 and 10 sources, with a median of 10. Every assignment records an access date of 2026-07-10; that common access date is not the same thing as the date the underlying page, post, registry record, or terms document was published.

Only 47 assignments have an exact publication date and 3 have month-only metadata. The remaining 102 lack a resolved publication date in the research record. That is a freshness limitation, not an automatic source-quality verdict. The correct next action is to inspect page history, terms version, post identifier, archive evidence, or checkout timestamp rather than inventing a date.

Authored review queues expose what remains unresolved

Across the 16 dossiers, researchers recorded 79 conflict items, 83 risk items, and 98 missing-proof requests. These are authored queue entries, not unique incidents and not prevalence estimates. One underlying problem can appear in more than one field, and one field can contain several connected facts.

A larger queue does not rank a provider as worse. It may reflect product complexity, multiple routes, fuller documentation, or more visible contradictions. The useful output is a prioritized request: identify the merchant, capture the controlling checkout, preserve renewal and cancellation behavior, reconcile current and legacy claims, and keep performance evidence separate from commercial terms.

A purchase-intent verification workflow

1. Verify the exact route before comparing price

Start from a provider-controlled route that can be independently matched to the offer, support account, checkout, and payment recipient. Record the domain, handle, account identifier, and capture time. Same-name websites, forwarded messages, resellers, bots, and private invitations can point to different operators or terms.

2. Save the final payable amount

Capture currency, tax, discount, sale expiry, billing interval, recurring or one-time treatment, deposit requirement, referral condition, exchange fee, copy fee, token amount, performance fee, and any minimum account balance. A headline monthly or lifetime number is not a total-cost comparison until those components are reconciled.

3. Identify the contracting and payment parties

Record the legal or operating name shown in the terms, invoice, card descriptor, wallet request, app, exchange route, and support reply. If those names differ, ask which party owes access, support, cancellation, and any refund. Do not infer legal responsibility from a Telegram admin name or website footer alone.

4. Separate access terms from trading permissions

A subscription can end while a bot, exchange connection, API key, copier, or managed account remains active. Confirm what the seller can view or trade, whether withdrawals are disabled, how access is revoked, what happens to open positions, and how the user proves that no new orders can be placed. Compare these boundaries across the 16-provider account-access audit.

5. Test renewal, cancellation, and refund mechanics

Read the controlling document and then inspect the actual account flow. Save the next-charge date, notice period, cancellation method, access end date, refund exclusions, dispute route, and confirmation message. If crypto, token, or direct-wallet payment is requested, establish what remedy exists before sending funds rather than assuming a card-style chargeback.

6. Keep commercial evidence separate from result evidence

A clear price does not validate a win rate, and a convincing signal example does not clarify a refund. Review original alerts, losses, edits, open calls, fees, slippage, funding, leverage, sizing, and follower-side fills in a separate result packet. Neither packet should silently compensate for gaps in the other.

7. Recheck at the decision moment

This dataset is dated 2026-07-10. Before buying, renewing, cancelling, or connecting an account, repeat the route, checkout, identity, terms, and permission checks. Preserve any difference from the frozen dossier as new evidence. Do not overwrite the historical capture or call the old record false merely because a provider changed it.

Method and reproducibility

The generator resolves the named Git commit, reads the four JSON objects through git show, validates their schema and research date, requires unique provider slugs, and recomputes every metric. It fails if the fixed cohort no longer matches the independently established row counts, statuses, access flags, lexical mentions, source totals, source-type distribution, publication-date states, or authored queues. This protects the page from concurrent working-tree edits and accidental denominator drift.

The lexical billing test applies case-insensitive refund, cancel, and renew patterns only to each offer row’s authored billing text. The source-date test treats YYYY-MM-DD as exact, YYYY-MM as month-only, and blank, null, or the literal unresolved value as lacking a resolved date. Host counts use the parsed URL hostname. Provider rows are sorted by display name and never by status, source count, or offer count.

node tools/generate-crypto-signal-provider-commercial-terms-audit.mjs --git-ref 5dcd30b2b1a0da9bacbaeec08244190dae19a49f --distribution-ref b2fd3858f7c26eea354451fcef3fa4d352616917 --distribution-json-url https://gist.githubusercontent.com/TheCryptoSimon/ca312a920b2f49184e22d82a53b63c8e/raw/95fe55198e92f8fac4046ff9a89179c7736a7960/summary.json --distribution-csv-url https://gist.githubusercontent.com/TheCryptoSimon/ca312a920b2f49184e22d82a53b63c8e/raw/6814a2c1c7e66b500c04e80d9de33fe16a18625e/summary.csv --distribution-version 76ab321559fcbd986b1d9fcb923aa736f484d409 --distribution-page-url https://gist.github.com/TheCryptoSimon/ca312a920b2f49184e22d82a53b63c8e --published-at 2026-07-10 --modified-at 2026-07-10
node tools/check-crypto-signal-provider-commercial-terms-audit.mjs --verify-public-distributions

The aggregate release does not reproduce third-party pricing prose. Readers who need a provider-level conclusion should open the committed dossier and the cited source route, then check the live checkout and controlling terms. Reproduction proves that the published aggregation matches the frozen files; it does not prove that a third-party offer remains available or enforceable.

Cite and download the aggregate release

The machine-readable release contains the exact aggregate metrics and the alphabetical provider matrix used on this page. It intentionally excludes raw checkout credentials, personal data, ratings, and profitability conclusions. Cite the canonical page, cohort date, frozen source commit, and denominator beside any extracted number.

• Download aggregate JSON

  8,483 bytes; SHA-256 1b53faf64d754b992ba029b53c053cd9c8095d41bb4e3cfdf7902de716097d39.

• Download aggregate CSV

  3,986 bytes; SHA-256 2e5513a648c1cb599805effd9df73bf078cf677775fe3048a1cff6e9883767f3.

CryptoSignalsReview Evidence Desk. Crypto Signal Provider Pricing and Commercial Terms Audit. Cohort captured 2026-07-10. Frozen source commit 5dcd30b2b1a0da9bacbaeec08244190dae19a49f. https://cryptosignalsreview.com/crypto-signal-provider-commercial-terms-pricing-status-audit/

Public release 76ab321559fcbd986b1d9fcb923aa736f484d409; matching repository release commit b2fd3858f7c26eea354451fcef3fa4d352616917.

Aggregate reuse terms: CryptoSignalsReview permits quotation and reuse of the aggregate JSON and CSV with attribution to the Evidence Desk, the canonical page, the 2026-07-10 cohort date, and the frozen source commit. Reuse must preserve the non-representative, non-ranking, non-verification, and non-performance boundaries. This permission does not grant rights in third-party names, marks, pricing copy, or source material.

Official context sources

The official sources below explain why identity, costs, promotions, and result claims need independent scrutiny. They do not validate, accuse, rank, or endorse any provider in the cohort.

• FCA: cryptoasset firms marketing to UK consumers

  Official context for fair, clear, not-misleading communications and the UK cryptoasset financial-promotion regime.

• Investor.gov: social media and investment fraud

  Official context for independently checking identity, registration, impersonation, testimonials, and unsolicited investment contact.

• CFTC: commodity trading systems sold on the internet

  Official context for examining costs, hypothetical results, loss capacity, and unsupported trading-system claims.

Related CryptoSignalsReview evidence

• Exchange eligibility audit

  Separates provider pricing from jurisdiction, KYC, referral, deposit, UID, and venue-product access questions across the same 16-provider cohort.

• Provider Transparency Dataset

  Separate 3,200-record inventory research with its own unit, snapshot date, and public distributions.

• Provider due-diligence checklist

  A general evidence framework; it is not this empirical 16-provider aggregation.

• Cornix marketplace sample audit

  A separate 85-row analysis of stars, reviewer denominators, activity fields, and offer flags.

• Pricing and fee disclosure library

  Procedural claim checks for pricing evidence, not a duplicate provider dataset.