Last updated: October 31, 2026
litecoin.watch does not require user registration or accounts. Reading public pages does not require a name or email address. Analytics, ordinary server logs and optional background alerts process the information described below.
We use Google Analytics to understand how visitors interact with the site — which pages are viewed, how long sessions last, and what devices are used. Google processes usage events and device/browser information under its own service terms and our analytics settings. Aggregate reports help us understand site usage; we do not describe all underlying analytics processing as anonymous.
Performance events (LCP, INP and CLS) report loading speed, interaction delay and visual stability to the same analytics service. They include the page path, device category and a per-measurement identifier used to combine updates. Our performance event payload excludes query strings, URL fragments and form values, and is disabled when Do Not Track or Global Privacy Control is enabled.
Help explanations use a separate first-party counter for opens and optional Yes/No feedback. It records daily totals for predefined page groups and term or field identifiers. Article views are grouped together. These requests exclude entered amounts, addresses, transaction IDs, notes, search text, URL queries and fragments, and use no cookies or visitor identifier. Feedback choices stay in page memory to prevent repeated votes during that view. Do Not Track and Global Privacy Control disable these counters. Counters older than 90 UTC days are removed when new counters are recorded. Ordinary hosting logs are described below.
Theme preferences, converter settings, portfolio transactions, saved mining scenarios, saved articles, recently opened article history and local price-alert targets are stored in your browser. The reading library also keeps your manually chosen read status and its change time, visit times and the last saved article section. Opening an article does not mark it as read. These records do not automatically sync between devices. You can export a JSON copy and preview a local import in another browser; reading-list files are read in that browser and are not uploaded to our server. The reading-list page lets you remove individual unsaved history or clear unsaved visits, read states and positions while keeping the history of saved articles. Editorial click events contain article identifiers, section names and tool destinations, not portfolio amounts, notes or form values. Optional historical FX lookups send a requested date to our server and rate provider, but not your holdings or transaction amounts. Optional background alerts are different: their targets and browser push subscription are sent to our server, and a device credential is retained in localStorage to manage them.
When you enable background alerts, we store your browser's push endpoint and encryption keys, a hashed management credential, target prices, currency, direction, creation and expiry times, and trigger/delivery status. A keyed hash of the connecting IP address is used to limit subscription abuse. We do not need your name or email address for Web Push.
Notification payloads are encrypted for the browser and relayed through its push provider, such as Google, Mozilla, Apple or Microsoft. The provider processes routing and delivery information. Your browser and operating system control permission and display behavior.
Targets expire after 90 days. Target records are removed no later than 90 days after expiry; browser subscription records inactive for 120 days are removed together with their targets. Expired or invalid subscriptions stop further alerts. Use the background-alert disconnect control to remove this browser's server records immediately. Disabling permission alone does not necessarily notify our server immediately.
A small local receipt cache prevents duplicate notification display. Clearing site data removes local credentials and receipt data but does not itself delete remote records; disconnect first where possible. Notifications already accepted by a push provider may remain in transit briefly.
The transaction checker sends a public transaction ID in a POST body to our server and then to Blockchair. It does not put that ID in a page URL or keep browser search history. Our server caches the status summary and up to 200 public input and 200 public output records, including reported addresses and amounts, for two minutes and uses a daily keyed IP hash for rate limiting. Expired cache entries and old counters are removed during subsequent lookups. Ordinary hosting logs may still record visits. The checker does not load Google Analytics or request wallet recovery material.
The payment-request generator checks addresses, creates QR codes and reconciles entered amounts locally. It does not send addresses, invoice references or amounts to a QR service or analytics. Downloaded files and copied payment links contain the details you enter, so share them deliberately. These tools do not connect a wallet or send a payment.
Batch payment CSV files are read and reconciled in the current browser page. Their contents are not uploaded, sent to analytics or saved in localStorage. Clearing the batch removes the selected files and results from the page; reports you downloaded remain on your device.
The chart-reading lab uses a published frozen price sample. The wallet migration planner uses published recovery evidence and accepts only choices about wallet software and backup formats; it has no field for recovery words, passwords or private keys and does not load Google Analytics. The invoice clock uses fictional payment events. Calculations and choices in these tools remain in page memory and are not uploaded or saved between visits. A download is created locally and contains the selected plan or scenario. General page visits and local recent-tool history follow the practices described above.
Our confirmation-time study samples publicly relayed transaction IDs through our own Litecoin Core node. The rolling export contains transaction IDs, observation times, outcome states and confirming block references. It contains no visitor-submitted addresses or invoice records. Cohort records are retained for seven days, with hourly database cleanup; downloaded public copies can persist separately.
Our web server automatically records standard access logs (IP address, browser type, pages requested, timestamps). These logs are used for security monitoring and performance analysis and are retained for a limited period.
Cookies on litecoin.watch are used strictly for session management and usage analytics (Google Analytics). We do not use cookies for behavioral advertising, profiling, or remarketing.
The site uses our own data endpoints and some third-party services for market data, fonts, analytics, charts and optional push delivery. Direct browser requests disclose connection information, such as an IP address, to the receiving provider. If you follow links to external sites, please review their privacy policies as we are not responsible for their data practices.
We do not sell user information. Service providers receive the information needed for the features described above, including analytics and optional notification delivery.
All data transmissions are protected using SSL/TLS encryption. We follow standard security practices to protect our infrastructure and any data we process.
You have full control over your privacy when using our site. You can clear localStorage data through browser settings. For background alerts, disconnect first if you want immediate deletion of the corresponding server records. You can block cookies or opt out of Google Analytics using browser extensions. If you have questions about your data, contact us at the address below.
We may update this policy from time to time. Significant changes will be announced on this page with an updated revision date.
By using litecoin.watch, you acknowledge and agree to the terms outlined above.
