Privacy policy
Effective 14 November 2026
This policy explains what happens to your information when you use ResumeWay: the Android app, the web app at resumeway.co/app (first served at resumeway.bobinjacob46.workers.dev/app, which still works), the ResumeWay browser extension, and this website (together, “ResumeWay”). “We” and “us” mean the people who make ResumeWay.
- Your profile, resume, answers, jobs and applications are kept on your device: in the Android app’s private storage, or in your browser’s storage for this site. We don’t have a copy, unless you choose to sign in.
- Signing in with Google, or linking your ResumeWay ID, is optional. If you do, your setup (profile, resume and photo, answers, field, companies and job portals) and your applications list are also kept for your account on our server, so they come back on your other devices and on a new one. Jobs are found again by a scan on each device. Delete it any time in Me → Account.
- Your details go to the companies and job sites you apply to, when you submit an application.
- When ResumeWay uses AI, job text and a short summary of your profile (and, for some tasks, your resume text) go to Groq, which runs the AI models, through ResumeWay’s AI server (or straight from your device, if you add your own Groq key under Me → AI → Advanced).
- If you buy a plan or resume re-edits, Razorpay takes the payment on its own page: we never see your card, UPI id or bank details.
- Once a day the app tells us it opened — its random id, which platform it runs on and its version — so we know how many people use ResumeWay. No name, email or anything from your resume goes with it.
- Where you are (the city ResumeWay shows, and the currency it prices in) comes from your phone’s mobile network and where your connection is. Your phone’s location is used only if you tap “Use my phone’s location”, and only the city is kept, on your device.
- There are no ads, no tracking cookies and no third-party analytics, and we never sell your information.
1. What stays on your device
ResumeWay does its work on your device. It keeps there:
- your profile (name, email, phone, city, links, work history, education, skills), your resume and photo, and resumes re-edited for particular jobs;
- your standard answers, answers ResumeWay remembered from earlier applications, and your own custom fields;
- the companies and job portals you follow, the jobs found, their match scores, and your settings;
- your applications, how each was confirmed, and screenshots of confirmation pages;
- API keys you enter (Groq, Adzuna, Jooble, a Google client ID) and, in the Android app only, passwords for job-site accounts you let ResumeWay create or save.
Android app: this is stored in the app’s private storage, which other apps can’t read. API keys and site passwords are encrypted with a key held by the Android Keystore and are left out of phone backups.
Web app: this is stored in your browser’s storage for this website (IndexedDB), on that computer or phone only. Anyone who can use your browser profile can open the web app and see it, so use it only on a device you trust. Clearing this site’s data in your browser deletes everything. The web app and the Android app don’t sync with each other unless you sign in with Google, or link your ResumeWay ID, on both (below).
Several accounts on one device: with “Add account”, each account on the phone or browser keeps its own setup, resume, applications and plan, apart from the others. Logging out keeps an account’s data on the device so you can switch back to it; “Remove from this phone” (or browser) deletes it from there.
If you sign in with Google
Signing in is optional; everything works without it. If you sign in, Google tells us your Google account’s id, your email address, your name and the address of your profile picture, and nothing else (we ask only for “openid email profile”). We keep these to know it’s you.
We then keep your setup for your account on our server (a database on Cloudflare): your profile, your resume and photo, your standard answers, remembered answers and custom fields, your field and locations, the companies and job portals you follow, and what each job site’s forms taught ResumeWay (their questions with the answers you gave there, and the way through an application on that site). It is used to bring your setup to the other devices where you sign in or link your ID, and to help you when you ask (see “What ResumeWay’s founder can see” below). We don’t show it to anyone, send it to employers, use it for AI or use it for advertising.
Your applications list is kept with your setup, so it comes back on a new phone or browser: for each application, the company, role, link, when you applied, its status, how it was confirmed, what the form was answered with, and whether its confirmation email came. The proof screenshot and a resume re-edited for one job are files that stay on the device where they were made.
Jobs and match scores (a scan finds them again), saved site passwords, API keys and Gmail settings stay on each device and are never sent to your account.
Each signed-in device holds a random session token (the web app keeps it in a secure, HttpOnly cookie for this site); we keep only a one-way hash of it, with which install it belongs to and when it was last used. Sign out in Me → Account at any time: that device keeps its setup and its session ends. Delete my account in the same place removes your account and everything kept for it from our server at once.
Your ResumeWay ID
When you add your resume, and when you open Me → Account, the app asks our server for the ResumeWay ID of the person on your resume, so that the same person has the same ID on every device and with every version of their resume. It sends your resume’s email address, phone number and first and last name. Our server keeps none of them: it keeps only keyed one-way hashes of them (HMAC-SHA-256 with a secret key), which let it recognise the same details again but can’t be turned back into them, the ID itself, and which installs of the app are linked to it.
To use your ID on a device, you ask for a code, and we email it to the address on your resume through our email provider (Brevo). We use the address only to send that email and don’t keep it; we keep a hash of the code for 15 minutes. Entering the code links the device: it is signed in to your ID the way signing in with Google does (above), so your setup follows you, and your linked devices share one allowance or plan. Nobody else is shown your ID, and a device can’t use it without the code. Deleting your account in Me → Account deletes the ID and its links too.
What ResumeWay’s founder can see, to help you
To answer your questions, put things right (such as a plan that didn’t arrive) and deal with misuse, ResumeWay’s founder can look up, on a page only they can open: your ResumeWay ID and when it was made; the devices linked to it with their platform (Android, iPhone or the web app), app version, country and the days the app was opened; your plan and what you used of it; and your payments. Only if you signed in with Google or linked your ResumeWay ID, so that your setup is kept on our server, can they also see that setup, your resume included. Everyone else’s profile and resume are only on their own device, and can’t be seen.
If you write to us, we can find your ID from the email address or phone number you give: it is turned into the same keyed hash, so the server still doesn’t keep it. Anything done to an account from that page (giving Pro, unlinking a device, deleting what’s kept for you) is logged with the time.
2. What leaves your device, and where it goes
| Where | What | When |
|---|---|---|
| Companies and job sites you apply to (for example through Greenhouse, Lever, Ashby, Workday, LinkedIn, Naukri, Indeed) | The details on the application form: your name, contact details, answers, resume and, where a form asks for one, your photo. | When you submit an application. ResumeWay fills the form; the form sends it. Their own privacy policies apply to what they receive. |
| Careers systems and job portals | Requests for public job listings (which companies’ jobs, and for some feeds your country). No personal details. | During scans. In the web app these requests pass through our relay (see section 8). |
| ResumeWay’s server (your account) | Your setup: profile, resume and photo, answers, field, companies and job portals (see “If you sign in with Google” above). | Only if you sign in with Google, whenever your setup changes. |
| ResumeWay’s server (your ResumeWay ID) | Your resume’s email, phone and name, turned into keyed hashes there and not kept; the email once more when you ask for a code, to send it. | When you add your resume or open Me → Account with one added, and when you ask for a code. |
| Brevo (email) | The code email: your address and the code. | Only when you ask for a code for your ResumeWay ID. |
| Google (sign-in) | Your sign-in happens on Google’s own page or in Google’s sign-in on your phone; Google tells us who you are. | Only when you sign in with Google. |
| Groq, Inc. (AI) | See section 3. | Only if you use AI. |
| Google (Gmail API) | See section 4. | Only if you connect Gmail job alerts. |
| Adzuna, Jooble | The job titles and location you search for, with your own API key. | Only if you add their keys. |
| Google (Android’s geocoder) | Your phone’s approximate location, to name the city it is in (see Where you are). | Only when you tap “Use my phone’s location” in the Android app. |
When ResumeWay reads a job portal (LinkedIn, Naukri, Indeed and others) it does so in a browser you can see: the Android app’s built-in browser, or a tab opened by the extension. Those sites see what they would see if you visited them yourself.
When you share a job to ResumeWay from another app (LinkedIn, Naukri, Gmail, a browser), what you shared stays on your device. ResumeWay opens the job’s link from your device, as a browser would, to read the posting, and then treats it like any job it found.
3. AI
ResumeWay’s AI reads your resume and screens jobs for every new install, and each plan has a monthly allowance of it. When the allowance is used up or the AI is busy, ResumeWay matches jobs on keywords and nothing is sent for AI.
With AI, ResumeWay sends Groq what each task needs:
- to score jobs and check job titles: the jobs’ titles and descriptions, and a short summary of you (your name, current title, years of experience, recent roles and companies, skills, a few highlights, your city, the locations you’re open to, your expected salary and the roles you want);
- to read your resume, suggest your field or re-edit your resume for a job: the text of your resume (and the job’s posting);
- to draft answers: the application’s questions, the job, and your profile and standard answers.
Your email address and phone number aren’t part of the scoring summary.
- With your own Groq key, requests go straight from your device to Groq under your agreement with Groq and Groq’s privacy policy. We don’t see them.
- With ResumeWay’s AI (the free allowance and paid plans), requests go first to our web server on Cloudflare, which looks up your install’s plan by its random ID, and then to our AI server, which passes them to Groq with our key and returns the answer. Neither server stores or logs what you send or what comes back. To keep allowances fair, the web server counts the jobs screened for each install, and the AI server stores the random ID made by your app or browser (not linked to your name), a one-way hash of your network address (for IPv6, of its /64 block) to limit how many new installs get the first-run allowance from one network, when you started and last used it, how many requests and AI tokens you used each day and month, and one-way hashes of the jobs you drafted answers for.
4. Gmail job alerts
If you choose to connect Gmail, ResumeWay asks Google for read-only access to your mail (gmail.readonly) using a Google Cloud project you set up yourself. It then searches for job-alert emails from LinkedIn, Naukri and Indeed from the last two weeks and reads the job listings in them, on your device. For each application you send, it also looks for the company’s confirmation email: it searches your mail after the time you applied and reads only each result’s sender, subject, first line and date, on your device, to tell you whether the confirmation came. The emails and your Google sign-in are never sent to us. ResumeWay’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can disconnect in the app, or remove access at myaccount.google.com/permissions.
5. Referral Buddy
Referral Buddy is off until you switch it on, and it has two halves.
- If you refer people at your own employer: you prove where you work with your own LinkedIn profile. The app opens LinkedIn on your phone, you sign in there as you normally would — we never see your password — and it reads four things the profile already shows anyone: the profile’s address, your name, your headline and the company you work at now. You see what it read before any of it is sent. We keep those four, the company’s name normalised so candidates can find it, and counts of how many candidates you picked up, referred, refused, let lapse and got hired. Candidates are shown your first name and last initial, your headline and your profile’s address, so they can see who would be referring them; the counts are only ever shown added together with everyone else’s at your company. When you leave, tap “I’ve left” and it is revoked at once; the app also revokes it by itself when your resume says you work somewhere else. We read nothing else on LinkedIn — no messages, no connections, no other profiles — and we never act there on your behalf.
- If you ask to be referred: nothing is shared until you tap “Ask for a referral” for that one company. We then send that company’s verified employees a card with your first name, your headline, your years of experience, your city, your skills, the roles you applied to there, and your photo if you left that switch on. Your surname, phone number and email address are never shared. Your resume stays locked until one employee takes your ask; only that person can open it, every opening is recorded, and nobody else at the company can. You can take the ask back at any time, which deletes the file straight away. If you use an employee’s referral ID in an application form instead, that employee is told which role you used it for, and sees the same card.
We never sell any of this, never pass it to the employer ourselves, and never give anyone your contact details: the referral itself happens inside your employer’s own system.
6. The browser extension
The ResumeWay extension lets the web app work in your browser. It:
- accepts requests only from the ResumeWay web app at resumeway.co (or its first address, resumeway.bobinjacob46.workers.dev);
- works only on job sites you allowed: the common job-site families with one click after install, and any other site after it asks you;
- opens applications and job-portal searches in new tabs when you ask in the web app, and acts only in the tabs it opened;
- runs ResumeWay’s form filler and page readers in those tabs, and passes what they read (the form’s questions, job listings, the text of a confirmation page) to the web app in the same browser;
- shows the web app in a side panel next to the page you’re on, when you press its button in the toolbar.
The side panel. While the panel is open, the extension reads the job posting in the tab you’re looking at, and reads it again when you switch tabs or the page changes. It does this only on sites you allowed (the panel asks first, in its own header, and only when you press Allow), and it reads only the posting: its title, company, place, description and the page’s address. It passes that to the web app in the panel, in your browser, so the web app can compare it with your resume; the web app keeps a tailored job on your device like any job you shared. On any other page, the web app learns only what kind of page it is (not a job page, waiting for your OK, a site you said no to, or a page it couldn’t read), never its address. The panel never clicks, types or fills anything in a tab it didn’t open. If you say no to a site, the extension remembers that until you close the browser (“Not now”) or until you take it back on its “Job sites ResumeWay may work on” page (“Not on this site”).
Applications you send. On job sites you allowed, the extension notices when you press a form’s Next or Submit (or its final Apply), and reads the questions and your answers on the page at that moment, so the application can be recorded in ResumeWay with what you sent, and the site’s questions answered the same way next time. It then checks the page the site shows next for its word that the application went (“Thank you for applying”, or the job listed as Submitted). Those answers stay in your browser: in the extension until the web app takes them, then in the web app on your device. Passwords and files are never read, and nothing is sent to us.
It doesn’t read your browsing history or any tab other than the one you’re looking at while the panel is open. The extension itself collects no analytics and sends nothing to us or to anyone else; the counts the web app sends from the panel, only if you say yes, are in section 8. It keeps only the list of tabs it opened, until you close the browser, and the sites you said no to. Its browser permissions are explained on the extension page.
7. Where you are
ResumeWay shows the city you’re in, prices plans in your currency (rupees in India, euros in Ireland and the euro area, dirhams in the UAE, pounds in the UK, US dollars elsewhere) and, before you set it up, prepares your job search for your country. It works out where you are like this:
- Without asking you anything: the Android app reads the country of the mobile network your phone is on and of its SIM, and your phone’s or browser’s language region. The app also asks our server where your connection is: Cloudflare, which runs the server, estimates the country and city from your network address. Our server sends that back and keeps nothing.
- Only if you ask: in the Android app, “Use my phone’s location” asks Android for permission to use your approximate location once, and uses Android’s own geocoder (a Google service on most phones) to name the city; on a phone without one, the app picks the nearest big city from a list it carries. The app keeps only the city and country, never the coordinates, and sends them nowhere. You can take the permission back in your phone’s settings at any time.
- Or you choose: type your city and pick your country instead. What you choose is kept until you change it.
Where you are is kept on your device only. It isn’t part of the setup kept for a signed-in account, and it isn’t sent with the daily “the app opened” message (which carries the country Cloudflare reports, as before).
8. This website and our servers
ResumeWay’s website, the web app and our small services run on Cloudflare.
- Visiting the website or web app: no analytics, ads or tracking. The website sets no cookies, and its fonts, images and scripts are served from this site; so are the web app’s, including the fonts it draws text with. Cloudflare processes your IP address and browser details to deliver pages and protect the service, and may keep short-lived operational logs.
- Cookies: only when you sign in with Google in the web app, two cookies that sign-in can’t work without: rw_oauth (for the few minutes you are on Google’s page, to check that the answer is for the sign-in you started) and rw_session (your session, HttpOnly and secure, until you sign out or 180 days after it was last used). Being strictly necessary for the service you asked for, they need no cookie banner; there are no other cookies.
- The checkout page: when you pay, the page loads Razorpay’s checkout from Razorpay, which runs the payment (see Payments below).
- The job-feed relay: browsers don’t let a web page read most job feeds directly, so the web app asks our relay to fetch them. The relay only fetches public job feeds of careers systems, forwards the answer, and stores nothing. It counts requests per IP address for one minute to prevent abuse.
- The posting reader: when you share or paste a job’s link into the web app, our server fetches that one page, as ResumeWay, and sends back only what describes the job: its title, company, place and description. It sends no cookies, signs in nowhere, and stores neither the link nor the page. If the site refuses, you can open the page in your own browser (with the ResumeWay extension) or paste its text. It counts requests per IP address for one minute to prevent abuse.
- The contact form: we keep your name, email address, topic and message, and a one-way hash of your IP address (to limit messages per hour), so we can reply.
- Downloads: downloading the Android app or the extension is like loading any page; nothing extra is collected.
- How ResumeWay is doing: once a day the app tells our server that it opened. It sends the random install id it already uses for the AI trial, which platform it runs on (Android, browser, browser extension, iPhone, desktop), the app’s version, and the country code Cloudflare reports for the request. It carries no name, email, address, resume text or job details. It is how we count how many people use ResumeWay, on what, and how many come back — and nothing else. It is also how we know how much AI and how many applications and resume re-edits are used in total. If you opened ResumeWay from an invite link, the ping also carries that link’s tag (such as “invite-w1”), so we know which invites brought people.
- What job sites ask: when an application goes on a job site, the web app sends our server what that site’s form asked (each question in the site’s own words, its type and the choices it offered) and the buttons pressed on the way through (such as “Apply”, “Next”, “Submit application”), with the site’s address (such as atlassian.com). It sends none of your answers, no name, resume, contact details or job title, and the server drops any question or choice that looks like an email address or phone number. A one-way hash of your install is kept with it so each person counts once. In return, the web app asks the server what it knows of a site you open, so it can find its way through that site’s application before you’ve applied there. Switch this off in Me → Sites ResumeWay learned.
- Closed openings: when you say a job opening is closed (or a posting you open in the side panel says it’s no longer open), the web app sends our server that job’s web address, so nobody is shown it once two people have said so. The server keeps only the address made short (its site, path and job number) and a one-way hash of your install, so the same person counts once. Nothing else: no name, resume or answers. To check which openings are closed, the web app sends the addresses of jobs in your list, and nothing about you.
- Side-panel counts (only if you say yes): after your first download in the extension’s side panel, the web app asks once whether to share counts of what you do there. If you say yes, it sends our server short records of what happened: the panel opened, a job was read, a tailor started or finished (and whether it worked, failed or fell back to the posting’s keywords), the changes or gaps were viewed, a PDF was downloaded, you marked a job as sent, or your file couldn’t be edited in place (and why). Each record carries the random install id, when it happened, the kind of site (LinkedIn, Naukri, Indeed, a careers site or other), whether AI was used, how many lines were kept as you wrote them and why, and random ids for that tailor run and that job, made on your device. It never carries the job’s address, its title or company, or anything from your resume. Records wait on your device until they are sent (at most 14 days); before you answer they are held there, and if you say no they are deleted and nothing is sent. You can change your answer at any time in the side panel. We use these counts only to learn whether tailored resumes get sent, and to fix what fails.
- Payments: ResumeWay uses Razorpay to take payments. The payment happens on Razorpay’s own checkout, and we never see or store your card number, UPI id or bank details. We keep the order itself: its Razorpay order and payment ids, what it bought, the amount, whether it succeeded, was closed or failed (with the reason Razorpay gives, such as a bank decline), and the install id it belongs to, so what you paid for reaches you and so our accounts add up. For a paid plan we also keep how much of each allowance period has been used. Razorpay processes your payment details as its own controller, under its privacy policy.
- Restore codes and devices: after a payment you get a restore code that puts the purchase on a second device. We keep only a one-way hash of the code, never the code itself, and the random install ids of the devices sharing the purchase (at most 2 at a time), with when each was added or removed. To stop guessing, we count restore tries per install and per network (a one-way hash of the network address), and delete those counts within a week.
9. What we never do
- We don’t sell or rent your information, or share it with recruiters, employers or data brokers. The only time anything about you reaches another person is Referral Buddy, and only for the one company you asked, when you asked (see 5).
- We don’t show ads or use your information for advertising.
- We don’t use your resume, profile or applications to train AI models.
- We don’t read your data on your device; we don’t have access to it.
- We don’t use third-party analytics, advertising or tracking tools, and neither the daily install ping nor the side-panel counts are ever joined to your name, your resume or the jobs you apply to.
- We never see your card, UPI id or bank details, and we don’t store them.
10. How long we keep things
- On your device: until you delete it, uninstall the app, or clear this site’s data in your browser.
- Your ResumeWay ID (the hashes of your resume’s details and the devices linked to it): until you delete your account in Me → Account. A code for it: 15 minutes.
- The log of what was done to an account from the founder’s page: 2 years.
- Your account and the setup kept for it: until you delete your account (Me → Account), which removes it at once. A sign-in session ends 180 days after it was last used, and its record is deleted 30 days after that.
- AI trial usage records: deleted automatically 12 months after their last request.
- Contact messages: deleted automatically 24 months after they’re sent.
- Relay and posting-reader requests: not stored. Per-minute request counts expire after a minute.
- Install records (the daily “the app opened” ping): the day-by-day records are deleted after 120 days, and an install is forgotten entirely 12 months after it was last used.
- Closed-opening reports: deleted automatically after 120 days.
- What job sites ask (their questions, choices and buttons): kept while it helps people apply there. It holds nothing about you but a one-way hash of your install.
- Side-panel counts: deleted automatically 12 months after they happened. Counts not yet sent wait on your device for at most 14 days.
- Payment records, restore-code hashes and the devices sharing a purchase: kept while your plan or credits last, and then as long as tax and accounting law requires us to keep payment records (in India, currently up to 8 years).
- Restore-try counts: deleted within a week.
- Referral Buddy: a referral identity lasts 90 days unless your profile is read again, and is revoked at once when you leave the company. A referral put to an employee is answered, refused or lapses within 72 hours, and what they said is kept with it so you can see it. A referral ask closes after 30 days if nobody takes it, and the resume shared with it is deleted 45 days after the ask closes, or straight away when you take the ask back.
11. Your choices and rights
Because your data is on your device, you control it directly: edit it in Me, remove your resume or photo, delete API keys and saved sign-ins, uninstall the app, or clear the site’s data in your browser. You can use ResumeWay without AI, without Gmail, without the extension and without signing in. If you signed in, Me → Account signs you out or deletes your account and everything kept for it.
You can ask us about, correct or delete what we hold. Contact messages we can find by your email address. AI trial records hold no name or contact details, so we usually can’t tell which are yours; they’re deleted automatically as above. You can withdraw your consent at any time by stopping the feature concerned; this doesn’t affect what was done before. We use your information on the basis of your consent (for what you ask ResumeWay to do), to provide the service you asked for (your account and what you buy), and our legitimate interest in keeping the service secure and fair.
Where you live. In India you have the rights the Digital Personal Data Protection Act, 2023 gives you, including to name someone to act for you. In the European Union (including Ireland) and the UK, the GDPR gives you the right to access, correct and delete your information, to get it in a portable form, to object to or restrict how it is used, and to complain to a data protection authority: in Ireland, the Data Protection Commission. In the United Arab Emirates, the Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) gives you similar rights. ResumeWay is run from India; what our servers keep is processed by Cloudflare, and AI requests by Groq in the United States, so your information may be processed outside the country where you live.
Write to us through the contact page (choose “Privacy”). We answer within 30 days.
Deleting your account and data
In the app: Me → Account → “Delete my account and what it keeps”. That removes at once your account, the setup and applications list kept for it, your ResumeWay ID (its hashes) and the devices linked to it. What is on the device itself goes when you uninstall the Android app, or clear this site’s data in your browser.
Without the app: write to us through the contact page, choose “Privacy or my data” and ask us to delete your account. Write from the email address on your resume, or give your ResumeWay ID, so we can find it. We delete it within 30 days and write back when it’s done.
What is kept: payment records, with the restore-code hashes and the devices sharing a purchase, for as long as tax and accounting law requires (in India, currently up to 8 years); and the log of what was done to an account from the founder’s page, for 2 years. AI trial usage records hold no name or contact details and are deleted automatically 12 months after their last request.
12. Security
Everything between your device, our servers and the sites ResumeWay uses is encrypted in transit (HTTPS). Keys and site passwords in the Android app are encrypted with the Android Keystore. Our servers keep as little as possible, which is the best protection we know. No system is perfectly secure; if we learn of a breach affecting you, we’ll tell you and the authorities as the law requires.
13. Children
ResumeWay is for people 18 and older looking for work, and the app asks you to confirm you are when you start. We don’t knowingly collect information from anyone younger. If you believe a child has given us information, tell us through the contact page and we’ll delete it.
14. Changes and contact
We’ll update this policy when ResumeWay changes, and change the date at the top. For significant changes we’ll give notice on this website and in the app before they take effect.
Questions, requests or complaints (including to our grievance officer): use the contact page.