Privacy and Data Handling

Keep private identity data separate from career content

Resume and Identification is designed around review, factuality, and separation of sensitive identity details from CVs, job matching, cover letters, proposals, Fiverr content, and public links. This page describes the intended application behavior; production deployments must also configure their server, storage, logs, backups, and third-party services appropriately.

Public Career Information

Only verified contact, education, experience, skills, projects, and other career details should appear in the professional CV.

Private Identity Information

Identification numbers, father name, date of birth, and similar sensitive fields must stay outside professional outputs.

Candidate Review

Extracted information and AI-generated suggestions should be reviewed and corrected before professional use.

Information used in a professional CV

Verified career and contact information

The CV workflow may use a candidate's verified name, professional contact information, location, links, summary, education, experience, skills, tools, projects, certifications, languages, and achievements.

  • Information should be included only when supplied or confirmed by the candidate.
  • Empty optional sections should not appear in the generated CV.
  • Unsupported employers, dates, skills, metrics, qualifications, and results must not be invented.

Private identity information

Never place these details in public career output

Sensitive information extracted from identification documents or entered by the candidate should remain in a separate private data structure.

Identification number, father name, date of birth, religion, marital status, identity-document images, and comparable sensitive information must not be included in the CV, opportunity matching, cover letters, freelance proposals, Fiverr content, or public links.

Uploaded CVs and identification images

Temporary processing and server-side safeguards

Uploaded documents may be processed to extract text and structured information. The application should validate file type and size, use safe generated filenames, and prevent uploaded files from being executed as code.

Retention depends on the deployed backend. A production operator should define when temporary files, generated previews, analysis records, logs, and backups are deleted. This template does not claim automatic deletion unless the backend explicitly implements it.

Browser draft storage

Local drafts for convenience

Builder fields, correction decisions, and verification drafts may be stored in the browser through localStorage. Uploaded document files should not be copied into browser draft storage.

  • Browser drafts are accessible to anyone using the same browser profile and device.
  • Clearing site data or using Reset Session may remove locally available workflow information.
  • Shared or public computers should not be used for sensitive identity-document processing.

AI-assisted processing

Extraction and suggestions require review

When an AI provider is configured, relevant text or images may be sent to that provider for OCR, analysis, rewriting, cover letters, proposals, or other requested content. Deployment operators should review the provider's terms, retention settings, regional processing options, and access controls.

AI output can be incomplete or inaccurate. Original content should remain visible, and candidates should accept, edit, or reject suggestions before they affect the rebuilt CV.

Job platforms and external links

Third-party websites have their own policies

Official search and application links may open external platforms such as LinkedIn, Indeed, Rozee.pk, Glassdoor, Upwork, Guru, or Fiverr. Those platforms control their own accounts, tracking, cookies, applications, and data practices.

Review the destination URL and the external platform's privacy information before sharing a CV, proposal, identity document, payment information, or personal contact details.

Production deployment responsibilities

Security depends on more than templates

A deployed service should use HTTPS, secure session settings, restricted upload directories, secret management, access controls, safe logging, appropriate retention limits, backups, dependency updates, monitoring, and applicable legal notices. This page is product guidance, not legal advice.