Explicit declaration of what data TryCareerLens collects, how AI models process it, and data retention windows.
Effective Date: August 4, 2026 | Last Updated: August 4, 2026
At TryCareerLens, we believe software engineers should know exactly what data is collected, how it is analyzed by Artificial Intelligence models, and who can view it. This document provides a line-by-line breakdown of our data collection practices.
| Data Category | Specific Fields Collected | Collection Trigger | Primary Purpose |
|---|---|---|---|
| Identity Data | Full Name, Email Address, Phone Number, City, State. | Account Registration | User authentication, candidate profile creation. |
| Resume Data | PDF/Word Document file, extracted skills, work history, degree tier. | Resume Upload | Parsing claimed technical trajectory & baseline background. |
| GitHub Metadata | Public repo names, language bytes, commit frequencies, Docker/k8s configs. | GitHub Connect (OAuth) | Analyzing real-world codebase output vs claimed skills. |
| Assessment Telemetry | Scenario responses, quiz scores, timing flags, integrity events. | Validation Tests | Evaluating technical comprehension & claimed vs validated skills. |
| Payment Telemetry | Razorpay order ID, payment ID, transaction status, billing amount. | Razorpay Checkout | Provisioning digital credits & recruiter plan subscriptions. |
| Placement Outcome Data | Anonymized time-to-hire, engineering score correlation, offer acceptance metrics. | Recruiter Offer Response & Placement Confirmation | Aggregated analytics to train assessment quality, optimize matching algorithms, and elevate evaluation accuracy. |
TryCareerLens utilizes Large Language Model (LLM) providers to parse documents and generate candidate feedback: