gistfile1.txt

# Privacy Policy for Lionstone Chrome Extension

**Last Updated:** January 13, 2026

## Overview
This privacy policy describes how the Lionstone Chrome Extension ("the Extension") collects, uses, and protects your information.

## Information We Collect
The Extension collects and processes the following types of information:

### Authentication Data
- User authentication tokens stored locally in Chrome's sync storage
- These tokens are used to authenticate API requests to our services

### User Input Data
- Serial numbers of units


## How We Use Your Information
The information collected is used to:
- Authenticate your requests to  API services
- Search and retrieve project and unit information
- Display unit details, secret keys, and management information
- Provide quick navigation links to our services

## Data Storage
- Authentication tokens are stored locally using Chrome's storage API
- No data is stored on external servers by the Extension itself
- All data is transmitted securely to  API endpoints via HTTPS

## Data Sharing
- The Extension does not share your data with any third parties
- Data is only transmitted to API services for authentication and retrieving your project information
- No analytics or tracking services are used

## Data Security
- All API communications are conducted over HTTPS
- Authentication tokens are stored securely using Chrome's storage API
- The Extension only accesses data you are authorized to view based on your authentication token

## Your Rights
You have the right to:
- Remove the Extension at any time, which will delete locally stored data
- Clear your authentication token from Chrome storage
- Request information about your data from our

services



These services have their own privacy policies and terms of service.

## Changes to This Policy
We may update this privacy policy from time to time. The "Last Updated" date at the top of this policy indicates when it was last revised.

## Contact
For questions or concerns about this privacy policy, please contact the extension developer through the Chrome Web Store support channel.

## Permissions Explanation
The Extension requires the following permissions:
- **storage**: To securely store your authentication token locally
- **host permissions**: To communicate with API endpoints for retrieving your project data