# Japan External Transmission Disclosures - **URL**: https://routeflick.com/japan-disclosures --- Last updated: 1 October 2026 95 Info Services, India operates RouteFlick. This page identifies measurement recipients, the information transmitted and its purpose. It distinguishes current measurement from prepared or currently inactive destinations; it is not a certification of compliance with Japanese law. ## 1\. Google Analytics 4 Recipient: Google. Core event collection goes through RouteFlick's server-side Google Tag Manager at sgtm.routeflick.com; the library loads from googletagmanager.com and may make auxiliary Google requests receiving HTTP technical metadata under Google's policies. Purpose: understand eligible public-page visits and bounded marketing interactions. Current Basic Mode loads the tag only after analytics acceptance. Application event fields: publication-owned page path/title, event name, bounded public content ID and analytics client/session information when consented. These fields exclude account IDs, email, query strings and user trip contents; not every library request is proxied through server GTM. Prepared regional Google mode is disabled by default. If separately activated, Opt-in Regions, including the UK and Switzerland, deny analytics storage until acceptance; Default-on Regions start storage granted, including unknown-country arrivals. Google may receive limited cookieless pings before acceptance and after Reject. One shared GA4 property is used. This does not establish a legal exemption. Anonymous-studio and funnel collection needs its separate release verification. ## 2\. Cloudflare Web Analytics Recipient: Cloudflare. Purpose: website usage and page-load performance measurement. Cloudflare describes a JavaScript beacon collecting page-view and performance metrics and says it does not use cookies or localStorage for usage measurement. The separately enabled beacon on routeflick.com may run before a Google choice and after decline; it is not controlled by Privacy Choices. It is not part of the Google consent controller. ## 3\. Advertising destinations -- currently inactive - Google Ads -- currently inactive; proposed server-side conversion measurement requires destination and consent validation before activation. - Meta (Facebook / Instagram) -- currently inactive; no Meta browser pixel is installed by this release and no Meta CAPI destination is enabled. - TikTok -- currently inactive; no TikTok browser pixel or Events API destination is enabled by this release. Recording an advertising preference does not activate these recipients. Proposed future hashed-email or click-ID matching needs separate review, verification and revised disclosures; hashes are not anonymous data. ## 4\. Purchases and your choices Purchase reporting is currently inactive. Dodo still processes payments and RouteFlick keeps financial receipts and service activity. The proposed future stripped Dodo purchase report to advertising recipients despite denied ads permission or Global Privacy Control is not active or verified as acceptable to those recipients. Privacy and provider review are required before activation, with no historical backfill. Use the footer Do Not Sell or Share / Privacy Choices control for current Google preferences, or contact support@routeflick.com. See also:[Privacy Policy](https://routeflick.com/privacy)[Terms of Service](https://routeflick.com/terms)[Refund Policy](https://routeflick.com/refund)