Privacy Policy
Effective Date: 20th May 2026
Your privacy matters to us. This Privacy Policy explains what information we collect and how we use it.
1. Information We Collect
1.1 Account Data
- Email address (collected at registration)
1.2 Usage Data
- Pages viewed and API-level interactions
- Session recordings, heatmaps, and click/scroll tracking captured by Hotjar
- Aggregated web analytics captured by Vercel Analytics
1.3 Payment Data
- Processed securely via Stripe
- No payment data is stored by UFC Predictor
1.4 Behavioural Analytics Data
For signed-in users, we send your Clerk user ID and email address to Hotjar as user attributes so that session recordings can be associated with your account — this lets us reproduce reported bugs against a specific account and improve the product experience.
2. How We Use Your Data
- Provide and improve services
- Send marketing emails
- Monitor usage and prevent abuse
- Diagnose bugs and improve the user experience using session recordings and aggregated usage analytics
3. Data Storage & Security
- Data stored on Cloud Service Providers
- We follow standard data protection and encryption practices
4. Sharing of Data
We do not sell or share your personal data with third parties, except for:
- Stripe (payment processing)
- Clerk (authentication)
- Hotjar (session replay & product analytics — used to diagnose issues and improve the user experience)
- Vercel (web analytics)
5. Your Rights
Under UK data protection law, you may:
- Request access to your data
- Request correction of incorrect data
- Request deletion (with account closure)
To exercise these rights, email support@ufc-predictor.com.
6. Cookies & Tracking
We use first-party cookies set by Hotjar to maintain session continuity for session recordings and heatmaps. We do not use advertising cookies.
You can opt out of Hotjar tracking at hotjar.com/legal/compliance/opt-out.
7. Third-Party Content
The platform does not embed third-party content such as YouTube or Twitter.
8. Updates
We may revise this Privacy Policy from time to time. The most current version will always be posted on this page with an updated effective date.