SnipBob
Get started

Privacy policy

Last updated: 2 November 2026

SnipBob’s service provider is responsible for the account and service information described here. Contact team@fetchfox.net with privacy questions.

Information we use

We store your email, profile name, project settings, authentication records and credit history to operate your account. Requests include submitted URLs, search terms and other operation parameters. Processing returns public content and associated information from the selected source platform. Operational records include the operation, result, timing and credit charge. Sign-in and contact-form throttling use short-lived hashed identifiers.

If you send an inquiry, your name, email, optional company, estimated usage and message reach our contact inbox so we can reply. Support messages and any diagnostic details you choose to share are used to investigate your question.

If you join the paid-plan waitlist, we store your email, the offers and currency you selected, your signup source and consent date to send launch updates. This does not create an account. Waitlist throttling uses short-lived hashed identifiers. Ask support to remove your email or withdraw consent at any time.

Why we process information

We use this information to authenticate you, deliver requested operations, meter credits, maintain reliability, prevent abuse, answer inquiries and meet applicable accounting or legal obligations. Where a legal basis is required, this includes providing the service you request, legitimate interests in operating and securing it, compliance with law, and consent where required. We do not sell your account information.

Providers and international processing

Hosting, database, cache, email and extraction providers receive information needed for their part of the service. URLs, search terms and related parameters may be sent to source platforms and extraction providers to fulfill your request. Our infrastructure includes AWS, MongoDB, Upstash and Resend. Provider processing may take place outside your country. Do not submit confidential content or information you lack permission to process.

For purchases processed by Dodo Payments, we retain billing identifiers, subscription status and transaction details needed to manage service access. We do not store your full payment card details. Dodo Payments is the merchant of record and handles payment-related personal data under its own privacy policy.

Retention

Waitlist entries expire 180 days after your latest signup unless you ask for removal sooner. Request logs are normally removed after 90 days. Short-lived processing caches remain until their configured expiry; Limits and freshness describes cache behavior. Account information remains until deletion is requested and processed. Credit and payment records may be retained where necessary for accounting, disputes or legal obligations. Existing backups and provider-held records follow their own retention schedules.

Your choices and rights

You can edit your profile, rotate your key and export your account data. Contact support to request access, correction, suspension or deletion. Depending on applicable law, you may also have rights to restrict or object to processing, withdraw consent or complain to a privacy regulator. We verify account ownership before acting on a request. Deletion revokes access, waits for in-flight work and removes identifying account data and request history, subject to necessary record retention.

Support chat and cookies

Authentication uses session and security cookies. When enabled, our Crisp support widget uses cookies to maintain a chat session and processes messages, contact details you provide, and browser and connection information. Chat cookies are limited to the current website hostname. We do not automatically send your account email or API key to Crisp. Do not paste passwords, keys or confidential content into chat. Crisp-held records follow its retention policies; contact support to request conversation deletion. See Crisp’s privacy policy.

Optional analytics and ad measurement

With your permission, Google Analytics measures public page visits, verified new signups, first successful requests and checkout outcomes. It receives static page titles and sanitized locations, not your email, name, account ID, API key, request inputs, extracted content or payment details. Account milestones and checkout events use a separate empty document so Google code cannot inspect account pages. We retain signup and dispatch timestamps in your account to prevent repeated milestone events; these are included in account exports and removed on erasure.

Analytics consent also allows a limited set of our campaign labels to be retained in your browser for up to 30 days. A separate, optional Google Ads measurement choice allows advertising cookies, click identifiers and conversion data to associate outcomes with an ad. Existing analytics permission does not grant this advertising permission. We do not enable personalized advertising or Google Signals. Other query parameters and fragments are excluded.

We do not load these Google tags before analytics permission, and browser Do Not Track or Global Privacy Control signals keep tracking off. Analytics preferences in the footer let you change or withdraw your choice; withdrawal clears the stored campaign attribution and our analytics cookies. Consent preferences last up to 180 days. Measurement is best effort: blockers, consent choices and interrupted requests can prevent delivery, so these reports are not the authoritative account ledger. Our operational account, security and support processing continues independently of optional analytics.

You can decline analytics or change your choice through Analytics preferences in the footer when analytics is configured. We remember that choice in your browser for up to 180 days. Analytics cookies are limited to this hostname and expire after up to 180 days without renewal. Withdrawing consent stops future collection and removes the analytics cookies we set; it does not automatically erase information already received by Google. Your browser’s Do Not Track or Global Privacy Control request keeps analytics off. See Google’s privacy policy. Essential sign-in cookies and the separate support-chat behavior described above are unaffected by this analytics choice.

Updates

We update this notice when our practices change and revise the date above. Material account-related changes will be communicated through the service or account email as appropriate.