> For the complete documentation index, see [llms.txt](https://lifi-chrome-tracker.gitbook.io/lifi-chrome-tracker-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lifi-chrome-tracker.gitbook.io/lifi-chrome-tracker-docs/overview/inside-lifis-architecture/understanding-the-tracking-system.md).

# Understanding the Tracking System

LiFi tracks a wide range of browsing behaviors directly within your browser, without sending any data elsewhere. This local-first model empowers you with rich insights into your digital activity, from how you spend your time to how websites interact with your privacy.

This page breaks down each tracking category, how it works, what it reveals, and why it matters.

### Navigation Tracking

#### What it Tracks

| Data Point      | Description                          |
| --------------- | ------------------------------------ |
| URL             | The address of the visited page      |
| Timestamp       | When the visit occurred              |
| Navigation Type | Load, reload, redirect, back/forward |

#### Use Cases and Benefits

* Understand which websites you visit most frequently
* Reconstruct your daily browsing flow
* Detect patterns like switching between work and distractions

### Time Tracking

#### What it Tracks

| Data Point        | Description                                    |
| ----------------- | ---------------------------------------------- |
| Time on Page      | Duration of activity per tab                   |
| Session Length    | Total time spent in a browser session          |
| Focus/Blur Events | Tracks when a tab or window is active/inactive |

#### Use Cases and Benefits

* Identify time-wasting sites vs productive usage
* Improve awareness of attention span and multitasking habits
* Build accurate session timelines

### Page Metadata Collection

#### What it Tracks

| Metadata       | Description                          |
| -------------- | ------------------------------------ |
| Page Title     | Name of the webpage                  |
| Referrer       | Previous page or source of the visit |
| Language       | Browser language setting             |
| Platform/Agent | Device and browser information       |
| Geolocation    | Optional city and country data       |

#### Use Cases and Benefits

* Understand where each session starts and how it flows
* See how different devices or platforms affect your habits
* Provide context to AI summaries and time analytics

### Search Query Tracking

#### What it Tracks

| Data Point    | Description                    |
| ------------- | ------------------------------ |
| Query Text    | Exact search input by the user |
| Search Engine | Google, Bing, DuckDuckGo, etc. |
| Timestamp     | When the search occurred       |
| Page Context  | Where the search was performed |

#### Use Cases and Benefits

* Analyze your most frequent searches over time
* Understand curiosity trends across platforms
* Track whether searches relate to productivity or leisure

### Interaction Tracking

#### What it Tracks

| Interaction Type  | Description                         |
| ----------------- | ----------------------------------- |
| Clicks            | Buttons, links, CTAs                |
| Hovers            | Elements the mouse rests over       |
| Scroll Milestones | 25%, 50%, 75%, 100% depth on a page |
| Forms             | Input focus and form submissions    |

#### Use Cases and Benefits

* Differentiate between passive browsing and active engagement
* Detect deep reading vs surface-level skimming
* Understand what grabs your attention on specific pages

***

### Cookie Tracking

#### What it Tracks

| Data Point      | Description                                  |
| --------------- | -------------------------------------------- |
| Cookie Events   | Set, update, or delete events per cookie     |
| Cookie Metadata | secure, httpOnly, sameSite, expiration flags |
| Domain Scope    | Tracks first-party vs third-party cookies    |
| Change Causes   | Why a cookie was changed or created          |

#### Use Cases and Benefits

* Reveal invisible trackers from ads or embedded scripts
* Spot domains that aggressively modify or inject cookies
* Improve your privacy awareness and scoring

### Quick Overview Table

| Tracking Area     | Reveals                                            | Main Benefit             |
| ----------------- | -------------------------------------------------- | ------------------------ |
| Navigation        | Which sites you visit and in what order            | Behavioral mapping       |
| Time              | How long you actually engage with each page        | Attention analysis       |
| Metadata          | Extra context for visits (titles, referrers, etc.) | Session clarity          |
| Search Queries    | What you look for across different engines         | Search behavior insights |
| Interactions      | What actions you take, not just pages you visit    | Engagement profiling     |
| Cookie Monitoring | Who is tracking you and how                        | Privacy risk awareness   |

### Final Thoughts

LiFi’s tracking system is built not to surveil you, but to **inform and empower you**. Each feature gives you a different lens to view your browsing — whether you're trying to cut distractions, understand your digital habits, or defend your privacy.

All data stays local. No account is required. No data is sent out.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://lifi-chrome-tracker.gitbook.io/lifi-chrome-tracker-docs/overview/inside-lifis-architecture/understanding-the-tracking-system.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
