Terms of Service

Usage policy and terms for using DevUpdate.io

Last updated: June 10, 2026

1. Acceptance of Terms

By accessing or using DevUpdate.io ("the Service"), you agree to be bound by these Terms of Service ("Terms"). If you do not agree to these Terms, you may not use the Service. We reserve the right to modify these Terms at any time, and your continued use constitutes acceptance of any changes.

2. Service Description

DevUpdate.io is a dependency tracking service that:

  • Analyzes git diffs of public GitHub repositories to detect code changes
  • Tracks release and version history of publicly available sources, including GitHub repositories, VS Code extensions (via the Visual Studio Marketplace and the Open VSX Registry), and other public release-notes pages
  • Generates AI-powered summaries of library releases and updates
  • Provides risk scores for dependency updates
  • Monitors lockfiles for dependency changes
  • Sends email notifications about risky updates
  • Publishes AI-generated descriptions and meta-summaries of tracked sources on public, unauthenticated discovery pages (the source explorer)
  • Delivers real-time updates over a persistent connection from your browser to our servers (e.g. subscription status after checkout, new releases on sources you watch) so the interface reflects backend changes without manual reload

The Service is provided "as is" and is subject to availability and our technical capabilities.

3. Account Registration and Security

To use DevUpdate.io, you must:

  • Be at least 16 years of age
  • Provide accurate and complete registration information
  • Verify your email address
  • Maintain the security of your account credentials
  • Not share your account credentials with others or allow multiple users to access the same account
  • Notify us immediately of any unauthorized access

You are responsible for all activities that occur under your account. We are not liable for any loss or damage from your failure to maintain account security. Each account is licensed for use by a single individual only. Sharing account credentials or allowing multiple people to use the same account is strictly prohibited and may result in immediate account suspension or termination. If you need multiple users, please subscribe to a Team plan with appropriate seat licenses.

Profile Field Integrity: You agree that your username, display name, and any other profile fields will not contain URLs, advertisements, promotional content, references to unrelated products or offers, or characters intended to impersonate another user or deceive readers. Accounts with profile fields that appear to be commercial spam, phishing lures, or automated signups may be deleted without notice.

Email Verification and Inactive Accounts: Accounts created with an email and password must verify the email address before signing in. We will email you a reminder around day 4 if you have not yet verified, and accounts that remain unverified 7 days after signup are automatically deleted along with any associated data. If you miss this window, you are welcome to sign up again.

Inactive Verified Accounts: To keep the platform tidy, verified free-tier accounts that have never added a tracked source and never connected a lockfile will be automatically deleted 30 days after signup. Before deletion we will send up to five reminder emails (around day 2, 5, 10, 20, and 27) inviting you to add a source or to share feedback about what you are missing; the day-27 message is an explicit warning that deletion is imminent. Adding a single source or lockfile at any point, upgrading to a paid plan, or joining a team removes your account from this cleanup cohort. After deletion we send a final notification to the address on file. If your account is deleted under this policy, you are welcome to sign up again.

Team Membership:Team members receive access through invitation from team admins or owners. Each team member must have their own individual account - team membership does not create a shared account. Team membership does not grant ownership of the team subscription; all billing and ultimate team control remains with the team owner. You must comply with the team's usage policies and the team owner's instructions regarding appropriate use of the Service.

Session Limits: To prevent account sharing and ensure security, each account is limited to a maximum of 3 concurrent active sessions. When you log in on a new device and exceed this limit, the oldest session will be automatically invalidated. A session represents an active login on a specific device or browser.

4. Acceptable Use Policy

You agree NOT to:

  • Use the Service for any illegal or unauthorized purpose
  • Attempt to gain unauthorized access to our systems or other users' accounts
  • Transmit viruses, malware, or other malicious code
  • Scrape, mine, or harvest data from the Service using automated means
  • Interfere with or disrupt the Service or servers
  • Circumvent usage limits or restrictions (e.g., free tier tracked-source limits)
  • Impersonate any person or entity
  • Use the Service (including profile fields such as username or display name) to spam, advertise, distribute links, or send unsolicited communications
  • Create accounts using automated tools, scripts, bots, or any other non-human means
  • Reverse engineer, decompile, or disassemble any part of the Service
  • Track sources you don't have legitimate interest in monitoring

Violation of this policy may result in immediate account suspension or termination.

5. Service Limits and Fair Use

Free Tier

The free tier (Hobbyist) allows monitoring of up to 100 tracked sources and 1 lockfile. We reserve the right to adjust these limits or introduce paid plans in the future.

Fair Use

Usage is not unlimited on any plan. We expect reasonable use of our Service based on typical customer usage patterns. Excessive usage that may strain our infrastructure includes:

  • Monitoring an unusually large number of tracked sources or lockfiles
  • Scanning extremely large codebases that require excessive processing
  • Requesting unusually frequent update scans
  • Any usage pattern that significantly deteriorates service quality for other users

We reserve the right to throttle, rate limit, or restrict accounts that exceed reasonable usage levels. Users with legitimate high-volume needs should contact us to discuss custom arrangements or pay-as-you-go overage options.

Release History Coverage

DevUpdate.io does notclaim to provide a comprehensive archive of a tracked source's entire release history. When you add a source for the first time, we perform an initial backfill of only the 3 most recent releasesas reported by GitHub at the time the source is added. This limit exists to keep onboarding fast and to respect GitHub's API rate limits.

After the initial backfill, we track all new releases going forwardfrom the point the source was added to your account. Releases published before the 3-release backfill window will not be retroactively imported, even if you upgrade your plan.

If you require historical release data beyond this window, please consult the upstream GitHub releases page directly. We reserve the right to adjust the backfill limit at any time based on operational constraints.

GitHub Rate Limits

Our analysis depends on GitHub's API. When we encounter rate limits, analysis may be delayed or incomplete. This is outside our control and not a breach of service.

6. Subscription Plans and Billing

6.1 Paid Subscriptions

DevUpdate.io offers paid subscription plans (Professional, Team) with additional features and limits. By subscribing to a paid plan, you agree to:

  • Pay the subscription fee through our payment processor, PayPro Global
  • Automatic renewal of your subscription unless cancelled before the billing date
  • PayPro Global's terms of service as our Merchant of Record

See the Plans docs for current per-tier pricing and feature comparison.

6.2 AI Credits

Most paid work on DevUpdate.io — generating per-user digests and release-intelligence summaries — consumes credits. One credit represents approximately 1,000 normalized tokens of LLM processing, with output tokens weighted more heavily than input tokens to match LLM-provider pricing.

Each tier includes a credit allotment per billing period:

  • Hobbyist: 500 credits per calendar month
  • Professional: 5,000 credits per month of your billing period (5,000 on a monthly plan, 60,000 on an annual plan)
  • Team: 5,000 credits per seat per month of your billing period, pooled across the team (5,000 per seat on a monthly plan, 60,000 per seat on an annual plan)

Included credits reset at the start of each billing period and do not roll over. Shared infrastructure work (for example, a release summary first computed for one user and reused by others) is generally not charged against your included credits. One exception applies: when you are the first user to track a source that has no deterministic parser, the one-time AI extraction and the initial release summaries generated for it are billed to your account. The exact operations that consume credits are listed in the Credits & Overage docs.

6.3 Refund Policy

EU 14-Day Right of Withdrawal: If you are a consumer established in the European Union, the Consumer Rights Directive gives you 14 days from the conclusion of your initial subscription contract to withdraw without giving any reason. This right applies to your first subscription payment; it does not apply to automatic renewal payments or to additional seats added to a Team plan mid-cycle.

Express Consent to Immediate Performance: Because DevUpdate.io consumes AI credits the moment you run a digest or release-intelligence summary, we ask you to expressly confirm at checkout that you want us to begin providing the paid service immediately. By ticking the consent box in the pre-checkout dialog, you acknowledge that if you exercise your right of withdrawal within the 14-day window after you have started using your included credits, your refund will be reduced proportionally to the credits you have already consumed.

Pro-rata Refund Formula: If you withdraw within the 14-day window, we refund your initial subscription payment multiplied by the proportion of your included credits that were still unused at the moment you request the refund:

refund = original payment × (1 − credits_used ÷ credits_included)

Examples: if you used 0 credits you receive 100 % of your payment back; if you used 30 % of your included credits you receive 70 % back; if you have fully consumed your included credits no refund is due under this formula. You can see the exact amount you would receive at any time in Settings → Subscription → Request Refund, which displays a live preview before you confirm.

Usage-based Overage Charges: Any metered overage credits you consume beyond your included allotment are billed at the per-credit rate shown on our pricing page at the time of consumption. These post-paid consumption charges are not part of the initial subscription payment and are not refunded under the right of withdrawal. Wallet top-ups and any auto-recharges are likewise consumed immediately on purchase and are non-refundable under the right of withdrawal.

How to Withdraw:The fastest way is to go to your account settings and click the "Request Refund & Cancel" button, which issues the cancellation and refund in a single step. Alternatively, you can contact our payment processor PayPro Global directly or email us at info@devupdate.io. We will process the refund via PayPro Global without undue delay; the payout typically appears on your statement within 5–10 business days.

After the 14-Day Window: Once the 14-day right of withdrawal has expired, subscription payments become non-refundable. You may cancel at any time to prevent future charges, in which case your subscription remains active until the end of the current billing period and is then downgraded to the Hobbyist tier.

Free Tier Available: A free Hobbyist tier is available to evaluate the service before committing to a paid plan. We strongly encourage all prospective customers to use it first.

6.4 Wallet, Top-Ups, and Auto-Recharge

When your included credits are exhausted before the period ends, billable AI work pauses. You can resume immediately by purchasing additional credits, or wait for the next billing period when your included credits reset.

Wallet top-ups. Additional credits are purchased through your wallet at €0.002 per credit (equivalent to €2 per million tokens). Top-ups are charged via PayPro Global in amounts between €1 and €500 and include progressive volume discounts at €50 (5%), €100 (10%), and €150 (15%) thresholds. Purchased credits stack with your included allotment and do not expire. Wallet top-ups are consumed immediately on purchase and are non-refundable.

Optional auto-recharge. You can opt in to auto-recharge in Settings → Wallet to keep working without manual top-ups. When enabled, your wallet automatically tops up via PayPro Global when its balance falls below a threshold you choose (€1–€25), refilling to a target you choose (€5–€100). Auto-recharge is opt-in only and off by default. Safety controls include a minimum 5-minute cooldown between charges and an automatic disable after 3 consecutive failed payment attempts. You can change or turn off auto-recharge at any time from Settings → Wallet; charges already initiated before you disable are not reversed.

6.5 Cancellation

You may cancel your subscription at any time from your account settings or through the PayPro Global customer portal. Upon cancellation, your subscription remains active until the end of your current billing period. After this period ends, you will be automatically downgraded to the Hobbyist (free) tier.

6.6 Team Subscriptions

Team subscriptions include multiple seats for team members. The team owner is responsible for all billing and member management. When a team subscription ends or is cancelled, all team members lose access to team features and are downgraded to the Hobbyist tier.

Credit pooling: AI credits on a Team plan are pooled across all seats (5,000 included credits per seat per month of the billing period). All member usage — digests, release-intelligence summaries — draws from this shared pool. Overage and wallet top-ups on a Team plan are billed to the team owner.

Seat Management: Team plans start with 5 seats. You may add additional seats at any time at €12/month per seat or €10/year per seat. Seat billing is flexible - you can add monthly seats to a yearly plan or vice versa. Each additional seat is billed independently according to its billing period (monthly or yearly).

When you add a seat to an existing subscription:

  • Monthly seats are billed immediately and renew monthly
  • Yearly seats are billed immediately and renew annually
  • Each seat can be cancelled independently without affecting other seats or the base plan
  • Prorated charges may apply when adding seats mid-billing cycle

When you remove a seat, that team member immediately loses access. The seat remains paid through the end of its current billing period but will not auto-renew. No refunds are provided for partial billing periods.

6.7 Team Roles and Access Control

Team subscriptions use a role-based access control system with three types of roles:

  • Owner: The account creator or designated owner has ultimate control over the team. The owner can transfer ownership to another admin, manage all members and admins, control billing, and is legally responsible for all team subscription charges and team member actions. Only the owner can transfer ownership or demote other admins. The owner cannot leave the team without first transferring ownership to another admin.
  • Admin: Team admins can invite new members with any role (Admin or Member), promote members to admin, remove members (but not other admins or the owner), view and cancel pending invitations, and manage team settings. Admins have significant control over team membership and are responsible for ensuring proper access controls.
  • Member/User: Regular team members can view team information, see other team members and their roles, view pending invitations, and leave the team at any time. Members cannot manage other team members or modify team settings.

Ownership Transfer: Team ownership can be transferred to another admin at any time by the current owner. Ownership transfers are permanent and cannot be reversed. The previous owner remains as a team admin but loses owner privileges. Ownership transfers do not affect billing - the new owner assumes all billing responsibilities.

Member Removal and Leaving: When a member is removed from the team or chooses to leave, they immediately lose access to all team features and are downgraded to the Hobbyist tier. Their individual account and personal data remain intact. Removed members can be re-invited if seats are available. The system prevents removal of the last admin to ensure teams always have management.

Liability and Responsibility: Team owners and admins are responsible for managing team access appropriately. You may be held liable for actions taken by team members you invite or grant admin privileges to, including but not limited to violations of these Terms, unauthorized access, or misuse of the Service. Ensure you only invite trusted individuals and regularly review team membership.

6.8 Usage Limits and Overages

Each subscription plan includes reasonable usage limits based on typical customer usage patterns. Usage is not unlimited. Factors that affect your usage include:

  • Number of tracked sources and lockfiles monitored
  • Size and complexity of codebases being scanned
  • Frequency of update scans and analysis requests

We reserve the right to throttle or restrict service for accounts that significantly exceed normal usage patterns or negatively impact system performance. AI-credit overage is handled via the wallet and (optionally) auto-recharge described in §6.4. For infrastructure-level limits that cannot be addressed through credit top-ups, contact us to discuss custom arrangements.

6.9 Price Changes

We reserve the right to change subscription prices with at least 30 days notice. Price changes will take effect on your next billing cycle. Existing subscriptions will be honored at their current price until renewal.

7. Programmatic Access (API Tokens & MCP Server)

API Tokens

Professional and Team subscribers may generate API tokens from Settings → API to access your tracked sources, releases, and analysis programmatically. Tokens carry the same access scope as your account; treat them like passwords. Sharing an API token with anyone outside your account (or, on a Team plan, outside the seats you are authorized to grant access to) violates §3 (Account Registration and Security). We store only a hash of the token; if you lose a token you must rotate it. Revoking a token from Settings → API invalidates it immediately.

MCP Server (Professional and Team)

The MCP server is available on Professional and Team tiers. It exposes the same data accessible via API token over the Model Context Protocol so that compatible AI clients can query your tracked sources, summaries, and risk data on your behalf. It is offered in two forms: a hosted endpoint operated by us at api.devupdate.io, and a self-run (stdio) server. The same usage limits, acceptable-use restrictions, and credit metering apply to MCP-driven requests as to direct API requests, regardless of form.

The hosted endpoint authenticates via your API token or via OAuth: third-party AI clients may request access, which you grant on an explicit consent screen and may revoke at any time from Settings → Connected AI Clients. Authorized clients receive narrowly scoped credentials limited to reading your tracked-source and available-upgrade data and dismissing upgrade notices; they act on your behalf, and you are responsible for the clients you choose to authorize. We may suspend an OAuth client's access where we reasonably suspect abuse.

8. Intellectual Property

Our Content

The Service, including its design, features, text, graphics, and software, is owned by DevUpdate.io and protected by copyright, trademark, and other intellectual property laws. You may not copy, modify, or distribute our content without permission.

Your Data

You retain ownership of data you provide (tracked-source URLs, lockfiles, account information). By using the Service, you grant us a limited license to process this data to provide our services.

AI-Generated Content

AI-generated summaries and analysis are created by our systems. You may use this content for your internal purposes but may not resell or redistribute it as a service to others.

Public AI-generated content (source explorer). Source descriptions and meta-summaries shown on /explore and on public source detail pages are generated by a large language model from publicly available metadata (e.g. README excerpts for GitHub sources, page excerpts for non-GitHub sources, and our own release-summary history). This content may be inaccurate, incomplete, outdated, or misleading. It is provided for discovery and orientation only and must not be relied on as an authoritative description of any third-party project.

No affiliation or endorsement. DevUpdate.io is not affiliated with, endorsed by, or representative of the source/repository owners or their projects. The presence of a source on the explorer does not imply any relationship between DevUpdate.io and the project, its maintainers, or any other third party.

Correction and removal. Source/repository owners (and anyone with a legitimate interest) may request correction or removal of an AI-generated description or meta-summary by emailing info@devupdate.io. We will act on legitimate requests within a reasonable timeframe.

9. Third-Party Services and Data

DevUpdate.io integrates with third-party services:

  • GitHub:We access public repository data through GitHub's API. You are responsible for ensuring you have the right to monitor the sources you add. You may also optionally connect a lockfile to a GitHub repository (public or private) so the Service performs recurring automated fetches of that file. Such access is granted through a GitHub App that you install yourself, is read-only and scoped to the repositories you select, and can be revoked at any time from your GitHub settings. You are responsible for ensuring you have the right to grant this access for the repositories you connect. You may also optionally enable GitHub starred-repository sync, in which case the Service will create tracked sources from your public GitHub stars and deactivate them when you un-star the corresponding repositories. You are responsible for the accuracy of the GitHub username you provide.
  • VS Code Marketplace and Open VSX Registry: When you track a VS Code extension, we make read-only requests to the public Visual Studio Marketplace and Open VSX Registry APIs to retrieve the extension's version history and changelogs. No authentication is used and no editor, workspace, or account data is accessed. You are responsible for ensuring you have the right to monitor the extensions you add.
  • AI Providers (currently OpenAI): Git diffs, release notes, repository metadata and README excerpts (for GitHub sources), and excerpts of public release-notes pages and registry/marketplace API responses parsed by our adapters (for non-GitHub sources) are sent to OpenAI for analysis and for generating source descriptions and meta-summaries. This data is from publicly available sources only. We may engage other LLM providers in the future; data sent for analysis is described in our Privacy Policy.
  • OAuth sign-in providers (Google, GitHub): When you sign in with Google or GitHub, those providers see your sign-in activity and share back the minimum profile data needed for authentication. Their handling of that data is governed by their privacy policies. See our Privacy Policy for the specific fields we receive.
  • AWS: We use AWS infrastructure for hosting, storage, and email delivery.

These services have their own terms and privacy policies. We are not responsible for third-party service availability, security, or compliance.

10. Disclaimer of Warranties

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO:

  • Warranties of merchantability or fitness for a particular purpose
  • Accuracy, completeness, or reliability of AI-generated analysis
  • Accuracy of source descriptions or meta-summaries displayed on public discovery surfaces
  • Currency or completeness of project status information (e.g. maintenance, release cadence, known issues)
  • Uninterrupted or error-free operation
  • Detection of all breaking changes or security vulnerabilities
  • Prevention of production issues caused by dependency updates

DevUpdate.io is an informational tool, not a guarantee. You are solely responsible for decisions about updating dependencies and must perform your own testing and validation.

11. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, DEVUPDATE.IO AND ITS OPERATORS SHALL NOT BE LIABLE FOR:

  • Any indirect, incidental, special, consequential, or punitive damages
  • Loss of profits, data, use, goodwill, or other intangible losses
  • Damages resulting from dependency updates, production incidents, or security vulnerabilities
  • Errors in AI analysis or missed breaking changes
  • Service interruptions, data loss, or third-party service failures

OUR TOTAL LIABILITY SHALL NOT EXCEED THE AMOUNT YOU PAID US IN THE 12 MONTHS PRIOR TO THE CLAIM (CURRENTLY €0 FOR FREE TIER USERS).

12. Indemnification

You agree to indemnify and hold harmless DevUpdate.io, its operators, and affiliates from any claims, damages, losses, liabilities, and expenses (including legal fees) arising from:

  • Your use or misuse of the Service
  • Violation of these Terms
  • Violation of any rights of another party
  • Your account credentials being compromised
  • Actions taken by team members you invited or gave admin privileges to
  • Unauthorized access or data breaches resulting from improper team member management

13. Termination

By You

You may delete your account at any time from your settings page. Account deletion is permanent and irreversible.

By Us

We may suspend or terminate your account immediately, without notice, if you violate these Terms, engage in fraudulent activity, or misuse the Service. We may also discontinue the Service at any time with reasonable notice.

In particular, we may delete, without individual notice: (a) accounts that fail to verify their email address within 7 days of signup; (b) accounts created by automated tools, scripts, or bots; and (c) accounts whose profile fields contain URLs, advertisements, promotional content, or other material that violates §3 or §4. These deletions may occur automatically as part of routine operations.

Effect of Termination

Upon termination, your right to use the Service ceases immediately. Data deletion follows our Privacy Policy procedures.

14. Modifications to the Service

We reserve the right to modify, suspend, or discontinue any part of the Service at any time, with or without notice. We may also change pricing, features, or limits. We are not liable for any modifications or discontinuation of the Service.

15. Governing Law and Jurisdiction

These Terms shall be governed by and construed in accordance with the laws of Germany, without regard to its conflict of law provisions. Any disputes arising from these Terms or use of the Service shall be subject to the exclusive jurisdiction of the courts in Germany.

16. Severability

If any provision of these Terms is found to be unenforceable or invalid, that provision shall be limited or eliminated to the minimum extent necessary, and the remaining provisions shall remain in full force and effect.

17. Entire Agreement

These Terms, together with our Privacy Policy, constitute the entire agreement between you and DevUpdate.io regarding use of the Service, superseding any prior agreements.

18. Shareable Release Summary Links

The Service lets you generate a public link to an individual release summary. By creating such a link, you acknowledge and agree that:

  • Anyone who has the link can view that release summary without a DevUpdate.io account. You are responsible for deciding with whom you share it.
  • Share links expire automatically 7 days after creation and may be revoked by you at any time before then.
  • Release summaries are AI-generated from third-party sources and are provided subject to the disclaimers elsewhere in these Terms.
  • We may disable or remove any share link, and may limit the number of active links available on a given plan, including to enforce the Acceptable Use provisions of these Terms.

19. Contact Information

If you have questions about these Terms, contact us:

Jakob Maximilian Pelz

Olenhoffweg 1a, 21614 Buxtehude, Germany

Email: info@devupdate.io

By using DevUpdate.io, you acknowledge that you have read, understood, and agree to be bound by these Terms of Service.