Privacy Policy

Who we are

Rezifi is operated by Rezifi AI LLP (LLPIN ACX-0634), a limited liability partnership registered in India with the Registrar of Companies, Haryana. In this policy, Rezifi AI LLP is the data fiduciary under India's Digital Personal Data Protection Act, 2023, and the data controller under the EU and UK GDPR.

Our Grievance Officer, as required under the DPDP Act, is Rishab Lamba (rishab@rezifi.com).

We have not appointed a representative in the European Union or the United Kingdom under Article 27 of the GDPR. Rezifi is operated from India, and our processing of EU and UK personal data is occasional — we will appoint a local representative if that changes. If you are in the EU or the UK, you can exercise every right in this policy by writing to us directly, and nothing about the missing representative narrows those rights.

For anything in this policy, or to make a request about your data, write to support@rezifi.com.

What this policy covers

This policy covers the Rezifi website at rezifi.com, the Rezifi app at app.rezifi.com, the Rezifi Chrome extension, and the emails we send you about your account.

It also covers the free ATS check, which you can use without an account at app.rezifi.com/check or from the upload box on rezifi.com/ats-resume-checker or rezifi.com/ats-resume-checker-for-freshers, which the rezifi.com homepage, the skill pages at rezifi.com/skills and the careers pages at rezifi.com/careers also open, and which the application form on a careers page starts when you attach your resume. What is different about a check is set out under "The free ATS check, without an account" in the next section, and wherever it matters below.

It also covers applying for a job at Rezifi itself, through rezifi.com/careers, set out under "Job applications to Rezifi".

It also covers the public job search that AI assistants and other software use without an account, and the search box on our job list pages, set out under "The job search for AI assistants".

It does not cover the job boards, employers, and applicant tracking systems you apply through, and that limit matters more here than it does for most products. When you use auto-apply, you are asking us to type your information into someone else's website, where you then check it and press its Submit button yourself. From the moment you submit, the employer and their applicant tracking system hold your data, and their privacy policy applies to it, not ours. We have no ability to retrieve or delete what they hold.

The same applies to job listings you view through our extension, and to Google Drive and Google Docs when you choose to import or export a resume.

Our Terms of Service, at rezifi.com/terms, cover the rest of the relationship — what Rezifi is, what you can do with it, and who is responsible for what. The two documents are written to agree with each other.

What we collect

Account and sign-in

When you create an account we store your name, your email address, whether that address has been verified, your profile image if your sign-in provider supplies one, and internal flags describing your account type and role.

Sign-in options are the ones shown on our sign-in page. Depending on which we have enabled, these include a social provider such as Google, a magic link sent to your email, or an email address and a password. If you sign in with a social provider, we store the tokens it issues us so we can keep you signed in. If you set a password, we store it hashed — we never hold it in readable form and we cannot recover it for you.

If you connect Google Drive — from your account page, or the first time you open a resume in Google Docs — Google issues us a refresh token for that connection, which we store. Its scope lets us see only the files we create, never the rest of your Drive, and we use it for one thing: creating the Google Doc when you ask us to. You can disconnect it on your account page at any time, which revokes the token at Google and removes it from our records; deleting your account does the same. The Google account you connect need not be the one you sign in with, and once connected it can also be used to sign in to your Rezifi account.

For each active session we store the IP address and browser user-agent that created it. We use these to keep your account secure and to let you recognise a session you do not think is yours.

Billing

If you pay for Unlimited, we store the mobile number you give us for the payment, the identifiers Cashfree assigns to your subscription or one-time payment and to each payment, its status, and the date and amount of each payment. We never see or store your card number or UPI details: you enter those on Cashfree's own page, and Cashfree returns the status of the mandate and of each payment.

Keeping the free trial to one per person

The free trial is one per person, whichever account you use it from. To keep it that way we keep a one-way fingerprint of your sign-in email; of the email addresses, phone numbers, LinkedIn and GitHub addresses on your resumes and on Your profile; of each resume file you upload; and of each copy of the extension you sign in from. A fingerprint is a keyed hash: it tells us that two accounts share one of those details, and it cannot be turned back into the detail. We use it for one thing: when an account shares one with an earlier account, the two share one free trial. Your name, address, school and employer are never used for it.

Resumes and documents

When you upload a resume we keep the original file as raw bytes, not just the text we extract from it, because rebuilding your exact formatting on export depends on the original document. Alongside it we store the parsed structure of your resume, which typically contains your name, email address, phone number, location, and any LinkedIn, GitHub, or portfolio links you have on it.

We keep every version you save, so you can go back to an earlier one. We also store the files we generate for you — PDFs, Word documents, thumbnails — and a set of derived artefacts we compute so the product does not have to redo expensive work: resume analyses, extracted skills, job-fit scores, a written profile summary, cached grammar and rewrite suggestions, and a numerical embedding of your resume used for matching.

When you tailor a resume we keep the suggestions with the tailored copy they were made for: the job it was tailored to (its company, title, link, and description), each suggested edit with the line it would replace, any wording you wrote in its place, and whether you applied or dismissed it. Keeping them is what lets you review the same suggestions in the side panel or the editor, with your own wording on both, pick up a review you left, and see which lines of the finished resume were changed.

If you bring a PDF or a Word file to start from a template, the text is taken out of it on our own servers. If you import from Google Drive, the file is selected in your browser through Google's own picker under a scope that only grants access to the specific file you choose.

The free ATS check, without an account

You can check a resume without signing in, at app.rezifi.com/check or from the upload box on rezifi.com/ats-resume-checker or rezifi.com/ats-resume-checker-for-freshers, which the rezifi.com homepage, the skill pages at rezifi.com/skills and the careers pages at rezifi.com/careers also open, and which the application form on a careers page starts when you attach your resume. A check started on rezifi.com goes to our API like any other, and its result opens at app.rezifi.com/check. We do not ask for your name or your email address. A check collects:

• The file you check, and the structure we read from it, which, like any resume, typically holds your name, contact details, work history and education.
• What we work out from it: the score and grade, what a machine reads from it, the list of fixes; for a check started from a skill page, which of that role's listed skills your resume names; and, for a check started by the application form on a careers page, which open jobs at other companies fit it. That includes suggested rewrites and grammar corrections, which we keep on our servers and show you only if you keep the check.
• A fingerprint of the file, so that sending the same file twice does not count as a second check.
• A random identifier, in a cookie in your browser, described under "Cookies".
• Your IP address, which we use to check that you are not a bot and to count checks. We hold it as it arrives for a few minutes at most, to limit how fast requests can come, and beyond that only as a one-way hash, which is deleted within 24 hours of your last check.
• Where your browser first came from to Rezifi, when our rezifi_first cookie holds it: the site that sent you, the page you landed on and any campaign tags, as described under "How you found us".

If you check a Google Doc, Google's own picker opens in your browser and grants access to the one file you pick. Your browser saves it as a Word file and sends us that file. We receive no access to your Google account.

Before a check runs, the page runs a bot check in your browser: Cloudflare Turnstile. Cloudflare's script reads technical signals from your browser to tell a person from a bot (Cloudflare names your IP address, your browser's user-agent and its TLS fingerprint among them), and we send Cloudflare your IP address again when we confirm the result. Cloudflare says it uses these signals to detect and block bots, not to identify, profile or target anyone. It processes them for us, and also on its own account to improve its bot detection, as its Turnstile privacy addendum explains. The bot check runs only where a check can start: on the free check page at app.rezifi.com/check, and on rezifi.com/ats-resume-checker and rezifi.com/ats-resume-checker-for-freshers, where its script loads only once you start using the upload box, and on the rezifi.com homepage, the skill pages at rezifi.com/skills and the careers pages at rezifi.com/careers only once you open the upload box or attach a resume to the application form there.

A check is deleted within 24 hours unless you sign in and keep it, and you can delete it sooner yourself. If you keep it, it becomes one of your resumes, and everything this policy says about resumes applies to it from then on. How long each part of a check lasts is set out under "How long we keep things".

Job search preferences and application answers

If you use the job feed, we store the preferences you set: the roles and locations you want, whether you need remote or hybrid work, a salary floor, employment types and company stages, companies and keywords to exclude, whether you need visa sponsorship, and any named filter sets you save.

If you use auto-apply, we store the details it needs to fill in forms: your preferred name and postal address, your work authorisation and whether you need visa sponsorship — recorded per country, because the answer differs by country — notice period, willingness to relocate, languages, years of experience, highest education, your current compensation and the salary you would accept, and your portfolio, LinkedIn, GitHub, Twitter and website links.

We also store, verbatim, the answers you give to job application questions, so that the next application does not ask you again: the short answers you type into a form the extension fills or correct there, which the extension reads from the page when you press the form's own Next or Submit button, and, once you submit the application, the short answers it wrote that you left as they were. That includes a date of birth, if a form asks for one. We never store a password, a one-time code, a government or tax identity number, a passport number, or a card or bank detail, whatever the form calls the field. Because these are free text, they contain whatever you chose to write. We keep a snapshot of the form fields on applications you submit, for the same reason.

Demographic information

Separately from everything above, you can optionally save answers to the voluntary equal-opportunity questions that many application forms ask: gender, ethnicity, veteran status, disability status, and pronouns. Every one of these is optional and every one is blank unless you fill it in. If you answer one of these questions yourself while the extension is filling a form, that answer is saved too, so you are not asked again — you can see and delete it under Your profile at any time. A question you declined to answer is never saved.

We use them for exactly one thing: pre-filling those voluntary questions when auto-apply fills a form for you. We do not use them to rank you, to match you to jobs, or to make any decision about you or your account.

You should know one thing before you fill them in: when auto-apply runs, these answers are sent to a third-party AI provider along with the rest of the form-filling request, so that it can work out which answer belongs in which box. We treat this information as sensitive personal data, and we know that sending it to a third party is the part of this policy a reasonable person would most want to be told about. You can withdraw it at any time by clearing the fields, which deletes the stored values.

What the browser extension collects

Nothing the extension reads on a page is sent to us before you have signed in.

On the job sites and hiring platforms the extension recognises — the six job portals listed in the extension section below, and the common applicant-tracking systems such as Greenhouse, Lever, Workday, and Ashby — the extension reads the job listing you are viewing — its title, company and description — inside your browser, so the side panel can show it to you and tailor against it. The listing is sent to us only while your side panel is open on that page. With the panel closed, the read stays in your browser: it is what lets the small Rezifi tab appear at the edge of a posting. We keep a record of which account captured a listing, for abuse control, and never show that to anyone.

On every other page you open, a very small check runs inside your browser to see whether the page looks like a job listing: it looks for the standard job-posting markup that career sites embed, or for words like "careers" or "jobs" in both the page's address and its title. The same check notes whether the page is a form on a form service such as Google Forms, Microsoft Forms or Typeform. Almost every page fails that check, and for those pages nothing else happens and nothing is sent. When a page passes it, the extension reads the listing so the side panel can offer to tailor your resume to it, and sends us an anonymous diagnostic event that names the site's domain — for example careers.example.com — so that we can see where reading a listing works and where it fails. The event carries no account, and nothing else about the page: not its address, not the listing, not anything you typed. On a form service's form, the extension reads the form inside your browser so the small Rezifi tab can offer to fill it, and the diagnostic event it sends does not name the site.

While the side panel is open, the extension also reads the page in the tab you switch to, so it can tell you whether there is a posting there to work from. If there is not, nothing from that page is sent to us — not its address, not its domain, not its content.

When you open one of the six job portals while signed in to Rezifi, the extension tells us which portal it is and when, so that your job feed only offers a quick apply on a portal where the extension is active, rather than letting you start and fail. It does not read whether you are signed in there, what you looked at there, or anything about your account on that portal.

When you use auto-apply on an application page, the extension reads that page's form — the field labels, their choices, and any values already on the page — and the text of the page, and after it fills the form, what landed in each field, so it can check its own work. It reads a form before you have asked it to fill anything in two cases: when you start tailoring while the application form is already open in that tab, so that your answers are ready by the time the plan is; and when you queue jobs from the panel, in which case it opens each application in a background tab and reads its form. Nothing is typed into a page until you start the fill or approve the queue. The value of a password field is never read, and a field that asks for a one-time code, a government or tax identity number, a passport number, or a card or bank detail is left out entirely: it is not read, not sent, not filled, and stays yours to type.

While it fills an application form, the extension notes which of that form's fields you change on the page. When you press the form's own Next or Submit button, it reads what those fields hold, so it can remember your answers for your next application, as described under "Job search preferences and application answers". It also records which questions it answered wrongly, meaning the answers you changed or cleared on the page, that you marked as wrong in the extension, or that the page itself changed after the fill: the question, the kind of field, where its answer came from (for example one of your saved answers, your resume, or its AI), how the answer was picked on the page (for example an exact match on a list, or the closest option), and the site, but never the answer itself. That record is linked to your account, and we use it to make auto-apply answer better.

How you found us

When you open a page of rezifi.com from another site, an app or a typed address, or open the Rezifi app while signed out, we count that visit. We note the address of the site that sent you, if your browser tells us (for example google.com or linkedin.com), the page you landed on, and any campaign tags in the link (the utm_source, utm_medium, utm_campaign and ref parts of a web address). We keep these only as a count per day. A visit is never stored with your IP address, your browser's user-agent, an identifier or your account, so a count cannot be traced back to you. On rezifi.com we leave out page loads by crawlers, scripts and computers in cloud data centres: to tell them apart we look at the headers your browser sends with the page request and at which network your connection comes from, and store neither.

So that we can tell which pages and sites lead people to sign up, we also keep the same facts about your browser's first visit in a cookie, rezifi_first, described under "Cookies". If you then create an account, or start a free check, from that browser, we file those facts with the account or the check: the site that sent you, the page you landed on, the campaign tags and the day of that first visit. We do not set this cookie, and so keep no first visit, if you are in the European Union, the European Economic Area, the United Kingdom or Switzerland, if we cannot tell which country you are in, or if your browser sends the Global Privacy Control signal. We work the country out from your connection's address when you arrive, and store neither.

Technical and diagnostic data

We record errors, the cost and token usage of the AI calls we make on your behalf, which jobs were shown to you and whether you clicked, saved, applied to, or hid them, which tailoring suggestions you accepted or dismissed, which suggested fixes on your resume's ATS score you were shown, applied, or dismissed, and the outcome of apply attempts. Some of this is linked to your account, because a report that cannot be traced back to a specific run is not much use for fixing your specific problem.

When you search the job feed, we keep what you searched for: the words you typed, the skill or company you picked, how many jobs the search found, how long it took and whether it worked. It is linked to your account, so that we can see which searches find nothing or the wrong jobs and fix them, and so that the search box can offer your recent searches again on any device you sign in on. Clear in that list deletes them. We delete each search 90 days after you make it, and all of them at once when you delete your account.

To have your job feed ready before you open it, we also keep, linked to your account, the country your browser's time zone points to, for 90 days after you last use Rezifi. We use it for nothing else, and delete it at once when you delete your account. Until 23 October 2026 we also kept the countries you chose to look at jobs in, for a week after the last one you chose; we no longer collect them, and the last of them are deleted by 30 October 2026.

When you save a search, we keep it until you remove it: the name you give it, the search itself (its words, the skill or company, and the filters), whether we email you its new jobs and how often, when you last opened it and when we last emailed you about it. We use it to show which jobs are new for it and, unless you turn its email off, to email you those jobs. It is linked to your account and in your data export, and it is deleted when you remove the search or delete your account.

We also keep a record of how you use Rezifi itself. For each day you use it, it notes which parts you used (for example your resumes, tailoring, the job feed, or filling in an application with the extension), how many times, whether you were on the web app on a computer, on a phone, or in the extension, and which half-hours of the day you were active. For the last 90 days it also notes the minute each of those uses happened (which part, from where, and how many times in that minute, nothing more), so we can see the order in which you used Rezifi on a day. It also notes the kind of browser and operating system you used (for example Chrome on Windows) and the country your connection came from. We work the country out on our own servers from the IP address of a request when it arrives, and, for sign-ins made before this record began, from the address stored with the session; this record keeps the country only, never the address, and we send the address to no one to do it. It also notes when something did not work for you: which part it was and what kind of error it was. It is linked to your account and holds counts only, never what you typed, uploaded, or read. We use it to see how many people use Rezifi, what they use, where they are and what they use it on, whether it works for them, and whether they come back. The day after you join, we also use it to see whether you have used Rezifi only on a phone so far, to decide whether to send you the one email about applying from a laptop, described under "Email from us". We also use it, and the country it notes, to decide whether to send you the one email with your resume in a template, described there too.

The extension also sends a diagnostic report at the end of every fill, whether it finished, was cancelled or failed, and again when you press submit, so we can work out why fills go wrong. Reports sent since 27 September 2026 are linked to your account and include the web address of the application page, the platform, timings, the version and build of the extension that sent them, the form's field labels and types, counts of what was filled and what was left blank, how each answer was chosen (for example, an exact match on a list, or the closest option), and the name of the resume file that was attached, which is built from your name. They do not include the values that were filled in. Reports linked to your account are part of your data download and are deleted when you delete your account. Reports sent before that date carry no account link and stay on the manual deletion schedule below.

Job applications to Rezifi

If you apply for a job at Rezifi through rezifi.com/careers, we collect what you send us: your name, your email address, the resume file you attach, any links you add and anything you write in the note. Like any resume, yours typically holds your contact details, work history and education. We ask for nothing else, and you do not need a Rezifi account to apply.

We use your application for one thing: to consider you for the role you applied to, or for another role at Rezifi that fits, and to contact you about it. The people at Rezifi who hire read it in our internal tools. The resume file in it is also used in the two ways set out next, and for nothing else.

When your application reaches us we send one email to the address you gave, to confirm it. It holds nothing you typed, and when you had the free check it says how to open your result. We send it through our email provider, and it is the only email an application starts by itself.

The careers pages also offer the free ATS check. On the application form, the check starts as soon as you attach your resume, with nothing to press: a separate copy of the file goes to the check before you press Send application, so a file you attach and never send is checked too. It is the free check described under "The free ATS check, without an account", handled like any other check, which includes reading by our AI providers, and deleted within 24 hours unless you keep it. The check does not affect your application: its result is never attached to an application or used to consider you. We do use it to choose the jobs at other companies we show you after you apply, by comparing what the check read with what those jobs ask for. No AI provider reads anything further for that, and we do not store the comparison.

If you choose a job after you apply, you sign in and keep that check, and the job waits for you in the editor: nothing is tailored until you press Tailor. So the sign-in screen can show the way in that fits your address, the link carries the email address you applied with in a part of the web address no server receives. If you then continue with Google, we pass that address to Google so it can offer the right account. If the resume you attached is a PDF, we set it in one of our designs and ask how you want to use it. If you use your own Word file or Google Doc instead, it takes the place of the copy we made from your PDF, and that copy is deleted.

If you sign in to Rezifi with the email address you applied with and have no resume in your account, we bring the resume from your application into your account, once, and tell you when we do. Only the same email address does this. It then works like any resume you upload, which includes processing by our AI providers, and you can remove it from your account, which does not touch your application. Your application stays with us as described here either way.

Before your application is sent, the form runs the same Cloudflare Turnstile bot check described under "The free ATS check, without an account", which receives your IP address and technical signals from your browser. Its script loads only once you start filling in the form. We also use your IP address to limit how many applications can come from one network in an hour: we hold it for up to two hours for that, and never store it with your application.

We keep your application for 12 months from the day you send it, so we can reach out if another role fits, and then delete it automatically. The schedule is under "How long we keep things".

To get a copy of your application, or to have it deleted sooner, write from the email address you applied with to support@rezifi.com.

The job search for AI assistants

Anyone can search Rezifi's open jobs from an AI assistant such as Claude or ChatGPT, or from other software, without an account. A search carries only what was asked for: the role, skill or company, the place, whether the job is remote, the level, and how many jobs to show. It needs no resume and no sign-in, and we never ask your assistant for either.

The search box on Rezifi's job list pages runs this same search, without an account, and everything in this section applies to it.

We use those words to answer the search and then let them go. We hold the answer in our server's memory for up to 10 minutes, so that the same search is not run twice. We do not save what was searched, in our database, our logs or our traces, and nothing ties a search to a person. We keep counts only: how many searches came in and how long they took.

The IP address the search comes from, which is yours on our job list pages and may be your assistant maker's from an assistant, is used to limit how fast searches can come. We hold it for a few minutes at most.

Your assistant is run by its own maker under its own privacy policy, and what you say to it is between you and them. If you open a job on Rezifi from a result, this policy applies as it does to any other visit.

How we use it

We use the information above to:

• Run your account, keep you signed in, and send you the emails your account requires — sign-in links and codes, and notices about your subscription, such as a payment that failed or a cancellation.
• Email you the new jobs for the searches you save, unless you turn that email off.
• Email you once, the day after you join Rezifi from a phone, about applying with your resume from a laptop, unless you have stopped it.
• Email you once to show your resume in one of our templates, if you are early in your career and your resume is still in your own layout, unless you have stopped it.
• Set up, charge and manage your subscription or one-time week, if you buy one.
• Store, parse, render, and export your resumes while preserving their formatting.
• Tailor your resume to a job description, suggest rewrites, check grammar, and produce insights about your resume.
• Check a resume without an account: score it, show you what a machine reads from it and what to fix, and delete it within 24 hours unless you keep it.
• Rank the job feed against your skills and preferences.
• Fill in application forms for you to check on the page and submit yourself, remember the answers you give so the next form asks less, and learn from the questions it answered wrongly.
• Debug problems, keep the service reliable, and control what our AI usage costs us.
• Understand how Rezifi is used, which parts people rely on, and whether they come back, so we can improve it.
• Understand which sites, pages and campaigns bring people to Rezifi, and which of them lead people to sign up.
• Detect and prevent abuse, keep accounts secure, keep the free trial to one per person, and keep bots off the free check and its use within its limits.
• Consider your application, if you apply for a job at Rezifi, and contact you about it.

We do not use your information for advertising, we do not build advertising profiles, and we do not sell it.

Our legal bases

Where the EU or UK GDPR applies to you, we rely on the following legal bases. Where India's DPDP Act applies, we process your personal data on the basis of the consent you give when you create an account and when you choose to use each feature, and, for the free check, the consent you give by attaching your resume to the application form on a careers page, or by pressing Check my resume, beside the notice that says Rezifi will check your resume and keep it for 24 hours and that links this policy, which sets out what the check does with it and who processes it. For a job application to Rezifi, it is the consent you give by pressing Send application, beside the notice that says we keep it for 12 months and that links this policy.

AI providers

This is the section most people will want, so it is near the front and written plainly.

To tailor your resume, generate insights, and fill in application forms, we send your information to third-party AI providers we work with. Tailoring sends the text of your resume and the job description. Auto-apply sends the most: your name, email address, phone number, location, your LinkedIn, GitHub and portfolio links, your work history and education — including your GPA, if it is on your resume — plus the text of the page you are applying on, any answers you have saved for reuse, and any demographic answers you have chosen to save.

To match you with jobs, we send them a short line about your work: your recent job titles, your field and your years of experience, never your resume, your name or your contact details. It is used to rank jobs for you and to label how close each one is to your work, in the job feed and when the extension shows how well a job on another site fits you.

A free check, made without an account, sends them the text of the resume you check, to read its structure, score it and find what to fix. Everything in this section applies to it, including what we say about training.

To show your resume in one of our templates in the email described under "Email from us", we send them the text of your resume again, to read it into the template. Nothing it makes is added to your account unless you choose to keep it.

We use several providers, and which one handles a given request can change as we tune the product for quality, speed, and cost. We do not publish which ones — that is commercially sensitive, and a printed list would go stale quietly. What we will do is tell you directly: if you want to know who currently receives your data, write to us and ask.

On training: we choose providers whose terms say they will not train their models on data sent through their APIs, and we have never given any provider permission to train on your data. We last checked each provider's published terms on 26 July 2026, and we repeat that check before adding a provider or changing which one handles your data. What we will not tell you is that we can independently verify what a provider does with your data once it reaches their servers, because we cannot, and no one in this market honestly can.

We do not use your data to train any model of our own.

Who else we share with

We share your information with service providers who process it only to run Rezifi, and only on our instructions. By category, with representative examples:

• AI providers, to tailor resumes, generate insights, map application fields, and match you with jobs. We work with several, and which one handles a given request changes as we tune for quality, speed, and cost. We do not name them here — which models we use is commercially sensitive, and any list we printed would go out of date quietly. Every one of them is covered by the commitment in the previous section, and if you want to know who currently receives your data, ask us and we will tell you.
• Cloud hosting and databases, which run our API and store your account and resume data — including Amazon Web Services and Crunchy Bridge.
• Caching, which briefly holds generated documents so we do not regenerate them on every request.
• Object storage and content delivery, which hold your resume files and serve them to your browser — including Cloudflare.
• Bot detection only where the free check runs (app.rezifi.com/check, rezifi.com/ats-resume-checker and rezifi.com/ats-resume-checker-for-freshers once you use their upload box, and the rezifi.com homepage, the skill pages at rezifi.com/skills and the careers pages at rezifi.com/careers once you open the upload box or attach a resume to the application form there) and on the job application form at rezifi.com/careers once you start filling it in, which receives your IP address and technical signals from your browser to tell a person from a bot: Cloudflare, through its Turnstile service. Cloudflare processes these for us, and also on its own account to improve its bot detection, as described under "The free ATS check, without an account".
• Email delivery, which sends your sign-in links and codes, your subscription notices, your job alert emails, the one email about applying from a laptop and the one email with your resume in a template — including Resend.
• Payments — Cashfree Payments India Private Limited, which sets up your subscription mandate and takes each weekly payment, or takes the single payment for a one-time week. We send it your name, email address, mobile number, a subscription or order identifier and an internal account identifier; it returns the mandate and payment status. Cashfree processes this in India.
• Error and performance monitoring, which receives technical traces of requests, including identifiers for your resumes but not their contents — including Grafana.
• Uptime monitoring and secret management, which handle no personal data of yours.

Three things that are not this kind of sharing, and are worth separating out:

• Parties you direct us to. When you export a resume to Google Docs, we act on your instruction using your own Google credentials. When you submit an application, the employer and their applicant tracking system receive it. Those are your choices, and their handling of your data is governed by their policies.
• Legal disclosure. We may disclose information where we are legally required to, or where it is necessary to protect our rights, our users, or the public. We will not do this quietly if we are permitted to tell you.
• Business transfer. If Rezifi is acquired or merged, your information may transfer as part of that. We would tell you before it changed how your data is handled.

We do not sell your personal information, and we do not share it with advertisers or data brokers.

The Rezifi browser extension

The extension requests access to all websites. We would rather explain that than bury it.

The reason is that job application forms live on domains nobody can list in advance — Workday, Greenhouse, Lever, Ashby, and thousands of company-specific career subdomains, each with its own address. Chrome has no permission for "the site the user is applying on", so an extension that fills in application forms has to ask for the broad permission or not work.

What that permission does and does not mean in practice:

• On six job sites — LinkedIn, Indeed, Naukri, Foundit, Wellfound, and Glassdoor — and on the common hiring platforms we recognise, such as Greenhouse, Lever, Workday, and Ashby, a script runs automatically when you open a job page, and reads the listing inside your browser. It reaches us only while your side panel is open on that page.
• On every other website you visit, only the small local check described under "What the browser extension collects" runs when a page loads. If the page does not look like a job listing, nothing else happens and nothing is sent. If it does, the extension reads the listing and sends an anonymous diagnostic event naming the site's domain — nothing else about the page, and nothing tied to your account.
• While the side panel is open, the extension reads the page in the tab you switch to, so it can tell you whether there is a posting to work from; if there is not, nothing from that page is sent. It also reads an application form that is already open when you start tailoring, or that you have queued, so your answers are ready — nothing is typed until you start the fill.
• Beyond that, the extension acts on a page only when you start something on it yourself — a manual capture, a fill.
• Nothing from a page that is not a job posting or an application form is sent to us.
• Nothing the extension reads is sent before you sign in.

The extension's use of the information it handles complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. In plain terms: we use what the extension reads only to provide and improve what the extension is for — helping you apply to jobs; we do not sell it, and we do not use or transfer it for advertising, to determine creditworthiness, or for lending; we transfer it only to the service providers described in this policy, who process it on our instructions for that same purpose, or where the law requires it; and people at Rezifi do not read it, except with your consent — for example when you ask us for help with a specific application — to investigate abuse or a security problem, to comply with the law, or in aggregated, anonymised form for running the service.

The extension stores a sign-in token in your browser's extension storage. That token is what lets the side panel talk to your Rezifi account, and it is removed when you sign out.

When you start auto-apply on a job's posting that has no form on it, it may press the posting's own Apply button to open the form. It never presses a job board's one-press apply, which would apply for you. When auto-apply runs, it reads the application form, sends the form's structure and the page's text to an AI provider to work out which of your answers goes where, fills the form in, and attaches your resume. It then leaves the filled form on the page for you to check, marking there what it left blank or is unsure about, and you correct anything on the page itself. On a form that runs over several steps, once you have pressed through the first step yourself it may press the employer's own Next or Continue for you when every answer on a later step came from your saved answers, your defaults or your resume; you can pause that at any time. It never presses Submit: submitting is always your own press, on the employer's own Submit button.

Cookies

Rezifi sets a session cookie when you sign in, and a short-lived signed cookie that caches your session so every request does not hit the database. Both are HttpOnly, both are restricted to our own domain, and neither can be read by another site.

Beside them sits one flag cookie that says only whether this browser is signed in, so rezifi.com can offer to open the app instead of asking you to log in. It holds a single fixed value and no personal data, it is set and removed by our own servers with your session, it can be read only by our own sites, and it grants nothing: the app still checks your real session when you arrive.

If you use the free ATS check without an account, our API sets one more cookie, named __Host-rezifi_check: a random identifier, HttpOnly, restricted to our own domain, and kept in your browser for 30 days from your first check. We use it only to count your checks against the daily limit, to show a check's result only to the browser that made it, and to let that browser keep the check when you sign in. It holds nothing but that identifier.

The free check's pages, and the job application form at rezifi.com/careers, also run Cloudflare's bot check, described under "The free ATS check, without an account". Cloudflare's own documentation says the bot check relies on cookies and local storage in your browser to do its work. They sit under Cloudflare's own address, not ours, and Cloudflare describes what Turnstile collects as strictly necessary for detecting and blocking bots.

When you first arrive at rezifi.com, or at the Rezifi app while signed out, from somewhere else, our servers set one more cookie, named rezifi_first, on our own domain. It holds the facts of that first visit, as described under "How you found us": the address of the site that sent you, the page you landed on, any campaign tags in the link, and the day. It holds no identifier and nothing about you, it is HttpOnly, so no script can read it, it can be read only by our own servers, and it is kept in your browser for 30 days. We read it once if you create an account or start a free check from that browser, to file those facts with it. It is never set if you are in the European Union, the European Economic Area, the United Kingdom or Switzerland, if we cannot tell which country you are in, or if your browser sends the Global Privacy Control signal.

That is the entire list of cookies we set. We set no advertising cookies and no third-party cookies of any kind. We run no third-party analytics scripts, no session replay, and no tracking pixels on any of our sites: the visits described under "How you found us" are counted by our own servers, from the page requests your browser already makes. The free check also runs Cloudflare's bot check script where it starts: the free check page at app.rezifi.com/check, rezifi.com/ats-resume-checker and rezifi.com/ats-resume-checker-for-freshers once you start using their upload box, and the rezifi.com homepage, the skill pages at rezifi.com/skills and the careers pages at rezifi.com/careers once you open the upload box or attach a resume to the application form there. So does the job application form at rezifi.com/careers, once you start filling it in. It is there to keep bots out, not to measure or follow you.

This is also why you will not see a cookie banner here. We do not think you should have to dismiss a consent dialog for cookies that are strictly necessary for the site to work: signing in, and, on the free check and the job application form, counting checks and keeping bots out. The one cookie that is not strictly necessary, rezifi_first, is set only where the law does not ask for your consent first, and never when your browser sends Global Privacy Control.

Where your data is stored

Our API, database, and caches run in India, in Amazon Web Services' Mumbai region. Your resume files are stored on Cloudflare's network and served from it, and Cloudflare runs the bot check on the free check's pages and the job application form on that network too. A job application to Rezifi, resume included, is stored in our database in Mumbai. Our AI providers may process your data in the United States or elsewhere, depending on the provider.

Your subscription mandate and payments are processed by Cashfree in India.

If you are in the European Union, the United Kingdom, or India, this means your personal data is transferred outside your country. Where the GDPR applies, we rely on standard contractual clauses approved by the European Commission, incorporated into our agreements with the service providers that store or process this data, for those transfers.

How long we keep things

We would rather show you the real schedule, including the parts we are not proud of, than write that we keep data "only as long as necessary" and leave you to guess.

The first three rows are the honest answer to the question most people are actually asking: we do not delete your resume on a timer. It stays until you remove it or close your account. The one exception is a resume checked without an account, in the rows after them: that one is deleted within 24 hours unless you keep it.

A check also leaves the same error and AI cost records as any other use of Rezifi. They name the check by an identifier, not by what your resume says, and follow the schedule for those records above.

Your choices and your rights

What you can do yourself, right now

• Delete any individual resume. This removes the file, every saved version, and everything we derived from it.
• Delete any individual application.
• Turn off the email for any saved search, or every job alert email at once, on the account page or with the link in any alert email, and remove a saved search.
• Stop any more emails like the one about applying from a laptop, with the No more emails like this link in it, in one click and without signing in.
• Stop the email with your resume in a template, with the link in it or in the notice before it, in one click and without signing in.
• Clear your preferences, including every demographic field.
• Cancel your subscription from the billing page. Your access runs to the end of the week you have paid for.
• Download a copy of your data from the account page — every resume with its original file, your applications, saved answers, preferences, job feed searches, saved searches, billing records and the extension's reports of the applications it filled, as one zip file, straight away.
• Delete your whole account from the account page. It cancels any live subscription first, then removes your resumes, applications, saved answers, preferences and account record immediately.
• Sign out, which ends that session, or sign out of every other device from the account page.

If you used the free check without an account

Delete the check at once from its result page. That removes the file and everything we worked out from it, the same way the 24-hour deletion does.

There is no account behind a check, so there is no download: the result page is your copy while the check lasts. And because we never asked for your name or email address, we cannot find a check from a request by email. If you write to us about one, we will help as far as we can.

If you applied for a job at Rezifi

Write to us from the email address you applied with, and within 30 days we will send you a copy of your application or delete it, whichever you ask for. An application is not part of a Rezifi account, so it is not in an account's download and deleting an account does not reach it.

Email from us

We send the email your account needs: sign-in links and codes, and notices about your subscription (a payment that failed or went through on a retry, a mandate that started or ended, a one-time week that started, and access that paused). Every one comes from an @rezifi.com address, and a subscription notice carries a reply address that reaches support@rezifi.com. These notices have no unsubscribe link: while the account is open we cannot stop sending the notices it depends on; close the account and they stop.

When you save a job search, we also email you its new jobs: at most one email a day, or a week if you choose, and only when there is something new, from alerts@rezifi.com. Every one of these emails has a link that stops it in one click, without signing in, and you can turn them off for one search or all of them on your account page. Your searches stay saved when the email is off.

The day after you join Rezifi, if you joined from a phone, have added a resume, and have not yet used Rezifi on a computer or through the extension, we send you one email about applying from a laptop, where the Rezifi extension fills in application forms with your resume. It names the most recent job from our job feed that you tailored your resume for, if that job is still open, and links the extension on the Chrome Web Store. We send it once, from hello@rezifi.com, with a reply address that reaches support@rezifi.com. Its link, No more emails like this, stops any more emails like it in one click, without signing in, and we keep a note that you stopped them.

If our read of your resume puts you early in your career, your resume is still in your own layout from a Word file or a Google Doc, you have not tried our templates, and you added it at least two days ago, we may send you one email showing it in one of our templates. To make that page our AI providers read the text of your resume, as they did when you added it, and we send nothing unless every line of it found a place. Someone at Rezifi may look at the page before it goes. The page is inside the email, and nothing is added to your account unless you choose to keep a copy. We send it once, from hello@rezifi.com, with a reply address that reaches support@rezifi.com. Its link, No more emails like this, stops it in one click, without signing in, and we keep a note that you stopped it. We do not send it to anyone in the EU, the EEA, the UK or Switzerland, to anyone whose country we do not know, or to anyone who has stopped the laptop email or turned off every job alert.

If your account was made before this email existed, we tell you by email first, at least seven days ahead, with the same link. If you stop it then, the email never comes.

Apart from the emails described here, we send you no newsletters, and we never email you about anyone else's products.

Your copy, and deleting your account

Both are self-serve on the account page. A copy of your data downloads at once as one zip file: every resume with the original file you uploaded, the document as we hold it and the list of its saved versions, your applications, saved answers, preferences, the jobs you saved or hid, your free-trial usage, the record of how you used Rezifi, where your browser first came from to Rezifi when we kept it, whether we sent you the email about applying from a laptop or you stopped it, the same for the email with your resume in a template and its notice, your signed-in devices and sign-in methods, and your subscription and payment records. It does not include rendered PDFs and thumbnails (made from the resume on demand), the document bytes of each saved version, internal document markup, the payment provider's own payloads, or the operational records described below.

Deleting your account is immediate. The page asks you to type a confirmation, cancels any live subscription first so nothing is charged afterwards, and then removes your resumes, applications, saved answers, preferences, the record of how you used Rezifi, and your account record. There is no recovery window — download your copy first if you want one. The free trial's one-way fingerprints and the count of the trial you used stay, as "Keeping the free trial to one per person" explains. The fingerprints are not in your copy, because there is nothing readable in them to give you.

One thing we want to be straightforward about: a small amount of operational data that identifies you only by an internal account identifier — error records, AI cost records, and the technical record of each tailoring run — is not reached by that deletion today and ages out on the schedule in the previous section. We are closing that gap. Subscription and payment records are kept after deletion only where tax and accounting law requires it, for the period in the previous section.

If you cannot sign in to do either yourself, write from the email address on your account to support@rezifi.com.

and we will delete the account, or send the copy, within 30 days of confirming the request.

If you are in India

Under the Digital Personal Data Protection Act, 2023, you have the right to access a summary of the personal data we hold about you and how we process it, to have it corrected, completed, or updated, to have it erased, to nominate someone to exercise your rights if you die or become incapacitated, and to a grievance redressal process. Contact our Grievance Officer, named above, in the first instance. If you are not satisfied with our response, you may complain to the Data Protection Board of India.

If you are in the European Union or the United Kingdom

Under the GDPR you have the right to access your personal data, to have it corrected, to have it erased, to restrict or object to how we process it, to receive it in a portable format, and to withdraw consent at any time where our processing is based on consent — including for your demographic answers. Withdrawing consent does not affect processing we carried out before you withdrew it.

You also have the right to complain to your local supervisory authority. We would appreciate the chance to put it right first, but you do not have to come to us before going to them.

If you are in California

Under the CCPA as amended by the CPRA, you have the right to know what personal information we collect and how we use and disclose it, to request that we delete it, to request that we correct it, and not to be discriminated against for exercising any of those rights.

We do not sell your personal information, and we do not share it for cross-context behavioural advertising, so there is nothing to opt out of. We do collect sensitive personal information — your demographic answers, and the contents of your resume — and you have the right to limit its use. In our case the limit is already narrow: we use it only to fill in the forms you ask us to fill in, and never to infer characteristics about you.

Security

We describe here only what we actually do.

• All traffic between you and Rezifi is encrypted in transit with TLS.
• Your files and database records are encrypted at rest by our hosting and storage providers.
• If you set a password, it is stored hashed by our authentication library, never in readable form.
• Your resume files are served through short-lived signed links, so a link cannot be reused or shared to reach your documents later.
• Administrative access to our internal tools is limited to a small allowlist of named accounts.

No service can promise that a breach is impossible, and we are not going to. If one happens and it affects your personal data, we will tell you and the relevant regulators within the time limits the law sets.

Children

Rezifi, including the free check made without an account, is not directed at anyone under 18, and we do not knowingly collect their personal data. We word this as "not directed at" rather than "we prevent", because we do not currently verify age at sign-up or at the check, and we are not going to imply a control we do not have.

If you believe someone under that age has given us their personal data, write to us at support@rezifi.com.

Changes to this policy

When we change this policy we update the date at the top of the page. If a change materially affects how we handle your personal data — a new category of information, a new purpose, or a new kind of recipient — we will tell you by email or in the app before it takes effect, and where the law requires your consent, we will ask for it rather than assume it.

Contact and complaints

For any question about this policy, or to exercise any of the rights above, write to support@rezifi.com.

If you need a postal address — for example, to serve a legal notice — write to us by email and we will provide it. Rezifi AI LLP's registered office is on public record with the Registrar of Companies, Haryana, under LLPIN ACX-0634.

If you are not satisfied with how we have handled a request, you can escalate: in India, to our Grievance Officer and then the Data Protection Board of India; in the EU or UK, to your local supervisory authority; in California, to the California Privacy Protection Agency or the Attorney General.

This policy is governed by the laws of India, and any dispute arising from it is subject to the exclusive jurisdiction of the courts at Gurugram, Haryana.