Privacy Policy

This website is operated by SUPERWEBTECH (OPC) PRIVATE LIMITED. Our registered legal name is written out in full here. The shorter form "Superwebtech (OPC) Pvt Ltd" that appears in the footer, in our email signatures and in this page's own metadata refers to the same company.

We are a private limited company incorporated in India as a One Person Company (OPC). Our registration details are:

Our registered office is Rudra Enclave Chipayan, H. No. 9, Bujarg, G B Nagar, Ghaziabad, Uttar Pradesh 201001, India. That address is both our registered office under company law and our principal place of business recorded for GST purposes; the owner has confirmed the two are the same.

We serve businesses and individual customers. We work with customers in India and in other countries, including in Europe, the United Kingdom and the United States. That is a statement about who we work with, not a legal position: which data-protection regime applies to a given visitor is a question we have not yet had answered by a lawyer, and this policy does not choose one.

Requests and questions under this policy are read and answered personally by Ramesh Singh as director of the company. We have not appointed a separate data-protection officer or privacy officer, and we do not publish one.

We are a technology company. We build websites, software products, AI systems and cloud infrastructure for business clients. We are not an online shop, a social network, a news service or a platform for user-generated content, and we do not run advertising on this site.

When you submit the project enquiry form on the Contact page, we receive the details you type into it. That information is the basic information we need in order to start a conversation with you. We use it to reply to your enquiry and for the follow-up to that reply, and for nothing else.

We do not use enquiry information to send you marketing. If you subscribe to updates through a newsletter signup form where one is offered, that is a different record with its own consent, described in section 3 — submitting an enquiry does not subscribe you to anything, and we do not copy enquiry details into our newsletter records. We do not sell enquiry information, we do not pass it to advertising companies or data brokers, and we do not use it to build an advertising or behavioural profile. The enquiry form itself has no marketing-consent control, because submitting an enquiry does not sign you up to be marketed to.

The form asks for:

Your enquiry is saved in a database in the third-party cloud hosting environment that runs this website. Alongside the details you submitted, we store the date and time the enquiry was received, an internal reference number, and the outcome of any email we sent about it.

Our team can also add an internal note to an enquiry and change its status (for example, from new to followed up). Those internal notes and status changes are stored in the same place.

Where newsletter signup is offered on this website, the signup form is a separate record from an enquiry. It asks for, and we store, the following: your name (required); your email address (required); your phone number (required); the newsletter topics you ask for; the fact that you consented, together with the date; a short code naming which part of the site the signup form was on; and the state of the subscription — whether it is active, whether you have unsubscribed, and whether our team has blocked the address from being emailed.

The topics recorded against a subscription are the set chosen on the signup form. Choosing no topic is allowed, and a subscription made with no topic chosen is recorded against our general updates instead. Signing up again with the same email address replaces the topics held by the earlier signup rather than adding to them, so the topics on file are the ones from your most recent signup.

Each signup also records where that signup came from: the page you were on when you pressed Subscribe; the first page you opened on this website during that visit; the web address you arrived from, if your browser told us one; and any campaign values carried in the link to that first page. It records which of the three ways in you reached the form — the Updates button, a prompt that appeared by itself, or the form opened by a page — whether you opened the list of topics at any point, and the topics the signup ended up recorded against. Every one of those is a place or an interaction, not an identity: none of them is your name, your email address, your phone number, your IP address, your device, or anything that identifies you, and none of them is sent to an advertising or marketing network. These entries are never changed afterwards. Changing your topics, unsubscribing, or an administrative correction all happened after the signup did, so each of them adds a new entry rather than altering what an earlier one recorded.

We use the recorded topics for one purpose: to work out which updates you have asked us for, and to be able to send you only those topics if this newsletter starts being sent. We do not use them to score you, to build a behavioural or advertising profile, or to select anything for you, and no advertising or marketing network is given them.

The signup form has its own consent box. It is never pre-ticked, and a signup is not accepted without it. That is a separate decision from the analytics choice described in sections 7, 8 and 14: accepting that choice does not subscribe you to anything, and declining it does not stop you subscribing. Nothing on this website adds you to a newsletter because of a cookie or analytics choice, and no such choice subscribes you to a newsletter.

We also keep a history of consent decisions about the subscription rather than replacing it, so we can show what you agreed to and when. A withdrawal recorded by you, a new consent recorded when you subscribe again later, and any action our team takes are kept as separate entries in that history; none of them overwrites the others.

Every newsletter message carries a link that stops future messages to that address. Following it opens a page that tells you what it will do and asks you to confirm, and the unsubscribe takes effect once you have confirmed it. It needs no account and no message to us. It does not stop one-off transactional email about a project you have asked us about, because that is not marketing and you asked for it directly.

If you unsubscribe, we keep a record against your email address so that the address is not emailed again by accident, and we keep the record of the consent you gave. That record is deliberately kept even if the subscription record itself is later deleted, because it is what stops the address becoming sendable again; it holds the email address and the reason, not a copy of the rest of your subscription, and nothing on this website uses it to contact you.

Our team can work with the subscriber list in the private area where subscriptions are managed: open a subscription and read its consent history, search and filter the list, change a subscription's state, block an address from being emailed, lift a block that one of our team added, delete a subscription record, and export the list to a spreadsheet file. Those administrative actions are recorded in the same consent history as your own decisions. None of them can reverse an unsubscribe that you made yourself: only a new signup that you make yourself can do that.

We do not currently send newsletters. The signup form records a subscription and its consent, but no newsletter has been sent from it, no email about a newly published article is sent from it, and no external email marketing provider is connected to it. If sending ever changes, this section and the provider list in section 13 will be updated before anything is sent.

A signup that succeeds is also recorded in the page analytics described in section 8, and only if you have accepted analytics there. It is a single event recording that a signup succeeded, and it carries only a small amount of non-personal information about the signup itself: the page it happened on, recorded as that page's address without the part of the link after the question mark, which of the three ways in you used, whether you opened the list of topics, and how many topics the signup was recorded against. It does not carry the web address you arrived from or the campaign values carried in the link you arrived on: those are kept in the signup record described earlier in this section, on our side, and are not copied into this event. It carries no name, no email address, no phone number, no reference to your subscription record, no unsubscribe link and no free text of any kind. If you decline analytics, your signup works exactly the same and this event is never sent; if you accept analytics and then subscribe, that is the same single event either way, and it is not joined to anything else we hold about you.

We do not attach any of the following to an enquiry, and none of these fields exist in our enquiry records:

The website saves your enquiry first, then attempts to send two emails. The first notifies our team that a new enquiry has arrived and contains your details. The second is an acknowledgement sent to the email address you gave us, confirming that we received it. The two emails are sent independently: if one cannot be delivered, the other is still attempted and your enquiry is still saved.

The notification email to our team contains your submitted details so that a person can answer you. It does not contain your IP address, your browser details or any technical tracking data.

If our email service is not available, the website does not claim to have sent anything. Instead, it prepares an unsent draft in your own email application with your details already filled in, so you can review the message and send it yourself if you want to.

Enquiry delivery is rate-limited. The site also keeps a short-lived, in-memory fingerprint of what you submitted, so that a double-click on the submit button does not send the same enquiry twice. That fingerprint is a one-way SHA-256 hash of the email address, name and message you submitted. It exists only in the memory of the running server, it expires after about a minute, and it is never written to the database, never emailed and never stored on an enquiry record.

The text, images and page content on this website are managed by our editors in a content management system (Sanity). Reading any page of this website does not require you to provide any personal information, and no part of the public website writes anything back into that system.

Some images and videos that appear in our articles are loaded directly from the content system's image delivery network rather than from this website. When your browser loads one of those images, that network sees your IP address and browser details, just as any web host does when it serves a file. It does not receive anything you type into the enquiry form.

Our editors use a separate content-studio tool at a dedicated address on this website to create and publish content. The studio requires the editor to sign in. It is not the public website, and signing in to it is not something we ask visitors to do.

Where booking is enabled, the "Book a call" button opens our scheduling provider (Calendly) in a new browser tab. We do not embed the provider's scheduler inside this website and we do not load any of its code here, so simply being on this page does not tell the provider that you visited.

If you choose to follow that link, you are leaving this website. From that point the scheduling provider handles your booking under its own privacy policy and its own terms, and it will see your IP address, browser details and the page you came from. Booking is optional and the enquiry form always works without it.

Links inside our editorial content, and any partner or reference link we choose to feature, take you to websites we do not control. Once you follow one, its own terms and privacy practices apply. We are not responsible for the content or the data practices of those sites.

The website's own application code — the pages you read, the enquiry form, the newsletter signup form where one is offered, and the services behind them — does not set any cookies. It writes only the items to your browser's local and session storage that are listed below, and nothing else. It writes nothing to IndexedDB. Nothing here is a tracking identifier, nothing is sent to us from it while you are only reading, and each item is discarded when you close that browser tab, in the case of session storage.

That is not the whole picture, because this website also loads third-party services into your browser. We use Google Analytics 4, Google's analytics service, to understand how this website is used and how it performs, and it may use cookies or similar browser technologies to do that. An identifier whose name begins with _ga is one of those. Cloudflare's Web Analytics also runs on this site and, according to Cloudflare, uses no cookies or local storage. Cloudflare's security features may set an essential cookie such as __cf_bm, which is separate from its Web Analytics. Section 8 describes all of these. Those identifiers are set by Google and by Cloudflare; they are not set by this website's own application code.

Neither Google Analytics 4 nor Cloudflare's Web Analytics is requested from its provider at all until you have accepted analytics in the notice described in section 14. If you have not been asked yet, or if you decline, this site has loaded neither service and has sent nothing to either. Accepting or declining makes no difference to the rest of the website: the pages, the enquiry form and the security checks in front of the site work exactly the same either way.

Our own application code sets two cookies of its own, and neither is used to follow you around. The storage items it writes are listed separately below, because they are not cookies and are not used to follow you around either:

This website uses two separate page-analytics services. They are independent providers that observe the same visits and report them separately, so their figures are not added together and are not one combined number.

We use Cloudflare Web Analytics to count page views and to see how quickly the pages load. It is loaded by this website, from Cloudflare, and only after you have accepted analytics in the notice described in section 14; until that choice is made, nothing is requested from Cloudflare for analytics and nothing is sent to it. Cloudflare's security features in front of this site are separate, are configured in our Cloudflare account, and are not affected by that choice.

Cloudflare's Web Analytics is designed to work without client-side state. According to Cloudflare, it does not use cookies or local storage, and it does not track individual visitors over time using IP addresses, user-agent strings or other identifying attributes for the purpose of reporting analytics. The metrics we see are aggregate page-view counts, page performance measurements and referrer categories — not a list of who visited.

We also use Google Analytics 4, which is provided by Google, to understand how this website is used and how it performs. Google Analytics 4 may use cookies or similar browser technologies, and the identifiers it stores in your browser are set by Google rather than by this website's own application code. It runs only after you have accepted analytics in the notice described in section 14; until that choice is made, nothing is requested from Google and nothing is sent to it. We are describing here what it is used for on this site. We are not stating here what legal basis applies to it, because that has not been decided; section 14 records that as an open question.

A page view is recorded when a page of this website opens in your browser, and again when you move to another page of this website without the page fully reloading — for example when you follow a link in the site. Each of those is one page view, and each analytics service counts them separately. Moving to an anchor further down the page you are already on is not a new page view. Where analytics is running, Google Analytics 4 records the page you are on at the moment you accept it, rather than the page that happened to load before you had decided.

We do not use Google Tag Manager, Meta Pixel, Hotjar, Microsoft Clarity, or any advertising, retargeting or cross-site tracking tag on this website, and we do not run an advertising or remarketing pixel. Whether any additional feature is switched on inside the Google Analytics 4 property itself is something we confirm internally rather than assert on this page; if that changes, this section is updated before the change is made.

This website asks before it enables either of its two analytics services. The notice described in section 14 offers a choice to accept or to reject, gives both the same prominence, and is shown only until a choice has been made. While that choice has not been made, neither Google's tag nor Cloudflare's Web Analytics beacon is loaded; rejecting stops both from loading, and accepting loads both. The choice can be changed afterwards at any time. Turning analytics off again removes the Cloudflare beacon from the page and clears its site token; because Cloudflare provides no way to stop a beacon that has already run within a page you are still looking at, the next page you open starts with neither service loaded. Whether this is the wording and the approach our legal review requires has not been decided, and this paragraph describes what the site does rather than asserting that the position has been approved.

Our network provider, Cloudflare, processes connection-level data such as IP address, browser details, requested URL, response status and timing in order to deliver the site, secure it and detect abuse. That processing is carried out by Cloudflare under its own terms and privacy documentation.

If bot-protection features are enabled on our Cloudflare account, Cloudflare sets a separate cookie named __cf_bm in your browser so it can tell an ordinary browser from automated traffic. That cookie is set by Cloudflare rather than by this website, it expires after roughly 30 minutes, and it is not used by the page analytics described above. Cloudflare Turnstile, where it is integrated, is used for bot and abuse protection and is operated by Cloudflare rather than by this website, and a challenge of that kind may store information of its own in your browser. Whether those features are currently enabled is confirmed by us rather than asserted here; if they are ever switched on in a way that changes what is stored, this section will say so.

Enquiry records are not deleted automatically. There is no fixed automatic deletion period, and there is no automatic anonymisation schedule. We retain enquiry records on an ongoing basis — for as long as we need the record to answer you and to meet our own business record-keeping needs.

This website has no automated process that removes or anonymises an enquiry for you. We have not published a retention period on this page because no period is set, and we would rather tell you that than state a period the system does not act on.

If you ask us to remove a specific enquiry, that is handled as a manual step by a person. We will consider the request and act on it where that is legally and operationally appropriate, and we will tell you what we did. See the next section for how to ask.

Nothing in this section states a retention period that any law requires of us, because we have not yet established which law applies to your enquiry.

Newsletter records are handled the same way. There is no fixed automatic deletion period for a newsletter subscription and no automatic anonymisation schedule, and this website has no automated process that removes one. The record of an unsubscribe is kept, because an address that has asked us to stop must not become sendable again by accident, and the record of a consent you gave is kept only while we rely on it. We have not set a period for either, and we would rather say so than publish one the system does not act on. A request to remove a newsletter record is handled as a manual step in the same way as an enquiry request, described in the next section.

The items this website writes to your own browser, described in section 7, are not copies of a record we hold. They stay in that browser unless you clear them, and clearing them does not unsubscribe you, does not withdraw a consent you gave, and changes nothing we hold about you.

Analytics data is handled by the providers described in section 8, and hosting and network request data by our hosting and network providers. None of it is written to this website's enquiry records or to its newsletter records.

If you have sent us an enquiry, you can ask us for a copy of the information you gave us, ask us to correct it, or ask us to delete it. Send the request to [email protected] and include the email address and the other details you used when you first contacted us. We use the details you submitted to find the right record and to check that the record is yours, because our enquiry records can only be searched by the information you gave us.

If you subscribed to updates rather than sent an enquiry, you can stop them without writing to us at all. Every newsletter message carries an unsubscribe link, and following it lets you confirm the unsubscribe on the page itself, which applies to that address from that confirmation. You can also ask us for a copy of what we hold about a newsletter subscription, ask us to correct the details on it, or ask us to remove it, using the same address and the same kind of identifying detail. The correction and removal parts of that process are the manual process described below.

These requests are handled manually, by the director of the company. This website has no automated process for them and there is no self-service portal. If you would rather deal with someone directly, say so in your message and we will arrange it.

A request to correct information is normally met by editing the stored record directly.

A request to delete an enquiry is considered by a person rather than by a system. We will act on it where that is legally and operationally appropriate — for example where the record is not needed in order to answer you or to meet a record-keeping obligation — and we will tell you what we did. We cannot promise that every deletion request will be carried out, because some records are needed for accounting, tax or legal reasons.

A request to delete a newsletter subscription is handled by a person in the same way. If you ask us to remove one, we stop sending to that address and we do not put it back into any sendable list. The record that you unsubscribed, and the record of any consent you gave, are kept as described in section 9, so we can show what you agreed to and when, and so that the address does not become sendable again by accident. Deleting a subscription record does not delete that record, because it is the thing that stops the address being treated as sendable again; it holds the email address and the reason, not a copy of the rest of your subscription. An unsubscribe you make yourself is not reversible by an administrator: our team cannot put an address back into a sendable list on your behalf. If you want updates again, you subscribe again yourself and that is recorded as a new consent, with its own date, alongside what came before it.

Our working target is to reply to a request within 7 days. That is an operational target the company has set for itself; it is not a deadline imposed by law, it is not a promise of a particular outcome, and it does not limit any right or obligation that may apply to you under a law that applies to us.

We take reasonable steps to protect the information we hold. The measures that are actually in place on this website are:

This is a business website intended for businesses. It is not directed at children, and we do not knowingly collect personal information from children. If you believe a child has sent us personal information through the enquiry form, email [email protected] with that detail so that we can find the enquiry and deal with it through the same manual process described in section 10.

We use a small number of external providers so that this website can run. We use a third-party cloud hosting provider to run the website and store application data. Each provider has a specific job, listed below. This section describes the role each provider plays; it does not set out the contractual terms of our arrangements with them, and it is not an exhaustive legal list of every organisation that may handle information on our behalf. How each provider is legally characterised under the law that applies to us has not yet been settled. The providers that handle visitor information on this website are:

Google Analytics 4 may store a persistent identifier in your browser, which allows a later visit from the same browser and device to be recognised as the same visit. That is a description of how the service works, and it is only used if you have accepted analytics. What legal basis applies to it is a question that has not been answered, and this section does not claim that it has been settled.

You decide whether Google Analytics 4 runs. The first time you open this website, a notice asks you to accept or to reject analytics. Your choice is kept as a single item in your browser's local storage, described in section 7. It stays in that browser, it is not sent to us, and we cannot see it.

You can change your choice at any time. Use the "Cookie settings" control at the bottom of every page; it opens the same settings, showing which option is currently selected. Turning analytics off stops Google's tag being requested and stops anything further being recorded from that point on. It does not remove anything already recorded, and it makes no difference to the rest of the website — the pages, the enquiry form and the security checks in front of the site behave the same way either way.

This choice controls both optional analytics services described in section 8: Google Analytics 4 and Cloudflare Web Analytics. Accepting loads both; rejecting loads neither; turning analytics off again removes them. It does not switch anything off in the protection Cloudflare applies in front of this website, and it does not switch off the site's own functions.

If you would rather block analytics at the browser level as well, your own browser controls remain available: blocking third-party requests, or blocking cookies for this site, will stop Google Analytics 4 from loading. Nothing on any page breaks when that happens — the website is fully usable without it — and the analytics figures described in section 8 become incomplete, because the visits they would have recorded are not recorded.

We will update this page when what we do changes — for example, if we introduce a new analytics provider, start sending newsletters, start using cookies, change how enquiry or newsletter information is stored, or change where newsletter signup is offered. The date below is the last time this page was changed. Continuing to use the website after an update means the updated policy applies from that point.

Questions about this policy, about an enquiry you have sent us, or about the information held about you, can be sent to [email protected]. Requests and questions are read and answered personally by Ramesh Singh as director of the company, rather than by a separate privacy team. If your question is about an enquiry, please include the email address you used so we can locate the record. Our registered office address is set out in section 1 if you need to send something by post.

If your question is about a newsletter subscription, the quickest route is the unsubscribe link: if we ever send you an update, that message carries the link, and following it lets you confirm the unsubscribe on the page itself, so you do not need to contact us at all. For anything else about a subscription — a copy of what we hold, a correction, or a request to remove the record — write to the same address with the email address you subscribed, and it will be handled the same way as an enquiry request, described in section 10.