Overview
Japanese Bot (“we”) built this policy so you know what telemetry leaves your device when you study our tickets. We aim for minimal collection and zero broker account access.
Data categories
Collected automatically
- • User-agent string and coarse device class
- • Approximate timezone (for countdowns and copy)
- • Route hits and feature toggles (aggregated analytics if enabled)
- • Diagnostic logs when something crashes server-side
We deliberately skip
- • Government IDs or passport scans
- • Broker passwords, API secrets, or wallet seeds
- • Clipboard scraping beyond what you paste into forms
- • Selling visitor lists to ad networks
Cookies & local storage
We rely on a tiny footprint:
- • Strictly necessary: keeps SSR pages and security headers functional
- • Preferences: optional dark/light theme and similar UI memory live in
localStorage
Use of information
- ✓ Keep countdowns aligned with your clock
- ✓ Debug latency and cache issues
- ✓ Spot abusive traffic patterns
- ✓ Improve copy and layout based on aggregate behavior
Processors & vendors
- • Massive.com — wholesale FX & CFD-style quote feeds
- • Vercel — edge hosting, TLS termination, and serverless workers
No behavioral ad auctions. If we add analytics, this section will name the vendor explicitly.
Your controls
- • Email us to ask what we store about a given inquiry
- • Request deletion of support-ticket content
- • Clear site data in your browser to wipe local preferences
- • Open a thread on /contact for privacy escalations
Talk to us
Privacy-specific notes belong on the contact page so we can route them correctly.