Privacy & data
Draftly is a browser-based resume builder. The short version: everything you type — your resume, and the jobs you track — is stored in your own browser on your own device, and is never sent to us. The one exception is anonymous, aggregate analytics about page visits and load times, described below. We’d rather tell you exactly what happens than hide behind legalese.
Your resume data stays in your browser
Every resume you build is saved in your browser’s local storage, on the device you built it on. There is no account, no server-side database, and no upload — the content of your resume (your name, contact details, work history and the rest) is never transmitted to Draftly or anyone else. It lives only on that device, in that browser, until you delete it or clear your browser data.
Importing a PDF or Word file happens on your device
When you import an existing resume, the file is read and parsed entirely inside your browser. Draftly extracts the text and structure locally and turns it into editable sections — the file itself, and its contents, never leave your device and are never uploaded to a server. Nothing about the file is retained after import beyond the resume you end up editing (which, again, stays local).
The job tracker is local too
Jobs you save in the tracker — the company, role, the job description you paste in, and any notes — are stored in your browser’s local storage alongside your resumes. When you use the keyword match, the job description is compared against your resume right there in your browser. The posting is not uploaded or sent anywhere.
What does leave your device: analytics
To understand how the site is used and to keep it fast, Draftly runs Vercel Web Analytics and Vercel Speed Insights on every page. These collect anonymous, aggregate data — things like which pages are viewed, the referrer, rough device and browser type, and performance timings (how quickly pages load). This is the one place data does leave your device.
This analytics data is not tied to an account (there are no accounts) and is not used to build a profile of you — it’s about pages and performance, not people. It does not include the contents of your resume or the jobs you track; that information never reaches the analytics layer because it never leaves your browser in the first place.
Fonts are loaded from Google
The site loads its typeface from Google Fonts. Like any third-party asset, your browser makes a request to Google’s servers to fetch it, which means Google receives your IP address and standard request metadata as part of serving the font. This is a normal part of how web fonts work, but we’d rather you know it’s happening.
No accounts today
Right now there are no user accounts — no email, no password, nothing to sign up for. Optional accounts that sync your resumes across devices are planned. When they ship, syncing will be opt-in: it will only ever cover what you explicitly choose to save to the cloud, and this page will be updated to describe exactly what that involves before it launches.
The trade-off of local-first
Because your work lives only in your browser, it is only as durable as that browser’s storage. If you clear your site data, use private/incognito mode, or switch to another device, the resume is gone — it was never anywhere else. Export a PDF or DOCX whenever you finish a session so you always hold a copy you control.
Questions
This page describes how Draftly works as of the date above; if the app changes in a way that affects your data, this page changes too. See also our Terms of Use.