Public correction process

Corrections & Content Updates

BTR Exchange publishes exchange-rate references, practical tools, and educational guides for readers who need context before checking a bank, card issuer, exchange office, broker, wallet, transfer provider, or metals dealer. This page explains how readers can report unclear, outdated, or incorrect content.

Updated 2026-06-30Reviewed by BTR Exchange editorial review

How corrections are handled

Report

Send the page URL, currency pair or topic, timestamp, device context, and the wording or number that looks unclear.

Reproduce

We check the visible page, related guide or glossary entry, rate context, and whether the issue can be reproduced from the supplied details.

Verify

Corrections are checked against the public methodology, source-category explanation, page limitations, and whether the current text could mislead a reader.

Update

When a correction is needed, we update the public page and related checks so the same issue is less likely to return silently.

Public history

Recent public content updates

Read methodology

2026-06-30

Review freshness signals aligned

Aligned visible review provenance, structured data modified dates, sitemap modified dates, and affected guide update metadata after the latest AdSense content-depth review.

Read methodology

2026-06-29

Exchange-rate glossary added

Added plain-language definitions for reference rate, provider quote, spread, delivered amount, settlement date, dynamic currency conversion, BNR reference rate, spot price, troy ounce, and stablecoin reference.

View glossary

2026-06-29

Guide review metadata made visible

Updated the guide index so each editorial guide shows updated date, word count, and BTR Exchange editorial review provenance.

View guides

2026-06-29

Editorial independence documented

Expanded the methodology page to clarify provider categories are comparison inputs, not endorsements, and that monetization cannot change methodology, guide conclusions, or correction priority.

Read methodology

2026-06-29

Publisher accountability strengthened

Updated the About and Contact surfaces so correction paths, informational publisher role, and review-safe support language are visible before monetization language.

Read about BTR

2026-06-29

Privacy and Google consent controls clarified

Documented Google AdSense and Analytics storage behavior and kept ad and analytics storage denied until a visitor makes a privacy choice.

Read privacy policy

2026-06-28

Temporary AdSense review sitemap narrowed

Kept converter and currency pages reachable, but focused the review sitemap on human-readable publisher, guide, methodology, glossary, legal, and tool pages.

Review methodology

Review standards

Correction standards and privacy boundaries

Corrections are meant to improve public explanations, not to expose private provider records or create one-to-one financial support. If a report includes sensitive details, we summarize the public issue and keep the private context out of the visible correction history.

Correction standards

A correction is prioritized when the current public page could cause a reader to misunderstand a reference rate, provider quote, fee, settlement timing, privacy choice, or limitation.

What does not become public

We do not publish private sender details, account identifiers, bank screens, wallet addresses, card data, identity documents, or provider account screenshots. Public notes describe the content issue, not the reporter.

Reader-safe correction outcomes

A reader-safe correction can clarify wording, add source context, update a stale example, fix a broken link, strengthen a warning, or add a test so the same misleading state is less likely to return.

Report evidence

Correction evidence checklist

Keep the affected URL, observed wording, expected wording, timestamp, device, source reference, and privacy redaction note together before sending a correction. A compact report is easier to reproduce and safer than a full provider screenshot with personal data.

Reference-rate mismatch

For a visible rate, pair, asset, or metals reference that appears stale or inconsistent, note the affected URL, the observed number, the expected wording or public source reference, and the timestamp. A provider quote, bank screen, card statement, wallet transaction, or exchange-office receipt can explain the private context, but redact account identifiers before sending anything.

Guide or glossary clarity

For a guide sentence or glossary definition that could be misread, copy the exact wording, explain the safer interpretation, and include the related page or term. This helps BTR decide whether the correction should add a warning, source note, calculation note, or cross-link instead of changing the whole page.

Privacy and advertising disclosure

For a privacy, consent, analytics, AdSense, or advertising-separation concern, describe the visible state, the browser or device, and the expected disclosure. The report should focus on public page behavior, not private Google account data, provider account data, or unrelated ad-personalization settings.

Reader-safe reporting

Correction review record

Keep the affected URL, public impact, observed wording, source reference, redaction note, reviewer action, and follow-up page in one correction review record. This keeps public editorial corrections separate from private provider support, refunds, disputes, and account access.

Public-impact check: Start with the public reader impact: whether a current page could misstate a reference rate, hide a fee boundary, blur provider responsibility, or make a privacy or advertising disclosure unclear. Reports are prioritized by public confusion risk, not by provider account urgency.
Evidence redaction check: Before sending supporting context, redact account identifiers, card numbers, bank screens, wallet addresses, identity details, and provider login pages. A compact public-page report is safer and easier to reproduce than a full private provider file.
Follow-up trace: When BTR updates a page, keep the reviewer action and follow-up page with the original report. The correction may appear in the affected guide, glossary, methodology, privacy policy, or this corrections history depending on what needed clarification.

Publication handoff

Correction publication handoff

Keep the affected URL, public impact, observed wording, redaction status, reviewer decision, history entry, and follow-up destination in one correction publication handoff. This gives a reviewer a clear route from a private report to a public page update without exposing provider-account material.

Public-impact route: Route the report by the public reader impact first: unclear reference-rate wording, missing fee boundary, stale example, privacy disclosure gap, or noindex/review-surface confusion. Private provider urgency does not decide whether a public correction is needed.
Redaction-status boundary: Record whether account identifiers, screenshots, wallet addresses, card details, identity data, and provider account pages were removed before review. A correction can cite the public issue without preserving sensitive material in the visible history.
History-entry stop: Stop the public note at the changed URL, the wording or behavior corrected, the reviewer decision, and the follow-up destination. Refunds, account access, provider support, tax decisions, and legal disputes remain outside the correction history.

Correction timeline record

A useful correction report separates the moment a reader noticed the issue from the moment BTR reviewed the page. Keep the observed date, affected URL, visible wording, expected clarification, reviewer action, and follow-up destination together so the correction history can explain what changed without exposing private provider records.

If a correction affects a guide, glossary definition, methodology note, privacy disclosure, or noindex boundary, the follow-up should point to the public page that now carries the clearer wording. This makes the update trace visible to readers and keeps review evidence separate from private support conversations.

What to report

A guide, glossary definition, or example is unclear or stale.
A page needs more provider, freshness, fee, or settlement context.
A link, form, mobile layout, or navigation path is broken.
A privacy, cookie, analytics, or advertising disclosure needs clarification.
A converter example could be confused with an executable provider quote.
A Romanian leu, crypto, or metals explanation needs a stronger reader warning.

Advertising separation

BTR Exchange may use AdSense code for publisher review and may show ads after approval, but ads, referrals, or future monetization must not affect methodology, guide conclusions, correction priority, or whether an error is fixed.

Provider categories are mentioned as comparison inputs. They are not endorsements, provider rankings, executable quotes, or promises that a bank, exchange, wallet, transfer app, card issuer, broker, or dealer will settle at the displayed reference.

For correction reports, include the page URL, amount or pair if relevant, timestamp, device, and the wording or result that should be reviewed.

How to contact us

Use the contact page for correction reports, unclear guide text, stale examples, or rate-display issues.

Read the rate methodology to understand source categories, fallback behavior, and limitations before reporting a rate interpretation issue.

Use the exchange-rate glossary when a term such as spread, provider quote, delivered amount, or BNR reference rate needs clearer wording.