GitHub events treated as sensitive data from the first webhook.
GitHub DevLog AI is designed to receive, validate, and organize webhooks in private workspaces. This page summarizes collection, use, retention, and data isolation.
Account
Name, email, hashed password, and basic data needed to authenticate the user.
Workspace
Workspace name, members, roles, invitations, rotatable Secrets, and usage preferences.
Webhooks
Technical headers, sanitized payload, event, Delivery ID, signature status, and received date.
We use data to operate the product, not to sell developer information.
Data is used to authenticate users, isolate workspaces, validate signatures, show history, calculate usage limits, send notifications, provide support, and protect the platform from abuse.
No public payload
Events belong to the authenticated workspace. One user cannot access another workspace’s webhooks.
Payments
Payment data is processed by Mercado Pago according to the contracted flow.
Legal obligations
We may retain or share information when necessary to comply with law, fraud prevention, abuse prevention, or a competent order.
A user can request export, correction, or deletion.
Before launch, this channel must point to the official support email. During beta, requests may be handled manually by the product administrator.