Privacy Policy

1. Information We Access

Visibility accesses the following data solely to power the features you see on screen:

• Location — Your approximate geographic coordinates (latitude and longitude) are requested to fetch local weather and air quality conditions. Coordinates are sent directly to Open-Meteo and are never stored by Visibility or transmitted to any other party.
• GitHub account & activity — If you choose to sign in with GitHub, Visibility reads your public profile (name, avatar, username) and open pull requests and issues authored by you. This data is fetched from the GitHub API using the OAuth access token you grant. The token and a short-lived cache of your activity are stored locally in chrome.storage.local on your device only.
• Bookmarks — Visibility reads your Chrome bookmark tree to display shortcuts on the dashboard. Bookmark data is read locally and is never transmitted off your device.
• Frequently visited sites — The Chrome topSites API provides a list of your most visited URLs to display as quick-access links. This data is read locally and is never transmitted off your device.
• Scratchpad notes — Any text you type in the scratchpad is saved to chrome.storage.local on your device and is never transmitted anywhere.
• Favicons — Site icons are fetched from Google's publicly accessible favicon service (www.google.com/s2/favicons). Only the domain name of each site is included in these requests.

2. How Information Is Used

All data accessed by Visibility is used exclusively to render your personal dashboard. Specifically:

• Location data is used to display weather and air quality conditions for your area.
• GitHub data is used to display your open pull requests, issues, and recently active repositories.
• Bookmark and top-site data are used to display navigation shortcuts.
• Scratchpad content is saved so your notes persist across browser sessions.

No data is used for advertising, analytics, profiling, or any purpose other than rendering your dashboard.

3. Data Storage

All data processed by Visibility is stored locally in chrome.storage.local on your device. This includes your GitHub OAuth token, cached pull request and repository data, weather cache, and scratchpad content. None of this data is sent to any server operated by the extension author.

Cached data (weather, GitHub activity) is automatically refreshed at regular intervals and expires after a short period. You can clear all stored data at any time by signing out of GitHub (which removes your token and activity cache) or by removing the extension.

4. Third-Party Services

Visibility communicates with the following third-party services as part of its core functionality:

• Open-Meteo (terms) — Used to fetch weather forecasts and air quality data. Your coordinates are sent as query parameters.
• GitHub API (privacy policy) — Used to retrieve profile information, pull requests, issues, and repositories for signed-in users.
• Google Favicon Service — Used to load site icons for bookmarks and frequently visited sites. Only domain names are transmitted.

No data is shared with any other third parties. The extension does not include any advertising networks, analytics SDKs, or tracking scripts.

5. Permissions

The extension requests the following Chrome permissions and uses each as described:

• geolocation — To fetch local weather conditions.
• storage — To persist settings, cache, and scratchpad data locally.
• identity — To launch the GitHub OAuth sign-in flow.
• bookmarks — To read your bookmark folders and items for display.
• topSites — To read your frequently visited sites for display.
• favicon — To access cached favicon data for local URLs.

6. Children's Privacy

Visibility is not directed at children under the age of 13 and does not knowingly collect personal information from children.

7. Changes to This Policy

If this privacy policy is updated, the “Last updated” date at the top of this page will reflect the revision date. Continued use of the extension after changes constitutes acceptance of the updated policy.

8. Contact

If you have questions or concerns about this privacy policy, please open an issue on the project's GitHub repository.