NODEDOTS / PUBLIC BETA / UPDATED 10 OCTOBER 2026

Privacy in the early beta

How the current waitlist and repository-review beta handle your information.

Waitlist

Joining the waitlist saves your email address, signup time, and consent so NodeDots can notify you when early access opens.

Signups are stored in Cloudflare D1. Resend sends the signup confirmation email. Emails include an unsubscribe link that lets you remove your signup. Hashed request identifiers help limit automated abuse. Joining the waitlist does not connect to repositories.

GitHub sign-in

Signing in shares your GitHub user ID and username with NodeDots. GitHub access tokens are encrypted before storage in Cloudflare D1. The browser receives an HTTP-only session cookie containing a random identifier. Sessions last at most eight hours. Signing out deletes the server session; refresh tokens are not stored.

Repository reviews

You choose which repositories the GitHub App can access. This first beta accepts public repositories only. NodeDots reads commit-pinned source and pull request metadata to generate an impact report without running your repository code. The review workflow uses the deterministic engine and does not send source to an external AI provider.

Reports include repository identifiers, commit identifiers, findings, and source evidence. Report contents are encrypted in Cloudflare D1 and available to the initiating user and GitHub users that the owner explicitly grants access to, while GitHub still confirms repository access through NodeDots. Reports and background jobs become inaccessible after seven days. A scheduled maintenance pass every 15 minutes removes expired reports, their saved finding decisions, release assessments and sharing grants, jobs, and sessions. Finding decisions and optional reasons are saved per user and report. A queued manual review temporarily stores an encrypted GitHub token and erases it on completion or failure.

Automatic reviews

A repository administrator or maintainer can explicitly enable reviews for new and updated pull requests. NodeDots verifies signed GitHub events and mints short-lived installation tokens for these jobs. Advisory GitHub checks include summary counts and a link to the initiating maintainer’s authenticated report. Reports are not automatically shared with teammates. Turning automation off prevents queued automatic jobs from proceeding.

Shipping setup and shared reviews

Repository shipping policies and change-intent briefs are encrypted in D1. Authorized repository users can read them; maintainers edit policy and repository writers edit briefs. These records persist until replaced or cleared using empty fields in Shipping setup. Uninstalling the App prevents access but does not automatically delete these records. Release-assessment notes are encrypted; actor identifiers, assessment status, and explicit sharing grants are stored with each report. Owners can revoke a report grant. Shared recipients can record their own finding decisions and release assessments. Copied or downloaded handoffs are controlled by the person exporting them.

Your controls

You can remove repositories or uninstall the app in GitHub settings, revoke user authorization on GitHub, and sign out of NodeDots. NodeDots checks current GitHub access before reading a saved report. Account sign-in and report pages are excluded from search indexing.

Further policy details

Operator identification, a dedicated privacy contact, waitlist retention, account deletion procedures, and the broader policy for a private-repository beta still need to be published. Private-repository access remains disabled in this deployment.

Contact NodeDots

Privacy requests and provider details

Cloudflare provides hosting and D1 storage, GitHub provides account authorization and repository access, and Resend delivers waitlist email. A dedicated private privacy-request channel and jurisdiction-specific rights procedure remain to be published. Use Contact NodeDots to request a private channel; do not post personal data or credentials publicly. This notice does not promise an automated account-deletion workflow.

Browser storage is explained in Cookies & storage. The hosted analysis path is described in Analysis & AI disclosure.