Privacy policy

1. Scope and contact

This policy covers Better Fetch's website, accounts, billing, hosted MCP server, API, browser sessions, and ready-made tools. Better Fetch is operated from Queensland, Australia. Privacy requests can be sent to privacy@betterfetch.co.

2. Information we collect

• Account: email address, account identifiers, login and security records.
• Billing: plan and subscription status. Stripe processes card details; Better Fetch does not store complete card numbers.
• Acquisition: first landing path, referring host, and campaign parameters.
• Service usage: request outcome, strategy, transport, timing, retries, response size, credit use, and whether optional routing was used.
• Support: messages and information you choose to provide.
• Optional website analytics: with your consent, device, browser, page, campaign, and interaction information collected through Google Analytics and first-touch attribution.

The business event ledger intentionally does not store requested URLs, page content, request headers, cookies, API keys, IP addresses, or browser-session names.

3. Retrieval and browser-session data

Better Fetch must transiently process target URLs, headers you supply, and retrieved content to fulfil a request. Synchronous results are returned to the caller rather than placed in the business event ledger. Asynchronous job payloads and results expire after roughly 24 hours.

When you use a named browser session, cookies and localStorage may be kept in an isolated browser profile and an encrypted portable snapshot. Session metadata and snapshots expire after the idle period shown on your plan, or earlier when you clear the session.

4. How we use information

• Provide, secure, meter, support, and improve the service.
• Authenticate users and connected clients.
• Process subscriptions, prevent fraud, and enforce quotas.
• Measure activation, reliability, capacity, and service economics.
• Communicate operational, security, billing, and product information.
• Meet legal obligations and enforce our terms.

5. Service providers and transfers

Better Fetch uses service providers including Fly.io for compute, Supabase for authentication and database services, Stripe for billing, Resend for email, Oxylabs for optional network routing, Google Analytics for website measurement, and Slack for internal operating alerts. They process information under their own terms and may operate in Australia, the United States, Europe, or other regions.

We do not sell personal information.

6. Retention

• Privacy-safe request events: up to 90 days.
• Product lifecycle events: up to 180 days.
• First-touch attribution: while the account is active or until an applicable deletion request is completed.
• Attribution, account, billing, and security records: while the account is active and as reasonably needed afterwards for legal, fraud, and accounting obligations.
• Browser-session state: until cleared or expired under the plan's idle-session policy.
• Asynchronous fetch jobs: approximately 24 hours.

7. Your choices and rights

You may revoke keys, disconnect OAuth clients, clear browser sessions, manage billing, reject optional analytics, change that preference, and stop using the service from the dashboard. You may request access, correction, export, restriction, objection, or deletion where applicable. Some records may be retained when required by law or necessary for security and dispute resolution.

See the security page for technical controls and disclosure instructions.

Change analytics preference.

8. Changes

We may update this policy as the service changes. Material changes will be dated here and, when appropriate, communicated through the service or by email.