Public service surfaces
The root, plans, two checkout forms, signals archive, dashboard, API guide, Telegram archive and Cryptohopper profile returned public content.
Independent provider evidence file | researched 2026-07-11
The current public footprint is active enough to inspect: prices, checkout forms, a 30-day signal archive, a subscriber dashboard and an API guide are reachable. That footprint does not yet identify the responsible legal operator or prove subscriber-account profitability.
The public footprint is substantial enough to research, but not sufficient for verified status or a profitability conclusion.
No account, checkout, payment, support message, exchange connection or trade was used.
Decision first
The reviewed public domain, plans, checkout forms, free-signal archive, subscriber dashboard, API documentation, alternate public API route, Telegram announcement channel and Cryptohopper seller profile were reachable on the research date.
The reviewed public pages did not identify a legal operator, named analyst, registration, jurisdiction or street address, and they did not provide a CSR-reviewed, loss-inclusive account return record.
Use the public feed or paper trading first. Before payment or any exchange connection, save the exact plan, refund process and official support route, then ask for the legal operator and a complete result export that includes losses, fees, slippage, sizing and drawdown.
Capture the plan name, billing period, price, included channels, bot access and any coupon before payment. Gold and Silver are not interchangeable.
Ask for the legal operator, registration, jurisdiction, support owner and governing terms. A brand handle and support email do not answer who owes fulfillment or a refund.
Deduplicate exchange-level rows into provider ideas, preserve the first timestamp, include every closure and loss, and reconcile fills, fees, slippage, leverage, sizing and drawdown.
Use the free public route or a paper account first. Do not grant withdrawal permission, and do not assume a bot integration protects you from stale routes, duplicate records or execution differences.
Evidence map
The evidence map counts the fifteen fixed findings in this dataset. A confirmed route or displayed price is useful, but it answers a narrower question than operator identity, contractual recourse or account-level performance.
The root, plans, two checkout forms, signals archive, dashboard, API guide, Telegram archive and Cryptohopper profile returned public content.
Two plan families and checkout methods are displayed. The reviewed checkout HTML did not expose governing terms, privacy, operator, jurisdiction or a refund-process acknowledgement.
The archive exposes rows that can be logged, but exchange replication means record volume cannot be read as independent trade ideas, wins or realized fills.
Cross-linked routes support attribution to the CQS brand footprint. They do not name the analyst, legal merchant or entity responsible for fulfillment and recourse.
Current displayed pricing
The provider labels the catalog as live billing data in staging. Gold is described as full Telegram access with premium channels and support. Silver is described as signal delivery through external platforms and a Telegram bot. A lower price therefore does not mean the same product at a discount.
| Plan | Monthly | Every 2 months | Every 3 months | Every 6 months | Yearly |
|---|---|---|---|---|---|
| CQS Premium Gold | US$50 | US$90 | US$120 | US$210 | US$300 |
| CQS Premium Silver | US$15 | US$27 | US$36 | US$63 | US$90 |
The provider describes Gold as full Telegram service with a premium chat room, exclusive content channels, support and connections to named third-party trading tools.
The provider describes Silver as premium signals on supported external bots and platforms, with Telegram delivery through one of its bots rather than the full Gold channel set.
Both checkout pages offered PayPal and cryptocurrency payment buttons, but CSR stopped before submission. A reachable checkout confirms a purchase route, not successful delivery, recurring-billing behavior, cancellation timing or refund fulfillment. Save the plan and demand the governing terms before using the form.
Original public-feed audit
At the observation time, the provider archive displayed 32,316 records across 1,616 pages for the prior 30 days. CSR froze the first twenty visible rows without filtering. The sample exists to identify the archive's counting unit, not to estimate performance.
Every displayed exchange row had its own ID.
Seventeen rows shared one XRP timestamp; three sampled rows shared one DOGE timestamp.
The sample's row multiplication was caused by venue coverage, not twenty separate ideas.
All twenty sampled records were open, long, scalping rows when captured.
The visible archive counts exchange-level records. In the fixed sample, one pair and timestamp produced 17 separate rows across exchanges. The 32,316 displayed records therefore cannot be treated as 32,316 independent trade ideas, completed trades, wins or subscriber fills.
All sampled rows were still open. This sample describes publication structure only and cannot estimate win rate, realized return, fees, slippage, drawdown or subscriber results.
Automation route check
/getSignal/?api_key=FREE&interval=20The public request returned a plain 404 response from the research location.
/api/v1/getSignal?api_key=FREE&interval=20The public request returned a valid empty JSON response with error code zero.
The public documentation described both paths as the same handler. On the research date, the documented primary path returned 404 while the alternate path returned a valid empty response. This is a route-parity observation, not evidence that premium delivery fails.
The May 2026 guide documents entry zones, targets, stops, exchange identifiers, signal types, risk fields and a literal FREE key. That structure can support paper-trade capture and deduplication.
Documentation cannot prove private feed uptime, message latency, downstream bot behavior, fill quality, revocation, subscription fulfillment or realized account results. Test the exact response contract before writing automation.
Performance-proof boundary
The provider's About page says daily reports demonstrate profitability under an immediate-entry and target-exit assumption, while also saying profit is not guaranteed. Cryptohopper describes displayed results using highest and lowest movement after a signal. In the reviewed platform stats rows, real-buy and real-sell columns were zero.
Preserve publication time, entry range, stop, targets, direction, leverage and every edit.
Match the alert to venue availability, latency, partial fills, fees, funding and slippage.
Include losses, expiries, manual closes, open risk and targets that were touched but not realistically filled.
Apply position sizing and leverage, then report equity curve and maximum drawdown, not summed percentages.
The fixed sample had no closed outcome, and the reviewed public surfaces did not supply the complete execution-ready population needed to calculate one. Visible volume, selected results and platform price excursions are useful inputs, but none independently answers what a subscriber account earned after costs and sizing.
Identity and recourse
The About page describes an unconditional first-month money-back promise for services bought on the website, limited to one use per customer. It also publishes an email, Telegram support handle and Discord route.
No named legal operator, registration, jurisdiction, street address, refund submission procedure, response deadline, processing deadline or dispute forum appeared on the reviewed About and checkout pages.
This is an evidence gap, not an accusation. The operator or terms may exist elsewhere or appear after authentication. Until they are attributable, a buyer cannot know from the reviewed public checkout who owes the service, which law governs the transaction or how the provider's promise would be enforced.
Fifteen attributable findings
Every finding keeps its evidence state, decision use and limitation together. The exact source mapping remains in CSR's internal audit record. Positive evidence is not hidden, and missing evidence is not upgraded into a misconduct claim.
Decision use: Treat the current site as a live rebuild surface, not as a finished-product assurance.
Limit: A staging label does not by itself prove that checkout, delivery or support is unavailable.
Decision use: Use direct attributable routes rather than assuming search visibility proves which provider page is official.
Limit: The directive is an indexing choice on the provider site, not a safety or legitimacy finding.
Decision use: Save the exact plan and period because the access scope differs between Gold and Silver.
Limit: Displayed prices can change and do not prove billing, delivery or total third-party bot costs.
Decision use: A reachable form confirms a purchase path exists, but the buyer still needs a written fulfillment and cancellation record.
Limit: No checkout form was submitted and no payment, account creation or fulfillment test was performed.
Decision use: Ask for the governing terms and operator before payment instead of inferring them from the buttons.
Limit: Terms may appear after an authenticated step or through support; that was not tested.
Decision use: Capture this wording before purchase and ask how to submit, time and prove a refund request.
Limit: The reviewed page did not state a response deadline, processing deadline, governing entity or dispute forum. CSR did not test a refund.
Decision use: Request the contracting party and jurisdiction before sending money or granting account access.
Limit: Absence on the reviewed pages is not proof that no entity exists elsewhere.
Decision use: These links support route continuity for the brand footprint.
Limit: Cross-linking does not establish the legal operator, analyst credentials, ownership continuity or profitability.
Decision use: The archive creates a reviewable starting point, but its counting unit must be normalized before any accuracy calculation.
Limit: The count is volatile and is not a count of independent ideas, completed trades, wins or subscriber fills.
Decision use: Deduplicate by provider idea, timestamp and instrument before calculating coverage or outcomes.
Limit: The sample is deterministic but small and was selected to describe page structure, not performance.
Decision use: Do not derive a win rate from open records or from selected result posts.
Limit: Later page states may close or revise records; CSR did not monitor this sample forward.
Decision use: Treat the statement as conditional provider marketing until an execution-ready, loss-inclusive account record is reconciled.
Limit: The reviewed statement does not itself establish fills, fees, slippage, position sizing, leverage, losing trades, drawdown or account return.
Decision use: Keep price-path metrics separate from realized subscriber account results.
Limit: Marketplace values are volatile, platform-defined and not a CSR audit of every signal or subscriber.
Decision use: A structured feed can support paper-trade logging and reproducible record capture before any exchange automation.
Limit: Documentation does not prove every field is current, every route is available or every downstream bot executes as intended.
Decision use: Test the exact route and response contract before building automation around the documentation.
Limit: One empty public request cannot assess premium delivery, uptime or historical reliability.
Evidence custody
The public record exposes what CSR concluded, how each fact is classified and what remains unproved. Exact external routes and capture metadata stay in the internal evidence file so this provider review remains a due-diligence synthesis rather than a traffic directory.
Website, plan, checkout, documentation and public-record responses establish what was displayed on the research date. They do not prove fulfillment, legal identity or subscriber results.
Unauthenticated responses preserve the documented-path conflict. They do not test a paid key, private delivery, uptime or downstream execution.
The dated public footprint supports brand-route continuity only. It is not a complete result sheet or an independent account record.
The platform record helps classify the product and displayed measurement method. Platform-defined movement is not realized subscriber return.
CSR retains the exact URLs, response metadata, capture hashes and finding-to-source mapping in the internal audit record. This public provider page deliberately does not render an outbound source directory. It shows the factual synthesis, evidence state, decision use and limitation needed for a payment decision.
Custody fingerprint: 11 dated captures across 4 hosts; capture-set SHA-256 00397853f320fb0dd8c76c10af5a74516a2513cfba5ca293f72699708006d081; research-file SHA-256 739da251af14be2d067e5e3334ee51eee7fbea1a9dd077b7710b4ff55eed3a27.
Method and machine-readable evidence
Prefer current provider-owned pages and directly linked platform records. Attribute every provider statement, separate observed behavior from marketing claims, and keep missing proof visible.
The public-feed sample is the first 20 visible rows on page 1 at the observation time. It is used only to identify the archive counting unit and cannot score performance.
account creation, login, checkout submission, payment, refund request, support message, private API access, exchange connection, order placement, trade execution.
Prices, records, routes and platform metrics are dated observations. Recheck them before making a decision.
Reuse boundary: You may cite the dated facts with attribution to CryptoSignalsReview while preserving each evidence-state label and limitation. Do not convert under-review status into endorsement, or a public record count into a win-rate or profitability claim.