GitRepoTrend ("we", "us", "our") operates gitrepotrend.com. This policy explains what data we collect, why we collect it, and how we protect it.
1. Data we collect
Email address — only if you voluntarily subscribe to our weekly newsletter. We verify your email with a one-time code before adding you to our list.
Usage analytics — we use Google Analytics (GA4) to collect anonymised page-view data (pages visited, time on page, device type). No personally identifiable information is collected through analytics.
Server logs — our Nginx server records standard access logs (IP address, user agent, requested URL, timestamp). Logs are retained for 30 days and used only for security and debugging.
2. How we use your data
Your email is used solely to send the weekly GitRepoTrend digest you subscribed to.
We never sell, rent, or share your email with third parties.
Analytics data is used in aggregate to understand which categories and features are most useful.
3. Cookies
We use the following cookies:
Google Analytics (_ga, _gid) — analytics cookies, set by Google. You can opt out via Google's opt-out tool.
Session storage (grt_v5) — stores repository data in your browser's sessionStorage (not a cookie) to avoid redundant API calls. No personal data. Cleared when you close your browser tab.
Local storage (grt_bk, grt_last_visit, grt_cookie_consent) — stores your saved bookmarks, last visit timestamp, and cookie consent preference locally in your browser. Never transmitted to our servers.
Analytics cookies (Google Analytics) are only set after you click "Accept" on our cookie consent banner. You can withdraw consent at any time by clearing your browser cookies.
Newsletter subscriber emails are retained until you unsubscribe.
Server access logs are retained for 30 days.
Analytics data is retained per Google Analytics default settings (14 months).
7. Security
We use HTTPS (TLS 1.2/1.3) for all connections. Email verification uses a time-limited one-time code. Subscriber data is stored in an encrypted PostgreSQL database. We follow industry-standard security practices.
8. Changes to this policy
We may update this policy occasionally. The "Last updated" date at the top will reflect any changes. Continued use of the site after changes constitutes acceptance.