Privacy Policy

Who we are

Rezome is built and run by Bitzberg, an independent project run by an individual in India (not yet a registered company), who is responsible for the data described here. Our servers are in the AWS Mumbai region in India.

What we collect

Your account. When you sign in with Google we receive your name, email address and profile picture — nothing else — and store them to run your account.

Your resumes. The content you type — work history, education, skills, a photo or signature if you add one, and so on — is stored so you can edit and download it later, along with your template and design choices. We also keep up to 30 earlier versions of each resume so you can restore one; they are deleted with the resume.

Imports. If you import an existing resume, the uploaded file is read on our own server to pre-fill the editor and discarded immediately. Only the extracted text you then see in the editor is stored, and the file itself is never sent anywhere. The import screen offers to have AI check how that text was read — a checkbox you can untick. When it is ticked, the lines of extracted text are sent to our AI provider (see “AI features” below), except any line holding your email address, phone number or a link. It tells us which section each line belongs to; everything that ends up in the editor is text from your own file.

Keyword matcher. The free matcher at /keyword-matcher runs entirely in your browser: the job description and resume text you paste are compared on your device and are not sent to us. If you choose to track the job, the posting is handed to the “Add application” form in your browser and is stored only if you save it there; until then it stays only in your browser, and your resume text never leaves the page.

Resume checker. The free checker at /resume-checker works without an account. The file you upload is read in memory on our own server to extract its text, scored by the same rules the editor uses, and discarded at once; the file and its text are not stored, and nothing is sent to an AI provider. We keep one record per check: the file format and the score. If you are signed in, that record is linked to your account; if not, it carries no name, account or address. If you choose to fix it in the editor, the resume is saved to your account like any other; until then it stays only in your browser.

Chat builder. A chat in “Build with chat” and the resume drafted in it stay in your browser; we store nothing from it until you create the resume, which is then saved like any other. What the chat sends to AI is described under AI features below.

Job applications. In Track Applications we store what you enter about each job you apply to: the company, role, link, where you found it, dates (including the last date to apply), location, a campus drive’s eligibility rules, which resume you sent, its stage, your notes and timeline entries, your Get ready ticks, interview rounds (time, online or in person, meeting link or venue, interviewers, the questions asked, your own note on how it went and any feedback you were given), and what you told each company, and whom, about your salary, notice period and last working day. If you record an offer we store its amounts (fixed pay, variable pay and joining bonus), joining date, location, reply-by date and your notes on it. We also keep whether you told us you are a student or a working professional, and, when you choose to add them, an application or reference number, a test login or hall-ticket number, a bond or service agreement, and a date to try again. Job links and job text you paste are read by our own code to fill in the form, not by AI.

People at the company. For each application you can add contacts — a recruiter, hiring manager, referrer, placement office or anyone else — with the name, phone number, email address and LinkedIn link you type in. These are other people’s details, so add only what they gave you for this job. We use them only to show them back to you: we never contact these people, and they are not sent to AI or put in reminder emails.

A job posting you paste is saved with its application, together with any analysis, match, tailoring suggestions or interview guide you generate for it. If the posting states a salary, our own code (not AI) copies that range from its text so you can see it on the application. Job descriptions saved on the older Jobs page stay in your account too, and you can ask us to delete them.

Reading a job link. If you paste a link to a job posting, our server fetches that public page from the site it is on to fill in the company, role, location and description for you. Only the posting’s address is requested; nothing about you is sent with it. Some sites refuse this, and then nothing is fetched. The Rezome browser extension, if you install it, reads the job page you are on only when you open it (its button, its keyboard shortcut or its right-click items): the job’s title, company, location, description, the pay and the people the posting names (a hiring team, a recruiter, an email address written in the job text). If you connect it to your account, it talks to Rezome and nothing else. When you open it on a job, it asks your account whether you have saved that job already (sending the page’s address and the company) and how many of the job’s skills your resumes mention (sending the job’s text); neither is stored. The job is saved only when you press Save. In your browser it keeps a sign-in token and your last choice of resume, and text you right-click to save only until its window opens. A person the posting names is saved as a contact only if you tick them. Without connecting, it passes what it read to Rezome inside your own browser and sends nothing itself. If you also allow it to read job links, a link from Naukri, Indeed, LinkedIn or a few other job sites that you paste into your tracker is opened by the extension in a background tab in your own browser, read the same way, and closed; what it read is shown on that Rezome page and saved only if you press Save. When a link you paste can’t be read and you choose to open it, the extension opens it in a tab next to your tracker and remembers that tab for ten minutes; what it reads there, when you press its button (or by itself on a job site you allowed), goes back to that tracker page and is saved only if you press Save. If you switch on the Rezome button for a job site (in the extension’s settings, or when it offers), a small button shows in the corner of that site’s job pages, and on no other site. On each one it reads the job the same way and asks your account whether you have saved it and how your resumes cover it (sending the page’s address, the company, the role and the job’s text; none of it is stored), and saves it only when you press one of its buttons; people the posting names are never saved from it. It keeps its answer for each page for ten minutes, and a list of the pages it read (their address and which details it found, not the text) until you close your browser, which you can see and clear in its settings. A connected extension is listed under “Signed-in devices”, where you can sign it out. The extension’s use of this information follows the Chrome Web Store User Data Policy, including its Limited Use requirements: it is used only to save and track your jobs, never sold, and never used for advertising. “Add to calendar” makes the calendar file on your own device.

Reminder emails. Rezome can email you about an interview or a test deadline (the evening before and that morning), an application that has gone quiet, and, if you turn it on, a daily summary. They go to your Google account’s email address through our email service provider, and contain the company, role, round and time — never your notes, your contacts’ details, an offer or what you told a company. You choose which ones you get under “Notifications” in the account menu, you can turn them off for a single application, and every email has a link that turns them off in one click. We keep a record of each reminder sent (which kind and when) so none is sent twice, and your notification settings, until you delete the application or your account.

Share links and comments. If you share a resume, people with the link can leave comments; we store each comment with the name the reviewer typed. Reviewers do not need an account and we collect nothing else about them, apart from the rate-limiting described under “Keeping the service safe”.

Feedback. If you send us feedback through the feedback page, we keep the message, the kind of feedback you picked, the page you came from, your browser’s identifying string and — if you are signed in or typed one — an email address to reply to. Each message is also emailed to the team at Bitzberg so that it gets read; that email stays in our mailbox until we delete it, and deleting your account does not remove it — ask us and we will.

Codes and perks. If you use a beta or invite code, we store which code you used and the perks it gave you (for example extra AI credits a day), with their end dates, against your account. A code never gates sign-up and Rezome works the same without one. Deleting your account removes the link between you and the code; a record that the code was used stays, so it cannot be used again.

Where you came from. When you first visit, a cookie notes four things in fixed categories: the source and campaign named in the link you followed (if it carried them), the kind of site that sent you (Google, LinkedIn, WhatsApp, Instagram, direct or other) and which part of Rezome you landed on. Never the link or the referring page itself. If that visit becomes an account, those four facts and whether you used a code are written down once, so we can tell which efforts bring people who find Rezome useful. They are in “Download my data”, and deleting your account removes the link to you. Codes, perks and this record are kept while a perk is on and for 13 months after, then deleted.

Inviting friends. If you join through a friend’s link, we record that the two accounts are linked, to give each of you the beta perks: yours when you join, your friend’s a week after you first download a resume. Neither of you sees the other’s details — your friend sees counts, you see “invited by a friend”. We never ask for anyone’s contacts; people share their own link. When two linked accounts sign in from the same network within a day we note it for a person to look at, nothing more.

The beta survey. Two weeks into the beta we may ask you, once, how you would feel if you could no longer use Rezome, who you are (a fresher, experienced, switching careers), and two short written answers. The two choices are kept as counts; the written answers are read by the team like feedback. “Not now” means we never ask again. Feedback you send while a beta member is marked as such, so we can read the beta’s own first.

Your age. Rezome is for people 18 and older. The first time you use the app we ask whether you are, and keep your answer with your account. If you say you are under 18 you can still make and download resumes and track applications, but we leave you out of beta codes with extra perks, invitations, the survey, the campaign reports and any marketing, and we delete the record of where you came from — we don’t track people under 18. Under India’s data protection law that would need a parent’s verified consent, which we don’t ask for.

Email about new features. There is no mailing list. If you tick “Email me about new features” under Notifications we may email you about once a month, and every such email has a link that turns it off. Joining the beta or using a code never ticks it for you.

The welcome email. When you create an account we send one email saying what Rezome does and where to start (and, if you joined with a beta code, what it gives you). It is the only email you get for having an account; there is no mailing list to be added to.

On your device. The editor keeps a copy of unsaved edits in your browser’s local storage so nothing is lost if a save fails or the page closes. It stays on that device until the browser clears it.

AI features

Most of Rezome’s AI features use an AI model that does not write text. It answers questions we ask about your text — which section a line belongs to, which of your bullet points best shows a job’s requirement, whether an achievement describes a result — with yes/no answers, choices and ratings. Every sentence you read in a review, a job match, a tailoring suggestion or an interview guide is your own text, the job posting’s text, or wording we wrote in advance; none of it is generated. The one exception is the chat builder, described below, which uses a second AI provider whose model does write text.

AI is optional and never runs on its own: it runs only when you click an AI button, leave an AI option ticked or send a message in the chat builder — reading an imported file, the chat builder, “AI Resume Review”, analysing a job description, matching a resume against it, suggesting changes to tailor a resume to it, and preparing for its interview. Nothing is sent to our AI provider while you browse, type or download.

AI Resume Review needs to read the resume, so it sends the text of your resume’s sections: your headline, summary, experience, projects, skills and any other sections you have added. Your name, email address, phone number, location, links, photo and signature (with the declaration’s place and date) are removed before the request is made. Counts — bullet points, figures, repeated words — are worked out by Rezome itself and never asked of the AI.

Chat builder. Each message you send in “Build with chat” — together with the earlier messages in that chat and the resume drafted so far — goes to our second AI provider, whose model writes the resume’s wording and its replies to you. Whatever you type is sent, so leave out anything you would not put on a resume. Before a draft is shown, Rezome checks it against your own messages and removes any name, employer, school, date, number, skill or contact detail you did not give.

Job descriptions. Nothing happens to a saved posting until you ask: analysing it sends its text to our AI provider, and matching a resume against it sends that posting’s requirements together with your resume’s section text — again with your name, email address, phone number, location, links and photo removed. We keep the analysis and the match so you can read them again without spending credits, and they are deleted when you delete the resume, your account, or the last application that uses the job description.

Tailoring. Asking for tailoring suggestions sends your bullet points and skill lists, your roles and employers, and the job’s requirements, with contact details and your photo removed. Suggestions only reorder what your resume already says, or use the job’s name for a tool you already list; nothing is reworded or added. We save them so you can come back to them, and nothing changes in your resume until you apply a suggestion yourself.

Interview preparation. Preparing for an interview sends your resume’s section text and the job’s requirements — with your name, email address, phone number, location, links and photo removed, as above. It does not send any tailoring suggestions you have not applied. The questions come from a list we wrote; the AI only picks the ones that fit this job and the lines of your resume you could use as examples. We save the guide to your account so you can read it again without spending credits; it is deleted when you delete the resume, your account, or the last application that uses the job description. We do not look up the company, its interviewers or its hiring process anywhere.

Whichever feature you use, the request goes from our server to that feature’s AI provider over an encrypted connection, using an API key that stays on our server and is never shared with your browser.

We don’t store the text we send. To enforce the daily AI limit we keep a usage record of each request — which feature, when, how long it took, how many characters and tokens, and whether it succeeded — but not the text itself, and we don’t write resume content to our logs. A resume review is saved to your account so you can read it again without spending credits; you can see it in the editor, and it is deleted when you delete that resume or your account.

Our AI providers may process your text outside India, including in the United States. Neither uses the data we send to train its models; the chat builder’s provider may keep requests for a limited time to detect abuse. What each does with that data is governed by its own privacy policy and data processing terms, not by us. If you would rather no resume text reach an AI provider, simply don’t use the AI buttons — every other part of Rezome works without them.

AI never edits a saved resume. The chat builder writes a draft that you read before choosing to create the resume from it. A review, a job match or an interview guide is something you read; a tailoring suggestion appears beside your own text and only replaces it when you choose to apply it — which you can undo like any other edit. A suggestion that no longer matches what your resume says is refused rather than applied, so an AI suggestion can never overwrite a newer edit of yours.

How we use it

Your data is used to provide the service: rendering your resumes, generating PDFs, running the features you ask for, keeping you signed in, and replying to your feedback. We do not sell your data, and we do not share your resume content with anyone except our AI provider when you use an AI feature, as described above.

We also look at activity records (described under “How long we keep it”) to see how Rezome is used, find what is broken and stop abuse. The few people who run Rezome can see account details and those records. They can open the content of a resume only to solve a problem, such as one you reported, and every time they do, who opened it, when and why is recorded.

Sharing a resume

A share link is a public page: anyone who has the link can see that resume as it is, including any contact details on it, and the comments reviewers have left. Search engines are told not to index it, and nothing else on your account is visible. You can turn the link off or replace it at any time from the editor; the old link then stops working. A share link works for 24 hours from when you create, replace or renew it; after that it stops opening until you renew it. We count how many times the link is opened and when it was last opened, and show that count only to you — nothing about who opened it is recorded.

Cookies and analytics

We set two first-party cookies of our own: one that keeps you signed in for 30 days, and one that lasts a few minutes during Google sign-in to protect it from tampering.

We use Google Analytics to understand how the site is used — which pages are visited and how people move between them. It sets its own cookies and receives the page address and standard browser information; it is not loaded on shared resume pages or the print page, so a share link’s address never reaches it, and we do not send it your name, email or resume content. We also tell it when an account is created, a resume is created (blank, imported, from chat or duplicated) and a resume is downloaded (the file format, template and page size), which button you press on the one-time “share Rezome” prompt after a download, and when the resume checker or keyword matcher gives a result (only a rough band such as “strong” or “low”, never the score or your text), so we can learn which channels bring people who actually use Rezome. Those signals carry no names, ids or resume content.

Third-party advertising partners (such as Google AdSense) may set cookies to show relevant ads on free pages; you can opt out of personalised advertising at Google Ads Settings. Ads never appear inside your downloaded PDFs.

Keeping the service safe

To stop abuse we count requests per account and, for pages that work without an account (share links, feedback and the resume checker), per network address (an IPv6 address shortened to its /64). Each count is a row in our database holding only that key, the count and when its window ends; windows last an hour at most, and a row is deleted soon after its window ends. Our web server keeps standard access logs for troubleshooting, which include network addresses and page addresses but never resume content. When something breaks on our server we may send an error report to an error-tracking service: the error’s text, where in our code it happened and the kind of page — never the page address, cookies, your resume or anything you typed.

How long we keep it

Your account, resumes, versions, job applications and AI results stay until you delete them. Backups of the database — one each night, and one before each change to the database’s structure — are kept on our server for 14 days. A copy of each nightly backup may also be kept in separate cloud storage, where it is deleted automatically after 90 days. So deleted data disappears from our server’s backups within 14 days and from every backup within 90 days. AI usage records (counts, not text) are kept after an account is deleted, linked only to a one-way hash of your Google account ID, so deleting and re-creating an account doesn’t reset the daily AI limit. For security we keep a log of sign-ins, sign-outs, account deletions and share-link changes — the time, the event, a one-way identifier of your Google account and your IP address (an IPv6 address shortened to its /64) — for 13 months, after which it is deleted. For each signed-in device we keep your browser’s user-agent string, an approximate network address (an IPv4 address, or an IPv6 address shortened to its /64), and when it signed in and was last active (to the hour); you can see these and sign any of them out under “Signed-in devices”. A device is signed out after 14 days without use, and every sign-in ends after 90 days.

We keep activity records of what you do in Rezome — creating, importing, downloading, restoring or deleting a resume, adding, moving or closing a job application, receiving a reviewer’s comment, sending feedback, opening the editor on a phone, tablet or computer, changing a template, design setting or section — with the time and a few facts such as the file format, template or page size, and how long a PDF took to make. They never include what you wrote, the name of a file, a job posting or your network address. They are kept for 13 months, then deleted. If you delete your account they are kept for the rest of that time without any link to you or your Google account, so they only count towards totals. They are included when you download your data.

Deleting your data

Deleting a resume removes it, its versions, its share link and its comments permanently. To delete your entire account, open the account menu on your dashboard and choose “Delete account”. Deletion is immediate and cannot be undone: your account, resumes, versions, comments, job applications and AI results are all removed. Three things are kept: feedback messages you sent, with the link to your account removed; activity records, with the link to your account removed; AI usage counts, as described above; and backup copies until they expire as described above. Anything the editor kept in your own browser stays there until you clear it.

Your rights

You can see and edit everything you have stored from your dashboard, download any resume as a PDF or plain text, and delete any of it or all of it yourself. “Download my data” in the account menu gives you everything we keep about your account as one JSON file: your profile, resumes with their version history and reviewer comments, job applications with their job descriptions, timelines, interview rounds, contacts and offers, your notification settings, AI results, a daily summary of AI credits used, feedback you sent, your signed-in devices and recent sign-in and sharing activity with the network address each came from. For safety it leaves out sign-in tokens and share links, and photos and signatures in older versions. If you want something corrected, contact us and we will help.

Changes to this policy

When a feature changes what it collects or sends, this page changes with it and the effective date at the top is updated.

Contact

Rezome is built by Bitzberg. Use the feedback page, email bitzberg.in@gmail.com, or reach us via bitzberg.in.