1. What Are Cookies
Cookies are small text files stored on your device when you use GitBuster. They help us maintain your chat sessions, remember your repository analysis preferences, and provide a smooth experience while using our AI-powered GitHub repository visualization and chat platform.
2. How We Use Cookies
2.1 Essential Cookies
These cookies are necessary for our platform to function properly and provide core repository analysis features.
- Chat session management and conversation continuity
- Repository analysis state preservation
- User interface preferences and settings
- Security features and CSRF protection
- Rate limiting enforcement
2.2 Performance Cookies
These cookies help us optimize repository processing performance and understand how users interact with our visualization features.
- Repository analysis performance metrics
- SVG visualization rendering optimization
- Chat response time monitoring
- Error tracking for failed repository analyses
- Vector store performance analytics
2.3 Functionality Cookies
These cookies enhance your experience by remembering your preferences and maintaining context across sessions.
- Recently analyzed repository URLs
- Visualization preferences (zoom, filter settings)
- Chat history and conversation context
- Theme preferences (dark/light mode)
- Search query history within repositories
- File type visibility preferences in visualizations
2.4 AI and Analysis Cookies
Specific to our AI-powered features for repository analysis and chat functionality.
- Vector embedding cache for faster AI responses
- Repository analysis progress and state
- Chat model preferences and settings
- AI response optimization data
- Code analysis context preservation
3. Third-Party Cookies
Our platform integrates with several third-party services that may set their own cookies:
- GitHub API: For accessing repository data and authentication
- AI/ML Services: For powering our chat and analysis features
- Analytics Services: To understand platform usage and improve performance
- CDN Services: For delivering D3.js and other visualization libraries
- Error Monitoring: To track and resolve technical issues
These third-party services operate under their own privacy policies and cookie practices.
4. Managing Cookies
4.1 Browser Controls
You can control cookies through your browser settings. However, disabling certain cookies may affect platform functionality:
- Essential cookies: Disabling these will prevent chat sessions and repository analysis from working properly
- Functionality cookies: You'll lose saved preferences and have to re-enter repository URLs
- Performance cookies: We won't be able to optimize loading times for repository visualizations
4.2 Platform-Specific Controls
Within our platform, you can manage certain data:
- Clear chat history and conversation data
- Reset repository analysis cache
- Clear search history and preferences
- Reset visualization settings to defaults
5. Cookie Duration
5.1 Session Cookies
Temporary cookies that maintain your active chat session and current repository analysis. These are deleted when you close your browser or after a period of inactivity.
- Active chat conversation context
- Current repository visualization state
- Temporary analysis cache
5.2 Persistent Cookies
Longer-lasting cookies that remember your preferences across visits:
- User preferences: Up to 1 year
- Recently analyzed repositories: Up to 30 days
- Performance optimization data: Up to 90 days
- Analytics data: Up to 2 years (anonymized)
6. Data Protection and Security
We take cookie security seriously, especially given the sensitive nature of repository data:
- All cookies containing repository data are encrypted
- Session cookies use secure transmission (HTTPS only)
- Chat conversation cookies are automatically purged after session timeout
- No repository source code is stored in persistent cookies
- Vector embeddings in cookies are anonymized and non-reversible
7. Impact on Platform Features
Without Essential Cookies: Repository analysis, chat functionality, and visualizations will not work.
Without Functionality Cookies: You'll need to re-enter repository URLs and reconfigure visualization preferences each visit.
Without Performance Cookies: Repository processing may be slower, and we can't optimize the experience based on usage patterns.
8. Updates to This Policy
We may update this Cookie Policy when we add new features to our repository analysis platform or change how we handle data. Significant changes will be communicated through the platform. Continued use indicates acceptance of updated cookie practices.
9. Contact Us
If you have questions about our cookie practices, data handling in repository analysis, or need help managing your preferences, please contact us: