Labels, sources, corrections

Reporting, Analysis, Opinion, Guide, Review, and Wire are different objects. Briefs, desk stories and daily reports say how they were written. Sponsored copy, if it ever appears, will say Sponsored and will not wear a review score.

We do not fabricate prices, authors, comments, or readership. CoinGecko and Polymarket responses are cached; stale snapshots are marked. News items come from publisher RSS, including CryptoSlate’s public feed. Each appears as a preview — headline, an excerpt of at most 60 words and a link to the full story on the publisher’s site. A preview page stays out of search indexes unless it also carries a Dextape brief, our own summary of the story. Publisher material is attributed separately from Dextape reporting.

How Dextape writes

Four kinds of item are machine-written, and each says so in its meta line with a link back here. Everything else on the site is written by people or is data shown as measured.

Brief

A summary of one wire story, written from the publisher’s own article text, never from a headline alone. It names and links the original. Stories that are mainly price predictions, promotions or opinion get no brief.

Daily report

The market in figures from a dated CoinGecko snapshot and the day’s wire headlines. The tables are the data; the narrative is written from the same snapshot and nothing else.

Desk

A desk story covers one news event, written from the publishers’ feed text and never from a fetched page. When three or more publishers report it, the story compares their accounts; an event fewer publishers carry gets a shorter story from its longest report, at most three fifths of that report’s length. Each names the outlet that reported the news near the top and links every source; after that it credits each fact to the person, company or document behind it, as the outlet reported it, and it opens with a three-point Quick take. Its image is an illustration generated by Dextape, never a photograph. A desk note on a wire page is shorter: context from the headline and excerpt, not reporting.

Guide

An evergreen explainer researched on the web and written from the pages it cites, at least three outlets, all listed under the guide. A second machine pass checks it against those pages before it is published.

What is checked before it appears

• Every figure must appear in the source text or the snapshot. A figure the source lacks rejects the draft.
• No run of eight or more words may repeat a source or headline, and no quotation marks are used.
• No investment advice, price predictions, market calls, performance claims or hype, in any voice. A desk story may not say that Dextape reported, contacted or verified anything.
• Plain reporting language only; the same rules reject filler phrasing.

A draft that fails any check is sent back with the reason and rewritten, up to a fixed number of attempts; one that still fails is not published. A matching figure proves that the number is in the source, not a claim about why a market moved. Drafts for longer pieces from the editorial desk also need corroborating sources and an editor’s review of the text, attribution and publication rights before release. We never present machine-written copy as interviews or firsthand reporting.

To report an error in any of these, send the desk a correction with the page URL and the claim in question. The item is withdrawn or corrected and the change is recorded.

Membership and commercial enquiries

Dextape Pro funds personal monitoring features. Membership does not buy favorable coverage. Any paid placement must be labeled Sponsored and kept distinct from editorial verdicts. Product support and commercial enquiries go through the contact form.

Usage analytics and email

We use Vercel Web Analytics on public pages to understand visits and referral sources. It provides aggregate page, browser, device and approximate location statistics without advertising cookies. We exclude personal workspaces, account pages, wallet tools and email confirmation links, and remove arbitrary query values. Only our defined campaign tags are retained for launch attribution.

Our first-party activity records include supported page visits and product actions, timestamps, route paths, referring site names and campaign tags. Your browser keeps only your last visit date in dx_last_visit so we can count returning readers, with no identifier stored. Signed-in activity may be associated with your account ID; anonymous sessions use a daily salted hash rather than a permanent reader identity. Authorized operators can review these records to investigate reliability and understand product use. We do not record passwords, keystrokes, form contents or arbitrary query values. Native measurement respects Do Not Track and Global Privacy Control. Embedded tools record supported product events through the same first-party ingestion service.

Email signup stores your email address and consent status in our subscriber database (the processors are named in our privacy policy). A subscription starts only after confirmation; every confirmation email includes an unsubscribe link. Request limiting uses salted daily network address hashes, not raw addresses, with old limit records removed as requests are processed.

Sources and corrections

To report an error, send a correction to the desk with the page URL, the claim you are questioning and any supporting primary evidence. Include the original publisher link when the item comes from our news wire.

Published editorial changes require a revision note in our internal audit ledger. The desk retains publication history and can withdraw a story when it no longer meets our standards.