Privacy notice

What we use and why

We store your GitHub full name and profile-picture link to identify your profile. If GitHub does not provide a name, we ask you to enter it. Profile pictures load from GitHub, which receives your IP address and browser request information. You do not need to upload a picture.

We use GitHub identity, repository and access information, PR titles and links, author and reviewer identities, activity dates, review states and synchronization status to show review queues and delays. Repository records do not retain source code, commit diffs or comment and review text. Notifications received from GitHub can contain private repository information.

New users need a verified contact email to set up repositories. We use a verified GitHub email when available, or ask you to verify an address. We retain your contact details and verification status to manage your account and send verification and welcome messages. Verification messages go only to your address; the operator receives a blind copy of your welcome message, which contains no private repository content. Mail to hello@reviewbeacon.dev is forwarded to the operator's inbox.

Sharing and service providers

Organization data is shared with explicitly authorized members using their last verified GitHub access. If access changes only on GitHub, a member may continue viewing currently stored repository data until that verification expires, at most one hour after the check began. During a GitHub outage, private data becomes unavailable when that period ends. Removing a member in ReviewBeacon or signing out blocks subsequent access checks immediately; content already shown cannot be recalled. These actions do not delete shared organization data.

We use hosting, database, email and monitoring service providers to run ReviewBeacon. Primary storage is in Germany, and encrypted recovery copies are stored in the EU. Providers and their subprocessors may also process data elsewhere, including the United States. Email services process recipients and message content. Monitoring records help detect service problems and can include account or repository identifiers; they exclude repository titles, review text, credentials and contact details. Processing is not limited to Switzerland or the EU.

Retention and deletion

We keep encrypted GitHub sign-in credentials to renew your access when you return or use ReviewBeacon. Successful navigation and actions keep your sign-in active for 30 days from that activity. Leaving a tab open does not count. Signing out ends that session and its ability to renew access. Expired sessions are removed during periodic cleanup, which can be delayed; they cannot grant access after expiry. Shared account setup and repository history remain.

Your stored name and profile-picture link remain with your sign-in identity while you participate. Verified identity-deletion requests remove these details within seven days. Signing out or deleting repository data does not remove your profile.

GitHub notification content expires within 30 days. Repository records remain while an account participates. Account deletion, uninstall and confirmed repository removal block access and schedule affected repository data for deletion within seven days; cleanup can be delayed. Suspension blocks access without deleting history. Signing in or refreshing GitHub access does not cancel deletion or restore removed local membership.

Contact details remain while you participate. Transactional delivery records and earlier access requests expire after 90 days. Earlier requests can include contact email, GitHub username, team size and use case; existing invitation records retain their original deletion obligations. Email copies are removed within 90 days. After verifying a deletion request, we remove matching application records and email copies within seven days. Email already accepted for delivery cannot be recalled.

We keep encrypted recovery copies on a seven-day retention schedule. Copies can remain after live data is deleted. Service-provider logs and underlying backup copies follow their own retention policies, and legal retention obligations can apply.

Your choices and rights

Your theme choice is saved in this browser, including after sign-out. It is not linked to your account. Clear site storage to reset it to System.

Your browser remembers your chosen interface language in a cookie, including after sign-out. When you are signed in, your chosen language is also saved with your account. Visiting a language-specific public page does not change your saved choice. Language, regional formatting and timezone are separate preferences.

Request repository-data deletion in Account settings, or manage repository selection and uninstall on GitHub. Signing out does not delete data. Repository-data deletion does not delete your sign-in identity, and a member's identity-deletion request does not necessarily delete shared organization records. Account settings

Contact ReviewBeacon using the email address below to request access to or correction of your personal data, contact or identity deletion, or earlier deletion of access requests and invitations. You can also ask about restricting or objecting to processing and obtaining a copy of your data; applicable law determines these rights. We verify requests before acting. You can raise a data-protection concern with your applicable supervisory authority. Do not send credentials or private repository content. hello@reviewbeacon.dev