Legal

Privacy Policy

What this website collects, what happens to it afterwards, and how to get it removed. Written to be read rather than to be survived.

Last updated: September 2026

The short version

This website has two forms and no user accounts. If you fill in a form, we get the details you typed and we use them to answer you. We do not sell anything to anyone, we do not add you to a mailing list, and there is no third-party captcha or chat widget quietly watching the page. Personal data belonging to developers and candidates is handled separately and is not mixed with website enquiries.

Who is responsible

JS Devs operates jsdevs.in and decides how the information described here is used. Written questions reach us at info@jsdevs.in, and the business operates Monday to Friday, 10:00–19:00 IST.

What the forms collect, field by field

There are exactly two places on this site where you can send us something, and both are on the contact page. Nothing else on the site accepts input.

1. The developer request form

This is the primary form. It collects your name, your email address, your company, the role you are hiring for, the seniority you want, the engagement type, how many people you need, the time-zone overlap you require, when you want them to start, and any free-text notes you add about the stack or the work. Name and a valid email address are required because without them we cannot reply; every other field can be left empty and the form will still submit.

2. The general enquiry form

This is for fixed-scope work and anything that is not a hire. It collects your name, your email address, your phone or WhatsApp number, your company, the enquiry type you select, your stack, your time zone, and your message. Name, a valid email address and a message are required; phone, company, enquiry type, stack and time zone are optional.

What is attached automatically

Your web server and ours record the ordinary technical information that any website receives: the IP address a request came from, the browser user agent, the time of the request, and the page you submitted from. The developer request form also records which page you submitted from, because the same form appears on more than one page and it is useful to know which one prompted you.

What happens the moment you press send

The submission is checked server-side, then two things happen to it. It is sent as an email to the inbox that handles enquiries, and it is written to the server’s error log as a delivery safety net. That second step is deliberate: email delivery occasionally fails silently, and a lead that exists only in a failed SMTP attempt is a lead that was lost without anyone knowing. The log entry means your enquiry is recoverable even if the email never arrives. Server logs are rotated and eventually overwritten in the ordinary course of server maintenance.

The spam checks, and why no third party is involved

Both forms carry two defences, and neither sends anything about you to another company.

  • An arithmetic question — a simple sum shown next to the submit button. The two numbers and an expiry time are carried in a signed token that travels with the form, so the server can check your answer without storing a session, a cookie or a database row. The token expires after a short window, which is why a form left open for a long time will ask you to answer a fresh sum.
  • A hidden field that a person never sees and never fills in. Automated submissions tend to fill in every field they find, so anything arriving with that field completed is discarded.

There is no reCAPTCHA, no hCaptcha, no bot-detection service and no fingerprinting. Proving you are a person here involves no company other than us.

Why we are allowed to process it

Because you asked us to. You typed the details into a form in order to get a reply, and we use them for that. Keeping a record of business enquiries and dealing with them is a legitimate interest of running the business, and once a contract exists, processing the contact details of the people involved is necessary to perform it. We do not rely on consent for marketing, because we do not do marketing to people who have contacted us.

Who else handles it

  • Our hosting provider, which runs the server the site sits on and therefore holds the logs and the files.
  • A transactional email relay, which carries the notification email from the website to our inbox. Outbound mail is routed through a third-party SMTP relay configured on the server; the relay sees the contents of the notification email in the course of delivering it. We do not publish the destination inbox address here, for the same reason we do not publish it anywhere else on the site.

Nobody else. Your enquiry is not sold, rented, syndicated to a lead marketplace, or shared with another agency.

Candidate and developer data is handled separately

This policy covers the website. It is not the whole picture for a staffing business, so the boundary is worth stating explicitly.

Personal data belonging to developers and candidates — CVs, work history, assessment notes, availability, contact details and payment information — is collected and held separately from website enquiries, under the agreements we have with those individuals. It does not flow into this website, and website enquiries do not flow into it.

When we share a CV or a profile with a client, it is shared on a confidential basis and for one purpose: evaluating that person for that role. Clients are expected to treat it accordingly — to restrict it to the people involved in the hiring decision, not to circulate it internally as a general document, and not to retain it once the decision is made and the candidate has not been engaged. If you are a developer and want to know what we hold about you, or want it removed, write to us and we will deal with it directly rather than through this page.

Cookies

The site does not set cookies for advertising, retargeting or profiling. WordPress itself sets cookies only for people who log in to administer the site, which is not you. Neither of the forms sets a cookie — the arithmetic captcha deliberately uses a signed token instead, precisely so that no state has to be stored in your browser.

Analytics

No analytics or tracking script is currently loaded on this site. There is no Google Analytics tag, no advertising pixel and no heatmap or session-recording tool. The site is built so that analytics loads only if a measurement ID is explicitly configured on the server; none is configured, so nothing is sent. If that changes, this section will change with it and this policy’s date will be updated.

How long we keep it

Enquiry emails are kept while the conversation is live and for as long afterwards as a business record needs to exist — a request from someone who later becomes a client is part of the history of that relationship. Enquiries that go nowhere are deleted once they are clearly dead. Server logs rotate on the hosting provider’s ordinary schedule. If you want your enquiry deleted sooner than any of that, ask, and we will delete it.

Security

The site is served over HTTPS, form submissions are validated server-side rather than trusting anything the browser sends, and every form carries a token that prevents it being submitted from another site on your behalf. Access to the server and to the enquiry inbox is limited to the people who need it. No arrangement is perfect, and we would rather say that plainly than claim otherwise: do not put passwords, production credentials, API keys or anything similar into a contact form. If you need to send us something sensitive, ask and we will agree a sensible way to do it.

Your rights

Depending on where you live, local data protection law will give you rights over information about you. Commonly these include the right to ask what we hold, to get a copy of it, to have mistakes corrected, to have it deleted, to object to a particular use of it, and to complain to a regulator in your own country. We do not make you prove a jurisdiction before we will act: write to us and we will deal with the request. There is no charge, and we aim to respond well inside any statutory deadline that applies.

International transfers

We operate from India and our clients are international, so information you send us will cross borders in the ordinary course of reaching us — that is inherent in emailing a company on another continent. We keep the number of parties involved small, which is the most meaningful protection available here, and we do not move enquiry data into additional systems or territories beyond the hosting and email delivery described above.

Children

This is a business-to-business website offering developer staffing. It is not directed at children and we have no reason to collect information about them. If a child has sent something through a form, tell us and we will delete it.

Links to other sites

Where this site links somewhere else — a WhatsApp conversation, a documentation page, another company’s site — that destination has its own privacy practices and this policy stops at our boundary.

Changes to this policy

If what we collect or how we handle it changes, this page changes and the date at the top moves. There is no archive of previous versions; the current page is always the operative one.

A note on what this is

This page is a plain-language description of what the website actually does, written by the people who built it. It is not legal advice, it is not a substitute for advice from a lawyer in your own jurisdiction, and it does not attempt to recite the text of any particular statute. If you need a data processing agreement or specific contractual language for your own compliance programme, ask and we will look at your document.

Contact

Questions, corrections or deletion requests: info@jsdevs.in, or call +91 63530 74980 Monday to Friday, 10:00–19:00 IST.