Privacy policy for a closed beta job-search workspace.

Karion collects the Google account identity Supabase Auth provides, resume files you upload, parsed resume data, pasted job descriptions, optional source URLs, generated recommendations, tailored resume data, evidence packs, application states, and operational logs needed to run the product.

Karion does not collect payment details in M1 because billing and paywalls are not part of this milestone.

Karion uses your resume and job descriptions to parse requirements, score fit, create evidence packs, generate tailored resume data, and track the application workflow you choose to record.

Karion may send resume or job text to configured Gemini models for the analysis features shown in the app. Gemini calls are logged with token counts, latency, estimated cost, purpose, and success or failure status for debugging and cost guardrails.

Karion does not submit job applications for you, message employers, generate follow-up emails, scrape private job boards, install a browser extension, or fetch data from your LinkedIn, Indeed, Naukri, or other third-party accounts.

Karion stores optional source URLs only for attribution and context unless a future milestone explicitly adds an approved public-source ingestion mode.

Karion stores M1 product data in the configured Supabase project and generated files in configured storage buckets. Access depends on the app authentication and Supabase policies configured for the deployment.

Closed-beta users should treat this as an early product. Ask the Karion owner for deletion or export help until self-serve account controls are implemented in a later milestone.