Make me a résumé.Open studio

Privacy architecture

Your draft
stays yours.

The editor stores resume content and the target job description in browser-local storage. The application code does not upload them.

01

You type

Identity, profile, skills, experience, bullets, and one target job description.

02

Browser stores

The studio writes one local draft under proof-resume-draft-v1.

03

You export

Print to PDF or download a JSON backup directly on your device.

Resume contentBrowser localStorage

Not sent by application code.

Job descriptionBrowser localStorage

Analyzed locally with deterministic rules.

PDF exportBrowser print system

Created through your browser and operating system.

JSON backupYour downloads folder

Created only when you request it.

AccountsNone

No identity provider or user database.

Product analyticsNone in application code

No tracking SDK, pixel, or resume-content telemetry.

Limits of local storage

Local does not mean indestructible.

Clearing site data, changing browsers, using private browsing, or losing the device can remove the draft. Local storage does not sync between devices. Download JSON backups regularly.

Shared devices

Anyone with browser access may see it.

On a shared device, another person using the same browser profile may reopen the local draft. Use a private device or remove the draft and site data when finished.

Site delivery

The host still receives ordinary web requests.

Loading any website exposes routine request information to its hosting infrastructure, such as an IP address, requested path, time, and browser headers. This repository adds no analytics layer and sends no resume fields with those requests. Actual infrastructure logs depend on the chosen host.

No account.No cloud resume database.No paid model API.

Resume studio

Build locally. Back up deliberately.

Build, tailor, save, and export in your browser. No account required.

Open the studio