1. Meaning of Clickstream Evidence Claims

Clickstream evidence claims are legal claims or disputes in which records of a user's digital activity—such as clicks, page visits, navigation paths, searches, button selections, timestamps, session identifiers, URLs, cookies, IP addresses, device identifiers and similar interaction data—are relied upon to establish a fact in issue.

A clickstream is essentially the chronological digital trail created when a person interacts with a website, application, online platform, advertisement, or digital service.

For example, a website may record:

User → enters website → views product → clicks "Add to Cart" → reads terms → clicks "Accept" → proceeds to payment.

That sequence can become important evidence in litigation concerning:

• online contracts;
• consent;
• arbitration agreements;
• privacy;
• consumer deception;
• online purchases;
• advertising;
• intellectual property;
• unauthorized access;
• cybersecurity;
• employment monitoring;
• website terms and conditions;
• digital fraud;
• authentication;
• user behavior;
• damages.

In Indian litigation, clickstream records are fundamentally electronic/digital records and their admissibility is governed today by the Bharatiya Sakshya Adhiniyam, 2023 (BSA). Sections 61–63 specifically address electronic and digital records and their admissibility.

2. What Constitutes Clickstream Evidence?

Clickstream evidence may include:

A. Navigation data

• pages visited;
• sequence of pages;
• hyperlinks clicked;
• navigation paths;
• time spent on pages.

B. Interaction data

• button clicks;
• checkbox selections;
• scrolling;
• form submissions;
• downloads;
• searches;
• log-ins and log-outs.

C. Transaction data

• "Buy Now" clicks;
• shopping-cart activity;
• payment-page interactions;
• confirmation clicks;
• subscription selections.

D. Authentication data

• login timestamps;
• session IDs;
• IP addresses;
• device identifiers;
• authentication logs.

E. Consent data

For example:

"I agree to Terms and Conditions"

The underlying clickstream may be used to establish whether, when and how a user allegedly accepted the terms.

F. Technical metadata

• timestamp;
• browser;
• operating system;
• IP address;
• cookie ID;
• device ID;
• server logs;
• geolocation information where collected.

3. Why Clickstream Evidence Is Legally Important

Clickstream evidence can answer questions that traditional documents cannot.

For example:

Question

Did the consumer actually click "I Agree"?

A contract document may show the terms, but clickstream data may show:

• whether the user visited the terms;
• whether the user clicked the checkbox;
• the time of acceptance;
• the session in which acceptance occurred;
• the device used;
• the IP address;
• the subsequent transaction.

Thus, clickstream evidence can establish a digital chronology.

4. Clickstream Evidence and Electronic Evidence

Clickstream evidence is not a separate magical category of evidence.

It generally falls within the broader concept of electronic/digital records.

The BSA expressly recognizes electronic or digital records under Section 61 and contains special provisions concerning electronic records under Sections 62 and 63. Section 63 governs admissibility of electronic records produced from computers, communication devices, computer systems, networks, intermediaries and related digital resources.

Therefore, a claim based on clickstream evidence involves two distinct questions:

Question 1 — Relevance

Does the clickstream prove something material to the dispute?

Question 2 — Admissibility/authenticity

Has the electronic record been properly proved and shown to be reliable?

A technically sophisticated dataset can still fail as evidence if the legal requirements for proving it are not satisfied.

5. Clickstream Evidence in Contract Formation

One of the most important applications is online contract formation.

Suppose a website alleges:

"The customer agreed to mandatory arbitration."

The defendant might produce:

• website terms;
• database records;
• click logs;
• timestamp;
• IP address;
• account ID;
• session ID.

The clickstream may help establish whether the user actually performed the contractual act.

This becomes particularly important with:

• clickwrap agreements;
• sign-in-wrap agreements;
• online subscriptions;
• software licences;
• e-commerce contracts;
• platform agreements.

6. Clickwrap and Browsewrap

Clickwrap

The user affirmatively clicks something such as:

"I agree to the Terms."

Clickstream evidence can be especially relevant because it may show the affirmative action.

Browsewrap

The website attempts to impose terms merely because the user browses the website.

The evidentiary question becomes more difficult:

• Was the user actually notified?
• Were the terms conspicuous?
• Did the user have constructive notice?
• Did the user manifest assent?

Clickstream evidence can therefore become important to proving notice and assent.

7. Clickstream Evidence in Consumer Claims

A consumer may allege:

"The website represented that the product was available for ₹999."

The company may produce clickstream and website records showing:

• the advertisement displayed;
• the price displayed;
• consumer's navigation;
• product selection;
• checkout;
• payment;
• cancellation.

Conversely, consumers may use clickstream evidence to establish:

• misleading advertisements;
• hidden charges;
• deceptive interfaces;
• unauthorized subscriptions;
• dark patterns;
• misleading consent mechanisms.

8. Clickstream Evidence in Privacy Claims

Clickstream evidence can be particularly significant in privacy litigation.

For example, a plaintiff may allege that a website tracked users after they allegedly refused consent.

Server records might establish:

1. user visits website;
2. privacy banner appears;
3. user refuses tracking;
4. tracking identifier is nevertheless generated;
5. subsequent pages are recorded.

The clickstream therefore potentially provides evidence concerning:

• consent;
• tracking;
• collection;
• disclosure;
• user choices;
• data retention.

9. Clickstream Evidence in Cybercrime

Clickstream and access logs may help establish:

• account access;
• unauthorized login;
• suspicious navigation;
• attempted transactions;
• credential use;
• IP address;
• session duration;
• sequence of actions.

But an important distinction must be made:

An IP address or clickstream entry generally identifies a digital event; it does not automatically establish who personally performed that event.

A person could be using:

• shared devices;
• corporate networks;
• VPNs;
• proxies;
• compromised accounts;
• public Wi-Fi;
• remote systems.

Therefore, attribution requires additional evidence.

10. Clickstream Evidence in Intellectual Property Claims

Clickstream records may be used in:

• copyright disputes;
• trademark disputes;
• online infringement;
• unauthorized downloads;
• digital advertising disputes.

For example, a plaintiff might establish that particular digital content was repeatedly accessed through an account.

The clickstream can establish:

• date;
• time;
• frequency;
• sequence;
• account;
• IP;
• device.

But it still must be connected reliably to the alleged infringer.

11. Clickstream Evidence in Advertising Litigation

Clickstream data can show:

• advertisement impressions;
• advertisement clicks;
• conversion rates;
• consumer journeys;
• purchases following advertising exposure.

This type of evidence is particularly important where damages depend on proving:

advertisement → consumer interaction → purchase.

A U.S. case involving this kind of technology is TNS Media Research, LLC v. TiVo Research and Analytics, Inc., where the litigation concerned systems involving clickstream data, advertising data, programming data and purchase data. The court's discussion illustrates how clickstream information can be collected, matched and analyzed with other consumer data.

12. Clickstream Evidence and Proof of Damages

Clickstream evidence may be used not only to establish liability but also damages.

For example:

1,000 customers

↓

Clicked advertisement

↓

Visited product page

↓

Purchased product

↓

Paid allegedly inflated price

The clickstream may help calculate:

• number of affected customers;
• number of transactions;
• conversion rates;
• timing;
• purchases;
• allegedly excessive charges.

However, courts may require a reliable methodology linking the data to the actual legal theory of damages.

13. Authenticity of Clickstream Evidence

This is one of the most important issues.

A party cannot simply print a spreadsheet and say:

"These are our website logs."

The opposing party can ask:

• Who created the record?
• What system generated it?
• How was it collected?
• Was the system functioning correctly?
• Was the data altered?
• Was the record complete?
• What database produced it?
• Who extracted it?
• What methodology was used?
• Are timestamps reliable?
• Can entries be deleted or modified?

The party relying on the evidence must establish its authenticity and satisfy the applicable statutory requirements.

14. Current Indian Law — Bharatiya Sakshya Adhiniyam, 2023

For proceedings governed by the current Indian evidence regime, Section 63 BSA is particularly important.

It provides the statutory framework for admissibility of electronic records produced through computers and communication devices.

The provision addresses circumstances such as:

• standalone computers;
• computer systems;
• computer networks;
• computer resources;
• intermediaries;
• electronic storage.

It also requires a certificate when a statement is sought to be admitted under the provision.

The statutory Schedule contemplates identification of the source/device, including potentially:

• computer;
• storage media;
• DVR;
• mobile;
• flash drive;
• CD/DVD;
• server;
• cloud;
• other digital source.

It also contemplates recording the relevant hash value and algorithm used.

This is highly relevant to clickstream evidence because website logs may exist on:

• cloud servers;
• web servers;
• third-party analytics platforms;
• content-delivery systems;
• application servers;
• databases.

15. Hash Values and Clickstream Evidence

A hash value is a mathematical representation of digital data used to help demonstrate that a particular digital file or dataset has not been altered.

For example:

Original clickstream export → SHA-256 hash → preserved evidence

Later:

Produced clickstream export → SHA-256 hash → compared with original

Matching hashes can provide powerful evidence concerning integrity.

Under the BSA's statutory certificate schedule, hash information is expressly contemplated for electronic/digital records.

16. Six Important Indian Case Laws

Case 1 — Anvar P.V. v. P.K. Basheer, (2014) 10 SCC 473

Importance

This is one of the foundational Supreme Court decisions on electronic evidence.

The Supreme Court held that electronic records presented as secondary evidence must satisfy the statutory requirements of Section 65-B of the old Evidence Act.

The Court treated Section 65-B as a special statutory mechanism governing proof of electronic records.

Relevance to clickstream claims

A party relying upon:

• website logs;
• database exports;
• digital activity records;
• server records;

must consider the applicable electronic-evidence requirements.

Principle

Electronic evidence requires legally compliant proof, not merely production of a printout.

Case 2 — Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal, (2020) 7 SCC 1

Importance

This three-judge Bench decision clarified the law relating to electronic records and the certificate requirement.

The Supreme Court reaffirmed Anvar P.V. and overruled the contrary approaches taken in Shafhi Mohammad and the relevant aspect of Tomaso Bruno.

It also clarified that a certificate is unnecessary where the original electronic record itself is produced in the legally relevant sense—for example, where the original device is itself produced and proved appropriately.

Relevance

Suppose clickstream evidence is stored directly on a device that can itself be produced and proved.

The legal analysis may differ from a situation where a party merely produces an exported spreadsheet from a remote server.

Principle

The method of proving electronic evidence depends upon whether the original electronic record or a computer output/secondary electronic record is being relied upon.

Case 3 — State (NCT of Delhi) v. Navjot Sandhu, (2005) 11 SCC 600

Importance

This earlier Supreme Court case took a more permissive approach to proving electronic records.

Its approach concerning Section 65-B was subsequently displaced by Anvar P.V.

Relevance

It remains important historically because it explains the development of Indian electronic-evidence law.

Principle

The case demonstrates the transition from relatively flexible proof of electronic material toward the specialized statutory requirements later emphasized in Anvar.

Case 4 — Sonu @ Amar v. State of Haryana, (2017) 8 SCC 570

Facts

The case concerned electronic evidence including call-detail records.

Importance

The Supreme Court considered the consequences of failing to raise a timely objection concerning certification of electronic records.

The decision discussed the distinction between:

• inherent inadmissibility; and
• objection concerning the mode or manner of proof.

The case also traced the transition from Navjot Sandhu to Anvar.

Relevance

In a clickstream case, an opposing party should carefully consider when and how an objection to electronic evidence is raised.

Case 5 — Tomaso Bruno v. State of Uttar Pradesh, (2015) 7 SCC 178

Importance

The case dealt with electronic evidence and CCTV-related evidentiary issues.

The decision had taken an approach that was subsequently treated as inconsistent with the strict Section 65-B framework in Arjun Panditrao.

Relevance

It demonstrates an important point:

The mere existence of potentially relevant electronic evidence does not eliminate the statutory requirements governing its proof.

For clickstream evidence, the same logic applies to server logs, website records and other digitally generated material.

Case 6 — Shafhi Mohammad v. State of Himachal Pradesh, (2018) 2 SCC 801

Importance

The Supreme Court had held that the certificate requirement could be relaxed in circumstances where the party seeking to rely on electronic evidence did not have possession or control of the relevant device.

However, this position was subsequently overruled by the three-judge Bench in Arjun Panditrao Khotkar.

Relevance

This is especially important for clickstream evidence because the relevant server may belong to:

• Google;
• Amazon;
• Meta;
• a payment processor;
• a hosting provider;
• an analytics provider;
• another third-party intermediary.

Arjun Panditrao provides the later controlling clarification on the certificate issue.

17. Important Additional Case — Shafhi Mohammad's Later Treatment

For examination purposes, it is important not to cite Shafhi Mohammad as the current controlling rule on the certificate requirement.

The Supreme Court in Arjun Panditrao Khotkar expressly rejected that part of Shafhi Mohammad.

Therefore:

Anvar P.V. → clarified by Arjun Panditrao Khotkar

is the safer modern formulation.

18. Clickstream Evidence and Chain of Custody

A strong clickstream claim should establish a chain such as:

Website/Application

↓

Server/database

↓

Collection

↓

Preservation

↓

Forensic extraction

↓

Hashing

↓

Certificate/documentation

↓

Expert/witness

↓

Court

Every stage creates potential challenges.

For example, the defendant may argue:

"The data presented to the court is not the same data originally generated by the website."

Therefore preservation procedures are crucial.

19. Reliability Problems With Clickstream Evidence

Clickstream data can be affected by:

Cookies

Cookies may be deleted, blocked or shared.

IP addresses

One IP address may correspond to multiple users.

Shared devices

Different people may use the same device.

Dynamic IP addresses

An IP address may change between users.

VPNs/proxies

The apparent location may not identify the actual user.

Bots

Automated software can generate large numbers of clicks.

Web crawlers

Search engines and other automated systems may create activity.

Ad fraud

Bots may generate artificial advertising clicks.

Tracking failures

Ad blockers or browser settings may prevent complete collection.

Data retention

Older logs may have been deleted.

Therefore, clickstream evidence is not automatically conclusive merely because it was generated automatically.

20. Clickstream Evidence and Attribution

A critical distinction is:

Event proof

"An account performed an action."

versus

Human attribution

"Person X personally performed the action."

The first may be established by:

• account ID;
• timestamp;
• session;
• IP;
• device.

The second may require additional evidence.

For example:

Account ABC clicked "Accept."

does not necessarily prove:

Mr. X personally clicked "Accept."

The court may need evidence linking Mr. X to the relevant account/device/session.

21. Clickstream Evidence and Consent

Consent disputes are likely to become increasingly important.

Consider:

Website displays privacy notice

↓

User clicks "Reject"

↓

Tracking cookie appears

↓

User navigates website

↓

Server records activity

The clickstream may be used to reconstruct whether the company respected or ignored the user's selection.

Similarly, in contractual disputes:

Terms displayed

↓

User clicks "I Agree"

↓

Timestamp recorded

↓

Account created

↓

Transaction occurs

The clickstream may help establish assent.

22. Clickstream Evidence in Class Actions

Clickstream evidence can become especially powerful in class action-type claims.

Suppose 500,000 consumers used the same website.

The database may show:

• identical interface;
• identical consent mechanism;
• identical tracking process;
• identical transaction structure.

Plaintiffs may argue that the common digital architecture demonstrates commonality.

For example:

"Every consumer was presented with the same allegedly deceptive interface."

Clickstream data can therefore support:

• commonality;
• predominance;
• damages calculations;
• identification of class members.

But individualized user behavior may also undermine class certification.

23. Clickstream Evidence and Expert Testimony

Complex clickstream evidence may require an expert.

An expert may explain:

• database architecture;
• logging system;
• timestamp methodology;
• session identification;
• cookie generation;
• data extraction;
• data cleaning;
• statistical analysis;
• attribution methodology;
• anomaly detection.

The opposing party can challenge:

• methodology;
• completeness;
• reliability;
• assumptions;
• statistical validity;
• data integrity.

24. Clickstream Evidence and Hearsay

Electronic records can raise hearsay questions, but the analysis depends upon what exactly the record contains.

A purely automated system-generated entry may be analyzed differently from a human-entered statement.

For example:

Server automatically recorded "User clicked button X at 14:03:22."

is different from:

Employee manually entered "Customer clicked button X."

The latter involves human assertion and potentially different evidentiary considerations.

25. Business Records and Clickstream Data

Clickstream logs maintained routinely as part of a company's business may potentially benefit from applicable business-record principles, but the electronic-record requirements still need careful consideration.

A company should ideally maintain documentation showing:

• how logs are automatically generated;
• system architecture;
• regularity of recording;
• retention procedures;
• access controls;
• alteration controls;
• extraction procedures.

This helps establish reliability.

26. Discovery of Clickstream Evidence

In civil litigation, parties may seek:

• raw server logs;
• database exports;
• analytics reports;
• event logs;
• cookie records;
• session data;
• API logs;
• authentication logs;
• metadata;
• source code governing tracking;
• data dictionaries.

A party should distinguish between:

Raw data

Original underlying records.

Processed data

Data cleaned or transformed.

Analytical output

Charts, summaries and reports generated from the data.

The closer the evidence is to the underlying source, the easier it may be to investigate questions of completeness and manipulation.

27. Common Defences Against Clickstream Claims

A defendant may argue:

1. The data is unauthenticated

There is no adequate evidence of origin.

2. The data is incomplete

Relevant sessions or logs are missing.

3. The records were altered

The extraction process changed the underlying information.

4. The click cannot be attributed to the plaintiff

The account/device/IP was shared.

5. The timestamps are unreliable

Different systems used different time zones or clock settings.

6. Automated activity generated the clicks

The activity may have come from bots.

7. The record is inadmissible

The statutory requirements for electronic evidence were not satisfied.

8. The data does not prove causation

A click does not necessarily prove that the user relied upon the website.

9. The data does not establish consent

Visiting a page is not necessarily agreement.

10. The evidence is statistically unreliable

The methodology may not support the conclusion being asserted.

28. Plaintiff's Best Strategy

A plaintiff relying upon clickstream evidence should ideally establish:

1. Source
2. Collection methodology
3. System architecture
4. Integrity
5. Chain of custody
6. Authentication
7. Statutory certificate
8. Hash verification
9. Expert explanation where necessary
10. Connection between digital event and legal injury

The evidence should tell a coherent story:

What happened → when it happened → how the system recorded it → how the record was preserved → why the record is authentic → what legal proposition it proves.

29. Defendant's Best Strategy

The defence should test:

Authenticity

→ Who generated it?

Completeness

→ Are all relevant logs present?

Integrity

→ Can the dataset be altered?

Attribution

→ Does the record identify the actual person?

Methodology

→ How was it extracted?

Reliability

→ Was the system functioning properly?

Interpretation

→ Does a click really prove consent, reliance or causation?

Legal admissibility

→ Has the applicable statutory procedure been satisfied?

30. Clickstream Evidence — A Practical Example

Suppose an online lender claims:

"The borrower accepted our arbitration agreement."

The lender produces:

• website terms;
• clickstream log;
• IP address;
• account number;
• timestamp;
• device information;
• database record.

The borrower responds:

"I never accepted the arbitration clause."

The court may examine:

Step 1

Were the terms actually displayed?

Step 2

Was an affirmative click required?

Step 3

Does the clickstream show the affirmative action?

Step 4

Can the account be connected to the borrower?

Step 5

Can the device be connected to the borrower?

Step 6

Is the electronic record authentic?

Step 7

Was it preserved without alteration?

Step 8

Has the applicable electronic-evidence certificate been supplied?

Step 9

Does the interface itself demonstrate legally sufficient notice and assent?

Thus, clickstream evidence may be highly relevant but is only one component of the overall proof.

31. Six Core Cases — Quick Revision Table

32. Present Legal Position in India

The historical cases above were decided under the Indian Evidence Act, 1872, particularly Section 65-B.

The current statutory framework is the Bharatiya Sakshya Adhiniyam, 2023, particularly:

• Section 61 — electronic or digital record;
• Section 62 — special provisions relating to electronic records;
• Section 63 — admissibility of electronic records. 

Section 63 specifically accommodates records generated or processed through computer systems, networks, computer resources and intermediaries, making it particularly relevant to modern clickstream evidence that may be stored across distributed cloud or platform infrastructure.

The statutory Schedule also contemplates identifying the digital source and recording technical information such as device details and hash values.

33. Important Distinction: Relevance ≠ Admissibility ≠ Weight

This is perhaps the most important conceptual distinction.

Relevance

Does the clickstream relate to a fact in issue?

Admissibility

Can the court legally receive it as evidence?

Weight

After admitting it, how persuasive is it?

For example:

A server log may be highly relevant.

But if its legal proof requirements are not satisfied, there may be an admissibility problem.

Even after admission, the opposing party may show:

The IP address was shared.

That may reduce its probative weight.

34. Conclusion

Clickstream evidence claims concern the use of digital interaction records to establish facts concerning online conduct, contractual assent, consumer behavior, privacy, advertising, cybersecurity, transactions and other digital disputes.

The principal evidentiary issues are:

Relevance → Authenticity → Integrity → Attribution → Completeness → Certification → Reliability → Probative value.

The most important Indian authorities are Anvar P.V. v. P.K. Basheer, Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal, Sonu @ Amar v. State of Haryana, Navjot Sandhu, Tomaso Bruno, and Shafhi Mohammad, with the important qualification that Arjun Panditrao is the controlling later authority that rejected the contrary approaches in Shafhi Mohammad and clarified the law after Anvar.

For modern litigation, the analysis should additionally be read against the Bharatiya Sakshya Adhiniyam, 2023, particularly Sections 61–63.

In short:

Clickstream data can provide a powerful digital reconstruction of what happened online, but the existence of a digital record does not by itself prove who performed the act, that the record is complete or unaltered, or that the record is legally admissible. Proper authentication, preservation, statutory compliance and contextual interpretation are therefore central to a successful clickstream evidence claim.