TraitMatch Cookie Policy
Version 1.8 — Effective 5 November 2026
This Cookie Policy explains how TraitMatch (“TraitMatch”, “we”, “us”) uses cookies and similar technologies on our websites and in our mobile app. For personal data generally, see the Privacy Policy: https://traitmatch.pages.dev/privacy.
1. What are cookies and similar technologies?
Cookies are small files stored on your browser or device. Similar technologies include local storage, session storage, mobile app storage, software development kits (SDKs), and device identifiers. For simplicity, this Policy calls all of them “cookies” where they store or access information on your device.
2. What we use today
Website (https://traitmatch.pages.dev):
• Essential local storage — theme preference (`tm-theme`) so the site remembers light/dark mode.
• Network requests — pages may load fonts from Google Fonts (typography). We do not use Google Fonts for advertising profiles or cross-site tracking.
• Edge/hosting — Cloudflare may process technical data (e.g. IP address, TLS, security signals) to deliver the site and protect against abuse. See Subprocessors.
• No analytics or advertising cookies on the public marketing site today — therefore we do not show a cookie consent banner on the public website.
Staff-only internal pages (if deployed, e.g. password-protected analytics tools for our team):
• Not part of the consumer Service. Access is restricted to authorised staff (e.g. Cloudflare Access). These pages may load additional scripts (e.g. chart libraries) without end-user consent because users of the Service are not directed there.
Mobile app:
• Essential — encrypted auth/session storage, security tokens, feature preferences, end-to-end encryption key material stored on device, push tokens (Firebase Cloud Messaging) needed to deliver notifications you enable
• Real-time features — WebSocket or HTTP connections for chat and presence (no advertising purpose)
• Consent records — when you accept Terms, Art. 9 sensitive-data consent, or (in future) analytics/marketing SDK consent, we may store your choice locally and log an audit entry on our servers (see Privacy Policy)
• We do not currently ship Firebase Analytics, Crashlytics, Google Analytics, or advertising SDKs in the production app, so the in-app cookie consent bar and granular preference controls are not shown.
• If we add optional analytics or marketing SDKs later, they will stay off until you consent via an in-app prompt and Settings controls we enable at that time.
Push notifications:
• Firebase Cloud Messaging may attach campaign labels to notification payloads for delivery diagnostics. That is not the same as enabling Firebase Analytics for users.
3. Categories (for consent when applicable)
• Essential — always on; required for login, security, chat delivery, wallet sync, and basic preferences
• Analytics — optional; usage/reliability measurement when enabled (app only, if we add it)
• Marketing — optional; campaign measurement or marketing SDKs when enabled (app only, if we add it; separate from product push notifications you turn on in Settings)
4. Legal basis
Essential technologies: performance of contract and/or legitimate interests (secure, functional Service). Non-essential analytics/marketing: consent in the EEA/UK and other jurisdictions where required (ePrivacy / national implementations). You may withdraw consent in-app when controls are available; withdrawal does not affect prior lawful processing.
5. How to control
• Website — clear site data / local storage in your browser (may reset theme preference)
• App — revoke camera, microphone, location, notifications in OS settings; delete account to remove server-side account data per the Privacy Policy
• Optional SDKs — when enabled in future: in-app cookie/SDK preferences and Settings → Legal
• Marketing push — Settings → Notifications (defaults off; independent of cookie “marketing” category)
6. Retention
Essential app/website storage persists until you clear it, delete the app, or delete your account (server-side data per Privacy Policy). Consent logs on our servers are retained as described in the Privacy Policy.
7. Changes
We update this Policy when technologies change. Version and effective date above will change. Material changes to non-essential cookies/SDKs will be preceded by consent where required.
8. Contact
Privacy: [email protected]
Support: [email protected]
Subprocessors: https://traitmatch.pages.dev/subprocessors