Reader privacy
Duel Privacy Notice
Reading the independent Duel information guide does not require a reader account or the submission of personal details. The interactive transfer-friction checker on the home page processes its inputs locally in the browser and does not send or save those values.
- Reader accountNot required
- Tool processingLocal in browser
- Tool storageNot saved
- HostingStandard logs may exist
Ordinary reading does not require a personal profile
The guide is an information resource rather than a reader-account service. A visitor can move through the main Duel review, payment guides, game guides and technical notices without creating a profile for the guide itself.
No forms, analytics or reader accounts are used by the guide. That keeps the reading path simple: the content is available without asking a visitor to provide a name, email address, phone number or similar profile details.
Editorial reading
Articles can be opened directly and followed through ordinary internal links.
No reader profile step
The guide does not require registration before its informational material can be read.
Technical notices stay connected
The cookie notice describes browser storage behavior, while the about section explains the guide's editorial role.
The transfer-friction checker keeps entered values in the browser
The home-page transfer-friction checker lets a reader enter a transfer amount, a network fee, an optional external service fee and a target fee percentage. Those values are used only to calculate the current net amount, total entered fees, fee burden and target transfer size.
The calculation runs entirely in the browser. The checker makes no network request with the entered values, does not use those values to identify the reader and does not save them for a later visit.
| Input or result | How it is handled |
|---|---|
| Transfer amount | Used locally to calculate the current result |
| Network fee | Entered by the reader and processed locally |
| Optional external fee | Entered by the reader and processed locally |
| Target fee percentage | Used locally to calculate the target transfer size |
| Calculated result | Displayed in the page and not saved by the checker |
Hosting infrastructure may record standard server logs
As with an ordinary website, the infrastructure that serves a requested page may maintain standard server logs associated with that request. Those technical logs are separate from the transfer-friction checker's local calculations.
The distinction is useful because a page request and an interactive calculation are different activities. Loading an article reaches the hosting infrastructure; changing a fee input inside the checker does not cause the checker to transmit that value elsewhere.
- Page request
- May be represented in standard hosting logs.
- Checker input
- Processed locally in the current browser page.
- Checker result
- Displayed locally and not stored for a later visit.
Browser controls remain the practical place to manage site data
A reader can use the browser's own privacy and site-data controls to inspect or clear data associated with websites. The companion cookie notice describes the guide's cookie and storage behavior in more detail.
These controls are also useful when a device is shared. Clearing site data, closing private information in open tabs and ending a browser session can reduce the chance that another device user sees material left on screen.
- Use browser privacy controls when reviewing stored site data.
- Close gambling and wallet-related tabs on a shared device.
- Avoid entering sensitive wallet information into fields that do not require it.
- Remember that the transfer-friction checker needs amounts and fees, not private keys or recovery phrases.
- Review the browser's site-data controls if you want to inspect or clear local website data.
- Use the cookie notice to understand which storage mechanisms this guide itself uses.
- Keep wallet credentials outside informational calculators and ordinary article fields.
The privacy model is intentionally narrow
The guide can be read without a reader account, while the transfer-friction checker keeps its inputs and results local to the browser and does not save them. Standard hosting logs may still exist when pages are requested, which is distinct from the checker's own behavior. That separation keeps the interactive feature useful without turning it into a data-collection flow.






