Skip to content

Privacy Policy

SignedOff Last updated: June 19, 2025

Overview

SignedOff is a GitHub App that enforces structured, enforceable checklists on GitHub issues. This policy explains what data SignedOff accesses, how it is used, and what we do not do with it. We have written this to be plain and direct — not to obscure anything.

The short version: SignedOff stores no data outside of GitHub. Your data stays in your GitHub account, under GitHub's own data residency guarantees. We do not sell, share, or monetize your data in any form.

What data SignedOff accesses

When installed, SignedOff requests the minimum GitHub permissions required to function. These include:

Issues — Read and write access to issues within the repositories where SignedOff is installed. This allows SignedOff to read issue content, post checklist comments, update checklist state, and enforce closure rules.

Organization members — Read access to organization membership and team membership. This is used exclusively to validate exception approval workflows — specifically, to confirm that an approver is a different user from the issue opener and belongs to the configured approvers team.

Repository metadata — Read access to repository and organization configuration. This allows SignedOff to read templates from .github and .github-private, and to apply allowlist and denylist rules.

Webhooks — SignedOff receives webhook events from GitHub when issues are opened, edited, closed, or commented on. These events are processed in real time and are not stored.

How data is stored

SignedOff does not operate an external database. All checklist state — item completion, exception flags, approval records — is stored directly inside GitHub issue comments, within your repository. This means:

  • Your data never leaves GitHub's infrastructure.
  • GitHub's own data residency and security guarantees apply.
  • Deleting an issue or its comments removes the associated SignedOff data entirely.
  • Uninstalling SignedOff removes its access immediately. No cleanup of external storage is required because none exists.

Cloudflare Workers and edge caching

SignedOff uses Cloudflare Workers to serve the SVG progress badge. When a badge is requested, the Worker reads the current checklist state from the relevant GitHub issue comment and renders an SVG response.

Badge responses are cached at the edge for 60 seconds to avoid GitHub API rate limit pressure. This cache is a short-lived response cache — it does not store personal data, issue content, or user identities. No persistent data is written to Cloudflare storage.

Cloudflare's privacy practices are governed by the Cloudflare Privacy Policy.

What we do not do

  • We do not sell your data.
  • We do not share your data with third parties, advertisers, or analytics services.
  • We do not read or store the content of your source code.
  • We do not retain webhook payloads after they have been processed.
  • We do not use your data to train machine learning models.
  • We do not track individual users across repositories or organizations.

GitHub's role

SignedOff operates as a GitHub App and is subject to the GitHub Marketplace Developer Agreement and the GitHub Privacy Statement. GitHub acts as a data processor for the data within your repositories. By using SignedOff, you are also subject to GitHub's Terms of Service and Privacy Statement.

Your rights

You have the right to:

  • Access — understand what data SignedOff holds about you. Because all state is stored in GitHub issue comments, you can view it directly in your repository at any time.
  • Deletion — remove SignedOff's data by deleting the relevant issue comments or uninstalling the app entirely. No additional deletion request is necessary.
  • Portability — your data is already in GitHub, in plain markdown inside issue comments. No export is required.
  • Withdraw consent — uninstall SignedOff at any time from your GitHub organization or repository settings. Access is revoked immediately.

If you are located in the European Economic Area, United Kingdom, or California, you may have additional rights under applicable privacy law. To exercise any of these rights, contact us at the address below.

Children's privacy

SignedOff is a developer tool intended for use by adults and organizations. We do not knowingly collect personal information from anyone under the age of 13. If you believe a minor has used SignedOff and you have concerns, please contact us.

Changes to this policy

We may update this policy from time to time. When we do, we will update the "Last updated" date at the top of this document. Continued use of SignedOff after a policy update constitutes acceptance of the revised policy. For significant changes, we will make reasonable efforts to notify users via the SignedOff website or GitHub Marketplace listing.

Contact

Questions, concerns, or requests related to this privacy policy can be directed to:

Signed Off [email protected]

About SignedOff

SignedOff is an independent project. Proceeds fund charitable work in memory of a father who believed that doing things right was never optional.