Our approach to data
daily.dev Recruiter is built on trust. Our data practices reflect this:
- Consent first: No data shared without developer consent
- Transparency: Developers see exactly what is shared
- Minimal collection: We only collect what is necessary
- No selling: We never sell candidate data
Data we collect
From developers (candidates)
When developers engage with opportunities, we collect:
| Data type | Purpose |
|---|---|
| Profile information | Identity and background |
| Screening answers | Match qualification |
| Engagement signals | Matching relevance |
| Contact details | Enable introductions |
From recruiters (you)
| Data type | Purpose |
|---|---|
| Account information | Service delivery |
| Job listings | Matching and display |
| Company details | Trust and verification |
| Payment information | Billing (processed by Stripe) |
How data is used
Matching
We use data to:
- Surface relevant opportunities to developers
- Match developers with appropriate roles
- Improve matching quality over time
Introductions
When both parties opt in:
- Contact information is shared
- Candidate brief is provided
- Introduction email is sent
Platform improvement
Aggregated, anonymized data helps:
- Improve matching algorithms
- Understand platform usage
- Enhance user experience
What we do not do
Never
- Sell data: To anyone, ever
- Scrape profiles: All data is provided with consent
- Share without consent: Developers control what is shared
- Use for advertising: No ad targeting with candidate data
- Retain unnecessarily: Data is deleted when no longer needed
Data boundaries
- Developers see job details before opting in
- Recruiters see candidate briefs only after opt-in
- Raw engagement data (article reads, etc.) is never exposed
Data flow
Before opt-in
- Developer sees job opportunity
- Developer reviews full details
- Developer answers screening questions
- Developer explicitly opts in
After opt-in
- Recruiter receives candidate brief
- Recruiter reviews and approves/passes
- If approved, introduction is made
- Contact information is shared
At every step, consent is explicit and informed.
Data retention
Active data
- Kept while relevant to ongoing hiring
- Used for matching and introductions
- Accessible to both parties as appropriate
After completion
- Hiring data retained for reasonable period
- Can be exported by either party
- Deleted upon request (see data deletion)
Regulatory compliance
- Retention follows GDPR and applicable laws
- Some data retained for legal/audit requirements
- Transparent about what is kept and why
Your responsibilities
As a recruiter using candidate data:
- Use data only for hiring purposes
- Respect candidates as partners, not leads
- Follow your own company policies
- Comply with applicable employment laws
Developer control
Developers can always:
- See what data is shared
- Withdraw from opportunities
- Request data deletion
- Export their data
We prioritize developer agency and control.