What we collect
- Identity: name, email, school + graduation year (from your application form), GitHub username (if you connect GitHub)
- Auth: Clerk handles your sign-in. They store an email and an OTP code; no passwords. See Clerk's privacy policy.
- Code reviews: when you submit a hunt, we clone your repo (read-only OAuth) and store the resulting review score + feedback + skill tags
- Squad activity: doubts you post, replies, prompt drafts you save, hunt completions
- Technical: IP addresses (hashed for rate limiting; we don't store the raw IP), user agent strings, page-view analytics via PostHog
Why we collect it
- To run the pilot — review your code, score your hunts
- To compose squads and connect you with squadmates
- To send pilot-related Slack notifications to your squad
- To investigate platform abuse (rate-limit bypass, etc.)
- To learn what works and what doesn't in the pilot
Where it lives
Application + squad + review data lives in a Postgres database (Neon, US-East). GitHub access tokens are AES-256-GCM encrypted before storing. Page-view analytics live in PostHog. Error traces live in Sentry. Slack notifications live in our private OwlHub Slack workspace.
What we don't do
- Sell your data to anyone
- Use your code to train AI models
- Share your application content with anyone outside OwlHub
- Track you across the broader internet
Your rights
Email support@owlhub.dev to request a copy, correction, or deletion of your data. We respond within 7 days.
Cookies
We use cookies that are strictly necessary (sign-in session via Clerk) and analytics (PostHog page views). No advertising cookies. No third-party trackers.