Legal

Acceptable Use Policy

Last updated: September 2026

Allowed use

✓Extracting structured data from publicly accessible webpages you have a lawful basis to process.
✓Price monitoring, catalog enrichment, research datasets, and agent tooling built on public web data.
✓Batch workloads within your plan's rate limits, using the batch API where offered.
✓Responsible testing of the demo playground within its published rate limits.

Prohibited use

✕Processing export-controlled technical data or software, including anything subject to U.S. EAR dual-use controls.
✕Processing financial, medical, or other sensitive personal data — government IDs, health records, payment credentials, precise geolocation tied to individuals, children's data, or bulk datasets covered by rules such as the DOJ bulk sensitive-data regulation (28 CFR Part 202).
✕Accessing credentialed, paywalled, or otherwise access-controlled content; circumventing logins, CAPTCHAs, or technical protection measures beyond the service's own documented stealth tier (see CFAA, DMCA §1201).
✕Directing excessive concurrent request rates at target sites in a manner intended or likely to degrade the target's availability.
✕Reselling, sublicensing, or publicly exposing API keys; proxying the service to third parties outside your own products.
✕Abusing the demo playground or sandbox keys: automated scraping of the demo, credential stuffing, or denial-of-service behavior.
✕Using extracted data to facilitate wrongdoing: fraud, harassment, spam, or unlawful surveillance.
✕Violating the terms of the target websites in ways that expose Domsect infrastructure to claims — you bear that compliance responsibility (see ToS §6).

Data sovereignty: US-Soil routing — Zero-Cross-Border Guarantee

For requests submitted with "us_soil": true, DomSect guarantees that all data processing — DOM stripping, machine learning inference, and ledger logging — is performed entirely within servers physically located in the United States. Under no circumstances will payload data be failed over or transmitted to compute clusters outside the U.S. Offshore failover is strictly disabled: if US capacity is temporarily unavailable, the request fails fast with HTTP 5xx at 0 credits rather than rerouting overseas. Tasks without the flag are billed at standard rates and may be processed across regions.

Note: this guarantee covers DomSect's internal compute and processing infrastructure. Fetching the publicly accessible target URL you submit travels over the public internet and is subject to that target domain's hosting location and routing.

Enforcement ladder

Level 1 — Warning

First minor or unintentional violations: written notice with a remediation window.

Level 2 — Rate-limit / suspension

Repeated violations, abuse of shared resources, or unremedied warnings: keys throttled or suspended.

Level 3 — Termination

Serious violations — export-controlled or sensitive-data processing, key resale, or deliberate circumvention: immediate termination and key revocation.

We may skip levels for serious violations, and we cooperate with lawful requests from authorities regarding abuse. Serious violations may also trigger your indemnification obligations under ToS §10.

Report abuse

Seen misuse of the service or a leaked key? Write to [email protected] with details — we act on every credible report.