Privacy Policy

2.1 Personal Information

• Email Address: For authentication, notifications, and account management
• GitHub Profile: Username, avatar, and basic profile information
• Account Preferences: Notification settings and monitoring preferences
• Notification Integrations: If you connect one, the Slack or Discord webhook URL you provide, or the Telegram chat ID and username of the chat you link. Used only to deliver your release notifications and deleted when you disconnect the integration.

2.2 Google Account Data

When you sign in with Google, we access the following data from your Google account via OAuth 2.0:

• Email Address: Your Google account email, used for authentication and sending release notifications
• Display Name: Your Google profile name, used to personalize your account
• Profile Picture: Your Google avatar, displayed in the application interface

We request only the minimum OAuth scopes necessary: email and profile. We do not request access to your Google Drive, Gmail, Calendar, or any other Google services.

2.3 GitHub Repository Data

• Repository Names: Only repositories you explicitly choose to monitor
• Release Information: Version numbers, release notes, and publication dates
• Monitoring Status: Active/inactive status and last check timestamps

2.4 Anonymous Usage Analytics

We use Vercel Web Analytics to understand aggregate site usage (page views, referrers, country-level location, device type). This is a privacy-friendly, cookieless analytics service:

• No cookies or persistent identifiers are stored on your device
• Visitors are counted via an anonymized hash that is discarded within 24 hours — no cross-site or cross-day tracking is possible
• Your IP address is processed transiently to generate the hash but is never stored
• Only aggregated, anonymous statistics are retained

We process this data on the basis of our legitimate interest (Art. 6(1)(f) GDPR) in understanding and improving our service. Because no personal data is stored and no tracking technology is placed on your device, this processing does not require your prior consent.

4.1 Security Measures

• HTTPS encryption for all data transmission
• Secure authentication via GitHub and Google OAuth 2.0
• Row-level security policies on database
• Encrypted database storage

4.2 Data Storage

• Data stored in secure, encrypted databases (Supabase)
• Automated backups
• GDPR-compliant data handling practices
• Data may be processed in the United States or European Union

6.1 Data Access and Control

• Access: Request access to your personal data
• Rectification: Request correction of inaccurate data
• Erasure: Request deletion of your personal data
• Portability: Request transfer of your data
• Objection: Object to processing of your data

6.2 Account Management

• View and edit your profile information
• Manage notification preferences
• Control repository monitoring settings
• Export your data in JSON format
• Delete your account and all associated data

7.1 Your California Rights

• Right to Know: Request information about personal data we collect, use, and share
• Right to Delete: Request deletion of your personal information
• Right to Correct: Request correction of inaccurate personal information
• Right to Opt-Out: Opt out of the sale or sharing of your personal information
• Right to Non-Discrimination: Not be discriminated against for exercising your rights

7.2 We Do Not Sell Your Data

GitWatchman does not sell your personal information to third parties. We do not share your personal information for cross-context behavioral advertising.

7.3 Categories of Personal Information

In the past 12 months, we may have collected the following categories of personal information:

• Identifiers (email address, GitHub username)
• Internet activity (repositories monitored, login history)
• Geolocation data (approximate, based on IP address)

7.4 How to Exercise Your Rights

To exercise any of these rights, please contact us at contact@gitwatchman.com or through our contact page. We will respond to verifiable requests within 45 days.

10.1 Data We Access from Google

We access your Google account email address, display name, and profile picture solely for the purpose of authenticating your identity and creating your GitWatchman account.

10.2 How We Use Google Data

• To authenticate and identify you within the application
• To send you email notifications about monitored repository releases
• To display your name and profile picture in the application interface

10.3 Storage and Retention of Google Data

Your Google account data is stored securely in our encrypted database (Supabase) and retained only while your account is active. When you delete your account, all associated Google data is permanently removed.

10.4 Sharing of Google Data

We do not sell, share, or transfer your Google user data to any third party, except as strictly necessary for service operation (e.g., Supabase for authentication processing). We do not use Google user data for advertising, analytics profiling, or any purpose unrelated to providing the GitWatchman service.

10.5 Limited Use Disclosure

GitWatchman limits its use of Google user data to the practices explicitly disclosed in this Privacy Policy. Our use of Google user data is limited to providing and improving the core functionality of the GitWatchman service. We do not allow humans to read your Google user data unless required for security purposes, to comply with applicable law, or with your affirmative consent.