Privacy Policy

1.1 GitHub Profile Information

When you authenticate using GitHub OAuth, we receive the following information from GitHub:

• Your GitHub username
• Your GitHub profile avatar (profile picture)
• Your GitHub user ID
• An OAuth access token granting us permission to act on your behalf

We only request the minimum permissions necessary to provide the service, specifically the ability to read your public profile for authentication and to sync settings via cloud storage.

1.2 Repository Tracking Preferences

We store your application preferences, which include:

• List of GitHub repositories you choose to track
• Label filter preferences for issue discovery
• Notification frequency settings
• Display preferences (language, theme)
• Options to hide closed issues

This data is stored in your browser's localStorage. If you are logged in with GitHub, your preferences are automatically synced to a secure cloud database tied to your account.

1.3 Usage Data and Analytics

We may collect anonymized usage data to improve our service, including:

• Pages visited and features used
• Browser type and version
• Operating system
• Referring URLs
• General geographic location (country/region level)

2.1 Service Provision

We use your information primarily to provide and improve the service:

• Displaying GitHub issues from your tracked repositories
• Filtering issues based on your label preferences
• Sending browser notifications for new issues (with your permission)
• Authenticating your identity to enable personalized features

2.2 Cross-Device Synchronization

When you sign in, your settings are automatically synced to a secure cloud database. This allows your preferences to be available across multiple devices. The data is tied to your authenticated account and accessible only by you.

2.3 Service Improvement

Aggregated, anonymized usage data helps us understand how the service is used so we can improve features, fix bugs, and enhance user experience.

3.1 Client-Side Storage (Your Browser)

The following data is stored exclusively in your browser's localStorage:

• GitHub OAuth access token
• GitHub user profile information (username, avatar URL)
• Application settings and preferences
• Tracked repository list

This data is stored only on your device and is never transmitted to our servers except when syncing via cloud storage.

3.2 Server-Side Storage

We do not maintain a server-side database of user data. Our servers (hosted on Vercel) process requests but do not persistently store personal information. The only server-side operation involving your data is the GitHub OAuth token exchange, which is processed in real time and not stored.

3.3 Cloud Sync

If you are signed in, your preferences are stored in a secure cloud database associated with your account. This data is:

• Not publicly accessible
• Tied to your authenticated account
• Deletable upon request through our GitHub Issues page

4.1 Data Stored by the Extension

The extension stores the following data on your device:

• GitHub API Token — stored in chrome.storage.local on your device only
• Settings & Preferences — stored in chrome.storage.sync and synced across your Google account-linked Chrome instances
• Issue Cache — stored in chrome.storage.local to reduce redundant GitHub API calls

4.2 Cross-Device Settings Sync

Extension settings (tracked repositories, label filters, notification preferences) are stored using chrome.storage.sync. Chrome automatically synchronizes this data across devices where you are signed in to the same Google account. This sync is handled entirely by Google Chrome and is subject to Google's Privacy Policy.

4.3 GitHub API Calls

All GitHub API requests made by the extension use only the API token you provide directly. The extension calls the GitHub API on your behalf to fetch repository and issue data. No requests pass through our servers — all API calls are made directly from your browser to api.github.com.

4.4 No External Data Transmission

The extension does not send any data to our servers or any third-party services other than GitHub (via direct API calls). Your GitHub token, repository list, and issue cache remain on your device.

4.5 Deleting Extension Data

You can remove all data stored by the extension at any time:

• Uninstalling the extension automatically clears all locally stored data
• You can clear individual data items through the extension's Settings panel
• Chrome's "Clear browsing data" settings can also remove extension storage

6.1 localStorage (Not Cookies)

We use browser localStorage (not traditional cookies) to store your settings and authentication token locally. localStorage data does not expire automatically and is not transmitted to servers with each request. You can clear this data at any time by clearing your browser's local storage or using our built-in "Clear All Data" feature in the settings.

6.2 Advertising Cookies

Google AdSense sets cookies to serve personalized advertisements. These cookies allow Google and its partners to:

• Remember your past visits to our site and other sites
• Show you ads relevant to your interests
• Measure the effectiveness of advertising campaigns

6.3 Opting Out of Ad Personalization

You can opt out of personalized advertising in several ways:

• Visit Google Ad Settings
• Use the Network Advertising Initiative opt-out page
• Configure your browser to block third-party cookies
• Use browser extensions that block advertising trackers

8.1 Delete Local Data

You can delete all locally stored data at any time by:

• Using the "Clear All Data" button available in the Settings panel of the application
• Clearing your browser's localStorage through browser developer tools
• Clearing all site data through your browser's privacy/security settings

8.2 Revoke GitHub OAuth Access

You can revoke our application's access to your GitHub account at any time by visiting your GitHub OAuth Application Settings and revoking access for "Pickssue". After revocation, you will be logged out and no further API calls will be made on your behalf.

8.3 Delete Synced Settings

Your settings are stored in a secure cloud database tied to your account. When you log out, your local data is cleared. To request deletion of your cloud-stored settings, please contact us through our GitHub Issues page.

8.4 Data Portability

Since your settings are stored in your own browser and optionally in cloud storage, you already have full access to and ownership of your data. You can view, export, or delete it directly without needing to request it from us.