Cookie policy

This website does not set cookies of its own. That is not a simplification for the sake of a shorter policy — it is the actual configuration of the site as published. Because nothing non-essential is being stored on your device or read back from it, there is no consent banner on this site and nothing for you to accept, reject or manage.

Stated as a list, so there is no ambiguity about what is absent:

• No first-party cookies are set by mnfinfotech.com. Not for sessions, not for preferences, not for measurement.
• No analytics tag is installed. We do not run a product analytics or web analytics script on these pages.
• No tag manager or container script is loaded, so there is no container through which tags could be added to these pages without a change to the code we publish.
• No advertising, conversion or remarketing pixel is present, and no visitor to this site is added to an advertising audience by us.
• No local storage, session storage or browser database is used to identify, profile or follow visitors between visits.
• No consent management platform, cookie banner or preference centre is deployed, because there is nothing that would require consent.

Cookies are only one of several ways a website can store or read information on the device you are browsing with. Because the techniques differ but the effect is similar, we describe them together and hold them to the same standard.

Cookie

A small text file a website asks your browser to store and send back on later requests. A first-party cookie is set by the site you are visiting; a third-party cookie is set by another domain whose code the page has loaded, which is how tracking across different websites usually happens.

Session and persistent cookies

A session cookie is discarded when you close the browser. A persistent cookie stays until it expires or you delete it, which is what allows a site to recognise a returning visitor.

Local storage and session storage

Browser storage that a page can write to and read from directly. It is not sent automatically with every request the way a cookie is, but it can hold an identifier just as effectively, so it deserves the same scrutiny.

Pixel or tracking tag

A tiny image request or script loaded from another party. Fetching it tells that party you loaded the page, and it is commonly paired with a cookie to attribute a visit, a conversion or an advertising click.

SDK identifier

An identifier used inside a mobile application rather than a browser, such as an advertising identifier or an installation identifier. It has no bearing on this website, but it may be relevant to apps we build for clients under their own policies.

Where the rest of this page says cookies, read it as covering all of the above. A rule that applied only to cookies in the strict sense would be easy to satisfy and would not tell you anything useful.

Serving a web page requires a request to reach a server and a response to come back. That exchange leaves ordinary technical records, and we would rather explain them than let the absence of cookies imply that nothing at all is recorded.

This site is statically rendered apart from the single endpoint that receives the enquiry form, and it is served by a third-party hosting provider. In the normal course of delivering and protecting the site, that provider records server request logs, which may include:

• The IP address the request came from
• The user agent string your browser sends, which typically names the browser and operating system
• The URL requested, the response status and the time of the request
• Technical information used to route traffic, serve the correct region and mitigate abuse

Our handling of that information, and the third-party processors involved in hosting and in delivering enquiry emails, is described in our privacy policy. This page is limited to storage on your device.

The one interactive part of this site is the enquiry form. It is worth describing here because forms are a common place for tracking to hide, and because we want to be specific about what ours does.

• Submitting the form sends what you typed to our own endpoint on this domain. No third-party form service or embedded widget is involved.
• The submission is validated on the server and forwarded by email to contact@mnfinfotech.com through a transactional email provider. It is not written to a database, and there is no customer relationship system behind it.
• The form includes a hidden field that ordinary visitors never see or fill in, which helps us discard automated submissions. It is a decoy field, not an identifier, and it stores nothing on your device.
• Simple rate limiting is applied in the server memory of the process handling the request, to blunt repeated automated submissions. It holds no cookie and sets nothing in your browser.

In short, the form asks for what you choose to type and nothing more. It does not fingerprint your device, does not pre-fill from a stored identifier and does not report your visit to an advertising platform.

A site can grow, and a future version of this one may genuinely need measurement. So that you know how we would think about it rather than being surprised later, these are the categories we would use and how we would treat each of them.

We have deliberately not listed any cookie names, providers or durations, because listing technologies that are not present would be inventing detail. When something real exists, it will be named here with what it does.

The commitment below is the practical part of this policy. It describes the order in which we would act, not merely our intentions.

1. 01Decide whether the measurement is genuinely needed, and prefer the option that stores least on your device.
2. 02Update this page first, naming what is being introduced, what it does and which category it falls into, before the technology reaches the live site.
3. 03Where consent is required by the law that applies to you, ask for it before the non-essential technology is set, and make declining as straightforward as accepting.
4. 04Keep strictly necessary functionality working whether or not you accept anything else, so that a refusal never costs you access to the site.
5. 05Record the change in the revision date shown on this page, so a reader can see that the document moved.

Your browser, not this website, is where cookie control ultimately sits. That is true of every site you visit, and it remains the most reliable control available to you.

• Every major browser lets you view the cookies and storage a site has set, and delete them for one site or for all sites.
• Most browsers can block third-party cookies entirely, and several now do so by default.
• Private or incognito windows discard cookies and storage when the window is closed.
• Browser extensions and content blockers can prevent tracking scripts from loading at all.
• Mobile operating systems offer their own controls over advertising identifiers, which apply to apps rather than to this website.

The exact steps differ between browsers and versions, so we point you to your browser settings and its own help documentation rather than reproducing instructions here that would go out of date. Blocking cookies broadly may affect other websites that rely on them, for example by signing you out of services. It will not affect this site, because there is nothing here for the block to remove.

Signals such as Do Not Track

Some browsers send a preference signal indicating that you do not wish to be tracked. Because we run no tracking technology on this site, there is nothing for such a signal to switch off; you are already in the state it asks for. If we ever introduce non-essential technologies, we will say on this page how those signals are treated.

This site links outward in places, and the moment you follow such a link you are on someone else's site under their rules. We have no control over what they store on your device.

• Platform and vendor documentation referenced in our writing about the tools we work with
• Application store listings or public product pages, where relevant to work we describe
• A client's own website, where we link to it in the course of describing an engagement

Those destinations set their own cookies, run their own measurement and are governed by their own cookie and privacy policies. Read theirs before deciding what to accept there. Our naming of a platform or product is descriptive only and implies no partnership, endorsement or affiliation, as set out on our trademark independence page.

Separately, when we build or operate something for a client, the cookies and identifiers used in that client's product or advertising account belong to that client and are covered by the client's own policies, not by this page. This page describes mnfinfotech.com only.

We review this page when we change how the website is built or hosted, and whenever a technology described here is added or removed. The revision date shown with this document is the date of the most recent change.

If you have a question about anything on this page, want to know whether a specific technology is in use, or believe you have found something inconsistent with what we have written, write to us by email. We read what arrives at that address and reply to genuine enquiries.

Email

contact@mnfinfotech.com

Business

MNF INFOTECH, a proprietorship owned by Nancy Gopal Savaliya, GSTIN 24HQXPB6184C1ZK

Registered address

1st Floor, Plot No 37, Marutidham Bunglows, Gurukul Road, Near ABC Circle Sarthana, Nana Varachha, Surat, Gujarat 395006, India

This policy is governed by the laws of India, and the courts at Surat, Gujarat have jurisdiction over any dispute arising from it. Where you are in a jurisdiction that grants you specific rights over information relating to you, write to the address above and we will consider and respond to your request.