At a glance: we handle account and billing details, API inputs and outputs, usage records, and website and device data to provide, bill for, secure, and improve the service. We do not sell personal information; we share it where needed to operate the service or meet legal obligations. Retention varies by data type and purpose; this policy does not specify a single deletion deadline. You can contact us about access, correction, or deletion requests.
1. Scope of this policy
This policy applies to information we collect through the AnyCrawler website, product console, API, documentation, support channels, and related operational systems. It covers information that identifies you directly, information linked to your account or workspace, and technical or usage data that becomes associated with a request. It also covers content you submit to the service, such as target URLs, crawl parameters, search queries, screenshot settings, metadata flags, and related request payloads.
This policy does not rewrite the privacy practices of the third-party websites you ask us to access. When you use AnyCrawler to fetch or render a page on the public web, the operator of that destination site may apply its own cookies, logging, bot detection, or access controls. Your use of AnyCrawler does not override those third-party rules, and you remain responsible for making sure your workflow is lawful and appropriate for the sites and data you target.
2. Information we collect
We collect information in three main categories: information you provide directly, information created by operating your account and workspace, and information generated when requests move through the product. The exact fields can vary by feature, but in practice the categories are consistent across the service.
Information you provide directly
When you sign up, contact us, or buy a paid plan, we may collect your name, email address, organization name, billing country, tax or invoicing details, and the content of support messages or sales conversations. If you use the console, we may also collect account profile settings, team membership details, and authentication data needed to secure access to your workspace.
Product and request data
When you use AnyCrawler, we may collect target URLs, crawl methods such as render or fetch, render options, screenshot options, search queries, response metadata, usage totals, request identifiers, timestamps, latency measurements, credit consumption, browser or fetch mode selection, and diagnostic events related to errors or retries. If a feature returns markdown, metadata, links, media, screenshots, or search results, we may store or log portions of those outputs where needed to deliver the response, support replay or debugging, investigate abuse, or operate caching and billing systems.
Website, device, and analytics data
Like most software services, we may automatically receive IP address, approximate location derived from IP, browser type, device characteristics, referrer information, pages viewed, session timing, and similar analytics or security signals when you visit the website or sign in to the product. We use this information to keep the site available, understand traffic patterns, improve navigation, and identify suspicious or abusive activity.
3. Why we use information
We use information first to provide the product you asked for. That includes creating and securing accounts, authenticating API access, routing crawl and screenshot jobs, operating render cache-aware responses, measuring credits used, generating invoices, and showing request logs, usage views, or playground results in the console. Without these uses, the core product would not function.
We also use information to operate the service responsibly. That includes detecting fraud, enforcing rate limits and concurrency controls, investigating security incidents, preventing abuse, identifying degraded infrastructure, and improving reliability and response quality. We may also use account and usage information to communicate service notices, respond to support requests, send transactional messages, and improve product documentation or onboarding flows.
4. How crawl, search, render, and screenshot data is handled
AnyCrawler processes live web content at your direction. That means the service may temporarily retrieve page HTML, rendered output, extracted markdown, metadata, links, media references, screenshots, or search results in order to return the response you requested. Depending on the feature and the system state, parts of that request or response may be cached, logged, or retained for a limited period to support service delivery, duplicate-request efficiency, incident response, and abuse prevention.
We do not claim ownership of the content you instruct the service to access, and we do not represent that every requested target is appropriate to crawl, capture, reproduce, or store. You are responsible for the inputs you send, the sites you target, the legal basis for your workflow, and the way you use the outputs. If your usage involves personal data, regulated data, or restricted web properties, you are responsible for determining whether AnyCrawler is appropriate for that use.
5. When we share information
We do not sell personal information. We may share information with service providers or contractors when that is reasonably necessary to operate, secure, support, or bill for the service. When we do, we aim to limit the shared information to what is needed for the relevant business purpose and to keep the use of that information tied to providing services for AnyCrawler.
We may also disclose information when required by law, regulation, court order, or other valid legal process, and when we reasonably believe disclosure is necessary to protect the rights, property, or safety of AnyCrawler, our users, the public, or the integrity of the service. If our business is involved in a merger, financing, asset sale, or acquisition, information may be transferred as part of that transaction subject to ordinary confidentiality and continuity protections.
6. Data retention
We retain information for as long as needed to operate the service, comply with legal obligations, resolve disputes, enforce agreements, and maintain reasonable business and security records. Different categories of data are retained for different periods. Account and billing records typically last longer than transient technical logs because they are tied to payments, taxes, and audit history. Request logs, cached responses, screenshot assets, and diagnostic traces may have shorter or feature-dependent retention windows based on storage cost, operational need, and abuse-prevention requirements.
If you close your account, we may continue to retain limited information where required for legitimate business purposes, compliance, fraud prevention, or recordkeeping. We may also de-identify or aggregate certain service data so it can no longer reasonably be linked to a person or specific workspace and use that information for analytics, capacity planning, or service improvement.
7. Security
We use administrative, technical, and organizational measures designed to protect information from unauthorized access, loss, misuse, or alteration. Those measures may include authentication controls, network protections, access restriction, logging, and operational review. No internet service can promise absolute security, and you should also protect your own credentials, API keys, and downstream systems because shared responsibility is part of any API workflow.
8. International use and transfers
This site does not currently publish a jurisdiction-specific data transfer framework or a country-by-country operations list. If our operational footprint, customer base, or legal obligations require more specific transfer disclosures, we may update this policy with additional detail at that time.
9. Your choices and rights
Depending on where you live, you may have rights to access, correct, delete, or limit the use of certain personal information, or to object to certain processing activities. You may also be able to request a copy of certain information associated with your account. We may need to verify your identity before acting on a request, and we may decline or limit a request when the law allows us to do so, such as when complying would interfere with security, legal obligations, or the rights of others.
You can also make practical choices directly inside the product by controlling what you submit, how you configure requests, whether you enable render cache-aware behavior, and which team members have access to your workspace and API keys. For formal privacy requests, contact us at support@anycrawler.com.
10. Children and sensitive data
AnyCrawler is designed for developers, technical teams, and business users. It is not directed to children, and we do not intend to collect personal information from children through the ordinary operation of the service. The product is also not marketed as a specialized environment for highly sensitive regulated data. If your use case involves sensitive categories of personal information, health data, student data, or similarly regulated data, you should evaluate that use carefully before sending it through the service.
11. Changes to this policy
We may update this policy as the product, law, and operational setup evolve. When we do that, we will update the published date on this page and, where appropriate, provide additional notice inside the product or through account communications. Your continued use of AnyCrawler after an updated policy takes effect means the updated version will apply to future use of the service.
12. Contact us
Questions, requests, or concerns about this policy can be sent tosupport@anycrawler.com. If you are contacting us about a specific workspace, billing issue, or privacy request, include enough detail for us to identify the relevant account and respond efficiently.
Questions about your data?Contact privacy support.