Privacy Policy

Crawlora is operated by the business or individual responsible for providing the Crawlora service. For purposes of this Privacy Policy, "Crawlora," "we," "us," and "our" refer to the operator of the Crawlora website, APIs, Playground, console, documentation, and related services.

Questions about who operates Crawlora, requests for legal notices, and data protection inquiries can be sent to the Privacy or Legal mailbox below.

This Privacy Policy applies to Crawlora's website, hosted APIs, Playground, console, documentation, account workflows, billing workflows, support, and related services.

This Privacy Policy does not govern third-party websites, public pages, APIs, content, databases, platforms, or services that may be accessed, referenced, or returned through Crawlora APIs. Third-party sources may have their own privacy notices, terms, robots rules, contractual limits, and access requirements.

For account, billing, website, support, security, product analytics, and usage metadata, Crawlora generally acts as an independent controller.

For certain Customer Data processed on behalf of a business customer through the API, Crawlora may act as a processor or service provider, and the customer is responsible for its own privacy notices, lawful basis, processing instructions, and required rights.

Customers are responsible for having a lawful basis and any required permissions for the data they submit to Crawlora or request through Crawlora. If your organization needs a data processing agreement, request one from the Legal mailbox below.

The categories below describe information Crawlora collects directly from users, from account and billing providers, from browser and server activity, and from API processing. The exact data collected can depend on your plan, settings, API calls, endpoint configuration, and whether optional analytics or marketing tools are enabled.

When you call Crawlora APIs, we process information needed to receive, route, execute, meter, secure, debug, and return the request. This may include the endpoint name, submitted URLs or parameters, request body fields, headers where applicable, timestamps, request IDs, response status, credit usage, endpoint weights, rate-limit context, cache status, retry or fallback status, parser status, error details, and recent IP addresses.

Crawlora uses this information for service delivery, billing, usage metering, abuse prevention, rate limiting, monitoring, endpoint reliability, debugging, customer support, and operational security. API logs may include customer-submitted URLs, parameters, endpoint names, and other request context.

For debugging, Crawlora also keeps a short-lived request log containing the request method, path, query string, headers, and the request and response bodies, each capped at 16 KB. Authorization headers, cookies, API keys, tokens, secrets, and other sensitive fields are redacted before storage. Because response bodies carry public web data, they can contain personal data that appears on the source page. Raw request logs are deleted after 14 days.

Do not submit sensitive personal data to Crawlora unless you have a lawful basis, the relevant agreement supports that use, and you have confirmed that the endpoint and workflow are appropriate for the data.

Some API Output may include information from public web sources selected by the customer or endpoint configuration. Depending on the source and request, Output may include app metadata, product details, search results, creator profiles, video metadata, podcast metadata, business profile data, public reviews, public usernames, ratings, prices, availability, public descriptions, business contact information, public profile information, or similar public content.

Some public web data may contain personal data depending on the source and customer request. Customers are responsible for determining whether their collection, storage, processing, transfer, and use of such Output is lawful for their intended purpose.

Crawlora does not grant users rights to third-party websites, content, brands, databases, APIs, public pages, or personal data. You are responsible for respecting applicable law, third-party rights, contracts, source-site terms, and your own privacy obligations.

Where privacy law requires a legal basis, Crawlora relies on the bases below depending on the context. Where consent is required, you may withdraw consent through available controls or by contacting us.

Crawlora uses cookies, local storage, session storage, and similar technologies for login sessions, API console authentication, CSRF and security controls, preferences, abuse prevention, analytics, product usage measurement, and marketing attribution.

Essential cookies and storage are used to operate the website, console, and account workflows. Google Analytics (traffic measurement) and Microsoft Clarity (session replay and heatmaps) are optional. They load only after you choose Accept analytics in the cookie prompt, and not at all if you decline or ignore it. You can change your choice at any time with Cookie settings in the site footer. If you withdraw consent after accepting, Crawlora stops both tools, clears their cookies, and reloads the page. Your choice is stored in your browser's local storage. Clarity masks on-page text and form inputs, and API key fields are masked explicitly; once you accept, signed-in console sessions are linked to your account ID, not your email address.

Separately, Crawlora sets two first-party cookies that record the site or campaign that first brought you to Crawlora, so that a later sign-up can be attributed to its source. They last 90 days and are not shared with Google or Microsoft. There is no separate Cookies page, so the core cookie information is included here.

Crawlora uses credit-based usage and billing workflows for paid plans. The pricing page and console describe public plan information, included credits, endpoint usage, and billing controls where available.

Crawlora uses Stripe as its payment processor. Stripe collects and processes payment details under its own terms and privacy policy, and Crawlora does not store full payment card numbers.

Crawlora may store billing metadata such as plan, subscription status, invoice status, billing email, payment provider customer ID, tax metadata, failed payment status, credits, endpoint usage, and account-level billing state.

Referrals. If you use the referral program, we record your referral code, which account referred which, the referral's status, and the bonus credits rewarded. We use this to grant rewards and to reverse them if the qualifying invoice is refunded or disputed.

Monitors. If you create a monitor, we store the page or sitemap URL, schedule, URL patterns, webhook URL and signing secret, and the result, detected changes, and delivery status of each check. We send requests to the webhook URL you provide, and we may email the account owner when webhook deliveries keep failing.

AI assistant connections. When you authorize an AI assistant or other client through OAuth, we store the authorization, including the client's identity and the tokens we issue, so it can act on your account until you revoke it in the console. The client receives the Output of the requests it makes, and its own privacy policy governs what it does with that data.

Logo Link and free tools. Logo Link requests and free-tool runs are handled like API requests: we process the domain or URL requested, a client identifier where one is used, and technical data such as the IP address to return the result, enforce limits, and prevent abuse.

Datasets. Datasets that Crawlora compiles from public web sources can include publicly available information about individuals, such as public profile details. To ask for a record to be corrected or removed, write to the Privacy mailbox, or use the abuse and removal process in the Acceptable Use Policy.

Crawlora shares information with vendors that help operate the Service, including cloud hosting, database and storage, authentication, payment processing, email delivery, analytics, monitoring and logging, customer support, and fraud or abuse prevention providers.

Service providers and subprocessors process information only for service-related purposes and under applicable contractual obligations. The providers you are most likely to encounter are listed below. This is a summary by function, not a complete subprocessor register; hosting and infrastructure providers are described by category.

Crawlora may share information with service providers and subprocessors, payment providers, organization or team administrators where team account features are used, professional advisors where necessary, and other parties with your consent.

Crawlora may also share information to comply with law, respond to lawful requests, enforce the Terms, prevent abuse, protect users or the Service, investigate security incidents, collect amounts owed, or support a business transfer.

We do not sell personal information for money. If we ever use advertising or analytics tools in a way that is considered "sharing," targeted advertising, or sale under applicable privacy laws, we will provide required notices and choices.

Information may be processed in countries where Crawlora, infrastructure providers, payment providers, authentication providers, support tools, analytics tools, or other service providers operate. Those countries may have privacy laws that differ from the laws in your country.

Where required, Crawlora uses appropriate safeguards for international transfers. Crawlora does not offer a specific hosting region, transfer mechanism, or data residency guarantee under this Privacy Policy; ask the Privacy mailbox below if your organization has a residency requirement.

Crawlora retains information for as long as needed to provide the Service, maintain accounts, support billing and tax records, debug and secure the platform, prevent abuse, resolve disputes, comply with legal obligations, and improve reliability. Retention may be longer where needed for legal, security, accounting, abuse prevention, backup, or dispute reasons.

Crawlora uses reasonable technical and organizational safeguards appropriate to the Service. These may include TLS in transit, access controls, API key protection, restricted administrative access, logging and monitoring, rate limiting and abuse detection, backup controls, and credential rotation practices where applicable.

No internet service can guarantee absolute security. You are responsible for protecting your account, sessions, API keys, credentials, and systems that call Crawlora. Contact security@crawlora.net if you believe your account, API key, or Crawlora data may be at risk.

Depending on your location and relationship with Crawlora, you may have rights to access data, correct data, delete data, export or receive a copy of data, object to processing, restrict processing, withdraw consent, opt out of marketing, opt out of sale, sharing, or targeted advertising where applicable, appeal certain decisions where applicable, and lodge a complaint with a privacy authority.

You can ask for your account to be deleted from Account settings in the console. Deletion requests are reviewed, and once one is approved your account is deleted after a 72-hour grace period, during which you can cancel the request. Any active subscription is cancelled when the request is approved. For other privacy requests, write to privacy@crawlora.net. Crawlora may verify your identity before responding. Some data may be retained where required or permitted for legal, billing, tax, accounting, security, abuse prevention, backup, or dispute reasons.

California and some US state residents may have rights to know or access personal information, delete personal information, correct inaccurate personal information, opt out of sale, sharing, or targeted advertising, limit use of sensitive personal information, appeal certain decisions, and receive non-discriminatory treatment for exercising privacy rights.

Crawlora does not sell personal information for money. If Crawlora uses targeted advertising or other tools that are considered sale or sharing under applicable law, Crawlora will provide required notices and choices.

Users in the EU, UK, and EEA may have rights under GDPR or UK GDPR, including access, rectification, erasure, restriction, portability, objection, withdrawal of consent, and complaint to a supervisory authority.

The legal bases table above explains the bases Crawlora may rely on for different processing activities. For data protection inquiries, including questions about representatives under GDPR or UK GDPR, write to the Privacy mailbox.

Crawlora is not directed to children and is not intended for users under 16 or the minimum age required by applicable law. Crawlora does not knowingly collect children's personal data. If you believe a child provided personal data to Crawlora, contact privacy@crawlora.net.

Crawlora may use automated systems to authenticate API calls, calculate credits, apply rate limits, detect abuse, classify errors, monitor infrastructure, and prioritize retry or fallback behavior. These systems are used for service operations, security, reliability, billing, and abuse prevention.

Crawlora does not describe these systems as making legal or similarly significant decisions about individuals.

If Crawlora is involved in a merger, acquisition, financing, restructuring, bankruptcy, or sale of assets, information may be transferred as part of that transaction, subject to appropriate protections.

Crawlora may update this Privacy Policy from time to time. Material changes may be posted on the website, console, docs, or sent by email where appropriate.

Continued use of Crawlora after the effective date of an updated Privacy Policy means the updated policy applies to your use of the Service from that effective date.

Use the contacts below for the relevant request. These mailboxes are not monitored 24/7.