Per-Request Storage Model
Scoring context (job description, resume, application answers) is stored with each scoring request. This means:- Job descriptions are submitted with each scoring call
- Each ScoringJob stores its own copy of the context
- Data is retained for 90 days from job completion
A future update will introduce a Job entity to store job descriptions once per job posting, reducing repetition. For now, include the job description with each request.
Retention Period
All scoring job input data is retained for 90 days from job completion (success or failure). After this period, input data is automatically deleted while output data is preserved.What Gets Deleted
After 90 days, the following data is permanently removed:| Data | Description |
|---|---|
| Resume files | PDF files stored during processing |
| Application answers | Q&A context from candidateData |
| Job description | The jobDescription you provided |
What Gets Preserved
Scoring outputs and metadata are retained indefinitely for audit and analytics:| Data | Purpose |
|---|---|
| Score (0-10) | Candidate ranking |
| Assessment | Verdict, strengths, concerns, interview focus |
| Timestamps | Audit trail (queued, started, completed, failed) |
| Error details | Debugging information |
| IDs | Job, application, and scoring job references |
Cleanup Schedule
Data cleanup runs automatically:- Frequency: Daily at 3 AM UTC
- Scope: All COMPLETED and FAILED jobs past retention period
Fetching Results
Results remain accessible via API indefinitely:If you have specific data retention requirements, contact us through the Embed Portal.