Privacy policy

What this site knows about you

Last updated 27 September 2026

Very little, and nothing you did not type. No analytics, no advertising, nothing loaded from another company. One cookie, and its only job is to keep the anti-spam picture working. If you send the form to my inbox, what you typed is stored on this server until I have dealt with it.

01Who this is

Sushil Yadav, working from Navi Mumbai, Maharashtra, India. This is a personal portfolio site. For anything on this page, including a request about your own data, reach me on +91 90296 32143 or at the email button on the contact form. I am the person who answers; there is no team and no ticket queue.

02What the site collects on its own

Almost nothing, and you can check every one of these by opening the developer tools in your browser:

  • One cookie, named PHPSESSID. The contact form shows a picture of five letters to keep robots out, and the server has to remember which five it drew for you. That is the whole of its job. It holds no name, no address and no record of what you looked at, it goes to nobody else, and your browser drops it when you close it. It is set as the page loads, because the picture loads with the page so that the form still works with JavaScript switched off.
  • One more cookie, and only if the web host asks for it. Shared hosting keeps its own robot filter in front of forms. If that filter answers your message with a challenge instead of passing it on, the page sets the small cookie it asks for, named something like humans_ and a number, and sends your message a second time so that it is not lost without telling you. That cookie belongs to the host, not to me: it carries one number, no name, and no record of what you looked at. If the filter does not challenge, it is never set.
  • No analytics, no tag manager, no advertising pixel, no heatmap, no session recorder.
  • No social media embed and no comment system.
  • Every file the page loads comes from this same address. The fonts, the animation library and the 3D library are copies stored here, not calls to Google Fonts or a CDN. An automated test in the project refuses to pass if that ever changes.

03The one thing your browser does store

When you send a message through the form, the page writes a single item into your browser's session storage: sy-sent, holding the time you last sent. It exists for one reason, to hold the form to one message a minute so a bot cannot hammer it. It is a timestamp and nothing else. It never leaves your device, it is not a cookie, and your browser discards it when you close the tab.

04The contact form, exactly

The form asks for your name, mobile number, email address, what you need, and a short description. There is also a hidden field you never see, which exists to catch automated submissions, and the picture of five letters described above.

There are two buttons and they do different things.

  • Send message posts what you typed to this website. It is written to a file on the server, which I read on a page only I can open, and a copy is emailed to me so that I see it sooner. Nothing else happens to it: no other system is told.
  • Send on WhatsApp opens WhatsApp on your own device with the message already written. Nothing reaches this server, nothing is stored and no email goes anywhere. Until you press send inside WhatsApp, nothing has left your device.

The form accepts plain text only. Links, web addresses and anything that looks like code are refused, and there is no way to attach a file. Everything the page checks is checked again on the server, because the page's copy of those rules is only a courtesy to you.

05What is kept, where, and for how long

If you used Send message, one line is added to a file on this server holding what you typed, the time, and a one-way scramble of the address your request came from. The scramble is there so the form can refuse a hundred messages from one place in an hour; the address itself is never written down and cannot be worked back out of it. The file cannot be fetched from the web, and the page that reads it needs a password.

The email copy is sent by this site's host to my own mailbox. It carries the same details you typed, travels through the host's mail server and my email provider, and sits in my mailbox like any other email. If it goes astray the enquiry is still in the file, which is why the file is written first.

I use it to reply to you, to understand the work and to quote for it. I do not add you to a mailing list, I do not sell or share your details, and I do not use them for advertising. I keep an enquiry while the conversation is live, and for my own records afterwards. Ask me and I will delete yours.

If you used WhatsApp or email instead, your message travels through WhatsApp, which is operated by Meta, or through your own email provider and mine. Those companies carry the message and their own privacy policies apply to that leg of the journey. I do not control them and cannot speak for them.

06Server logs

This site is served by a web hosting provider, and like nearly every web server theirs records standard access logs: the IP address a request came from, the date and time, which file was asked for, and the browser string. That happens at the hosting layer, before any of my code runs. It is used to keep the site working and to investigate abuse. It is not joined to anything you type into the form.

07Your rights under the DPDP Act

India's Digital Personal Data Protection Act, 2023 gives you rights over personal data held about you. For anything you have sent me, that means you can ask me for a summary of what I hold, ask me to correct it, ask me to erase it, and nominate someone to exercise these rights if you cannot. Ask on the number or the email in section 01 and I will act on it.

If I do not deal with your request properly, you can take the complaint to the Data Protection Board of India. I would rather you told me first and gave me the chance to put it right.

08Children

This is a site about professional work. It is not directed at children and I do not knowingly collect anything from them.

09When this page changes

The date under the heading is the date it last changed. On 27 September 2026 the form gained a server, so the version of this page that said it had none stopped being true and was rewritten rather than quietly amended. If the site ever gains analytics or an advertising cookie, this page will say so before that goes live, not after.

Written to describe what the code on this site actually does, checked against the code on 27 September 2026. If you find that this page and the site disagree, tell me: the page is wrong and I want to fix it.

Back to the site Terms of use