What you submit

The flow starts with two text blocks: the target job description and your current resume. They are used to generate one structured patch report, not a lasting candidate profile.

What the app should actually retain

Raw job descriptions, full resumes, generated reports, and intermediate artifacts are kept for no more than 24 hours in the normal flow. After a paid unlock, a signed-in user may explicitly save a job description or resume to the library: up to five of each type, for up to 30 days, with view and delete controls. Text that is not explicitly saved never enters that library. We retain only the minimum audit metadata needed for report generation, access control, payment state, feedback, and required event logging.

How long reports stay available

Reports and related raw content that was not explicitly saved are automatically cleared after 24 hours. Saved job descriptions and resumes are retained for up to 30 days and can be deleted at any time; they are also cleared at expiry. Users can delete reports earlier, and deleted report content should stop being accessible immediately. If a serious problem requires a refund or technical-support email, contact us within the 24-hour window; once the email arrives, original report access is closed and the order data moves into a refund-case archive used only for human review, excluded from automatic cleanup, and manually deleted after the case ends. After that window, the original data may be gone and we may be unable to investigate the issue.

How payments and third parties fit in

Payments are handled by PayPal. Model calls and infrastructure may create necessary server-side records, but those records should never expand into a permanent job-search database or a fabricated-resume pipeline.