Privacy & data controls

How analysis inputs, optional saved records, and current user controls work in this limited public beta.

At a glance

Current request
Analysis text is used for the current request.
Saving
Running an analysis does not automatically save it.
Saved records
Optional saves contain structured skills and metadata.

Platform or service logging cannot be guaranteed absent. Avoid unusually sensitive information.

This page is a product data-handling summary, not a formal legal privacy policy, compliance certification, security audit, or penetration-test report.

Plain-language summary

Job Fit & Skill-Gap Analyzer uses rule-based matching with a curated cross-domain skill taxonomy and reviewed aliases rather than semantic AI.

Analysis compares résumé information or a structured profile with a job description, and input text is used to produce the current response.

Optional saved records are structured: saved analyses hold skills, categories, counts, and job metadata, while resume profiles hold profile metadata and skill lists.

Platform or service logging cannot be guaranteed absent, so avoid unusually sensitive information.

Analysis inputs

Pasted résumé and job-description text is used to produce the current analysis response. Plain .txt uploads are read as transient convenience inputs.

Uploaded files are not stored as files by the application. Running an analysis does not automatically save the result.

Unsaved results remain part of the current workflow rather than becoming an account record in the application save path.

Saved analyses

When you explicitly save an analysis, the account-owned structured record may contain:

  • job title, company, source URL, and notes;
  • counts and timestamps;
  • matched skills and categories;
  • missing skills and categories; and
  • data used to derive recurring gaps.

Saved records are associated with the signed-in account. Clerk identity and Supabase row-level security are used for account scoping, but this is not an absolute-security guarantee.

Resume profiles

Resume profiles are structured skill sets rather than full résumé documents; they do not provide full résumé parsing, PDF or DOCX parsing, or AI extraction. They may contain profile name, optional description or notes, extracted skill names, user-added skill names, source type, and timestamps.

Raw résumé body text is not part of the structured profile. Transient .txt uploads are not automatically saved as profiles.

Selecting a profile creates temporary structured analysis input from profile metadata and skill lists for the current comparison.

Your controls

  • Run an analysis without saving it.
  • Clear transient browser inputs.
  • Review individual saved analyses, with older analyses available through manual progressive loading.
  • Delete individual saved analyses, or delete selected checked loaded saved analyses after explicit confirmation.
  • Create, edit, and delete profiles.
  • Use supported exports for individual saved analyses, selected checked loaded saved analyses, currently loaded saved analyses, comparisons, and recurring-gap views where export or download controls are available.

Current limitations

  • The taxonomy is broad but not exhaustive.
  • Differently worded skills may be missed when they do not match explicit recognized phrases or reviewed aliases.
  • Phrase detection does not prove proficiency, evidence strength, or hiring fit.
  • Human interpretation remains necessary.
  • Selected deletion and selected export apply only to checked analyses in the current loaded result set; unloaded records are not included.
  • No account-wide export or export-all control.
  • No account-wide select-all or one-click delete-all control.
  • No automated retention schedule.
  • No restore flow or undo flow.
  • No profile export.
  • Deleting a Clerk account is not claimed to automatically delete Supabase rows.
  • No formal legal privacy-policy review, penetration test, or comprehensive security audit has been completed.
  • No absolute privacy or security guarantee is provided.

The current product is a limited public beta and portfolio application for rule-based planning, saved structured results, and recurring-gap review.

Service providers

Technical data path

At a high level, Vercel hosts the Next.js web application and analysis proxy; Render runs the FastAPI rule-based analysis service; Clerk provides authentication; and Supabase stores structured account-owned records.

A June 22, 2026 two-user human verification checked saved-analysis isolation for the then-current saved-analysis schema and UI. That verification was point-in-time and does not create an ongoing guarantee.

This provider summary and verification do not create contractual, geographic, encryption, retention, legal, compliance, or absolute-security guarantees.