The rules for a tool that keeps nothing.

What Resumeboard is, and what it is not

Resumeboard is a resume builder written in plain HTML, CSS, and JavaScript. It lives at https://resumeboard.vercel.app, and the files your browser downloads are the whole application. There is no build step behind them, no package manager, and no process that runs when you press a key.

Utkarsh wrote it and operates it. He is an individual, not a registered company, and these terms are between you and him. The about page explains the design decisions behind the thing you are agreeing to use.

What it gives you

• An editor where the page itself is the editing surface, so what you see while you type is what prints.
• A set of templates you can switch between at any time.
• Exports to PDF and to plain text, plus a JSON file you can keep as a backup.
• Writing guides and an ATS reference, both static pages in the same folder.

No account, no server, no sync

None of those three exists. There is no sign-up, no login, no profile, no email address collected, and no database behind the page. Your resume is written to storage inside your own browser and is never transmitted.

The consequence is the one that decides this whole page. The app cannot sync between your devices, cannot recover a file it has lost, and cannot restore anything on request, because there is no copy of your work anywhere it could reach. What is on one device stays on that device unless you move it yourself, with the export file. The privacy page sets out exactly where the data sits and what the browser can do to it.

Your content, and the licence you give us

Everything you type is yours. You keep ownership of your name, your contact details, your employment and education history, your photo if you add one, and every other word in the document. We claim no ownership of any of it, and nothing you type becomes ours to license, resell, publish, or train anything on.

That is not only a promise. There is no server holding a copy of your resume, so there is nothing for us to do any of those things with.

The licence, stated narrowly

Running the site needs your browser to download the files and execute them. That is the entire licence you give: permission for your browser to fetch and run this application on your own device.

It does not include any of the following.

• Copying the site as a whole, or offering it as your own service.
• Rebranding it, removing the attribution from the templates and guides, or passing it off as your work.
• Selling it, bundling it into a paid product, or charging for access to it.
• Claiming any kind of ownership over a resume produced with it. The document is yours from the first character.

Quoting a short excerpt from the site, or linking to any page on it, is fine.

The example resumes

The resumes under examples are fictional. No real person, employer, school, or client is described in them. You can read them, load one into the editor, and start from it. They exist to show the structure a finished resume has, and using one as a starting point is what they are for.

Acceptable use

There is one narrow list of things you must not use the builder to do, and the reason for each of them is ordinary.

• Unlawful content. Do not use the site to write, keep, or share anything whose purpose is to break the law where you are.
• Fraud. Do not describe qualifications, employers, degrees, dates, or references that you do not have. A resume that misstates the truth is not a sharper resume, it is a false statement.
• Defamation. Do not put a defamatory statement about a real, identifiable person into a document made with this app.
• Harassment. Do not use the app to threaten, harass, stalk, demean, or intimidate anyone, or to target anyone because of a protected characteristic.
• Infringement. Do not paste material you do not have the right to use, including a photograph or a confidential document that belongs to somebody else.
• Impersonation. Do not present yourself as a person, employer, or organisation you are not, and do not use the app to produce a document that appears to have come from us.

A share link is a document you have handed to whoever holds the string. Sending one to somebody with no reason to read the resume is your responsibility. The app cannot tell who you sent it to, because it never finds out.

The source of this site is published and readable in full, so there is nothing here to reverse engineer. These terms do not pretend otherwise, because reading the code is how you check that they are true.

Children and parental permission

Resumeboard is not directed at children under 16, and it collects nothing about anyone, so no information is held about a child. There is no account to have been created and nothing to delete on a server.

If you are under 16, ask a parent or guardian before you put personal details into a resume you intend to send anywhere. If you are the parent or guardian of a child under 16 who has used the site, the data is in the browser profile on that device, and you remove it the same way you would for yourself: delete the site's data in the browser. The step-by-step deletion instructions apply.

If you believe a child has been sent something harmful through this site, write and it will be read. Be clear about what you can and cannot expect in reply: we hold no copy of any document and can only act on the files the site itself serves.

Third-party services

There is exactly one external service in the whole codebase, and it only runs if you ask it to.

cdnjs, on the PDF import path only

Reading a PDF needs a real PDF engine, and this project ships none. When you choose Import, then PDF, then pick a file, the app adds a script tag pointing at a version-pinned copy of pdf.js on cdnjs. Before anything is fetched, the import panel shows you both addresses, and the cancel keeps working while the download is in flight.

These are the exact URLs, taken from the constants at the top of assets/js/ui/importer.js:

https://cdnjs.cloudflare.com/ajax/libs/pdf.js/3.11.174/pdf.min.js https://cdnjs.cloudflare.com/ajax/libs/pdf.js/3.11.174/pdf.worker.min.js

The version is pinned rather than tracked, so the file you receive is the file anyone receives that day. The script tag carries crossorigin="anonymous" and referrerpolicy="no-referrer", which means the request carries no cookies and nothing about the page you came from.

Once it loads, the library runs inside your browser and is handed the bytes of the file you picked. Your PDF is not uploaded. Nothing about it reaches cdnjs or anyone else: not the file, not its name, not its size, not the text inside it. cdnjs sees one request for two public JavaScript files, in the same way it sees a request from any other site on the web. If you never use the PDF option, the request is never made.

The other three import routes — a .docx file, a .json file, and pasted text — are unpacked in the browser and make no request at all.

pdf.js is not ours and stays under whatever licence it is published under on the page it comes from. If you reuse any part of it, read that licence yourself at the addresses above rather than taking this page's word for it.

The host

The site is a folder of static files served over HTTPS by a static host. The host delivers files and does not run this application. Nothing here runs on Google's infrastructure, and there is no API, database, or serverless function behind any page.

There is no advertising network, no analytics vendor, no session replay tool, no error-reporting service, and no font or icon server on any page. The privacy page itemises the rest.

Your responsibilities, and what this service does not do

You are responsible for your document: what is in it, whether it is true, where you send it, and whether the file you exported is the one you meant to send. We have no way to check any of that, and we would not check it if we could.

• The importer is a heuristic, not a model. A PDF or a .docx gets you close, not correct. Read the result before you send it.
• Nothing here is a review, a score, or a guarantee. The app flags empty fields and thin sections as you type. It does not tell you whether a claim will hold up in an interview, and it does not know what a particular employer or applicant tracking system will make of the result.
• The app cannot recover a lost resume, undo a lost file, or merge two versions of a document. There is no server to ask.
• You are responsible for your own backups. The app makes a JSON export in two clicks and then keeps no copy of it anywhere.
• Do not leave personal or confidential details in a resume you are about to send to a stranger, and think twice before putting a photograph of yourself into a share link.

Features change. We may fix bugs, redesign the editor, or remove something you rely on, and we do not owe you a new version of a page you liked. There is no deprecation schedule and no frozen build.

No account, no recovery, no availability guarantee

Three things an online service normally provides are all missing here, on purpose. It is worth being blunt about what that costs.

No account

Nothing identifies you. There is no profile, no password, no sign-in history, no record of who typed what, and no way to prove later that you were the one who wrote a given document.

No recovery

If the data is gone, it is gone. A browser may evict site data when a device is low on space, clearing your browsing data removes it, a private window discards it on close, and a different browser, a different profile, or a different address is a different storage bucket that starts empty.

There is no backup held for you and nothing to request, because a deletion here is complete: there is no copy on any server. Export the JSON file and keep it somewhere you control. The export steps are on the privacy page.

No availability guarantee

Resumeboard is offered as it is. There is no uptime commitment, no service level, no response-time promise, and no support desk that is awake. Pages can change or be taken down. The builder can break in a browser update. Files can move, and a link you saved in an old resume or bookmark may stop resolving. Plan around that rather than around a promise we have not made.

Intellectual property

The app itself

The code, the visual design, the stylesheets, the icons, and the writing inside the builder are Utkarsh's. They are published so that you can read them and check what the software actually does, and reading them is not a breach of these terms.

What is not permitted is copying the site as a whole, presenting it as your own, or selling it. Using the app, exporting what you write, and quoting a short excerpt from these pages are all fine.

The templates, guides, and reference pages

The templates, the writing guides, the example resumes, and the ATS reference pages are part of the same work and carry the same terms. You may use the output of a template in your own resume, which is the entire point of them. You may not republish the template gallery, the guide text, or the reference material as your own product.

Material that is not ours

pdf.js belongs to its authors and is only fetched if you use PDF import. The fonts are whatever your operating system already has. There is no other third-party code running on this site, and the pages you are reading are not generated by anyone else's service.

Disclaimer of warranties

Resumeboard is provided as is. To the fullest extent the law allows, no warranty of any kind is given, express or implied, including any warranty of fitness for a particular purpose, merchantability, non-infringement, accuracy, or uninterrupted availability.

In plain terms: we do not promise that the app is free of errors, that it will always be available, that an export will be exactly what you intended, that an employer or an applicant tracking system will read your resume the way you hoped, or that these pages are a complete statement of your legal rights.

Some jurisdictions do not permit certain warranties to be excluded or limited. Where that applies, the exclusion above is cut back to the narrowest extent the law allows, and a warranty the law refuses to take away from you still stands.

Limitation of liability

To the fullest extent the law allows, Utkarsh is not responsible for loss arising out of your use of Resumeboard. That includes loss of data, a lost job or a missed opportunity, loss of profit or income, and damage to your reputation or to somebody else's.

The total amount that would be owed for anything connected with the site is capped at one thousand Indian rupees (INR 1,000), or the amount you paid us, which is zero, whichever is greater.

The following are not excluded, and no wording on this page tries to exclude them:

• Liability for fraud or fraudulent misrepresentation.
• Death or personal injury caused by negligence.
• Liability for negligence where that negligence is gross.
• Liability for deliberate or intentional misconduct, including wilful misconduct.
• Any right or remedy that applicable law does not permit a person to give up or limit. If a court finds a clause on this page unenforceable, that clause falls away and the rest of these terms continue to apply.

The reason this section can be short is the same reason the privacy page can be short. There is no account, no stored document, and no payment, so there is nothing for either side to be the custodian of.

Indemnity

You agree to cover Utkarsh against claims, losses, and reasonable costs that come out of your use of the site, including the following.

• Content you put into a resume, an export, or a share link that infringes somebody else's rights or exposes them to a claim.
• A false or misleading statement you put into a document, including a claim about a qualification, a job, or a reference that is not true.
• Anything you do with a share link after you send it.
• Any claim that your use of the site breached the acceptable use rules above.

This is not permission to blame you for using a resume builder. It does not apply to a claim we caused, it does not apply to anything the law of India does not permit it to cover, and it is limited to the same cap as the section above.

Suspension or withdrawal

The site can be withdrawn or restricted at any time, with or without notice. In practice that means taking the files down, changing the address, or blocking access. We will use that power reasonably and not to settle a disagreement about content, but we are one person: if the site is being used to defame somebody, to impersonate somebody, or to distribute something unlawful, taking it down is the only proportionate response available.

Because there is no account and no server-side copy of any document, restricting access does not delete anything. It removes the files from the server. What you already exported, downloaded, or saved in your own browser stays where it is, and no amount of withdrawal reaches back to your device.

You can stop using the site at any time, with no notice and nothing to cancel. Deleting the stored data is something you do yourself, and the privacy page has the exact steps.

Changes to these terms

These terms can change. The version in force is always the one on this page, and the date near the top tells you which one you are reading. There is no archived copy to compare against, because there is no server to keep one.

A material change — one that alters what you must do, what you own, what is permitted, or what we can be liable for — takes effect no sooner than 30 days after the new version is published here. Until that date, the version you started using continues to govern you. A correction of a typo or a broken link is not material and does not need that notice.

Continuing to use the site after a material change takes effect means you accept it. If you do not accept it, stop using the site. There is nothing to unsubscribe from, because there is no account and nothing is sent to you.

The privacy page moves for the same reasons and on the same notice. If the two ever disagree, that is a mistake to report rather than something to argue about, and both should be fixed.

Governing law and courts

These terms are governed by the laws of India.

The courts with jurisdiction where the operator resides can hear a dispute arising from them, and either of us can bring a claim there. You are not required to travel to India to raise a problem, though. Write to the mailbox first, and most things are settled in a message.

Nothing in these terms takes away a right or a remedy that the consumer protection law of the place you live gives you, if such a right exists there.

How to reach us about these terms

There is one mailbox and Utkarsh reads it. There are no role addresses, so put a prefix in the subject line and the right kind of message gets picked up first.

Write to Utkarsh6624@gmail.com. Utkarsh is the person who receives and answers each one, including a complaint about the site itself. Be aware of what that means in practice: we hold no copy of your document, we cannot delete anything from your device, and the most a complaint about the app can realistically produce is a fix.

There is no privacy@ or legal@ address, because there is no second mailbox behind either one. The contact page has the same prefixes and a short note on what makes a bug report easy to act on.