Sign in to unlock generation

Your profile, generated files and tracker rows are stored per account on the server, so nothing generated is shared between users.

This is Google’s own sign-in widget. Google verifies you and hands back a signed credential, which the backend checks before creating or signing into your account. Your Google password never reaches this app.

Next step

Then your workspace opens

Signing in doesn’t spend anything on its own. On the next screen you press one button and the deferred work runs: your resume is parsed.

Google verifies your identity; we only check its signed credential — no password is created or stored for a Google account.
Sessions live on the server, so signing out ends one everywhere — not just in this browser.
A session renews itself while you're working and can be revoked per device from Settings.
Generated files are written to a per-user directory and only served back to you.

One moment — fetching what this page needs.

Back to preview

Sign in to unlock generation

Your profile, generated files and tracker rows are stored per account on the server, so nothing generated is shared between users.

Next step

Then your workspace opens

Signing in doesn’t spend anything on its own. On the next screen you press one button and the deferred work runs: your resume is parsed.

Google verifies your identity; we only check its signed credential — no password is created or stored for a Google account.
Sessions live on the server, so signing out ends one everywhere — not just in this browser.
A session renews itself while you're working and can be revoked per device from Settings.
Generated files are written to a per-user directory and only served back to you.