# Privacy Policy - **URL**: https://routeflick.com/privacy --- Last updated: 17 October 2026 RouteFlick is operated by 95 Info Services, India ("we", "us"). This Privacy Policy explains what information we process when you use routeflick.com, why we process it, and your choices. It distinguishes current services from a prepared regional measurement release that is disabled by default. [7\. Your rights and account deletion](https://routeflick.com/privacy#account-deletion) ## 1\. Information we collect We collect only what we need to run the service: - Account data -- your email address (and an authentication token) when you create an account, handled by our authentication provider. - Trip data -- the routes, stops, styling and settings you create. These are stored so you can return to them across devices. - Media you add -- photos and audio you attach to a trip. Photos are downscaled in your browser; media is stored privately and only accessible to your account. - Support messages -- if you contact us, the message, your email, and basic device info (browser, plan, and -- only if signed in -- the current trip) so we can help faster. - Cancellation feedback -- if you cancel a paid plan and choose to tell us why, the reason you pick and any comment you add (up to 500 characters), stored with our support messages so we can understand why people leave and improve RouteFlick, and also passed to our payment processor with the cancellation. We keep our copy until you delete your account, and deleting your account deletes it; the copy our payment processor received is kept under its own retention policy. - Payment data -- if you buy a paid plan, our payment processor handles your card details. We never see or store full card numbers; we receive only a transaction reference and your plan status. - Render activity -- when you export a video we record that a render finished, with its quality, frame rate, aspect ratio and the length of the video. This is how we understand how RouteFlick is actually used. Your trip, your route, your place names and the video file itself are never part of this record. - Your last render -- if you are signed in, the trip you most recently rendered and a small still frame from that video are saved to your account, so you can pick that render back up on another device. The video file is not uploaded. - Usage -- minimal technical logs (e.g. error reports) needed to keep the service reliable. ## 2\. On-device by default RouteFlick renders your video in your browser -- your footage is not uploaded to a render farm. Photos and audio are stored locally (in your browser) first, and only synced to our private storage when you save a trip to your account so it follows you across devices. When a render finishes we record the fact that it did, with its settings and length, so we can see how the app is used; that record holds no trip content and no part of the video. Separately, if you are signed in, we also save the trip you just rendered and a small still frame from it to your account, so the studio can offer that render back to you on another device. The video file itself is never uploaded. ## 3\. How we use information - To provide the service -- save and load your trips, render and export videos, and apply your plan's entitlements. - To support you -- answer questions and troubleshoot issues you report. - To process payments -- via our payment processor, and to apply the correct plan. - To keep the service secure and reliable -- prevent abuse and fix errors. - To understand how the app is used -- counts and settings of the videos people export, so we can decide what to build next. - To send essential service emails (e.g. account, support replies, receipts). We do not send marketing email without your consent. ## 4\. Service providers We share data only with vendors that help us operate, under their own terms: - Hosting, database and storage (our backend provider) -- account, trip and media data. - Payment processing -- to take payments and manage plans. - Email delivery -- to send transactional and support emails. - Google Analytics 4 -- configured public-page event collection is delivered through RouteFlick's server-side Google Tag Manager at sgtm.routeflick.com. The current Basic Mode requires analytics acceptance. Application event fields exclude account IDs, email, trip contents and query strings. The Google library loads from googletagmanager.com and can make auxiliary requests to Google, which receive HTTP technical metadata under Google's policies; not every library request is proxied through our server GTM. - Cloudflare -- website delivery, security and separately enabled Cloudflare Web Analytics, described below. This is separate from Google Analytics and our consent controller. Google Ads, Meta and TikTok advertising destinations are not enabled by this release. Their proposed future use requires separate verification and updated disclosures before activation. Financial receipts and service activity records remain part of operating your account, not advertising events. ## 5\. Cookies & local storage Essential storage keeps the app working: an authentication token to keep you signed in, your theme preference, and in-browser storage (IndexedDB) that holds media locally so exports are fast and offline-capable. These are always on because the app needs them. Current Google measurement (Basic Mode): Google's browser tag loads only after you accept analytics and sends eligible public-page views and bounded marketing interactions to our server-side GTM endpoint, not directly to GA4. The current mode does not measure studio, account, Admin or shared-trip pages. Decline or withdrawal stops this Google measurement; Do Not Track and Global Privacy Control also prevent it in Basic Mode. Google may use analytics cookies after acceptance. Your Basic choice is stored locally as rf-consent until you change it or clear browser storage. Use the footer Privacy Choices control or Analytics preferences on this page to change it. Prepared regional Google mode -- disabled by default: if separately activated, analytics storage remains denied until acceptance in Opt-in Regions, including the EU/EEA, India, the UK and Switzerland. In Default-on Regions it starts granted until you change your choice; a missing or untrusted country uses Default-on. Country classification uses an uncached country signal supplied by Cloudflare, not a country value you enter. Google Advanced Consent Mode permits limited cookieless measurement pings before acceptance and after Reject; rejecting analytics storage does not stop every Google request. Cookieless does not mean no information is sent or establish a legal exemption. One shared GA4 property is used, not a separate UK/Swiss property. Account and Admin pages and trip contents remain excluded. Anonymous studio and funnel measurement require their separate release verification before activation. Regional choices cover analytics storage and advertising measurement separately, are stored on this device as rf-measurement-consent, expire after twelve calendar months, and are requested again when purposes change. Closing a notice is not acceptance. Global Privacy Control keeps advertising permission off in this prepared mode; it does not turn off Google analytics storage that your region or choice otherwise permits, and Do Not Track is not used in regional mode. Advertising preferences can be recorded, but advertising destinations remain inactive. The Do Not Sell or Share / Privacy Choices control is offered to every visitor, including California visitors, without claiming that we can detect your US state. Prepared account and funnel features -- separately verified before activation: signing in acknowledges the linked Terms and Privacy Policy without a checkbox; it does not grant optional analytics or advertising permission. A current explicit Privacy Choices decision may be handed off to a genuinely new account. Optional account choices are saved by an authenticated server procedure for twelve calendar months, can be changed through Manage account purchase choices, and never grant this browser permission. A temporary same-browser signup handoff expires after 24 hours; confirmation on another device asks for a fresh choice rather than transferring a browser grant. Checkout can continue without saving optional choices. The separately gated funnel covers route\_created, preview\_played, export\_started, export\_completed, confirmed sign\_up and begin\_checkout. Its event fields exclude account identifiers, email, trip content and arbitrary caller properties. An export event is usage measurement, not proof of a purchase or a successfully delivered payment report. Cloudflare Web Analytics is enabled separately on routeflick.com and is not controlled by Privacy Choices. Its beacon can run before a Google analytics choice and after a decline. Cloudflare documents its usage measurement as not using cookies or localStorage, and describes page-view and page-load performance metrics. This provider description is not a finding that all processing is anonymous or consent-exempt. It is distinct from the Google tag and from account or trip activity records. Purchase reporting is currently inactive: the old direct GA4 purchase sender is retired. Payment processing, financial receipts, subscriptions and Admin Activity continue to operate regardless of advertising choices. Proposed future Dodo-webhook-only reporting covers newly registered subscription checkout payments, not renewals or historical backfill, through server GTM. Meta purchase forwarding excludes buyers whose advertising permission is denied, absent or expired, or whose Global Privacy Control signal is on; their financial and service records remain. A separately verified Meta destination could receive consented purchases only after provider-required matching information and revised disclosures are approved. The current stripped payload lacks that matching information, so Meta remains inactive. The proposed stripped purchase exception for Google Ads and TikTok despite denied advertising permission or Global Privacy Control is also inactive, not legally approved or verified as accepted by those recipients; it does not grant advertising permission or authorize identifiers. Privacy and provider review are required before any recipient activation. Legacy withdrawal requests can still be retried on this page; they do not enable new purchase delivery or recall an already sent event. ## 6\. Data retention We keep your account and trip data for as long as your account is active. You can delete individual trips at any time, and deleting your account removes your trips and synced media. Support messages and payment records may be retained as required for legal, accounting and fraud-prevention purposes. ## 7\. Your rights and account deletion You can delete your RouteFlick account on our website without installing or reinstalling the mobile app. [Open RouteFlick to delete your account](https://routeflick.com/create) - Sign in with the email address linked to your RouteFlick account and enter the code sent to that address. If you are already signed in, check that it is the account you want to delete. - Open the account menu using the account icon or the Open menu button. - Choose Delete account, read the confirmation and confirm only when you are ready. This action cannot be undone. See Data retention above for account and trip data, synced media, and records retained for legal, accounting or fraud-prevention purposes. Exported files stored outside RouteFlick app storage are not removed by account deletion. For a subscription purchased through our website, account deletion cancels the subscription immediately and ends access to the remaining paid period. If you have a refund question, contact support before deleting. For a subscription managed by Google Play or another store, check that store's subscription settings; do not assume that deleting your RouteFlick account cancels store billing. If you cannot sign in or the deletion request fails, contact support@routeflick.com for help. Do not send passwords, sign-in codes or payment-card details. Depending on where you live (for example under the EU/UK GDPR or California's CCPA), you may have the right to access, correct, export or delete your personal data, and to object to or restrict certain processing. You can exercise most of these in-app, or contact us and we will help. We will not discriminate against you for exercising your rights. ## 8\. Security We use access controls, encryption in transit, and per-account isolation so each user can only reach their own trips and media. No system is perfectly secure, but we work to protect your data and will notify you of a material breach as required by law. ## 9\. International transfers Our providers may process data in countries other than yours. Where required, we rely on appropriate safeguards (such as standard contractual clauses) for these transfers. ## 10\. Children RouteFlick is not directed to children under 13 (or the minimum age in your country), and we do not knowingly collect their data. If you believe a child has provided us data, contact us and we will delete it. ## 11\. Changes We may update this policy as the service evolves. We will revise the "Last updated" date above and, for material changes, provide a more prominent notice. ## 12\. Contact Questions about this policy? Use the in-app Contact form or email support@routeflick.com. See also:[Terms of Service](https://routeflick.com/terms)[Refund Policy](https://routeflick.com/refund)[Japan External Transmission Disclosures](https://routeflick.com/japan-disclosures)