Privacy Policy

1. Introduction

Welcome to BTR Exchange ("we," "our," or "us"). We are committed to protecting your privacy and ensuring transparency in how we handle your information. This Privacy Policy explains how we collect, use, and safeguard data when you visit our website, btr.ro.

2. Information We Collect

We do not require user accounts or personal registrations to use our currency conversion tools. However, we may collect certain information automatically:

• Usage Data: Information about how you use our site, such as pages visited and time spent.
• Device Info: IP address, browser type, and operating system for optimized delivery.
• Cookies: We use cookies to remember your currency preferences and for analytics.
• Contact Form Data: If you send a message, we process the name, email address, message, and optional page context you provide so we can reply and investigate the issue.

3. Data we do not collect

BTR does not ask for bank credentials, card numbers, wallet seed phrases, private keys, exchange account passwords, or identity documents. The website does not create visitor accounts, hold balances, execute transfers, process trades, or request payment credentials for conversion tools.

If a reader needs to report a provider quote, bank screen, card statement, wallet transaction, or transfer receipt, they should summarize the visible rate, fee, timestamp, and provider name instead of sending private documents or account screenshots.

4. Contact-form handling

Contact messages are used to reply, reproduce the report, and decide whether a public correction is needed. A message may include the submitted name, email address, page URL, optional context fields, and the report text.

Correction reports may lead to public page updates, but we do not publish the sender's name, email address, private provider details, or sensitive financial information as part of a correction note.

5. Third-Party Services

We use third-party services to enhance our platform and provide monetization:

• Google AdSense: We include Google AdSense code for site review and, when ads are enabled, to serve advertisements. Google and its partners may use cookies, web beacons, IP addresses, and similar identifiers to place and read cookies or collect information as a result of ad serving on this website.
• Google Analytics: We use analytics to understand traffic patterns and improve our financial tools. Analytics may process device, browser, page, referrer, and event information.
• API Providers: Financial data is sourced from market data providers; no personal data is shared with them.

Learn more about how Google uses data from partner sites at Google's partner-sites disclosure page.

6. Advertising, Cookies, and Choices

Ad technology may use cookies or similar identifiers to deliver, measure, and protect ads. Depending on your location and Google settings, ads may be personalized or non-personalized. You can manage Google ad personalization through your Google account and browser settings.

BTR starts Google ad and analytics storage in a denied state and shows a privacy choices control so you can accept or reject that storage on this browser. If you change your mind later, use the privacy choices button to reopen the controls.

BTR Exchange does not ask visitors to create accounts and does not intentionally send personally identifiable information to Google ad systems. Do not include sensitive personal or financial details in contact form messages.

7. Google services during AdSense review

During AdSense review, BTR keeps the Google publisher script available so Google can verify the site, but visible ad units remain off until approval. Google ad and analytics storage starts denied until a visitor makes a privacy choice in this browser.

Advertising setup, Analytics measurement, or future referral links do not change correction priority, methodology wording, guide conclusions, or whether a reader-reported privacy issue is fixed.

8. Privacy choices checklist

Keep the page URL, browser, consent choice, message date, requested action, and redaction note together when sending a privacy request. This helps BTR separate a website privacy issue from a provider account issue or a browser-level Google setting.

• Contact report redaction: When a privacy question is connected to a rate, provider quote, card statement, wallet transaction, bank screen, or transfer receipt, summarize only the public page behavior and redact account numbers, wallet addresses, identity details, screenshots, and provider login information before sending a message.
• Google storage choices: The privacy choices control affects Google ad and analytics storage on this browser. If you are checking a consent issue, note whether you accepted, rejected, cleared browser storage, changed devices, or used private browsing before reporting the result.
• Correction and deletion requests: For a contact-message correction, deletion, or access request, identify the message date, email address used, page URL or topic, and requested action. BTR can review contact-form records and public correction notes, but it cannot change records held by banks, wallets, card issuers, exchanges, transfer providers, Google, or other third parties.

9. Privacy request record

Keep the privacy topic, page URL, browser state, consent choice, message date, redaction note, and requested action in one privacy request record. This gives BTR enough context to review a site privacy issue without receiving private financial documents.

• Consent-state check: When the concern is about Google storage, analytics, AdSense review code, or the privacy choices control, record the browser state before changing it. Note whether storage was accepted, rejected, cleared, blocked by browser settings, or checked in private browsing so BTR can separate a site issue from a local browser setting.
• Message-record boundary: When the concern is about a contact message, identify the message date, email address used, page URL or topic, and requested action. Do not attach bank screens, card statements, wallet screenshots, identity documents, or provider account pages when a short redacted description is enough.
• Google and provider data boundary: BTR can review public page wording, contact-form handling, and first-party privacy choices. It cannot access, correct, delete, or export records inside Google accounts, banks, wallets, exchanges, card issuers, transfer providers, or metals dealers.

10. Privacy response handoff

Keep the privacy topic, consent proof, page URL, contact record, redaction status, third-party data boundary, and requested response in one privacy response handoff. This keeps privacy support focused on public BTR behavior and avoids collecting sensitive financial records.

• Consent-proof route: For a consent issue, keep the public page URL, browser state, accepted or rejected storage choice, banner visibility, and expected result together. This lets BTR test the site behavior without asking for private Google account settings.
• Contact-record boundary: For a contact-form request, identify the message date, email address used, affected public page, requested action, and redaction status. Do not attach bank, wallet, exchange, transfer, card, or identity records when a short message reference is enough.
• Third-party data stop: BTR can correct its public privacy wording and first-party contact handling. It cannot access, export, delete, or change data held by Google, banks, card issuers, wallets, exchanges, transfer providers, analytics systems, or metals dealers.

11. Consent troubleshooting record

If a visitor reports that the privacy choices banner, Google consent state, Analytics behavior, or AdSense review code appears unclear, BTR reviews the public browser behavior rather than asking for account-level Google settings. A useful report includes the page URL, whether the visitor accepted or rejected storage, whether browser storage was cleared, and whether an extension or private browsing mode may have blocked scripts.

Keep the consent choice, browser state, affected page, visible banner state, expected result, actual result, and redaction note in one consent troubleshooting record. This helps BTR correct public privacy wording or script behavior without collecting sensitive financial data or private Google account screenshots.

12. Data Security

We implement industry-standard security measures to protect the integrity of our site and any data collected. However, please be aware that no transmission over the internet is 100% secure.

13. Your Rights

Depending on your location (e.g., GDPR for EU residents), you may have rights regarding your data, including the right to access, correct, or delete information. Since we do not store personal profiles, these rights typically apply to cookie-based identifiers.

14. Contact Us

If you have any questions about this Privacy Policy, please contact us through the contact page or at legal@btr.ro.