> 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/privacy-by-design-in-lifi.md). # Privacy by Design in LiFi Privacy in LiFi isn’t a secondary feature. It is a foundational design principle that shapes every part of the extension — from how data is collected, to where it’s stored, to how you interact with it. This page explains how LiFi protects your privacy through thoughtful architecture, local-first data handling, and full transparency. ### Local-Only Data Storage LiFi stores **100% of user data locally** using Chrome's built-in **Storage API**. This means: * **No third-party servers** receive your data * **No external sync** unless you explicitly export it yourself * **No cloud dependence** for analytics or tracking All browsing activity, interaction records, and AI-generated summaries are stored within the browser’s secure local storage. You can view, export, or delete this data at any time from the dashboard. #### Why this matters: | Benefit | Explanation | | -------------------- | ------------------------------------------------------------- | | Data stays on device | No risk of data leaks or breaches from cloud infrastructure | | No account required | Users don’t need to log in or create profiles | | Works offline | Analytics features continue functioning even without internet | *** ### User Consent for External Actions LiFi integrates with AI models (e.g., Google Gemini) to provide intelligent summaries. However: * **No data is ever sent without your explicit permission** * You must **manually trigger** AI-powered insights * Prompts are generated locally, and only relevant summary data is transmitted This opt-in model ensures that you remain fully in control over when — and if — your data leaves your browser. *** ### No Sensitive Personal Data Collection LiFi does **not** collect any of the following: * Passwords * Payment information * Personally Identifiable Information (PII) such as names, emails, phone numbers By design, the extension avoids input fields where sensitive data is typically entered. Additionally, smart filters are used to ignore common sensitive form fields. *** ### Sandboxing and Security Architecture LiFi uses **content script sandboxing** to ensure that data collection is safe and isolated. Each content script runs in a separate execution environment that: * Cannot modify webpage behavior * Cannot read or interfere with other scripts on the page * Only extracts high-level behavioral data (like page titles, interaction events) Combined with Chrome’s **Content Security Policy (CSP)**, this architecture prevents malicious access and enforces strict boundaries between LiFi and the websites you visit. *** ### Privacy Scoring and Cookie Detection LiFi actively monitors cookies from all visited sites to help you stay aware of invisible tracking mechanisms. | Feature | Function | | ---------------------------- | ---------------------------------------------------------- | | Cookie change tracking | Detects when new cookies are added or old ones are removed | | Third-party cookie detection | Highlights cookies that originate from non-visited domains | | Cookie metadata analysis | Flags insecure or privacy-invasive cookie configurations | | Privacy scoring engine | Assigns a privacy score to each session or domain | This gives users the tools to understand how websites handle their privacy — even if the site itself doesn’t explain it. *** ### Compliance-Ready Privacy Controls LiFi includes features that align with modern privacy regulations (like GDPR and CCPA), including: | Control Feature | User Right Supported | | ---------------------- | ------------------------------ | | Full Data Export | Right to access | | Complete Data Deletion | Right to be forgotten | | Manual Tracking Toggle | Right to opt out of processing | | Transparent Logs | Right to be informed | There is no hidden data collection and no hidden logs. Users can audit their own data at any time via the dashboard or exported JSON files. ### Summary LiFi demonstrates that powerful analytics can coexist with complete user privacy. Its privacy-first design ensures: * You never lose control over your data * You can see exactly what’s being tracked — and why * You can enjoy AI-powered insights without sacrificing security Privacy isn’t a feature in LiFi. It’s the foundation of the entire system. --- # 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/privacy-by-design-in-lifi.md?ask=&goal= ``` `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.