PRIVACY
Last updated: 22 July 2026
Short version: the resume checker never sends your file anywhere and never asks who you are. There are no analytics and no tracking cookies. If you choose to sign in — optional, and only needed to save roles — we store your email, name and avatar from that provider, and nothing else.
Who is responsible
This site is operated by Rahul Rajelli, sole proprietor, India. For any privacy question or request, contact hello@robosimtools.com.
ATS X-Ray — your resume is never uploaded
When you drop a PDF into the checker, it is parsed by JavaScript running in your own browser. The file is never transmitted, never stored, and never seen by us or by any third party. Nothing persists after you close the tab.
This is not a promise you have to take on trust. The page's Content Security
Policy sets connect-src 'self', which means the browser itself
will refuse any connection to a third-party server. Open your browser's
network panel and run a scan: you will see no request carrying your file.
The same applies to any job description you paste. It is used in your browser and discarded.
Resume Matcher — opt-in, and this one does send your resume
Separately from the in-browser checker, signed-in users can run the resume matcher, which compares your resume against live roles. Unlike the X-Ray checker above, this feature does send your resume text to a server — matching against thousands of roles cannot be done purely in your browser. It runs only when you choose to use it, and only if you are signed in.
When you run it, your resume text is processed by Cloudflare Workers AI and Vectorize (our infrastructure provider) to produce the match. Your resume is used for that request and is not stored in our database.
If the shared daily matching budget is used up, the site offers a
“bring your own key” option. If — and only if — you choose
it and paste a Google Gemini API key, your resume text is sent to
Google’s Gemini API
(generativelanguage.googleapis.com) under your own key and
quota, and that processing is governed by Google’s terms. Your key is
used for that one request and is never stored, logged, or sent back to you.
If you never paste a key, your resume is never sent to Google.
Live Roles — public job data only
The job listings come from the public job-board APIs that Greenhouse, Lever and Ashby publish so employers' careers pages can display their own openings. We store the job title, company, location, link and description text. This is published business information. It contains no data about you.
Accounts — only if you choose one
You can use the resume checker and browse roles without ever signing in. An account exists for three things today: saving roles, telling us whether a match was any good, and — entirely optionally — telling us what happened after you applied.
On a match result, you can mark it GOOD or NOT RELEVANT. If you do, we store that opinion against your account and the role — nothing else about the match, and never your resume text. Being honest about where this stands today: nothing currently reads this back to change what you see. It is being collected so that when ranking is improved, there is real data to improve it with, rather than starting from nothing. This page will be updated the day that changes.
On a role you have saved, you can optionally mark it Applied, Interview or Offer. This is entirely self-reported — we never infer it, never check your email, never scrape anything to guess at it — and it is visible only to you. It exists because it is the one number that would actually show whether this site helps anyone get hired, which page views and match counts do not.
Sign-in is via GitHub or Google. No password is ever stored — there is no password field on this site, by design. From your chosen provider we receive and store your email address, display name and avatar URL, plus an identifier for that provider. We also store the roles you save.
Your session is a cookie. It is HttpOnly (no script can read
it), Secure and SameSite=Lax, and it expires after
30 days. The database stores only a cryptographic hash of your session
token, never the token itself, so a copy of the database is not a set of
usable logins. The cookie is strictly functional — it is not used for
analytics or advertising, which is why there is no cookie banner.
Deleting your account erases it. The record is removed, not flagged as inactive, and your saved roles and sessions are deleted with it. Nothing is retained afterwards.
What the server does receive
- Your IP address. Unavoidable — it is how a response reaches you. We use it for one purpose beyond delivery: rate limiting, so a single source cannot overwhelm the site. It is not stored in our database and is not used to build a profile.
- Standard request logs held briefly by our infrastructure provider, Cloudflare, whose privacy terms govern that processing.
We use no analytics, no advertising or tracking pixels, and no third-party embeds. The only cookie is the functional session cookie described above, and only if you sign in. There is no tracking to consent to, which is why you are not being asked.
Your rights
Under India's Digital Personal Data Protection Act, 2023 — and equivalent laws elsewhere — you have rights of access, correction, erasure and grievance redress over personal data held about you. If you have never signed in, we hold nothing about you beyond transient request logs. If you have an account, you can delete it yourself at any time, or write to the address above and we will do it and confirm what existed.
Changes
If this site adds any further feature that sends your data to a server, it will be strictly opt-in, will say so at the point of use, and this page will be updated to describe it. The in-browser X-Ray checker will remain in-browser.