Skip to content
    Electron Publish Pro
    Back to Home

    Security

    What happens to your code and GitHub access when you run a Release Readiness Check. This page describes the beta as it works today.

    GitHub Token Encryption

    Your GitHub access token is encrypted with AES-256-GCM before it is stored, and is decrypted only inside our server functions when a check runs.

    No Code Storage

    A check reads your file tree and up to 77 config and entry files through the GitHub API. We don't clone your repo. Only the report is saved.

    AI Processing

    The files a check reads are sent to Anthropic's Claude API to write the report. Don't run the check on a repo whose config files you can't share with a third-party AI service.

    Per-User Data Access

    Accounts, projects and reports are stored in Supabase (PostgreSQL) with row-level security, so each user can read only their own data.

    GitHub Permissions

    Reading a private repository through a GitHub OAuth app requires the broad repo scope. We use it only to read the files a check needs. You can revoke access at any time in GitHub under Settings → Applications, and disconnect GitHub from your account settings.

    Who Runs This

    Electron Publish Pro is a small, founder-run product in public beta. There is no security certification. Data is in transit over HTTPS, and the infrastructure is Supabase and Vercel.

    Deleting Your Data

    You can delete a project and its reports, or your whole account, from the dashboard. Deleting your account removes your stored GitHub token.

    Report a Vulnerability

    If you find a security issue, please email hello@electronpublish.com. We appreciate responsible disclosure and will reply as soon as we can.