Privacy at SourceBrief

SourceBrief is designed as a simple public-repo utility. The core tool does not require an account, private GitHub access, cookies, analytics, or localStorage.

Last updated: 4 September 2026

Information you enter

When you enter a public GitHub repository URL or owner/repo name, that value is used in your browser to request public information from GitHub. Do not enter private repository names, tokens, passwords, secrets, or confidential business information.

Public GitHub data

SourceBrief reads publicly available GitHub repository data such as repository metadata, README content, directory signals, language data, topics, and related repository search results. This data is provided by GitHub’s public interfaces and may be rate-limited, stale, incomplete, or unavailable.

Accounts and private repositories

SourceBrief does not ask you to sign in and does not request access to your private GitHub repositories. The current utility is intended for public repositories only.

Cookies, analytics, and storage

The core SourceBrief utility does not require cookies, analytics scripts, or localStorage. If that changes, this policy should be updated before those features are activated.

Feedback

If you use the feedback feature, SourceBrief prepares text for a public GitHub issue in the SourceBrief project repository. Submitting that issue is your choice. Anything you post to GitHub may be public and handled under GitHub’s own terms and privacy policy.

Advertising

SourceBrief currently includes inactive ad placeholder zones only. No live Google AdSense code, publisher credentials, or ad requests are present. If ads are activated later, third-party advertising partners may use cookies or similar technologies, and this policy should be updated to explain that clearly.

Contact

For privacy questions or content concerns, use the contact page. Please do not include secrets, credentials, private repo details, or confidential data in public issue reports.