RepoLogbook
Policy draft

Privacy

This pre-launch policy describes the data boundaries implemented by the service and remains subject to legal review.

Data collected

GitHub account identity, authorized repository metadata, traffic aggregates, referrers, popular paths, stars, preferences, and operational diagnostics.

Credential handling

User access tokens are used only during sign-in and are never stored. Repository access tokens are short-lived and are never written to storage.

Retention and deletion

Your plan controls how much history stays visible. Deleted data remains recoverable for 30 days before it is permanently removed. Account controls provide a portable JSON export and permanent deletion of your analytics, reports, badges, sessions, pending background work, communication history, and any administrator records that identify you.

Communications

Service messages, weekly digests, and Product updates use separate delivery categories. Digests and Product updates start enabled during beta and can be disabled independently; global and category unsubscribe, bounce, and complaint suppression always wins. After account deletion, a minimal irreversible suppression record is kept to prevent prohibited redelivery.