Acceptable Use Policy

Crawlora provides hosted APIs that turn public web pages into structured JSON. This Acceptable Use Policy explains what Crawlora is built for, what it must not be used for, and how to report abuse or request a takedown. It applies to everyone who accesses the Service: account owners, team members, agents, and any system that calls Crawlora with your API keys.

This policy supplements the Terms of Service and the Privacy Policy. Read all three together. Where this policy and the Terms address the same topic, the Terms control on questions of contractual rights, liability, and billing; this policy controls on the specific use restrictions and reporting processes described below.

Crawlora cannot review every request in advance, so compliance is a shared responsibility. You decide which sources to target, which data to collect, and how you use the output. You are responsible for confirming that your specific workflow is lawful for your jurisdiction, industry, and data subjects before you run it at scale.

Crawlora is designed to collect information that is publicly accessible without logging in, creating an account, or defeating an access control. Our infrastructure — proxy routing, retries, browser rendering, browser clusters, and challenge-aware execution — is reliability tooling for reaching public pages dependably. It is not a mechanism for breaking into private systems, and you must not use it that way.

Many high-interest sources publish some pages openly and place others behind a login. Professional networks and social platforms such as LinkedIn and Instagram are common examples: a public profile or post that anyone can view without signing in is public, while anything that requires an account, a private session, or accepting platform terms as a logged-in user is not. Crawlora is only for the public surface. Collecting data that sits behind authentication, a paywall, or a private account is out of scope and prohibited, even when a workaround is technically possible.

If you are unsure whether a source is in scope, treat content that a signed-out visitor cannot reach as off limits, and confirm your own legal basis before collecting personal data from any source.

The list below is not exhaustive. We may treat conduct that is harmful, deceptive, or unlawful as a violation even if it is not named here, and we may decline or stop work that creates legal, security, abuse, billing, operational, or reputational risk.

Some public pages contain personal data. When you collect personal data through Crawlora, you act as the controller (GDPR) or business (CCPA/CPRA) for that processing. You are responsible for establishing a lawful basis — for example, one of the GDPR Article 6 bases — for providing any required notice to data subjects, and for honoring data-subject and consumer rights such as access, correction, deletion, and objection.

For the account, request, billing, configuration, and log data you generate by using Crawlora, Crawlora acts as your processor and service provider. How we handle that data is described in the Privacy Policy. Enterprise customers who need a data processing agreement can request one through the contacts below.

Crawlora does not sell personal information and does not use the personal data inside your Output for our own purposes. You must not submit special-category or otherwise sensitive personal data unless your plan or written agreement supports that use and you have a lawful basis for it. If you receive a data-subject or consumer request that concerns data Crawlora holds about your account, contact [email protected] and we will assist.

Crawlora aims to collect public data without degrading the sites it reads. We expect you to respect the access signals, robots directives, terms, and rate limits of the sources you target, and to review them before collecting at scale. Responsibility for honoring those signals for a given workflow sits with you, because you choose the targets and the volume.

Crawlora applies its own rate limits, credit weights, throttling, caching, and normalization to keep usage sustainable for both you and the sources. Do not attempt to evade these controls. We may slow, queue, throttle, block, or suspend traffic — including individual API keys — when usage creates operational, legal, security, or abuse risk to Crawlora or to a source site.

Crawlora publishes its own crawler directives at /robots.txt, which welcome well-behaved search and AI crawlers while keeping private surfaces out of scope. We ask that you extend the same courtesy to the sites you collect from.

If you believe Crawlora is being used in a way that violates this policy, or that data about you was collected or is being used unlawfully, tell us and we will investigate. You do not need an account to file a report.

Send reports to [email protected]. To help us act quickly, include the information below. We acknowledge reports within five business days and act on valid reports as appropriate — for example, by purging cached copies, blocking a source or workflow, restricting a feature, or suspending an account.

Crawlora respects the intellectual property of others and responds to valid notices under the Digital Millennium Copyright Act and comparable laws. If you believe content returned by Crawlora, or content hosted on a Crawlora property, infringes a copyright you own or control, send a written notice to [email protected].

If material you provided was removed or disabled in response to a DMCA notice and you believe that was a mistake or misidentification, you may send a counter-notice to [email protected] with your signature, identification of the removed material and its prior location, your contact information, and a statement under penalty of perjury that you have a good-faith belief the material was removed by mistake. We may restore the material as permitted by law. Crawlora may, in appropriate cases, terminate accounts of repeat infringers.

Crawlora retains account information, request metadata, logs, and billing records only as long as needed to operate and secure the Service, meet legal and accounting obligations, prevent abuse, and resolve disputes. Request inputs and Output may be cached transiently to improve reliability and to reduce repeat load on source sites; those caches expire automatically.

Specific retention periods, the categories of data we hold, and your choices are described in the Privacy Policy. When you close your account, we delete or de-identify the data we no longer need, subject to backups that age out on a rolling schedule and to any legal hold we are required to keep.

To request deletion of data Crawlora holds about your account, contact [email protected]. Some records — for example, billing and tax records — may be retained for the period the law requires even after a deletion request.

We may rate-limit, throttle, suspend, revoke API keys, block requests, or terminate accounts that violate this policy or that create legal, security, abuse, billing, operational, or reputational risk. Where practical we give notice and a chance to fix the issue, but urgent risks may require immediate action.

Crawlora may update this policy as the platform, sources, and applicable laws change. Material changes will be posted on this page, and may also be sent by email or shown in the console where appropriate. Continued use of Crawlora after the effective date of an updated policy means you accept the update.

Use the right mailbox for the relevant request. These mailboxes are monitored during business hours and are not guaranteed to be staffed around the clock.