Terms of Service

1. Service Description

FetchLens provides an AI Lens on your verified domain: an embeddable AI widget for site visitors and an optional MCP endpoint for AI clients (Cursor, Claude, ChatGPT, etc.). Lenses run capture flows that collect stated buyer intent and deliver leads to your CRM (HubSpot, Slack, webhook). FetchLens crawls your public sitemap to ground widget and MCP responses in your site content.

Legacy bot-detection analytics may remain available during transition but are not the primary product.

2. Eligibility

You must be a website owner or authorized operator to install FetchLens middleware on a site. By using FetchLens, you confirm you have the right to add server-side middleware to the site(s) you register.

To create a Lens, verify ownership via your Site Tag sent as an x-api-key header from your origin on the first authenticated middleware request. FetchLens may suspend Lens endpoints if domain ownership is disputed or verification is revoked.

3. Privacy Policy Disclosure

By installing FetchLens on your website, you agree to disclose the use of FetchLens in your site's privacy policy. You should inform your users that HTTP request metadata (User-Agent, URL path, country) may be processed by FetchLens for bot detection and security purposes. See our Privacy Policy for details on what data is collected.

If you deploy a Lens with an embeddable widget, you should also disclose that visitors interacting with the widget submit queries that are processed by FetchLens to generate AI-powered responses using your crawled site content.

4. API Keys and Security

API keys issued to you are confidential. You are responsible for keeping your API key and signing secret secure. Do not expose them in client-side code, public repositories, or browser-accessible locations. If you believe a key has been compromised, contact us immediately.

5. Acceptable Use

You agree not to:

• Use FetchLens to collect personal data beyond bot detection purposes
• Reverse-engineer, redistribute, or resell the bot detection intelligence
• Exceed rate limits or attempt to circumvent API security measures
• Use the service for any unlawful purpose
• Use Lens only on domains you own or are authorized to operate
• Use the MCP endpoint to circumvent content licensing or access restrictions
• Inject misleading content into system prompts that misrepresents your site

6. Data Ownership

Data generated by your Lens (widget sessions, MCP interactions, CRM delivery logs) belongs to you. Session and delivery logs are retained for 60 days, then automatically deleted. Your CRM remains the system of record for leads.

Crawled content derived from your site remains yours. Delete all Lens data at any time via the dashboard (delete property or delete Lens). FetchLens does not claim ownership of your crawled content.

7. Service Availability

FetchLens is provided on an "as is" basis. We strive for high availability but do not guarantee uninterrupted service. The middleware is designed to fail silently — if the FetchLens API is unreachable, your site continues to function normally with no impact on user experience.

8. Limitation of Liability

FetchLens is not liable for missed bot detections, false positives, data loss, or any indirect damages arising from use of the service. Bot detection is probabilistic by nature — we provide confidence levels but cannot guarantee 100% accuracy.

For Lens: FetchLens is not liable for incomplete crawls, outdated cached content, inaccurate AI-generated responses from MCP or widget queries, or content gaps caused by robots.txt restrictions, JavaScript-rendered pages, or sites exceeding the crawl page cap. AI responses are generated using third-party language models and may contain errors.

9. Termination

Either party may terminate service at any time. Upon termination, API keys are deactivated. Lens session and CRM delivery logs are deleted per our 60-day retention policy or immediately when you delete the property.

Upon Lens or property deletion, crawled content and D1 capture data are purged immediately. MCP endpoints and widget embeds stop serving responses.

10. Subscriptions and Billing

Certain features (production MCP, Sage voice, Teams Lens) may require a paid subscription. Billing terms, pricing, and tier details will be available on the billing page when subscriptions launch. Subscriptions are managed through Razorpay. Cancellation takes effect at the end of the current billing period.

11. Contact

For questions about these terms, contact us at contact@fetchlens.ai or contact@bubblspace.com.