Privacy Policy

Visitors may provide an email address or account details when they request a magic link, save destinations, save comparisons, or return to saved city pages. Potential partners may also provide contact, company, website, category, coverage, and message details through the partner inquiry form so Retire City Finder can review fit and respond. Account and partner inquiry flows should explain what is collected before submission.

Retire City Finder measures public browsing, filter use, city-card clicks, city-tab visits, comparisons, account prompts, save intent, magic-link requests, UTM campaign fields, and ad-click identifiers so the product can improve destination discovery and understand acquisition quality.

The product uses first-party Supabase event logging and may send non-sensitive product events to PostHog, Meta Pixel, Google Analytics 4, Google Ads, Google Tag Manager, Microsoft Clarity, Vercel Web Analytics, and Vercel Speed Insights when those services are configured.

Submitted email addresses, payment details, and private account notes should not be sent to product analytics vendors. Analytics events should use destination slugs, route paths, viewport details, source/campaign fields, and sanitized metadata instead of direct personal contact details.

When a visitor uses a clearly labeled affiliate or sponsored partner link, Retire City Finder may record non-sensitive click context such as the offer, placement, city slug, page path, campaign/source fields, and a click identifier. Partner networks may later send conversion or payout status so performance can be reconciled. Retire City Finder should not put submitted email addresses, phone numbers, personal addresses, saved-city lists, health information, financial details, budget answers, passwords, tokens, or other secrets into affiliate URLs or partner callback metadata.

PostHog autocapture and session replay are disabled by default unless explicitly enabled in production configuration. Microsoft Clarity may support behavior recordings and heatmaps, so product events sent to Clarity should stay limited to non-sensitive route, city, source, campaign, viewport, and account-state signals.

Public city pages use destination data, source context, and comparison signals. Personal details should not be required to browse core public city information.

Account holders can use the data deletion instructions to request removal of account profile details, saved-city records, saved-comparison records, and related personal account identifiers after ownership can be verified.

Use the published Retire City Finder contact channel for privacy requests and account questions.