Privacy policy

• Your profile is shown to recruiters we have approved by hand. Nobody else.
• Your phone number and email address are not in search results at all. A recruiter has to reveal them one candidate at a time, and every reveal is recorded.
• We do not sell your data, nobody buys it, and we do not run advertising trackers.
• You can delete your profile yourself, at any time, and your resume goes with it.

The rest of this page is the same thing in detail. It is worth reading the deletion and contact-reveal sections at least.

To go live you give us your name, phone number, email address and city, your function and sub-function, your total years of experience, your availability band, your expected CTC band and at least three skills. Your name and email arrive prefilled from Google when you sign in.

Everything else is optional and you can add it later or not at all:

• Work history, headline, industries, portfolio link and current CTC band.
• Whether you would relocate, and where.
• Answers to a few questions specific to your function.
• Your resume, as a PDF.
• Gender.

We also record each daily check-in, changes you make to your availability band, and the Google account identifier that signs you in.

Gender is optional and the control starts on “Prefer not to say”. It has no effect on your ranking or on where you appear in results. Some employers run diversity-focused searches, so it works as a filter — and every search that filters on it is recorded against the recruiter who ran it, so the filter is observable rather than silent.

Two purposes. The first is showing your profile to approved recruiters so they can hire you. The second is reading your resume, if you upload one, so that your profile form can be filled in for you rather than by hand — “How we read your resume” below sets out exactly what that involves.

We do not sell your data, and nobody is given it for their own use. The one outside service that touches it is the AI that reads your resume, which processes it on our behalf and under our instruction. We do not use it to train anything. There is no bulk export of profiles — not for recruiters, and not through any admin screen.

You give consent when you first go live, through a tick box that is separate from accepting the terms. We store the moment you gave it and the version of this policy it was given against. This is version 2026-07-25.

Keeping the version means we can always say which text you agreed to, rather than assuming it was this one. If the policy changes, consents already given stay attached to the version they were given under.

You withdraw consent by deleting your profile, which you can do yourself at any time.

Approved recruiters, and nobody else. A recruiter registers with a corporate email address, has their LinkedIn checked against the company they claim, and is approved by a person before they can run a single search.

Search results carry your name, headline, skills, experience, availability and check-in freshness. They do not carry your phone number or your email address — those fields are absent from the response, not hidden inside it. There is nothing on the page for a browser tool to reveal.

Seeing your phone number and email address is a separate, deliberate action a recruiter takes on one candidate at a time. There is no way to reveal a page of results at once, and no bulk export exists.

• Every reveal is recorded with the recruiter, you, the time, and the search that produced you.
• A recruiter can reveal at most 100 candidates in any rolling 24 hours. Past that the request is refused.
• Revealing the same person a second time spends a second one of those. We do not quietly forgive a repeat.

The record is the point. It means any misuse of a contact detail can be traced back to the account that took it, and we watch reveal patterns for the signature of automated scraping.

A resume is the most sensitive single file on this platform and it is handled accordingly.

• It is stored in a private container. No public link to it exists and none can be created.
• Its stored filename is a random identifier, never your name — a name-derived filename leaks who you are into access logs before anyone opens anything.
• When an approved recruiter opens it, we issue a link that expires after five minutes, is read-only, and reaches that one file and nothing else. Each issue is recorded as a view.
• There is no download button. A recruiter reads it in their browser.
• On upload we confirm the file really is a PDF by reading its contents rather than trusting its name, and we strip its metadata and any embedded scripts before storing it.

That last step matters more than it sounds: resumes routinely carry the previous employer’s system metadata, and a PDF can carry active content. Neither survives the upload.

You see that something happened and roughly who it was, deliberately without enough to act on it directly.

• Your activity feed shows a recruiter’s company sector — “a SaaS company”. It never shows the company name, the recruiter’s name, or anything they wrote about you.
• When a recruiter shortlists you, you are told straight away. That notification carries the sector and nothing else. The recruiter’s private note and the label they filed you under never form part of it.
• If a recruiter removes you from a shortlist, you are not told. Nothing is sent.
• Repeated views by the same recruiter on the same day are counted once, so the feed reflects interest rather than refreshes.

One tap a day records that you are still available, and that freshness is what recruiters filter on. Three days without one pauses your profile and it drops out of search.

Paused is not deleted and not deactivated. Your profile and everything in it stays exactly as you left it, and a single check-in puts you back in search.

A recruiter can report a profile. You are told that a report was received and which category it fell into, never who made it, and you get a reply box that reaches the same queue.

A report claiming misrepresentation is always read by a person before anything happens to your profile. Nothing suppresses a profile automatically.

Your profile, your resume file and our database are hosted in India, on Microsoft Azure.

Everything you enter — your name, phone number, work history, skills and the resume you upload — is stored on Indian servers and stays there.

Uploading a resume is optional. If you upload one, we use it to save you filling in the form by hand.

Here is what happens. We check the file is a real PDF, strip out anything hidden inside it, and store it. We then extract the text and send that text — and nothing else — to an AI service on Microsoft Azure, running in our own account. The service reads the text and returns a structured version of it: your name, your phone number, the skills it recognised, and your work history.

We use it for that and nothing else. It is not used to advertise to you, is not sold, and is not shared with recruiters or any other third party. Microsoft does not use it to train AI models.

Nothing is published without you seeing it first. Everything the AI fills in appears on your profile form for you to read, correct or delete. Your profile does not go live and no recruiter can see it until you have gone through the form and given your consent at the end. If the AI gets something wrong, you change it before anyone else ever reads it.

Some things we never fill in from your resume. We do not take your email address from it — that comes from your Google sign-in. We do not guess your availability, your notice period or your salary, and we do not write your headline for you. Those are yours to say.

If you would rather none of this happened, do not upload a resume. You can fill in your profile by hand and it will work exactly the same way.

We set one cookie, to keep you signed in. It cannot be read by scripts on the page and it does nothing else.

For traffic figures we use Plausible, which is cookieless and does not build a profile of anyone. There are no advertising pixels, no third-party trackers, and no other third-party scripts anywhere on this site.

• Your profile stays for as long as your account does.
• Reveals, resume views, administrative actions, sign-in failures and rate-limit trips are kept in our operational logs for 90 days.
• Phone numbers, email addresses, resume identifiers and session tokens are stripped from log lines before they are written, including inside error traces.

After you delete your profile, one anonymous row remains so that our counts stay correct. It names nobody — see the next section for exactly what it holds.

Deletion is self-serve and takes two steps: you ask for it from your profile, then confirm from a link we email you. The second step exists so that a single mistaken tap cannot erase your account.

On confirmation we remove your name, phone number, email address, city, headline, portfolio link, skills, work history, industries, relocation preferences and every optional answer you gave. Your sign-in identifier and email address are replaced with values that cannot be used to reach you or to find you again, which also frees you to sign up from scratch later.

Your resume file is removed from storage within 24 hours.

Two things survive, neither of which names you. The first is the record that consent was given and when — that is what lets us demonstrate consent history, as the DPDP Act asks. The second is an anonymised row holding a function, a band and check-in dates, so that historical counts do not silently change. Neither can be traced back to you.

Under the Digital Personal Data Protection Act 2023 you can:

• Ask what personal data we hold about you and how it has been used.
• Correct anything inaccurate — every field on your profile is editable by you at any time, without asking us.
• Have your data erased, which is the deletion above and needs nobody’s permission but yours.
• Withdraw consent, with the same effect.
• Nominate someone to exercise these rights if you are unable to.
• Raise a grievance, and escalate it if we do not resolve it.

For anything on this list that you cannot do from your profile, write to privacy@joinin7.in.

When this policy changes we publish it with a new effective date and a new version. Consents already given remain attached to the version they were given against, so which text you agreed to is always answerable rather than assumed.