Who Runs Crypto Signal Providers? Operator and Team Disclosure Audit

Operator evidence and team evidence are separate

The operator field asks which entity appears to operate or contract for the service and whether the reviewed evidence reconciles that claim. The team field asks how named or pseudonymous people were evidenced. Combining both into one trust score would hide important differences: a provider can name people while the contracting entity remains unresolved, or provide entity documentation while the people promoting signals remain pseudonymous.

These statuses are not legal conclusions. They are dated editorial evidence states designed to stop a missing answer from being silently converted into a positive or negative claim. The most useful comparison is not which label looks strongest. It is what exact evidence would change the label and whether that evidence reaches the same entity, route, checkout, invoice, and support path the buyer will use.

The observed status combinations

The cross-tab keeps operator and team findings visible together without collapsing them. Each provider appears once. The combinations reveal that named-team disclosure and operator reconciliation often move independently, which is why a provider-level badge or single transparency percentage would be misleading.

A team described as confirmed in one dossier does not change that dossier’s separate operator evidence state. Likewise, a conflicted operator state does not mean every named person is fictitious or every provider claim is false. It means the reviewed operating-entity evidence did not reconcile cleanly enough to present as confirmed.

Provider operator and team disclosure matrix

Rows are alphabetical, never ranked. Entity, jurisdiction, and person fields reproduce the CSR-authored research record at the cohort date. Parenthetical wording such as provider-claimed remains part of the evidence boundary. Readers should not use a name from this table to contact, identify, or investigate a private person; only public professional claims relevant to the service belong in the review.

The matrix is a starting point for due diligence, not a verdict. A current checkout can be operated by a different merchant, affiliate, app, exchange, reseller, or wallet than a public website footer suggests. Recheck the exact route at the decision moment and preserve any difference from this dated record as new evidence rather than rewriting the earlier capture.

Registry evidence appears in only part of the cohort

The source set contains 12 registry assignments, 12 unique registry URLs, and 7 registry hostnames across 9 providers. The shared source type combines 5 corporate or entity lookup rows with 7 domain-registry rows. It therefore cannot support a legal-registration coverage rate.

A responsible registry check records the jurisdiction, exact entity spelling, registration number if found, status date, filing type, and mismatch between the registered entity and the merchant, domain, app publisher, payment recipient, or messaging route. Search failure is not proof of non-registration because spelling, jurisdiction, access limits, stale indexes, and nominee structures can affect results.

Named people are disclosure claims, not automatic confirmation

The dossiers record 19 person-name assignments representing 19 exact case-insensitive names across 12 providers. 4 providers have no named person in the team field. This count describes the research objects, not the size of any provider’s staff or the number of people operating in private.

Name presence and team status are deliberately independent. One provider-claimed team row contains no person name, while 2 unresolved team rows retain historical person-name entries. The one confirmed team row contains 3 names. Those edge cases prevent a named-person count from being presented as a confirmation rate.

Provider-published biography pages, social profiles, webinars, interviews, and channel introductions can establish that a name was claimed. Independent role confirmation needs a separate source or a verifiable continuity trail. Credentials, licenses, trading history, or employment should be checked against the body that issued or recorded them, not inferred from a portrait, follower count, testimonial, or repeated biography.

Identity questions already appear in the authored review queues

For transparency, the audit applies one literal case-insensitive keyword family only to CSR-authored conflict, risk, and missing-proof entries: operator|owner|ownership|identity|entity|registration|registry|company|team|role|credential|legal|jurisdiction. The result measures wording visibility, not unique incidents. A single underlying issue can appear in more than one queue, and a relevant identity question can use different wording and therefore remain outside the count.

The missing-proof queue is the most actionable output. It converts an unresolved state into a request that could change the record: a current registry extract, exact contracting entity, merchant or invoice identity, independently supported team role, official cross-link, or written explanation of a mismatch. The count must never become a provider score or allegation rate.

The source trail and date boundary

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. 14 providers have at least one independent-boundary or registry row, but source-type coverage does not confirm identity or source independence. All assignments carry the common access date 2026-07-10; access date is not publication date and does not prove that a page remained unchanged before or after capture.

Missing publication metadata is a freshness limitation, not proof that a source is unreliable. For identity claims, date sensitivity matters: entities change names or status, teams change, domains expire, social handles are reassigned, and payment routes move. A buyer should preserve the current source and timestamp instead of treating this dataset as a permanent identity register.

A pre-payment identity verification workflow

1. Start from the exact official route

Record the domain, app publisher, Telegram or Discord handle, bot, support route, and checkout path. Require those routes to cross-link where practical. A same-name directory entry, forwarded post, private message, or search result is discovery evidence, not proof that the account controls the service. The 16-provider official-channel and Telegram route audit measures this route-attribution question separately; an attributable channel still does not establish the legal operator.

2. Identify the contracting and payment parties

Compare the entity in the terms, privacy notice, invoice, card descriptor, wallet request, app listing, exchange referral, and support reply. Ask which party owes access, cancellation, refund handling, and data protection. Do not infer legal responsibility from a channel administrator name or website footer alone.

3. Reconcile jurisdiction and registry evidence

Use the official registry for the claimed jurisdiction where available. Preserve exact spelling, number, status, filing date, and registered activity. If the search does not return a record, document the query and limitation rather than claiming the company does not exist. If it returns a record, still connect that entity to the domain, merchant, and offer.

4. Separate named-person disclosure from role proof

A public name can be useful, but it does not establish authority, employment, credentials, or control. Check professional continuity, issuer records for claimed credentials, and the relationship between the person and the contracting entity. Avoid collecting private addresses, phone numbers, family details, or unrelated personal data.

5. Verify the route again at payment or permission time

Impersonation risk rises when payment, exchange UID, API key, bot permission, wallet connection, or managed-account access moves into a private conversation. Confirm any changed route through the independently reached official surface. Do not grant withdrawal permission, share seed phrases, or treat a direct-message urgency claim as identity proof.

6. Keep identity, terms, and performance packets separate

An identified company can still publish incomplete results, and a transparent signal archive can still have unclear billing or ownership. Review the commercial terms audit for the separate pricing and billing decision. Require original alerts, losses, edits, fees, slippage, leverage, sizing, open calls, and drawdown in a performance packet.

7. Preserve the unresolved state

If evidence does not settle the question, the correct output is unresolved, conflicted, provider-claimed, or pseudonymous, plus the next proof request. Do not invent a positive identity conclusion to complete a review, and do not convert missing proof into an accusation.

Method and reproducibility

The generator resolves the named Git commit, reads four JSON objects through git show, validates their schema and 2026-07-10 research date, requires unique provider slugs, and recomputes every measure. It preserves the exact operator status, entity text, jurisdiction text, team status, public name list, source assignments, registry source routes, and authored queues. Provider rows are sorted alphabetically and never by status, source count, or commercial value.

Host counts use parsed URL hostnames. Named-person uniqueness uses a case-insensitive exact string, not real-world entity resolution. A non-placeholder entity or jurisdiction means only that the exact field value is not Unresolved. Registry-family classification uses the documented host allowlist in the generator and must not be rewritten as legal-registration coverage.

The frozen research attaches sources at the provider-record level. It does not provide stable source IDs or direct operator.sourceRefs and team.sourceRefs. The audit can therefore prove that a dossier had a source packet, but it cannot claim a one-to-one source citation for every identity sentence. Publication metadata classifies YYYY-MM-DD as exact, YYYY-MM as month-only, and blank, null, or the literal unresolved value as lacking a resolved date.

node tools/generate-crypto-signal-provider-operator-team-disclosure-audit.mjs --git-ref 5dcd30b2b1a0da9bacbaeec08244190dae19a49f --distribution-ref 17d72e5460e648baef9d3e596e2e3a67a50a60d9 --distribution-json-url https://gist.githubusercontent.com/TheCryptoSimon/e9af8e93a21bf2261a425dfd46df2be9/raw/bae0f47ac9699963dd594bcaf978b89b458ffad5/summary.json --distribution-csv-url https://gist.githubusercontent.com/TheCryptoSimon/e9af8e93a21bf2261a425dfd46df2be9/raw/2ecb34f012e1f7318573836d599f7862d08bbb96/summary.csv --distribution-version ed3e8889e0ac45fa7ca2f5a270fea7e8b9667dd3 --distribution-page-url https://gist.github.com/TheCryptoSimon/e9af8e93a21bf2261a425dfd46df2be9 --published-at 2026-07-11 --modified-at 2026-07-11
node tools/check-crypto-signal-provider-operator-team-disclosure-audit.mjs --verify-public-distributions

Reproduction proves that the published aggregation matches the frozen CSR research objects. It does not prove that a provider’s present operator, team, registration, route, payment recipient, or offer matches the 2026-07-10 capture. Current verification remains a separate human task.

Cite and download the aggregate release

The machine-readable release contains the exact aggregate metrics and alphabetical provider matrix used here. It omits private identifiers, contact details, ratings, and profitability conclusions. Any reused count should retain the cohort date, frozen source commit, denominator, and evidence-state boundary.

• Download aggregate JSON

  20,933 bytes; SHA-256 51d67cd219c7c51149bfa19a864d99425c0e10963511f892d2f8f0cfec645f12.

• Download aggregate CSV

  6,643 bytes; SHA-256 a8bbbfa6fa38980646acbd49eb0187847f60a40804593e580b73dd19f291b823.

CryptoSignalsReview Evidence Desk. Who Runs Crypto Signal Providers? Operator and Team Disclosure Audit. Cohort captured 2026-07-10. Frozen source commit 5dcd30b2b1a0da9bacbaeec08244190dae19a49f. https://cryptosignalsreview.com/crypto-signal-provider-operator-team-disclosure-audit/

Public release ed3e8889e0ac45fa7ca2f5a270fea7e8b9667dd3; matching repository release commit 17d72e5460e648baef9d3e596e2e3a67a50a60d9.

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

Official context sources

These official sources explain why identity, registration, promotion, costs, and unsupported result claims require independent scrutiny. They do not validate, accuse, rank, or endorse any provider in the cohort.

• Investor.gov: social media and investment fraud

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

• FCA: cryptoasset firms marketing to UK consumers

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

• CFTC: commodity trading systems sold on the internet

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

Related CryptoSignalsReview evidence

• Compare 21 provider dossiers

  Open the individual evidence files that supplied this fixed cohort; coverage is not endorsement.

• Official-channel and Telegram route audit

  A separate 16-provider analysis of site, app, channel, bot, handle, cross-link, and same-name route attribution.

• Provider commercial terms audit

  A separate 64-row analysis of pricing status, billing language, access flags, and source dates.

• Win-rate and accuracy claims audit

  A separate 16-provider analysis of percentage claims, result accounting, and the proof needed for reproduction.

• Provider Transparency Dataset

  Separate 3,200-record inventory research with a different unit, snapshot, and evidence boundary.