1. Scope
This policy describes how RepoLore processes information when it provides read-only analysis of public GitHub repository history. It applies to the RepoLore website and the RepoLore plugin experience.
2. Information processed
RepoLore may process a public GitHub repository URL and identifier; a file path and selected line range; commit SHA; Pull Request or Issue number; a repository-history search query; and public information returned by the GitHub API. The hosting layer may also produce minimal operational and security metadata.
3. Why we process it
We use this information to provide code-history analysis, retrieve public GitHub evidence, protect availability, and diagnose failures.
4. Recipients and processors
Information may be processed by the GitHub API, the hosting provider, and OpenAI/ChatGPT as the environment through which the plugin is invoked. Their processing may be governed by their own terms and privacy notices.
5. Retention
Application results may be cached in memory for up to 60 seconds. RepoLore does not intentionally persist repository content or tool inputs in an application database. Operational and security logs may be retained for up to 30 days and then deleted or aggregated.
6. No sale, advertising, or profiling
RepoLore does not sell personal information, use it for advertising, or use it for profiling. The initial website version uses no cookies or analytics.
7. Security
Reasonable administrative and technical measures are used to protect information appropriate to the service. No method of transmission or processing can be guaranteed completely secure.
8. Your choices and requests
For privacy questions or requests, contact [email protected]. Please avoid sending passwords, access tokens, or other secrets.
9. International processing
Infrastructure providers may process information in locations where they operate. Those locations may differ from your own.
10. Children's privacy
RepoLore is not directed to children, and we do not knowingly seek to collect personal information from children.
11. Policy updates
We may update this policy as the service changes. The effective date and last-updated date above will reflect the current version.
12. Contact
Dmitrii Sergeev
[email protected]