Privacy Policy

Data access

The extension may read repository metadata, directory entries, repository HTML, and the current repository route from an authorized Gitea instance. This access is used only to render and synchronize the file tree.

Existing-session requests run only in the matching Gitea tab. Chrome may include that site's session cookies in same-origin requests, but the extension does not read, copy, store, or export cookie values.

Local storage

The extension stores the following information in chrome.storage.local:

• Configured Gitea instance URLs and enabled state.
• An optional user-provided read-only token for each HTTPS instance.
• Sidebar size, collapsed state, expanded paths, and repository UI state.
• Directory cache entries used to improve navigation performance.
• Anonymous diagnostic counters, the latest error category, and update time.

Chrome local extension storage is not an encrypted credential vault. Use a minimum-scope read-only token and remove it when it is no longer needed. Tokens cannot be saved or sent for HTTP instances; legacy HTTP token records are deleted when read.

Data collection and sharing

Gitea Code Tree has no developer-operated backend, remote analytics, advertising system, or third-party telemetry. It does not upload repository code, filenames, paths, repository identifiers, private domains, cookies, tokens, or browsing history to the developer.

Data is not sold, rented, used for advertising, or shared with third parties. Diagnostic export is initiated by you and contains only the local diagnostic summary described above.

Permissions

The fixed storage permission saves local configuration and state. The fixed scripting permission registers the file-tree interface and enables same-origin page-session requests.

HTTP and HTTPS host access is optional. Chrome requests permission only after you add an instance. Access is restricted to enabled, authorized Gitea origins and their configured subpaths.

Security

Network requests go directly between your browser and the Gitea instance you specify. Gitea Code Tree does not proxy this traffic through a developer-operated service.

Use HTTPS for private repositories and authentication. Do not configure a token for an HTTP endpoint because HTTP does not protect credentials or repository data in transit.

Your controls and data deletion

You can manage stored data from the extension's Options page:

• Remove a token without deleting the instance.
• Disable an instance to stop future page injection.
• Delete an instance and its related token, cache, and repository state.
• Clear all configured instances, tokens, preferences, caches, and diagnostics.

Revoking Chrome site access unregisters the affected content script and removes an active sidebar. Uninstalling the extension removes its extension-local Chrome storage according to Chrome's platform behavior.

Chrome Web Store Limited Use

Gitea Code Tree's use of information received through Chrome extension permissions complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Permission-derived data is used only to provide or improve the extension's user-facing repository navigation features. It is not used for advertising, credit assessment, lending, or any unrelated purpose.

Policy changes

Material changes to this policy will be published on this page and reflected by the last-updated date. Extension behavior and Chrome Web Store disclosures must remain consistent with this policy.

Contact

For privacy questions or deletion assistance, email aqqzdsthl@gmail.com. You can also use the project's GitHub issue tracker for non-sensitive support requests. Do not include tokens, cookies, private repository names, code, or other sensitive information in a public issue.