Privacy Policy

Two forms, kept apart deliberately

The matching form and the training form ask different questions because they are different requests, and we keep the answer to each separate rather than merging them into one contact record. Neither creates a login, a cookie profile, or a marketing subscription. There is no third-party chat widget, no ad pixel, and no bot-detection vendor watching the page — the two defences below run entirely on our own server.

Your browser and our server also record what any web request carries: the IP address, the browser identifier, and the time. Nothing beyond the table above is asked for on either form.

What we do with a submission

Two things happen the moment you press send. The details go out as an email to the address that handles enquiries, and they are written to the server's error log as a fallback. The second step exists because outbound email occasionally fails without warning, and an enquiry that only ever lived inside a failed send is one nobody would know to chase. The log entry means it survives even if the email does not arrive. Logs are rotated and eventually overwritten as part of ordinary server maintenance — we do not keep them indefinitely on purpose.

How we know you are not a bot

Two checks, both server-side, neither sending anything to another company:

• A quick sum. The two numbers and an expiry are carried in a signed token attached to the form, so we can check your answer without a session or a database row. Leave the form open too long and the token expires, which is why it will ask for a new sum.
• A field you never see. It sits off-screen. A real person never fills it in; automated form-fillers usually do, and anything that arrives with it completed is quietly dropped.

No reCAPTCHA, no hCaptcha, no fingerprinting. Both checks are ours.

The legal basis, briefly

You filled in a form because you wanted a reply, and replying is what we do with what you send. Keeping a record of enquiries so we can act on them is a legitimate business interest; once an engagement exists, handling the contact details involved is necessary to run it. We do not rely on consent for marketing, because contacting us is not consent to be marketed to.

Who else sees it

Our hosting provider, which runs the server and therefore holds the logs and files. And a transactional email relay, a third-party SMTP service configured on the server that carries the notification email from the form to our inbox — it sees the message in the course of delivering it, in the same way any postal service sees an envelope's contents are inside it. We do not publish the destination inbox, for the same reason we keep it off the rest of the site. Nobody else gets it. It is not sold, rented, or handed to a lead marketplace.

Developer data lives somewhere else entirely

This policy is about the website. A marketplace has a second, larger category of personal data it holds — developer profiles, live coding evaluation results, reviews of AI-assisted work samples, reference-check notes, availability and payment details — and none of it touches this website or these two forms. It is collected and held under the separate agreements we have with the developers themselves.

Code samples or prompts a developer shares while being evaluated stay confidential to that evaluation. When a profile is shared with a client for matching, it is shared for one purpose only — deciding whether to engage that person — and on that confidential basis. A developer who wants to know what we hold, or wants it removed, should write to us directly rather than go through this page.

Cookies and analytics

No cookies for advertising, retargeting or profiling. WordPress sets a cookie only for someone logging in to administer the site, which is not a visitor filling in a form — and the captcha above deliberately uses a signed token rather than a cookie, so nothing needs to be stored in your browser at all.

Nothing is currently loaded: no Analytics tag, no ad pixel, no session recording. The theme only wires up a tracker if a measurement ID is explicitly configured on the server, and none is. If that changes, this paragraph changes with it and the date at the top moves.

Retention and deletion

An enquiry that becomes an engagement is kept as part of that relationship's record. One that goes nowhere is deleted once it is clearly finished with. Server logs rotate on the hosting provider's own schedule regardless. Want yours gone sooner than that? Ask, and it is deleted.

Kept reasonably secure

HTTPS throughout, server-side validation rather than trusting what a browser claims, and a token on every form that stops it being submitted on your behalf from somewhere else. Access to the server and the inbox is limited to the people who need it. Nothing is unbreakable, so we will say plainly what we would rather you not send us this way: passwords, production credentials, API keys, or code you consider proprietary. If something sensitive needs to reach us, ask first and we will find a better channel.

Your rights, and where we operate from

Depending on where you live, local law gives you rights over your own data — typically to see what is held, correct it, delete it, object to a use of it, or complain to a regulator. We do not ask you to prove which law applies before acting; write to us and we deal with it, inside any deadline the relevant law sets. We are based in India and work with clients internationally, so a message you send us crosses a border to reach us, the way any international email does. We keep the number of parties who touch it small, which is the real protection here, rather than moving your data through additional systems beyond hosting and email delivery.

A few short ones

Children. This is a business site for developer matching and training. It is not aimed at children and we do not knowingly collect anything about them; tell us if a child has submitted something and it will be removed.

Other sites. A link off this site — to WhatsApp, to documentation, to somewhere else entirely — leads to a destination with its own privacy practices. This policy covers our own pages only.

Changes. This page changes when what we do changes, and the date at the top moves with it. There is no version history; the live page is the current one.

Not legal advice. This is a plain description of what the site does, written by the people who built it, not a substitute for advice from a lawyer in your jurisdiction. If you need a formal data processing agreement, ask and we will review your paperwork.

Contact

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