Last updated: 2026-05-16

Privacy Policy

How TapeFlow handles privacy, cookies, ads, logs, and third-party infrastructure.

Key summary

  • TapeFlow currently has no accounts, payments, comments, newsletters, or portfolio storage.
  • Access logs, device data, IP addresses, browser details, ad cookies, and security logs may still be processed by the site and its infrastructure providers.
  • When Google AdSense is enabled, Google and advertising partners may use cookies or similar technologies for ad delivery, measurement, frequency capping, and fraud prevention.

1. Information processed

  • Request data such as IP address, timestamp, URL, referrer, user agent, operating system, device type, and language.
  • Infrastructure logs from hosting, CDN, database, and server-rendering providers.
  • Ad-related identifiers and events used by Google AdSense and advertising partners.
  • Market-data requests created by indicator pages, chart range changes, and history loading.
  • TapeFlow first-party code does not currently use localStorage or sessionStorage, but AdSense or a consent tool may use cookies or local storage.

2. Purposes

  • Provide market indicators, charts, radar screens, and source links.
  • Detect abuse, outages, suspicious traffic, and ad fraud.
  • Operate caching, CDN delivery, server rendering, and database reads.
  • Display AdSense ads and support measurement, fraud prevention, and personalized or non-personalized ads.

3. AdSense and consent

TapeFlow loads the Google AdSense script when advertising is enabled. For users in the EEA, UK, and Switzerland, TapeFlow applies consent-management steps required by Google policy and applicable local law.

  • Non-personalized ads may still require cookies for frequency capping, reporting, and fraud prevention.
  • TapeFlow must not pass directly identifying information such as emails, phone numbers, government IDs, or account numbers to Google ad requests.
  • Users can manage some ad personalization through Google ad settings, browser settings, and any deployed consent-management interface.

4. Third-party services

  • Cloudflare for hosting, caching, CDN, and security.
  • Supabase for public market-data storage and database reads.
  • Google AdSense for advertising.
  • Market-data sources including KRX, KOFIA, Stooq, Cboe, Naver Finance, and TradingView.

5. Retention and rights

TapeFlow does not currently maintain user account profiles. Infrastructure, security, ad, and request logs are retained according to each provider's configuration and policy. Market data may be retained long term to provide historical charts.

  • Users may clear or block browser cookies.
  • Users may adjust Google ad personalization settings.
  • Where a CMP is deployed, users may revisit privacy and cookie settings to withdraw consent.
  • Operational privacy contact: anc5557@naver.com

6. Security and policy compliance

  • TapeFlow reviews legal, advertising, cookie, security, and data-provider requirements as the service changes.
  • Third-party infrastructure and advertising services operate under their own policies, and users can limit some tracking through browser and ad settings.
  • This policy will be updated when legal requirements or service architecture materially change.

Revision history

Pre-deployment legal baseline

Version 2026-05-16.1 · 2026-05-16

Prepared the Privacy Policy, Terms of Use, Data and Investment Risk Disclosure, Data Sources and License Notice, and Contact page as the deployment baseline.