Cookie & Tracking Policy
How we use cookies, local storage, and mobile device identifiers to power PaceMatch.
1. Introduction & Overview
SUMMARY: We believe in full transparency regarding cookies and device storage technologies used on PaceMatch.
This Cookie & Tracking Policy explains how PaceMatch Inc. ("we", "us", or "our") uses cookies, local device storage (including React Native AsyncStorage), web beacons, and mobile device identifiers across our mobile applications, web portals, and legal documentation hubs.
2. What Are Cookies & Local Storage Technologies?
SUMMARY: Cookies and local storage are small data files stored on your phone or browser that keep you signed in and remember preferences.
Cookies are small text files placed on your browser or device when you visit a website. In our mobile applications, we use local storage technologies (including React Native AsyncStorage) and mobile advertising/diagnostic identifiers. These technologies allow the app to remember your active session, authenticate secure API requests, and preserve your customized app settings across app relaunches.
3. First-Party vs. Third-Party Technologies
SUMMARY: First-party technologies are placed directly by PaceMatch; third-party technologies are placed by trusted infrastructure partners.
First-party storage items are set directly by PaceMatch (e.g., maintaining your offline profile cache and active workout mode). Third-party items are set by vetted cloud infrastructure partners (such as Supabase for session authorization, Firebase for crash prevention, and Cloudflare Pages for CDN caching).
4. Categories of Technologies We Use
SUMMARY: We use Essential (login & security), Performance (PostHog analytics), Functional (theme & filters), and Notification (FCM) storage.
We categorize our cookies and local storage technologies as follows:
• Strictly Necessary / Essential: Indispensable for the operation of PaceMatch. These include Supabase authentication tokens, CSRF protection, and session encryption keys. Without these, you cannot log in or navigate the app.
• Performance & Analytics: Help us analyze app usage patterns and optimize speed. We use PostHog to capture high-level funnel metrics (e.g., match success rates) and Sentry for crash diagnostics. These metrics do not sell or expose personal identifiable information.
• Functional & Preferences: Remember your choices and UI customizations, such as your AMOLED dark theme preference, selected workout modes (SWEAT / NETWORK / TRANSIT), and search distance filters.
• Communications & Push Notification Tokens: Firebase Cloud Messaging (FCM) device push tokens that enable real-time delivery of mutual match announcements and chat alerts.
5. How You Can Control Cookies & Storage
SUMMARY: You can control permissions and storage through your in-app settings, phone OS settings, or browser tools.
You have full autonomy over local storage and tracking technologies:
• In-App Settings: You can clear your cached discovery cards, local draft messages, and session data at any time via Profile > Settings > Clear Local Cache.
• Mobile OS Controls: You can revoke notification permissions or location access anytime in iOS Settings or Android App Permissions.
• Browser Controls (Cloudflare Pages): When browsing our web documentation, you can set your web browser to reject or delete cookies. Note that disabling essential cookies may impact web portal functionality.
6. Policy Updates & Inquiries
SUMMARY: We may update this policy periodically. Inquiries can be sent to privacy@pacematch.com.
We may update this Cookie Policy from time to time to reflect operational, legal, or regulatory changes. We encourage you to review this policy periodically. For questions, contact us at privacy@pacematch.com.