Contact

There is one mailbox, and Utkarsh answers everything in it.

Resumeboard is run by Utkarsh, and he is the only person behind it: no company, no support desk, no ticket queue. Everything you send goes to Utkarsh6624@gmail.com, and every message in it is answered by the person who wrote the code. The subject line is how it gets sorted, and the table below is the routing.

One mailbox, six prefixes

Pick the row that matches what you are writing about. The prefix goes at the start of the subject line, in square brackets, exactly as written. If a message arrives with no prefix and it is not obvious what it is about, one question comes back before an answer, which costs you a round trip.

Subject prefix	Send it when your message is about
[Privacy]	A privacy request, a question about what the app stores or does with your data, or a complaint and grievance about how you were dealt with. There is no server to write to, so most of these are answered with the file and the line in it.
[Legal]	A legal notice, a copyright claim, or a claim that something published here infringes your intellectual property.
[Security]	A vulnerability, or anything that could expose one person's resume to someone who should not see it. This is the most urgent category on the page.
[Abuse]	Content published on this site that is unlawful, or that you believe infringes somebody's rights. There is more on exactly what to send further down.
[Press]	An interview, a question about the project, or a request to be quoted. These are answered, but Utkarsh is not a publicist and there are no embargoed briefings.
[Bug]	Something in the app does not do what it says. This is the largest category by a long way, and the one that can be acted on most often.
No prefix	A feature request, a question about the writing, or anything else. Write a plain subject line and one sentence about what you want.

There is one address and no others. Mail to privacy@, legal@, security@ or support@ at this domain does not arrive, because those mailboxes do not exist. If you want something read as a notice rather than as a question, say so in the body as well as in the prefix. If you cannot tell which row fits, use [Bug]. Guessing wrong costs one reply.

For a professional profile rather than a message about the app, LinkedIn is the right place: linkedin.com/in/utkarsh-choudhary-116a9736a.

What to expect

The realistic answer is a single person working alone, so here is what can actually be committed to rather than what a support page usually promises.

Every message is read and answered by Utkarsh. There is no ticket system, no first-line team and no autoresponder standing between you and the person who wrote the code. That includes the messages that cannot be acted on, which get a plain answer saying so.
[Security] and [Abuse] first. Acknowledged within 2 working days.
[Legal] and [Privacy] next. Acknowledged within 3 working days.
[Bug], [Press] and everything else. Acknowledged within 5 working days.
If you write more than once about the same thing, the thread is worked as one message rather than each reply being handled separately.

Those are acknowledgement times, not resolution times. Resolution depends on the fault and on how long the work takes, and a fix is not promised for a bug report at all. It depends on whether the fault can be reproduced, and some of them are in the browser rather than in this codebase. If a report needs more work than it is worth, you will be told that and told what would be done instead, rather than left waiting.

If Utkarsh is ill, travelling or simply away from the keyboard, the wait is longer and nothing on this page will report it. There is no status page and no out-of-office notice, because either one would be a second piece of software standing in for a person.

What can and cannot be done for you

This is a browser-only app. That buys the privacy and it costs the support, and the cost is not small enough to leave implied.

Fix a bug and ship it. The site is static files on a host the operator controls, so a fix is an edit and a deploy, and it reaches every visitor at once.
Change or withdraw a page after a report about what is on it.
Answer a question about how any part of the app works, and point at the file and the line it comes from.
Say exactly what is stored and where, and how to delete it yourself.
Say what changed in a release, because the same person makes the deploy and writes the note.

Recover a resume. It was never uploaded anywhere, so there is no copy on a server, in a log, or in a backup to restore from. If it is not in the file you exported, it does not exist anywhere. Clearing your browsing data, a private window, and a browser reclaiming space under pressure all end the same way, and none of them is recoverable by the operator or by anyone else.
Say whether a share link was forwarded. The resume in a share link sits in the part of the address after the #, and browsers never send that part of a URL to anyone. No server logged it, no referrer carried it, no analytics saw it. Nobody can audit a string that has left your hands.
See, restore or delete anything on your device. Your resume is in your own browser storage, in the database called resumeboard. Only you can open it and only you can remove it. The privacy page has the exact steps, and they are yours to run.
Investigate a machine. If the fault is in your browser, your profile, your extensions or your operating system, the only thing that can be acted on is what you paste into the message.
Look at anything you have not sent. There is no access to your files, your screenshots or your history beyond what you put in the email.
Offer a support contract, a refund or a service level. There is no paid tier and nothing to refund.

Reporting unlawful or infringing content

Start with what is actually on the site, because it narrows this a long way. There is no user-generated content here. Nobody can publish to resumeboard.vercel.app, because there is no account to sign up for and no server to publish to. Every page under this address was written by the operator. The one point where anybody else's code runs is the version-pinned PDF library that PDF import fetches at runtime from cdnjs.cloudflare.com, after you ask it to.

That matters, because a report sent here can be acted on. The site is a set of static files served over HTTPS from a host the operator controls, so a page that was published here can be corrected, edited or withdrawn, and one deploy updates it for everyone. There is no third-party marketplace, no user content to moderate and no hosting provider to escalate to. A claim that is well founded and points at a specific page gets resolved rather than merely filed.

Include these in the message:

The exact address of the page, copied from the address bar, including the part after the # if it is there.
What is wrong with it, in a sentence or two, quoting the offending line if there is one.
For an intellectual-property claim: what the work is, that it is yours or that you are authorised to act for its owner, and which part of the page reproduces it. A link on its own is not a claim.
Where you can be reached. Replies go to the address you wrote from, so if that address stops working, say so in the message instead of assuming the reply landed.

Leave out personal details about other people. If the claim is about a page that names somebody, say what is wrong with the page instead of pasting everything else on it.

What happens next:

Acknowledged within 2 working days, by the operator.
The page is checked against what you have described.
If the claim is clear, the content is removed or corrected and pushed to the live site. Five working days is a realistic figure for a claim that needs no questions asked.
If it is unclear, or if two people disagree about the same page, one specific question is asked and the answer is waited for. A page will not be pulled on a bare assertion with nothing on it to check, and it will not be pulled because the message contained a threat. Either of those would turn this section into a fiction.
A counter-notice runs the same way in the other direction: same address, same [Legal] or [Abuse] prefix, same list of what to include, same turnaround.

One limit is worth stating rather than leaving implied. Because the only thing that can be acted on is a file on a static host, there is no key to revoke, no account to close and no stored record to delete. If the claim is about a page, the page is what changes.

Disputes and escalation

Almost everything here resolves in the email thread it started in, and for most people that is genuinely where it resolves. The steps below are for the cases where it does not.

Reply to the thread. If the first answer did not answer your question, quote the line that did not and say what is missing from it.
Start a new message with [Legal] in the subject line and describe what you think went wrong. That is the only escalation step that exists.
There is no step three. Resumeboard is run by Utkarsh, an individual. He is not a registered company, and there is no manager, no review board and no ombudsman to escalate to. Saying that plainly is more useful than describing a process that is not there.

The other two policy pages describe the same route rather than a competing one. The terms set out this process, and the grievance process in the privacy page is this process under its privacy name. Both end at the same mailbox.

If a matter cannot be settled by email, these pages are governed by the laws of India, and the courts competent where the operator resides have jurisdiction over a dispute. No city is named here on purpose: a city written into a policy page goes stale, and the residence that counts is the one that exists when the dispute does. Nothing on this page waives anything that cannot lawfully be waived.

Before you write

If an export came out wrong, say which format and which template — that is almost always enough to reproduce it.
If a pasted resume came out empty or half-built, paste the source text too. The parser is a heuristic, not an AI, and its blind spots are worth knowing about.
If something looks broken, a screenshot of the whole browser window helps more than a description.

A bug worth reporting

Open the page, make the change, and run node tools/deploy.js from the project folder. It checks every link, every referenced file, the page metadata and the asset cache stamp in under a second, and exits non-zero if anything is broken. A failure there means the build is not safe to ship.

Last updated 4 October 2026. The terms and the privacy page carry the same date.