GitHub-Freshness

GitHub Freshness Privacy Policy

Last updated: July 15, 2026

简体中文

GitHub Freshness includes an open-source userscript for GitHub pages and a separately distributed browser extension. It reads repository and file update times visible on the GitHub page the user is currently viewing, then uses color highlighting, date formatting, file sorting, and related features to help users evaluate repository activity. The browser extension source code is not included in the public repository.

We value user privacy. GitHub Freshness does not operate a user account system, display advertising, track user behavior, or sell, rent, or share user data for advertising, profiling, or marketing purposes.

Scope

This Privacy Policy applies to:

• the GitHub Freshness userscript;
• the GitHub Freshness browser extension;
• the userscript and project documentation published in the public project repository.

This Privacy Policy does not apply to GitHub, Tampermonkey, Greasy Fork, the Chrome Web Store, CDN providers, or other third-party websites or services. When users visit these services, the privacy policy of the corresponding third party applies.

Data We Process

The primary GitHub Freshness logic runs locally in the user’s browser. To provide its features, the project may process the following data locally:

1. Information visible to the user on the current GitHub page

   This may include repository links, repository names, displayed repository update times, file update times, and update times shown in search results. This information comes from GitHub pages the user is visiting and is authorized to view. It may relate to public repositories or private repositories the user has permission to access. It is used only to highlight, sort, and format content on the current page.

2. User settings

   Settings selected or entered in the settings panel may include:

   • the light, dark, or automatic theme mode;
   • the freshness period, such as a number of days, weeks, months, or years;
   • background colors, text colors, file icon colors, and their enabled states;
   • the date-formatting option and date format;
   • the file-sorting option and sort direction;
   • the Awesome project detection option;
   • the current theme and interface language;
   • settings JSON files the user explicitly imports or exports.

   These settings control how GitHub Freshness appears and behaves on GitHub pages.

3. Optional GitHub token

   When the user manually enables Awesome project detection and enters a GitHub token, GitHub Freshness uses that token to request public repository metadata from the GitHub API and reduce the effect of GitHub API rate limits.

   A GitHub token is optional. Users may leave the field empty or remove the token from the settings panel at any time. The token is stored in the userscript or browser extension settings storage. The browser extension uses chrome.storage.sync, so the browser provider may synchronize the token through the user’s own browser account. Exported settings JSON files never include the saved token.

4. Temporary page state

   GitHub Freshness may use sessionStorage markers to prevent the same informational message from appearing repeatedly on one page. This state is used only for interface control during the current browser session.

How Data Is Stored

GitHub Freshness does not upload user settings to a server operated by the project author.

• The userscript stores settings and the optional GitHub token with GM_setValue and GM_getValue.
• The browser extension stores settings and the optional GitHub token with chrome.storage.sync.
• A small amount of temporary state may be stored in browser sessionStorage.

When browser synchronization is enabled, the browser provider may synchronize settings and the optional GitHub token stored in chrome.storage.sync through the user’s browser account. This synchronization is provided and controlled by the browser provider, not by a server operated by GitHub Freshness. Users should also review the privacy policy of their browser and account synchronization service.

The settings import and export feature is only for user-managed backup and recovery. Exported files are generated by the user’s browser and saved to the user’s device. When a user imports a JSON file, its contents are written to the local project settings storage.

Network Requests and Third-Party Services

GitHub Freshness may make the following network requests:

1. GitHub page access

   When the user visits GitHub, the userscript or extension runs on https://github.com/* pages to read content currently visible to the user and adjust its presentation.

2. GitHub API requests

   When Awesome project detection is enabled, GitHub Freshness may request:

   https://api.github.com/repos/{owner}/{repo}

   This request retrieves repository metadata. If the user has entered a GitHub token, the request includes the token in the Authorization header. The token is sent to GitHub and is not sent to a server operated by the GitHub Freshness author.

3. Third-party dependencies used by the userscript

   The userscript may load runtime dependencies through @require or @resource from third-party CDNs. These dependencies may include jQuery, SweetAlert2, Pickr, Luxon, and related style resources. The browser extension includes these dependencies in its distributed package.

4. Project-related links

   The settings panel and documentation may contain links to the GitHub repository, project documentation, the author’s homepage, GitHub token settings, and the Telegram community. These websites open only after the user actively clicks the corresponding link.

What We Do Not Do

GitHub Freshness does not:

• collect identity information such as names, email addresses, telephone numbers, or physical addresses;
• collect or analyze browsing history for advertising, profiling, or marketing;
• upload user settings, GitHub tokens, or GitHub page contents to a server operated by the project author;
• sell, rent, or transfer user data;
• include hidden, obfuscated, or encrypted tracking logic.

Permission Usage

The browser extension requests the following primary permissions:

• activeTab: used to open the settings panel in the current GitHub tab after the user clicks the extension icon;
• storage: used to save user settings;
• https://github.com/*: used to read visible GitHub page information and adjust page presentation;
• https://api.github.com/*: used to request GitHub repository metadata when Awesome project detection is enabled.

These permissions are used only for core GitHub Freshness features.

GitHub Token Security Recommendations

Users who choose to enter a GitHub token should:

• prefer a GitHub fine-grained personal access token;
• grant only the minimum permissions required to read public repository metadata;
• set an appropriate expiration date;
• never share the token with other people;
• immediately revoke the token in GitHub settings if they suspect it has been exposed.

Data Deletion

Users may delete data stored by GitHub Freshness by:

• clearing the GitHub token in the settings panel and saving the settings;
• resetting or changing settings in the settings panel;
• deleting settings JSON files they exported;
• deleting the userscript storage through the userscript manager;
• clearing extension data or uninstalling the extension through the browser extension manager.

After the userscript or extension is uninstalled, the browser or userscript manager will generally remove the corresponding data stored on the device. Data synchronized through chrome.storage.sync may be affected by the retention behavior of the user’s browser account and synchronization service. The rules of the browser, userscript manager, and account synchronization service apply.

Children’s Privacy

GitHub Freshness is intended for developers and GitHub users and is not specifically directed to children. We do not knowingly collect personal information from children.

Policy Changes

If the way GitHub Freshness processes data changes materially, this file will be updated and the latest version will be maintained in the project repository. Users should review this Privacy Policy when installing or updating the userscript or extension.

Contact

For questions about this Privacy Policy or how GitHub Freshness processes data, contact us through GitHub Issues:

https://github.com/rational-stars/GitHub-Freshness/issues

You may also join the Telegram community:

https://t.me/GitHubFreshness

Limited Use Statement

GitHub Freshness uses user data only to provide the project’s core features and complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. We do not use user data for purposes unrelated to core features, sell or transfer user data to third parties, or use user data for advertising, credit assessment, or user profiling.

This site is open source. Improve this page.