Data we access
LogBytes accesses repository commit metadata from repositories you explicitly authorize. This includes commit timestamps, authorship metadata, branch context, and related identifiers required to build timeline sessions.
Privacy summary
Privacy-first developer tracking
LogBytes is designed for teams that need trustworthy reporting without sacrificing control over data.
Data we do not access
LogBytes does not push code, create repositories, or modify repository settings on your behalf. The system is designed around read-only ingestion needed for timeline reconstruction and reporting.
Security and access controls
Authentication and authorization are enforced with role-based controls so teams can limit who can view and manage timeline data. Sensitive fields are excluded from activity logging by default.
Ownership and retention posture
Your organization retains control of deployment environment decisions, retention windows, and backup strategy. LogBytes is built to support transparent data governance in your own operational setup.