1. The service
FetchNode provides Django portfolio operations across errors, availability, requests, jobs, releases, analytics, conversion and search context, shared evidence and project-scoped MCP tools. Features can evolve as the service develops. The public demo contains illustrative sample data and is not a customer environment.
2. Accounts and security
You are responsible for accurate account information, secure credentials, authorized workspace access and promptly revoking exposed project keys. Do not share private server keys in browser code or public repositories.
3. Your monitoring data and shared links
You retain responsibility for the applications and data you send. You must have appropriate rights, notices and lawful bases, including consent where required for browser analytics. Do not deliberately send passwords, payment-card data, authentication tokens, health data or other unnecessary sensitive information.
Before creating a shared evidence link, review its exact snapshot and intended audience. Anyone holding an active bearer link can view the selected aggregate maintenance or before/after evidence until it expires or you revoke it. You are responsible for opting into any website name or request volume that is appropriate to share and for revoking a link that reaches the wrong recipient. A measured comparison does not prove what caused the change.
Coding agents and changes to your website
When connecting a coding agent, you are responsible for the agent and provider you authorize, its project credentials and its repository and execution permissions. MCP issue actions, including resolving, ignoring or snoozing an issue, change FetchNode issue state; they do not repair code or deploy a website. Review proposed changes, tests and production deployment separately. Monitoring and agent access do not replace hosting, backups, updates or end-to-end tests.
4. Acceptable use
Do not use FetchNode to break laws, probe systems without permission, distribute malware, bypass rate limits, interfere with the service or monitor people or applications you are not authorized to operate.
5. Plans, billing and cancellation
Paid plans renew at the interval selected in Stripe Checkout until canceled. Prices and included limits are shown before purchase. You can manage payment details, invoices and cancellation through the Stripe customer portal. After paid access ends, the workspace returns to Free limits; existing data remains subject to its applicable retention period.
Extra event capacity is an optional one-time purchase, available on every plan. Stripe shows the total and applicable tax before payment and creates an invoice. Purchased event credits are shared across the workspace, never expire, and remain available after a plan change or cancellation. Included monthly events are used first; credits are consumed only after those events are used up. Unused credits carry over to future months. Purchases do not renew or change your subscription. New measurements are rejected when the available event capacity is exhausted; uptime checks continue. Rejected measurements cannot be recovered by a later purchase.
6. Availability and generated advice
FetchNode is provided on a reasonable-efforts basis. Monitoring tools can miss, delay or group events and are not a substitute for backups, application security, emergency response or independent business records. AI-generated SEO advice can be incomplete or incorrect and must be reviewed before changing a production website; it does not guarantee rankings, traffic, conversions or revenue. Planned or emergency maintenance may temporarily affect availability.
7. Suspension and termination
Access may be limited or suspended to protect the service, respond to abuse, enforce plan limits or comply with law. You may stop using the service and cancel a paid subscription at any time.
8. Liability
To the extent permitted by law, FetchNode is supplied without guarantees that it will be uninterrupted or detect every production problem. Neither party excludes liability that cannot legally be excluded. Questions about a specific commercial agreement can be sent through support.
9. Changes
These terms may change as the product, plans or legal requirements evolve. Material changes will be reflected by a new effective date and, when appropriate, an account notice.