NODEDOTS / PUBLIC BETA / UPDATED 10 OCTOBER 2026
Security & data handling
The controls implemented in the current public-repository beta, and their practical limits.
Repository access
You select which repositories the GitHub App can access. Saved reports require an authenticated session and current repository authorization. A sharing grant does not bypass this authorization. Private repositories remain disabled in the hosted beta.
Source and credential handling
Source is read at captured commits and treated as input for static analysis. Repository code is not executed. GitHub tokens and report contents are encrypted before D1 storage. Shipping policies, briefs, and release-assessment notes are also encrypted. Metadata, access grants, and finding decision records are stored for workflow and access checks.
GitHub webhooks are signature-verified and delivery-deduplicated. Automatic jobs use short-lived installation credentials. A queued manual job’s encrypted token is erased on completion or failure. Necessary session cookies are HTTP-only and Secure on HTTPS.
Retention and practical limits
Report access expires after seven days, with scheduled cleanup of related records. Policies and briefs persist until replaced or cleared. Uninstalling the App prevents access but does not automatically delete all stored workflow records. NodeDots has not published an independent security audit, certification, or uptime guarantee.
Report a concern
A dedicated private security reporting channel has not yet been published. Use Contact NodeDots to request a private reporting channel before sending sensitive details. Do not publish credentials, customer data, or a working exploit in a public issue or social post. Stop testing if you encounter another person’s information; do not download or retain it.
This guidance does not create a bug-bounty program, legal safe-harbor promise, or authorization to test third-party systems.
Read the data and permissions guide →