Privacy notice
Last updated:
This notice explains the data processing and browser storage currently implemented by CoinETF. It covers the CoinETF screen and server; external services have their own policies.
Preferences stored in your browser
Favorite and comparison ETF tickers and your language, currency and theme are stored in this site's localStorage for return visits. Enabled price-alert settings are also stored only in this browser. Alerts are checked only while the page is open; enabling notifications requests browser permission and does not provide server push. Preferences do not automatically sync across devices or browsers and are not stored in a CoinETF visitor account database.
Clearing saved preferences
Remove this site's site data or local storage in your browser settings to clear favorites and display preferences. They will return to their defaults. This does not also delete the hosting service's authentication data or request logs.
Sign-in and access checks
Public prices do not require sign-in. Administrator functions require the hosting account and administrator password. The server verifies a password against a verifier stored in secret settings, without storing its plaintext, and uses a secure administrator session cookie. Visitor profiles and account-based favorite storage are not provided.
First-visit language
At the entry URL without a language, the hosting platform's approximate country and the browser language suggest a display language. This feature does not separately store raw IP addresses or send them to an external geolocation service. VPNs and networks may produce an inaccurate location. Explicit language URLs and saved language choices take priority.
Google advertising
Public price pages may load Google AdSense code to connect the real publisher account and request site review. Even before approval or without a visible ad, Google and its partners may process IP addresses, cookies or similar storage for ad delivery, measurement and fraud prevention. Manual ad units require separate activation; Auto ads depend on the AdSense account settings. This is separate from the site's aggregate visitor statistics.
Google ad code remains disabled for the EEA, UK, Switzerland and unknown locations until the required certified consent-management setup is ready. Global Privacy Control or Do Not Track signals in the web request block code loading; manual ads also check these browser signals. See Google's data use and ad-personalization settings below.
Connection information and external services
Hosting and authentication services handling web requests may process or record IP addresses, request times and browser information for operation and security. Actual fields, retention and operator access depend on their policies and settings. This notice does not promise an unverified retention period or deletion deadline.
Price queries are handled by the collection path so the browser does not receive provider secret keys. Opening an external product document can expose connection information to that external site. Font files are served by this site.
Audience statistics and return visits
The following collection and retention description concerns CoinETF's own statistics. Google Analytics 4 (GA4) and Cloudflare Web Analytics are described separately. For site operation and usage analysis, we count page views, predefined actions, approximate connection countries and new or returning sessions. We store no analytics identity cookies, browser IDs, device fingerprints, raw IP addresses, full referral URLs or typed content. Global Privacy Control, Do Not Track, exclusion preferences, marked review visits and recognized automation suppress statistics.
Acquisition analysis stores only predefined search engine or community categories and aggregate counts for public landing pages. Full referral URLs, original search queries and arbitrary campaign values are not stored. Direct entries and entries with no available source are grouped together; entry counts are not exact people counts.
New and returning sessions are estimated within 30 days from a truncated network prefix (IPv4 /24, IPv6 /48), hashed with a server secret. This is limited pseudonymous network state, not an anonymous personal identifier. Shared networks may merge visitors and address changes may split them. These are not exact people counts. A new session starts after 30 minutes of inactivity.
Recognition state expires 30 days after its last activity; daily deduplication records cover 30 days and aggregate counters cover 90 days. Legacy daily visit hashes cover today and yesterday. Expired records are pruned on the next write or read. Only administrators can view detailed aggregates. Raw addresses and individual action histories are not stored. New metrics start when enabled; prior return visits are not reconstructed.
Page views, predefined actions and visit sessions are also counted in hourly aggregates retained for 90 days. These aggregates do not store individual arrival times or action histories. Administrator visit statistics use Korea Standard Time (KST, UTC+09:00), regardless of the selected language. Archive timestamps explicitly labelled UTC use UTC separately.
The retention rules above apply to CoinETF's own counters. Public-page visits and loading performance are also sent to Cloudflare Web Analytics. It uses no analytics identity cookies and separately aggregates page paths, referrers, approximate countries, device types and performance. It does not run on administrator pages; marked reviews, exclusion preferences, GPC and DNT are checked before loading. Ad blockers may prevent some visits from being counted.
Website analytics settings
If allowed, Google measures page use, contact-link clicks, cookies, browser identifiers, device and approximate region. Prices and charts work if you decline.
Google's SDK may process IP addresses and standard session/engagement events. We send only public canonical page paths, without queries, fragments, email, message content, search terms, holdings or user_id. A contact click is not a sent email.
Local permission and analytics cookies last 90 days. The verified Google web property is set to 2 months for events and 14 months for users, resetting user retention on new activity. This is not a deletion deadline for all standard aggregated reports.
Withdrawing stops analytics now and attempts to clear known analytics cookies. If the denial is saved, the page reloads when needed and analytics does not resume without new permission. A storage failure is reported separately. Data already sent is not retroactively deleted.
Separate from advertising consent. You can withdraw in Privacy at any time.
Metricool statistics settings
Anonymous aggregate statistics are enabled by default to understand visits to public pages. You can stop or resume them here. Google Analytics and advertising settings remain separate.
Eligible public page and referring page addresses, viewport size and connection information including IP are sent to Spain-based Metricool. Addresses containing queries or fragments and private paths are excluded. Metricool states that it uses no tracking cookies or device identifiers and does not store IP addresses. We do not combine these aggregates with GA4, login accounts, advertising or personal social profiles. Visits from the EEA, UK, Switzerland and undetermined countries are excluded. Do Not Track, GPC and review-traffic exclusions also apply.
Default aggregation does not save a permission record. Selecting ‘Use statistics’ in settings saves that choice on this device for 90 days; a stop choice may remain longer. This is not a deletion deadline for Metricool’s aggregated reports.
Existing stop choices are preserved. You can stop or resume statistics at any time in Privacy. Stopping prevents future requests and reloads the page when needed. Data already sent cannot be recalled.
Email inquiries
Operated by: Independent CoinETF operator
If you email the public contact address, we process your sender address, a name if you provide one, your message and any files you voluntarily attach. We use this information to reply, investigate errors and improve the service.
Cloudflare Email Routing forwards contact messages to the operator's external email service. Routing and mailbox services are subject to the respective providers' privacy policies. The private destination mailbox address is not published on the site.
We retain inquiry records as needed to handle the inquiry and follow up on it. You may send requests about your inquiry data, including correction or deletion, to the public contact address. Please do not send unnecessary sensitive information such as brokerage account details, passwords or API keys.