Privacy policy

What Salary-Calculator.in collects, the Analytics and AdSense cookies set on its own domain, why calculator inputs never leave the browser, and DPDP rights.

This privacy policy states what Salary-Calculator.in collects from a visitor, what Google Analytics and Google AdSense collect through the two scripts the site loads, what is written to the visitor’s own device, and what a visitor can do about each of them. It applies to every page on the salary-calculator.in domain.

The site itself collects nothing. Salary-Calculator.in is a static website with no user accounts, no login, no newsletter, no comment system and no contact form, and no page on it asks a visitor to identify themselves. There is no application server behind it that could receive a submission.

Two Google scripts do collect. Google Analytics 4, under measurement identifier G-TH9VBW0CY1, loads on every page in production; Google AdSense, under publisher identifier ca-pub-5905124826063393, loads on every page except stubs, the search page and the policy pages, this one included. Between them they set eight named cookies, four of them on the salary-calculator.in domain itself, and the sections below name each one, its lifetime and the Google document that states it.

Two logs exist. Hostinger’s web server records every request in an access log, as any web server does, and the site generates a second log of its own that records hits from AI crawlers. The second one is described in full below, including the fields it holds, rather than left implicit.

The rest of this page works through the calculators, the search box, the device storage, the cookie table, the two Google services, the two logs, the position under the Digital Personal Data Protection Act, 2023, the rights that Act gives and the date each tranche of the Digital Personal Data Protection Rules, 2025 takes effect.

What Salary-Calculator.in collects directly

Nothing. No page on the site asks for a name, an email address, a mobile number, an employee code, a Permanent Account Number or a Pension Payment Order number, and there is no account system, no login, no registration, no newsletter, no comment section, no contact form and no upload anywhere on it.

That follows from how the site is built rather than from a promise. Hugo compiles every page to a static HTML file, and Hostinger serves those files as files. No application server, no database, no application programming interface and no form handler exists in the deployment, so no component could accept a submission even if one were sent to it.

Calculator inputs stay in the browser

Every calculator on salary-calculator.in runs in the visitor’s browser and transmits nothing. Basic pay, pay level, city classification, date of birth, length of qualifying service, pension amount, commuted portion and gross income are read by JavaScript on the device, computed there, and written back into the page.

This is checkable in two ways. A visitor can open the browser network panel, work through any calculator, and watch the request list stay still while the figures change. The scripts are minified but readable at their published URLs, and none of the 23 calculator scripts on the site contains a fetch call, an XMLHttpRequest or a navigator.sendBeacon call.

A computed figure is an estimate of an entitlement rather than a sanction of one. The figure that binds is the one the drawing and disbursing officer, the pay and accounts office or the Central Pension Accounting Office computes on the service record, which the editorial policy sets out in full.

What the site search box sends to the server

The header search box submits by GET, so the search term travels to the server in the URL. A search for commutation factor loads https://salary-calculator.in/search?q=commutation+factor, and that request line is recorded in the Hostinger access log and is sent to Google Analytics as part of the page location, because Google Analytics reports the full address of the page its tag fires on.

The lookup itself is local. Pagefind queries a search index built at deploy time and served as static files from the salary-calculator.in domain, so no search service receives the term, and the site neither reads it server side nor stores it anywhere of its own.

This corrects an earlier statement on three pages. Until 10 September 2026 this page, the about page and the contact page each said that the search term is not sent to a server. The local index lookup is what that sentence was reaching for, but the term does sit in the request URL and does reach the server, and all three pages now say so.

What is stored on the visitor’s device

One value is written by the site’s own code: the chosen colour theme, kept in browser local storage under the key sc-brand. It holds one of four colour names, blue, red, tiffany or orange, so the choice survives a page reload. It is never transmitted, is not readable by any other site, and is removed by clearing browser storage.

Everything else stored on the device comes from the two Google scripts, and the next section names it.

Cookies set on the salary-calculator.in domain

Four of the cookies a visit produces are written on salary-calculator.in itself, which makes them first-party cookies even though the site’s own code does not set them. The rest sit on Google’s own domains. The table names each one, its default lifetime and the Google document that states it.

CookieSet byDomainDefault lifetimePurpose
_gaGoogle Analytics 4salary-calculator.in2 yearsDistinguishes one visitor from another
_ga_TH9VBW0CY1Google Analytics 4salary-calculator.in2 yearsHolds session state
__gadsGoogle AdSensesalary-calculator.in13 monthsAdvertising and security
__gpiGoogle AdSensesalary-calculator.in13 monthsAdvertising and security
__eoiGoogle AdSensesalary-calculator.in6 monthsSecurity
IDEGoogledoubleclick.net24 months outside the EEA and the UK, 13 months insideAd selection and measurement
NIDGooglegoogle.com6 monthsSecurity, analytics, functionality, advertising
test_cookieGoogledoubleclick.net15 minutesChecks whether the browser accepts cookies

The lifetimes for _ga and _ga_TH9VBW0CY1 are stated in the Google Analytics Help article on GA4 cookie usage, and the rest in Google’s advertising cookies page at business.safety.google. Browsers cut those figures independently: Chrome caps any cookie at 400 days and Safari caps a script-set cookie at seven days.

Which advertising cookies actually appear on a given visit depends on the advertisement served and on Google’s own configuration. Salary-Calculator.in does not choose them, cannot read the values, and receives nothing from them. The AdSense script is suppressed on stub pages, on the search page and on the policy pages, so no advertising cookie is set by a visit to this page.

Google Analytics

Google Analytics 4 counts visits and shows which pages are read, under measurement identifier G-TH9VBW0CY1. It collects the visitor’s IP address, approximate location derived from it, device and browser type, the referring page, and the pages viewed with their timing.

The IP handling for a visitor in India differs from the widely quoted European position. Google states that for users outside the European Union, Switzerland and the United Kingdom it uses the IP address to detect spam traffic and to derive approximate location metadata such as city, region and country, that it never associates a raw IP address with a user identifier, and that it discards the raw address after that use. The stronger rule, that Google Analytics does not log or store individual IP addresses at all, applies to users in the European Union, Switzerland and the United Kingdom.

The data is read here as aggregate page and session counts, to decide which topics to write about next. It is not used to identify an individual reader, is not joined to any other data set, because no other data set exists on this side, and is not sold or shared with anyone beyond Google. Google’s handling is governed by the Google privacy policy. A visitor stops the collection by installing the Google Analytics opt-out browser add-on or by blocking the script.

Google AdSense

Google AdSense display advertising funds the site, under publisher identifier ca-pub-5905124826063393. Google and its advertising partners set the cookies named in the table above and use device identifiers to select advertisements, to measure whether an advertisement was seen, and to cap how often the same one is shown to the same visitor. Where personalised advertising is active, that selection may draw on a visitor’s earlier browsing on other sites carrying Google advertising, which Google describes at policies.google.com/technologies/partner-sites.

Salary-Calculator.in does not receive, hold or read the advertising data, and cannot identify any visitor from it. Advertisements are selected programmatically by Google and are not chosen by this site. No advertiser sees a page before publication, requests a page or influences what a page says, and there are no affiliate links, referral links, sponsored posts or paid placements anywhere in editorial content.

Personalisation is controlled at Google My Ad Center, which is the working control from India. The industry opt-out pages at optout.aboutads.info and youronlinechoices.eu cover the North American and European advertising programmes. Blocking the AdSense script with a content blocker stops the collection outright.

No third-party embeds, fonts or widgets

Three network destinations appear in the site’s own markup: googletagmanager.com for the analytics tag, pagead2.googlesyndication.com for the advertising tag, and the site’s own domain for everything else. There is no third-party font request, no social widget, no comment platform, no video embed, no tag manager container and no analytics service beyond the one named above.

The typeface is a self-hosted copy of Noto Sans, preloaded from /fonts/ on salary-calculator.in, so reading the site sends no request to a font service. Social preview images are served from the same domain. A visitor who blocks the two Google scripts therefore contacts no server other than Hostinger’s for the whole of a reading session.

Hosting and server logs

The site is hosted on Hostinger. As with any web server, requests are recorded in an access log holding the IP address, the requested URL including its query string, the timestamp, the referring page and the browser user-agent string.

That log exists to run and secure the service. It is not read for analytics, is not joined to any other data set, and is not shared other than where a law requires it. Its retention is set by Hostinger as the hosting provider and not by this site, and the site owner has no interface that exposes it.

The AI crawler log

Salary-Calculator.in keeps one log of its own, and it records AI crawlers rather than readers. Hostinger’s shared hosting exposes no raw access log to the site owner, so a small PHP script generates one, for the narrow question of which articles the answer engines fetch as sources.

A request reaches that script only when its user-agent string matches a listed crawler: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended, meta-externalagent, Bytespider, Amazonbot, YouBot, cohere-ai, DuckAssistBot, MistralAI-User, bingbot, and one synthetic agent kept in the list so the path can be tested. Every other request, including every browser and every Googlebot fetch, is served as a static file and never touches it.

Each logged hit is one tab-separated line holding the UTC timestamp, the crawler name, the requested path, whether the page resolved, the requesting IP address and the first 200 characters of the user-agent string. The addresses recorded therefore belong to crawler infrastructure rather than to a person reading the site. A visitor who set a browser’s user-agent string to one of those names would be logged like a crawler, which is the only route by which a human request lands in the file.

The log is written outside the public directory in month-by-month files, readable only by the account that owns them, and summarised in a weekly report. Removal of an old monthly file is a manual step rather than a scheduled one. The logging code is wrapped so that a logging failure cannot change what the crawler receives, and the page served through that path is byte-identical to the static file.

Who the Data Fiduciary is under the Digital Personal Data Protection Act 2023

Section 2(i) of the Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023) defines a Data Fiduciary as any person who, alone or in conjunction with other persons, determines the purpose and means of processing of personal data, and Section 2(j) defines the Data Principal as the individual the data is about. Section 3(a) applies the Act to the processing of digital personal data within the territory of India where the data is collected in digital form. Section 2(t) defines personal data as any data about an individual who is identifiable by or in relation to that data.

Google determines the means of the analytics and advertising processing and holds the data. Salary-Calculator.in determines that the processing happens at all, by choosing to load the two scripts, and says so rather than describing Google as a controller, which is a term from European law and not from the Act. The site holds none of the data and cannot retrieve, correct or erase a record inside Google, which is why every control named on this page is a Google control.

The figures a visitor types into a calculator would be personal data if they were collected. They are not collected, so on that side of the site the Act has nothing to attach to.

Salary-Calculator.in shows no cookie consent banner and presents this page instead. Section 4(1) of the Act permits the processing of personal data for a lawful purpose for which the Data Principal has given consent or for certain legitimate uses. Section 5(1) requires a notice, accompanying or preceding the consent request, that names the personal data and the purpose, the manner of exercising rights under Section 6(4) and Section 13, and the manner of complaining to the Data Protection Board of India. Section 6(1) requires the consent itself to be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action.

Rule 3 of the Digital Personal Data Protection Rules, 2025 prescribes what that notice must contain, and Rule 1(4) brings Rule 3 into force eighteen months after the Rules were published. The timetable is set out in the section on the Rules below.

A visitor who does not want the two Google scripts to run blocks them in the browser and loses nothing by doing so. No page is withheld, no calculator is degraded and no notice is repeated on the next visit.

Rights of a Data Principal, and where they can be exercised

Sections 11 to 14 of the Digital Personal Data Protection Act, 2023 give a Data Principal four rights against a Data Fiduciary. Section 11(1) gives the right to a summary of the personal data being processed, the processing activities undertaken, and the identities of the other Data Fiduciaries and Data Processors the data has been shared with. Section 12 gives the right to correction, completion, updating and erasure. Section 13(1) gives the right to readily available means of grievance redressal, and Section 13(3) requires that route to be exhausted before approaching the Data Protection Board of India. Section 14(1) gives the right to nominate another individual to exercise those rights on the death or incapacity of the Data Principal.

Salary-Calculator.in holds no personal data of its own, so there is no record here to summarise, correct, export or erase. A request about analytics or advertising data is made to Google through the controls linked above, because Google is the only party holding it.

The contact page carries the route for correspondence and states plainly that a published address is not yet in service. Rule 9 of the Digital Personal Data Protection Rules, 2025 requires a Data Fiduciary to publish the contact information of a person able to answer questions about the processing of personal data, and falls in the eighteen-month tranche. That contact information will appear on this page.

What changes when the Digital Personal Data Protection Rules 2025 commence

The Rules were notified as G.S.R. 846(E) on 13 November 2025 by the Ministry of Electronics and Information Technology, under sub-sections (1) and (2) of Section 40 of the Act, following the draft published as G.S.R. 2(E) on 3 January 2025. Rule 1 splits their commencement into three tranches.

TrancheRulesComes into force
Immediate1, 2 and 17 to 21On the date the Rules were published in the Official Gazette
One year4 (registration and obligations of a Consent Manager)One year after that publication
Eighteen months3, 5 to 16, 22 and 23Eighteen months after that publication, in May 2027

The eighteen-month tranche is the one that reaches a site of this kind. Rule 3 fixes the contents of the notice given to a Data Principal. Rule 6 sets the reasonable security safeguards a Data Fiduciary must apply. Rule 7 sets the route and the timetable for intimating a personal data breach. Rule 8 fixes the period after which a specified purpose is deemed no longer to be served, which starts the erasure clock. Rule 9 requires the published contact person. Rule 10 prescribes verifiable consent for the personal data of a child. Rule 14 prescribes how a Data Principal exercises the Section 11 to Section 14 rights.

Section 1(2) of the Act provides that it comes into force on such date as the Central Government appoints by notification, and that different dates may be appointed for different provisions. This page will be updated as those dates take effect rather than after them.

Children

Section 2(f) of the Act defines a child as an individual who has not completed the age of 18 years. Section 9(1) requires a Data Fiduciary to obtain the verifiable consent of a parent or lawful guardian before processing a child’s personal data. Section 9(2) bars processing likely to cause a detrimental effect on the well-being of a child. Section 9(3) bars tracking, behavioural monitoring and targeted advertising directed at children.

Salary-Calculator.in is written for serving and retired central government employees, for candidates for government posts, and for professionals working in the field. It is not directed at children, it runs no age gate because it collects nothing that would need one, and it does not knowingly hold information about anyone under 18. Advertising on the site is served by Google against the general audience of a page on pay, pension or income tax, and is not directed at children.

Transfers outside India

The analytics and advertising data is handled by Google, which processes data on servers in more than one country under the terms of the Google privacy policy. Section 16(1) of the Act empowers the Central Government to restrict, by notification, the transfer of personal data by a Data Fiduciary to a country or territory outside India.

Salary-Calculator.in transfers nothing itself. It holds no personal data, operates no processor arrangement of its own, and has no mechanism by which data could be moved anywhere, because there is nothing on this side to move.

Articles on this site link to official sources, among them dopt.gov.in, doe.gov.in, doppw.gov.in, incometax.gov.in, pfrda.org.in, egazette.gov.in and meity.gov.in, and this page links to Google’s own policy and opt-out pages. Each of those sites operates under its own privacy policy, and this policy does not extend to them.

The site sets no Referrer-Policy header of its own, so a browser applies the default in the Referrer Policy specification, strict-origin-when-cross-origin. On a click through to an external site that sends https://salary-calculator.in as the referrer and not the address of the page being read.

Blocking the analytics and advertising scripts

A visitor who blocks both scripts loses no functionality. Every page and every calculator works in full without them, because all content is server-rendered as static HTML and all calculation runs on the device. Nothing on the site is held behind a script, an interstitial or a consent wall.

Both scripts are emitted only in production builds, so a local build of the site loads neither. Neither is emitted on a stub page, on the search page or on the policy pages. The Google Analytics opt-out browser add-on stops the analytics collection across every site that uses Google Analytics, and any content blocker stops both scripts here.

Changes to this policy

A substantive change to this policy is published on this page, and the visible Updated date at the top changes with it, which also moves the dateModified in the page structured data and the lastmod entry in the sitemap. A change that widens what is collected, or that adds a service which collects it, is described in this section when it takes effect rather than folded silently into the text above.

Two changes were made on 10 September 2026. The statement that a search term is not sent to a server was corrected, on this page and on the about and contact pages, because the header form submits by GET and the term therefore sits in the request URL. The statement that the site sets no first-party cookies was corrected: the site’s own code sets none, but four of the cookies set through it, _ga, _ga_TH9VBW0CY1, __gads and __gpi, are written on the salary-calculator.in domain and are first-party cookies for that reason.

External references

Frequently Asked Questions (FAQs)

Does Salary-Calculator.in collect any personal information?
No. The site has no account system, no login, no registration, no newsletter, no comment section, no contact form and no upload, and no page asks for a name, an email address, a mobile number, an employee code, a Permanent Account Number or a Pension Payment Order number. Hugo compiles the whole site to static HTML files that Hostinger serves as files, so there is no application server, no database and no application programming interface anywhere in the deployment that could accept a submission.
Do calculator inputs leave the browser?
No. Basic pay, pay level, city classification, date of birth, length of qualifying service, pension amount, commuted portion and gross income are read by JavaScript on the device, computed there, and written back to the page. None of the 23 calculator scripts on the site contains a fetch call, an XMLHttpRequest or a sendBeacon call, and the site has no server-side component that could receive one.
How can a visitor check that a calculator sends nothing?
By opening the browser network panel and working through any calculator on the site. Changing a value and recomputing produces no new entry in the request list. The published scripts are minified but readable at their own URLs, and a search through them for fetch, XMLHttpRequest or sendBeacon returns nothing across all 23 files.
Does Salary-Calculator.in set cookies?
The site’s own code sets none. Two Google scripts set cookies through it: Google Analytics 4 under measurement identifier G-TH9VBW0CY1, and Google AdSense under publisher identifier ca-pub-5905124826063393. Several of those cookies, including _ga, _ga_TH9VBW0CY1, __gads and __gpi, are written on the salary-calculator.in domain itself and are first-party cookies for that reason, even though the site’s own code does not set them.
Which cookies are set, and how long do they last?
Google Analytics sets _ga and _ga_TH9VBW0CY1, both first-party on salary-calculator.in with a default expiry of two years, per the Google Analytics Help article on GA4 cookie usage. Google AdSense sets __gads and __gpi on the publisher domain for 13 months, __eoi for six months, IDE on doubleclick.net for 24 months outside the European Economic Area and the United Kingdom, and NID on google.com for six months, per Google’s advertising cookies page. Browsers cap these independently: Chrome limits a cookie to 400 days and Safari limits a script-set cookie to seven days.
What does Google Analytics do with the IP address of a visitor in India?
Google states that for users outside the European Union, Switzerland and the United Kingdom it uses the IP address to detect spam traffic and to derive approximate location metadata such as city, region and country, that it never associates a raw IP address with a user identifier, and that it discards the raw address after that use. The separate rule that Google Analytics does not log or store individual IP addresses applies to users in the European Union, Switzerland and the United Kingdom, and not to a visitor in India.
Is the analytics data used to identify individual readers?
No. The data is read as aggregate page and session counts to decide which topics to write about next. Salary-Calculator.in runs no user identifier, no login, no customer list and no other data set that a visit could be joined to, and does not sell or share the analytics data with anyone beyond Google.
How is personalised advertising turned off?
Through Google’s My Ad Center at myadcenter.google.com, which is the control that works from India, or by blocking the AdSense script with a browser extension. The industry opt-out pages at optout.aboutads.info and youronlinechoices.eu cover the North American and European advertising programmes respectively. Salary-Calculator.in does not select advertisements, does not receive the advertising data and cannot switch personalisation off on a visitor’s behalf.
Why does the site show no cookie consent banner?
Because it presents this page instead. Section 6(1) of the Digital Personal Data Protection Act, 2023 requires consent to be free, specific, informed, unconditional and unambiguous with a clear affirmative action, and Rule 3 of the Digital Personal Data Protection Rules, 2025, which prescribes the contents of the notice that accompanies a consent request, comes into force eighteen months after those Rules were published. A visitor who does not want the two Google scripts to run blocks them in the browser and loses no page, no article and no calculator by doing so.
What happens to a term typed into the site search box?
It travels to the server in the URL. The header search box submits by GET, so a search for commutation factor loads https://salary-calculator.in/search?q=commutation+factor, and that request line is recorded in the Hostinger access log and is sent to Google Analytics as part of the page location. The search itself then runs on the device: Pagefind queries an index built at deploy time and served as static files from the same domain, so no search service receives the term and the site stores it nowhere of its own.
What does the web server log?
The same fields any web server records: the IP address, the requested URL including its query string, the timestamp, the referring page and the browser user-agent string. Hostinger keeps that access log to run and secure the service. It is not read for analytics, is not joined to any other data set, and is not shared other than where a law requires it.
Does the site keep a log of its own?
Yes, one, and it records AI crawlers rather than readers. A request is routed to the logging script only when its user-agent string matches a listed crawler such as GPTBot, ClaudeBot, PerplexityBot or Google-Extended, and every other request, including every browser and every Googlebot fetch, is served as a static file without touching it. Each logged hit is one tab-separated line holding the UTC timestamp, the crawler name, the requested path, whether the page resolved, the requesting IP address and the first 200 characters of the user-agent string, written to a monthly file outside the public directory.
Who is the Data Fiduciary for the analytics and advertising data?
Section 2(i) of the Digital Personal Data Protection Act, 2023 defines a Data Fiduciary as any person who, alone or in conjunction with other persons, determines the purpose and means of processing of personal data. Google determines the means and holds the data. Salary-Calculator.in determines that the processing happens at all, by choosing to load the two scripts, and states that rather than describing Google as a controller, which is not a term Indian law uses. The site holds none of the data and cannot retrieve, correct or erase a record inside Google, which is why every control named on this page is a Google control.
What rights does a visitor have, and against whom?
Sections 11 to 14 of the Digital Personal Data Protection Act, 2023 give a Data Principal the right to a summary of the personal data being processed and the identities of parties it has been shared with, the right to correction, completion, updating and erasure, the right to readily available means of grievance redressal, and the right to nominate another individual to exercise those rights on death or incapacity. Salary-Calculator.in holds no personal data, so there is no record here to summarise, correct or erase, and a request about analytics or advertising data goes to Google. Section 13(3) requires a Data Principal to exhaust the Data Fiduciary’s own redressal route before approaching the Data Protection Board of India.
When do the Digital Personal Data Protection Rules, 2025 take effect?
In three tranches fixed by Rule 1. Rules 1, 2 and 17 to 21 came into force on the date the Rules were published, which was the Gazette of India Extraordinary carrying G.S.R. 846(E) dated 13 November 2025. Rule 4, on the registration and obligations of a Consent Manager, comes into force one year after that publication. Rules 3, 5 to 16, 22 and 23, which carry the notice contents, the security safeguards, the breach intimation route, the erasure timetable, the published contact person and the mechanism for exercising rights, come into force eighteen months after it, in May 2027.
Is the site directed at children?
No. Section 2(f) of the Digital Personal Data Protection Act, 2023 defines a child as an individual who has not completed the age of 18 years, and Section 9(3) bars a Data Fiduciary from tracking or behavioural monitoring of children and from targeted advertising directed at children. Salary-Calculator.in is written for serving and retired central government employees, for candidates for government posts and for professionals in the field. It runs no age gate because it collects nothing that would need one, and it does not knowingly hold information about anyone under 18.
Does blocking the analytics and advertising scripts break anything?
No. Every page and every calculator works in full without them, because all content is server-rendered as static HTML and all calculation is local. The Google Analytics opt-out browser add-on at tools.google.com/dlpage/gaoptout stops the analytics collection, and any content blocker stops both scripts. Neither script is emitted on a stub page, on the search page or on this and the other policy pages.
Is anything stored on the device apart from cookies?
One value. The chosen colour theme is kept in browser local storage under the key sc-brand, holds one of four colour names, blue, red, tiffany or orange, and survives a page reload so the choice does not have to be made again. It is never transmitted, is not readable by any other site, and is removed by clearing browser storage.

References

  1. Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023), assented on 11 August 2023 and published in the Gazette of India Extraordinary, Part II, Section 1, No. 25, dated 11 August 2023.
  2. Digital Personal Data Protection Rules, 2025, notified as G.S.R. 846(E) dated 13 November 2025 by the Ministry of Electronics and Information Technology, Gazette of India Extraordinary, Part II, Section 3, Sub-section (i), No. 760.
  3. Draft Digital Personal Data Protection Rules, 2025, published as G.S.R. 2(E) dated 3 January 2025, Gazette of India Extraordinary, Part II, Section 3, Sub-section (i).
  4. Sections 2(f), 2(i), 2(j), 2(t), 3, 4, 5, 6, 9, 11, 12, 13, 14, 16 and 40, Digital Personal Data Protection Act, 2023.
  5. Google Analytics Help, “Cookie usage on websites”, on the _ga and _ga_<container-id> cookies and their two-year default expiry.
  6. Google Analytics Help, “Usage of IP address for non-EU, non-Switzerland, or non-UK users”.
  7. Google, “Advertising cookies”, business.safety.google, on the __gads, __gpi, __eoi, IDE, NID and test_cookie cookies, their domains and their lifetimes.
  8. Google privacy policy and “How Google uses information from sites or apps that use our services”.