Send rate-display reports, guide corrections, methodology questions, privacy questions, or technical issues that affect the BTR review surface. Include the page URL, currency pair, timestamp, and device details so we can reproduce the issue and decide whether a public correction is needed.
Do not send full account numbers, card numbers, wallet seed phrases, private keys, identity documents, bank login credentials, or unredacted provider screenshots. If a bank, card issuer, exchange, wallet, transfer provider, or dealer screen helps explain the issue, redact names, account identifiers, balances, transaction IDs, wallet addresses, and any document details before contacting BTR.
BTR cannot unlock third-party accounts, reverse transfers, settle disputes with a provider, quote a guaranteed exchange price, approve a payment, recover wallet access, or provide personalized financial, tax, investment, legal, or accounting advice. Those cases should go directly to the responsible provider or qualified professional.
Use corrections for public page updates, methodology for source or calculation questions, privacy for consent and contact-form handling, and this form for reproducible site behavior.
BTR Exchange prioritizes reports that affect how readers understand reference rates, provider quotes, fee examples, privacy controls, correction history, or page accessibility. The goal is to fix confusing public information first, then document meaningful content updates through the corrections process.
Report a conversion result, fee/spread calculation, freshness label, provider status, or noindex review boundary that appears wrong or confusing.
Flag unclear guide wording, stale examples, missing source context, glossary definitions that need plain-language edits, or methodology copy that needs more precision.
Ask about Google services, the privacy choices control, contact-form data handling, or a public page that should explain privacy behavior more clearly.
The most useful reports separate public page evidence from private provider account details. Send enough context to reproduce the public issue, then redact anything that belongs only to you, your bank, card issuer, wallet, exchange account, transfer provider, accountant, or identity document.
Use this when a converter amount, fee/spread result, freshness label, or provider-status note appears wrong. Keep the page URL, timestamp, visible rate, expected result, actual result, device context, and redaction note together so the report can be reproduced without exposing private account data.
If a screenshot would help, summarize the visible issue first and remove names, balances, transaction IDs, account numbers, wallet addresses, card details, identity documents, and login screens before sending anything to BTR.
Tell us whether you expect a wording clarification, stale example update, source-note correction, calculator behavior fix, privacy copy update, or public correction-history entry. BTR will review the public page, not settle the underlying provider transaction.
Keep the contact reason, affected URL, public symptom, private-data redaction, requested outcome, and follow-up route in one contact record. That keeps a useful public-page report separate from a private provider dispute BTR cannot settle.
Use this route when the BTR page itself may be stale, unclear, inconsistent with methodology, missing a correction link, or confusing a reference value with an executable provider quote.
Keep provider account disputes, chargebacks, frozen accounts, wallet recovery, bank approvals, card reversals, tax treatment, and legal advice with the responsible provider or professional.
If BTR changes a public page, the correction path should identify the affected URL, explain the wording or behavior changed, and keep private sender details out of the public update history.
Keep the contact reason, page URL, reporter-safe evidence, redaction status, unsupported provider issue, escalation route, and expected public follow-up in one contact escalation record. This makes the report actionable without turning the contact form into a provider-support queue.
Start by deciding whether the evidence belongs to a public BTR page, a private provider account, a privacy request, or a technical delivery problem. BTR can verify public page behavior and wording, but it cannot use private provider screens as public proof without redaction.
If the issue requires a bank, card issuer, wallet, exchange, transfer provider, dealer, tax adviser, accountant, or legal professional, keep that escalation outside BTR. Send BTR only the redacted public-page symptom and the route where the reader should be redirected.
When BTR can act, the expected result should be a public wording clarification, correction-history note, methodology update, privacy-copy adjustment, or product bug fix. Private account disputes remain with the responsible provider.
Keep the contact channel, affected URL, public evidence, redaction state, unsupported provider request, correction destination, and expected public outcome in one contact intake handoff. This turns the contact form into a public-site review route instead of a queue for private provider disputes.
Use the affected BTR URL, visible heading, public rate or wording, device context, and timestamp as the route into a report. That evidence lets BTR review what any reader can see without depending on private provider records.
Stop before attaching full bank screens, card statements, provider account pages, wallet addresses, identity files, or transfer receipts. Summarize the private context and send only redacted evidence that explains the public page issue.
If a report changes public guidance, the follow-up path is the affected page, the corrections history, or the methodology note. If the issue belongs to a provider account, the contact record should say that the provider remains responsible.
Contact messages are reviewed for correction value, privacy impact, and reproducible site behavior. We do not treat the contact form as financial advice, transaction support, account recovery for third-party providers, or a place to send private banking, card, wallet, exchange, tax, or identity-document data.
We check the submitted URL, amount, currency pair, device context, and timestamp against the current public page and available provider context.
We decide whether the issue is a data-source limitation, a stale example, unclear guide wording, a privacy disclosure gap, or a product bug.
If the report changes how readers should interpret a reference rate, fee example, privacy choice, or limitation, we update the page and correction history.
For general site support, accessibility problems, contact-form delivery issues, or reports that need attachments, please reach out by email.
support@btr.roFor unclear guide text, stale examples, methodology questions, or data-display issues, read the public corrections process and send the page URL plus the exact section we should review.
business@btr.roWe aim to respond within 24-48 business hours. For rate or content corrections, include the currency pair, timestamp, and whether the problem appeared on the homepage, embed, guide, or SEO conversion page. Read our corrections and content updates page and our methodology policy for how these reports are prioritized.