ShipNotes — Disclaimers

Operated by QVANS LLC · 3955 Greenfield Ct, Boynton Beach, FL 33436 · legal@getshipnotes.app · Governing law: Florida, USA · Effective: September 16, 2026

These statements describe the product as implemented (verified against the codebase on September 16, 2026): a GitHub App with read-only Contents, Metadata, and Pull requests permissions and release, push, and installation events, plus an optional GitLab webhook integration; collection limited to PR number, title, body, labels, and merge date per release range (no diffs, no source files); AI drafting through DeepInfra, Groq, and xAI inference APIs, routed through Cloudflare AI Gateway for request logging and cost monitoring; encrypted integration tokens and Slack webhook URLs; an explicit publish flow; hosted public changelog pages with RSS; Stripe billing (Free, Starter, Pro, Enterprise); Cloudflare Email Service for transactional email; Sentry error monitoring; Neon and Cloudflare hosting.

1. Your code stays yours — and confidential

ShipNotes reads only the pull-request metadata needed to draft your release notes — PR titles, bodies, labels, and merge dates for the release range — under read-only, least-privilege permissions you grant. We never read diffs or your source tree. Your repository data is used solely to generate your notes, is never shared with other customers, and is never used by us to train AI models; we only use inference providers whose API terms prohibit training on customer inputs. Uninstalling the GitHub App deactivates the connection and revokes the installation token; deleting your account deletes cached repository data immediately.

2. AI-generated drafts

Release notes are drafted by large language models from your merged PRs. Drafts may contain inaccuracies, miss or misdescribe changes, or phrase things in ways you wouldn't. Review before publishing — nothing goes live until you publish, and published notes are your content.

3. Pre-publish sensitivity check

Publishing makes your notes public on your changelog page and RSS feed, and posts to Slack if you configured it. Check for anything that shouldn't ship: security-fix details, secrets or internal URLs pasted into PR bodies, unannounced features, customer names. QVANS LLC is not responsible for information you publish. You can edit a published note at any time; to remove one entirely, contact legal@getshipnotes.app.

4. Hosted changelog pages

Each changelog is published by the respective project team using ShipNotes. Content is the publisher's responsibility. To report abuse or request removal of infringing content: legal@getshipnotes.app.

5. Third-party services

ShipNotes depends on GitHub and GitLab (source data and webhooks), Groq, DeepInfra, and xAI (AI drafting, with automatic failover), Slack (optional notifications via a webhook you configure), Stripe (billing), Cloudflare (hosting, CDN, AI Gateway, and transactional email), and Neon (database). Outages or API changes at these providers can interrupt the service; we target prompt restoration but do not warrant uninterrupted availability.

6. Output ownership

As between you and QVANS LLC, you own the release notes generated from your repositories, including drafts, your edits, and your published changelog. We assign to you any rights we may hold in generated notes and claim no rights in your source data.

7. Subscription

The Free plan includes 1 active repository. Paid plans — Starter ($19/month, 3 active repositories), Pro ($49/month, unlimited), and Enterprise ($99/month, unlimited) — renew automatically each month until cancelled. Cancel anytime in Billing with effect at period end; cancelling is as easy as subscribing. Plan limits are metered on active repositories and enforced in-product. Payment failures trigger an email before any downgrade or suspension.

8. Limitation of liability

The service is provided "as is". To the maximum extent permitted by law, aggregate liability is capped at fees paid in the preceding 12 months, and indirect or consequential losses (including losses from published content or missed release communications) are excluded. Mandatory rights under applicable law are unaffected. The full terms are in the Terms of Service.

9. Slack notifications

Posts to your Slack channel are made automatically by ShipNotes when you publish a release. Configure or disconnect the webhook in ShipNotes → Repository settings.

10. GitHub permissions rationale

Why these permissions? Contents (read-only): resolve release-tag commit SHAs. Metadata (read-only): required by GitHub for all apps. Pull requests (read-only): read PR titles, bodies, and labels to draft notes. Events: release and tag push trigger generation; installation events let us deactivate the connection when you uninstall. We request no write access to any repository resource.