Privacy while reading and using the MetaWin reference
Section element
PRIVACY
The site is an informational reference. Reading it does not require an account or the submission of personal details, and the interactive withdrawal-threshold checker on the homepage processes the values you enter directly in your browser.
Reading
The reference can be read without creating a user profile or submitting personal information.
Interactive checker
The withdrawal-threshold checker compares your entered scenario with its route rules inside the browser.
Hosting layer
As with any website, hosting infrastructure may keep standard server logs needed to deliver and protect the service.
Reading the reference does not depend on a personal account
The site is designed as a public informational guide. You can move between the about page, topic guides and legal notes without signing in or creating a profile.
There are no forms, analytics systems or reader accounts on the site. That keeps the normal reading experience focused on the content itself rather than on building a reader profile.
The withdrawal-threshold checker works locally in your browser
The homepage includes an interactive withdrawal-threshold checker. You enter an amount and choose a withdrawal route, and the checker compares that scenario with the stated route minimum used by the tool.
- You enter a withdrawal amount in the checker.
- You choose the custodial or Web3-wallet route.
- The browser compares the amount with the route threshold.
- The result appears immediately on the page.
The values are processed locally in the browser. They are not sent elsewhere and are not stored for later visits.
| Interaction | Where it happens | Persistence |
|---|---|---|
| Amount entry | In your browser | Not stored between visits |
| Route selection | In your browser | Not stored between visits |
| Threshold result | Calculated in your browser | Displayed for the current interaction |
The related payments section explains the actual withdrawal context behind those route minimums, while the checker remains a quick scenario test.
Hosting may create standard server logs
As with any website, the hosting layer may keep standard server logs as part of delivering pages, handling errors and protecting the service. These records are part of normal website infrastructure rather than the withdrawal-threshold checker.
Reader-facing interaction
- Open a page
- Follow an internal link
- Use the homepage checker locally
Infrastructure context
- Hosting can record routine request information.
- Such records can support delivery, reliability and abuse prevention.
- The checker itself does not transmit its input values.
Keep gambling-account details out of general browsing contexts
This reference does not need your MetaWin login, wallet keys, seed phrase or account credentials. When moving from informational pages to any gambling service, keep authentication details inside the service you intend to use and never paste a wallet seed phrase into an unrelated page.
- Use wallet and account credentials only where you intentionally authenticate.
- Treat seed phrases and private keys as secrets that should not be shared.
- Check destination addresses carefully before any blockchain transfer.
- Use the cookie and storage note for the site-wide storage policy.
Reading stays simple, and checker input stays in the browser
The privacy model is straightforward: the reference can be read without a reader account, the withdrawal-threshold checker processes its values locally, and ordinary hosting infrastructure may still produce standard server logs.
