Terms & Conditions

Acceptance of these Terms

By accessing or using UpRender, creating an account, connecting a domain, authorizing a Google integration, submitting a sitemap, configuring middleware, routing bot traffic, using AI Visibility features, or purchasing a subscription, you agree to these Terms and to our Privacy Policy. If you use UpRender for an organization, client, agency customer, employer, or other legal entity, you represent that you have authority to bind that entity.

If you do not agree to these Terms, you must not use the Services and must remove any UpRender middleware, proxy, DNS, CDN, API, or edge-function configuration from your infrastructure.

If a signed order form, master services agreement, data processing addendum, security addendum, private-hosting agreement, or enterprise statement of work conflicts with these Terms, the signed agreement controls only for the customer and services covered by that signed agreement.

Definitions

Service Description

UpRender helps JavaScript-powered websites become readable, citable, and indexable by AI search engines and traditional crawlers. The Services are designed to route bot requests through a rendering pipeline while allowing human visitors to continue to receive the original customer website.

3.1 Core rendering and routing

• UpRender may detect known AI and search crawlers, route eligible bot requests through a rendering pipeline, and serve cached or freshly rendered HTML snapshots.
• The Services may generate or preserve metadata, headings, structured data, Open Graph tags, canonical tags, and other crawler-facing page elements.
• Caching, TTLs, route-level rules, custom headers, bot allowlists, bot blocklists, and purge behavior depend on your plan and configuration.
• Bot detection is probabilistic. UpRender does not guarantee detection of every bot or exclusion of every non-bot.

3.2 AI Visibility, analytics, and optimization tools

• The Services may provide page-level AI readiness or AEO scores, metadata audits, schema recommendations, content-density signals, entity extraction, author context, topic clustering, render history, bot analytics, and live request feeds.
• Scores, recommendations, and analytics are informational and may be incomplete, delayed, estimated, or inaccurate.
• UpRender does not guarantee rankings, indexing, traffic, impressions, clicks, conversions, AI citations, answer engine inclusion, or revenue outcomes.

3.3 Coming-soon and beta features

Features described as alpha, beta, preview, early access, experimental, coming soon, roadmap, or pilot may be changed, delayed, limited, suspended, or discontinued at any time unless a signed Order Form expressly states otherwise.

Accounts, Authority, and Authorized Users

4.1 Account registration

You must provide accurate, current, and complete account, organization, billing, and contact information. You are responsible for maintaining that information and for all activity under your account, API keys, tokens, team members, integrations, and domains.

4.2 Organizational authority

You represent and warrant that you own or are authorized to control every domain, subdomain, route, sitemap, Google Search Console property, Google Analytics property, proxy configuration, and Customer Content connected to UpRender.

4.3 Security of credentials

You must protect passwords, API keys, OAuth tokens, edge-function secrets, CDN credentials, source repositories, environment variables, and dashboard access. UpRender is not responsible for losses caused by compromised customer credentials.

Domain, Proxy, Middleware, and Rendering Setup

5.1 Customer-controlled integration

UpRender may provide integration instructions for Express, Next.js, Nginx, CDN rules, edge functions, reverse proxies, or other middleware. You are responsible for implementing, validating, deploying, monitoring, and rolling back those configurations in your own environment.

5.2 Anti-cloaking obligation

UpRender is intended to improve crawler access to the same substantive content available to human users. You must not use the Services to deceive crawlers, hide materially different content, manipulate rankings through deceptive cloaking, or violate search engine guidelines.

5.3 Caching and stale content

Cached pages may remain available until purged, expired, refreshed, or deleted according to plan settings and technical constraints. You are responsible for cache purges, route exclusions, emergency rollback, and monitoring where content freshness is important.

5.4 Sensitive routes

You must not route private dashboards, authenticated pages, checkout pages, user account areas, health records, financial account pages, admin panels, staging secrets, internal tools, or other sensitive routes to UpRender unless you have a signed enterprise agreement that expressly permits it.

Google Search Console, Google Analytics, and Webmaster-Tool Integrations

6.1 Authorization

If you connect Google Search Console, Google Analytics, or another Google API, you authorize UpRender to access, process, display, and use the authorized data only for customer-facing features such as indexing diagnostics, sitemap submission status, URL inspection details, search performance metrics, analytics summaries, dashboard reporting, and AI Visibility insights.

6.2 Limited Use and AI model restrictions

UpRender's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google API user data to train generalized or non-customer-specific AI or machine learning models.

6.3 Customer responsibility

You are responsible for your Google account, Google properties, permissions, OAuth consent, user access, API quotas, data retention settings, and compliance with Google terms. UpRender is not responsible for Google outages, quota limits, policy changes, or decisions by Google regarding crawling, indexing, or ranking.

6.4 Revocation

You may disconnect Google integrations through UpRender, your Google account, or any available authorization controls. Disconnection may disable related dashboard features and reports that depend on Google data.

AI Audits, Metadata, Schema, Sitemap, and llms.txt Outputs

7.1 Informational nature

AI audit results, AEO scores, metadata suggestions, schema suggestions, entity extraction, and llms.txt outputs are generated by automated systems. They are informational and may be inaccurate, incomplete, outdated, duplicated, noncompliant, or unsuitable for your use case.

7.2 Human review required

You are responsible for reviewing, approving, editing, testing, and monitoring all Rendered Output before relying on it. You must ensure that generated content is truthful, lawful, non-infringing, technically valid, and aligned with your website strategy.

7.3 No professional advice

UpRender does not provide legal, tax, accounting, security, medical, financial, investment, advertising, or professional SEO advice.

Customer Responsibilities

1. Lawful authority. You must have the right to use every domain, URL, Google property, Analytics property, sitemap, source page, and data source connected to UpRender.
2. Configuration and monitoring. You must test proxy rules, route filters, bot rules, headers, cache controls, metadata injection, sitemaps, llms.txt files, robots directives, and purge workflows.
3. Backups and rollback. You must maintain independent backups, rollback plans, source-code control, CDN configuration history, DNS change history, and disaster-recovery procedures.
4. End-user notices. You are responsible for privacy notices, cookie notices, consent, contractual disclosures, and customer-facing terms for your own website and end users.
5. Content legality. You must ensure Customer Content does not infringe intellectual property, violate privacy rights, mislead users or bots, or breach applicable law.
6. Incident handling. You must promptly investigate and remediate misconfigurations, exposed secrets, suspicious routing, unauthorized access, or security incidents related to your use of the Services.

Acceptable Use Restrictions

You must not, and must not permit any third party to:

• Use UpRender for domains, content, properties, or data you do not own or control
• Use the Services to deceive bots, search engines, AI systems, or platform reviewers through manipulative cloaking
• Route private, authenticated, regulated, or sensitive content without appropriate authorization
• Upload or route malware, phishing pages, credential-harvesting pages, spam, or illegal content
• Attack, overload, probe, scan, reverse engineer, scrape, or interfere with UpRender's systems
• Attempt to bypass plan limits, render quotas, rate limits, API limits, or billing controls
• Resell or white-label UpRender unless your plan or written agreement permits it
• Use the Services for safety-critical, emergency, life-support, medical diagnosis, or high-risk activities
• Violate export control, sanctions, anti-corruption, consumer protection, advertising, privacy, or platform rules

Plans, Subscriptions, Usage, and Billing

You authorize UpRender and its payment processors to charge the payment method you provide for subscriptions, renewals, upgrades, add-ons, overages, taxes, and other amounts due.

Refunds, Cancellation, and Plan Termination

11.1 General no-refund rule

Except as required by law or expressly stated in a signed Order Form, fees are non-refundable and non-creditable once charged.

11.2 Non-refundable situations

• No refund is owed because a search engine or AI system did not crawl, index, rank, cite, or display your content.
• No refund is owed for downtime caused by your DNS, CDN, middleware, redirects, robots.txt, or origin infrastructure.
• No refund is owed for unused time after cancellation, unused quotas, or your failure to disconnect integrations.

11.3 Cancellation

You may cancel a self-serve subscription through the dashboard. Cancellation stops renewal at the end of the current billing period. You are responsible for removing UpRender routing rules after cancellation.

11.4 Mandatory rights

Nothing in these Terms limits refund, cancellation, cooling-off, or warranty rights that cannot be waived under applicable law.

For full refund details, see our Refund Policy.

Support, Service Levels, and Availability

Support channels and response targets depend on plan. Published support targets are initial response targets unless a signed SLA states otherwise. They are not guaranteed resolution times.

UpRender may perform maintenance, updates, bot-list changes, and infrastructure migrations. We will use commercially reasonable efforts to reduce disruption. Unless your Order Form includes a specific uptime SLA and service-credit remedy, the Services are provided without uptime guarantees.

Data Protection, Security, Backups, and Data Damage

13.1 Security measures

UpRender uses commercially reasonable administrative, technical, and organizational safeguards. However, no service is completely secure. UpRender does not guarantee that unauthorized access, data loss, or service interruption will never occur.

13.2 Customer backups

13.3 Data damage

To the maximum extent permitted by law, UpRender is not responsible for loss, corruption, deletion, exposure, or damage to Customer Content caused by customer configuration, third-party services, crawler behavior, AI outputs, cache state, or use outside documented guidance.

Intellectual Property, Licenses, and Confidentiality

14.1 UpRender ownership

UpRender and its licensors own all rights, title, and interest in the Services, software, APIs, dashboards, designs, documentation, render infrastructure, algorithms, models, templates, workflows, trademarks, logos, and platform technology.

14.2 Customer ownership

You retain ownership of Customer Content. You grant UpRender a worldwide, non-exclusive, royalty-free license to host, cache, render, reproduce, transform, transmit, display, analyze, and otherwise process Customer Content as necessary to provide the Services.

14.3 Confidentiality

Each party may receive confidential information from the other. The receiving party will use reasonable care to protect confidential information and will use it only to perform obligations under these Terms.

Disclaimers, No Guarantees, and Limitation of Liability

16.1 Service disclaimer

To the maximum extent permitted by law, the Services and Rendered Output are provided "as is," "as available," and "with all faults." UpRender disclaims all warranties, whether express, implied, statutory, or otherwise.

16.2 No outcome guarantee

UpRender does not guarantee that any page will be crawled, indexed, ranked, cited, displayed, or used by Google, Bing, ChatGPT, Gemini, Claude, Meta, or any other search engine, AI system, bot, or platform.

16.3 Liability cap

To the maximum extent permitted by law, UpRender's total aggregate liability will not exceed the greater of USD $100 or the fees actually paid by you for the affected Services during the three (3) months immediately before the event giving rise to the claim.

Indemnification

You will defend, indemnify, and hold harmless UpRender from claims arising out of: (a) Customer Content; (b) your domains, websites, integrations, or proxy configurations; (c) your breach of these Terms; (d) your violation of law or third-party rights; (e) your use of AI outputs, metadata, schema, sitemaps, or llms.txt files; or (f) your clients, end users, or authorized users.

Suspension, Termination, and Survival

We may suspend or limit access immediately if we reasonably believe your use creates security, legal, operational, or reputational risk. You may stop using the Services and cancel your subscription as described in the dashboard. Upon termination, your right to use the Services ends and UpRender may disable rendering, purge caches, and revoke API access.

Governing Law, Disputes, and General Terms

Before filing a formal claim, each party agrees to try to resolve the dispute in good faith by providing written notice and allowing at least thirty (30) days for business-level discussions. Either party may seek injunctive or equitable relief to prevent unauthorized access, misuse of intellectual property, or other irreparable harm.

We may update these Terms from time to time. Material changes will be posted on this page. Continued use after the effective date means you accept the updated Terms.

Contact

Legal notices and questions about these Terms may be sent to: