Terms & Policies — SiteRows

Last updated: May 2026

Terms of service

These terms govern your use of SiteRows (“we”, “us”, “our”) at siterows.com, including the web app, API, and PRO subscription. By creating an account or subscribing to PRO, you agree to these terms.

PRO subscription

SiteRows PRO is billed at $10 USD plus applicable tax per month. When you subscribe, the first $10 (plus tax) is charged immediately. After that, you are charged $10 (plus tax) every month on a recurring basis until you cancel.

Merchant of record

Our order process is conducted by our online reseller Paddle.com. Paddle.com is the Merchant of Record for all our orders. Paddle provides all customer service inquiries and handles returns.

Acceptable use

You agree to use SiteRows lawfully and responsibly. You must not use the service to attack, overload, or scrape targets in ways that violate applicable law, site terms, or robots.txt where enforced. SiteRows reserves the right to suspend or terminate any user account that engages in abusive, fraudulent, or excessive requests, or that otherwise threatens the stability or reputation of the service.

PRO API limits — POST /Scrape

PRO accounts are subject to the following limits on POST /Scrape requests. Values below are loaded from our live service policy and may be updated from time to time.

Setting	Description	PRO limit
`max_bytes_egress_per_day`	Maximum bytes sent back to the client per token per day for POST /Scrape.	2,147,483,648 (2 GB)
`max_bytes_egress_per_hour`	Maximum bytes sent back to the client per token per hour for POST /Scrape.	268,435,456 (256 MB)
`max_bytes_fetched_per_day`	Maximum bytes fetched (downloaded from target sites) per token per day for POST /Scrape.	8,589,934,592 (8 GB)
`max_bytes_fetched_per_hour`	Maximum bytes fetched (downloaded from target sites) per token per hour for POST /Scrape.	1,073,741,824 (1 GB)
`max_concurrent_fetches`	Maximum concurrent URL fetches during POST /Scrape (0 = server default/unlimited).	8
`max_fetch_workers_cap`	Maximum number of fetch workers used by the scraper for this tier.	12
`max_page_size`	Maximum allowed pagination page size (`limit`) for POST /Scrape.	2,000
`max_requests_per_day`	Maximum authenticated requests per token for POST /Scrape per day.	5,000
`max_requests_per_hour`	Maximum authenticated requests per token for POST /Scrape per hour.	1,000
`max_requests_per_minute`	Maximum authenticated requests per token for POST /Scrape per minute.	100
`max_requests_per_month`	Maximum authenticated requests per token for POST /Scrape per month.	100,000
`max_requests_per_second`	Maximum authenticated requests per token for POST /Scrape per second.	10
`max_requests_per_week`	Maximum authenticated requests per token for POST /Scrape per week.	20,000
`max_response_body_bytes_per_url`	Maximum bytes read from a single fetched URL response body.	10,485,760 (10 MB)
`max_response_json_bytes`	Maximum size of the JSON response body.	20,485,760 (20485760 bytes)
`max_result_cell_chars`	Maximum characters per returned cell value.	4,000
`max_result_columns`	Maximum result columns returned in a single POST /Scrape request.	500
`max_result_rows`	Maximum result rows returned in a single POST /Scrape request.	10,000
`max_sql_length`	Maximum SQL query character length accepted in a single POST /Scrape request.	12,000
`max_unique_hosts_per_request`	Maximum distinct hosts allowed in a single request.	10
`max_url_length`	Maximum URL character length accepted in a single POST /Scrape request.	3,000
`max_urls_per_day`	Maximum number of URLs fetched per token per day for POST /Scrape.	50,000
`max_urls_per_hour`	Maximum number of URLs fetched per token per hour for POST /Scrape.	5,000
`max_urls_per_minute`	Maximum number of URLs fetched per token per minute for POST /Scrape.	500
`max_urls_per_month`	Maximum number of URLs fetched per token per month for POST /Scrape.	1,500,000
`max_urls_per_request`	Maximum number of URLs accepted in a single POST /Scrape request.	250
`max_urls_per_second`	Maximum number of URLs fetched per token per second for POST /Scrape.	250
`max_urls_per_week`	Maximum number of URLs fetched per token per week for POST /Scrape.	250,000
`sql_timeout_sec`	Maximum time allowed for SQL execution (seconds) in a single POST /Scrape request.	30
`wall_clock_sec`	Maximum wall-clock time allowed for this endpoint request (seconds). For POST /Scrape and POST /Crawl, the server may return partial results when the cap is hit; other endpoints return HTTP 429.	30

PRO API limits — POST /Crawl

PRO accounts may use POST /Crawl subject to the limits below. Values below are loaded from our live service policy and may be updated from time to time.

Setting	Description	PRO limit
`allowed`	Whether POST /Crawl is allowed for this tier (false = server returns 403).	Yes
`contact_url`	Contact URL used for crawler identification (e.g., in User-Agent/robots).	https://github.com/ozerskym/WebQL
`default_timeout_sec`	Default per-request network timeout for crawler fetches (seconds).	60
`max_bytes_egress_per_day`	Maximum bytes sent back to the client per token per day for POST /Crawl.	4,294,967,296 (4 GB)
`max_bytes_egress_per_hour`	Maximum bytes sent back to the client per token per hour for POST /Crawl.	536,870,912 (512 MB)
`max_bytes_fetched_per_day`	Maximum bytes fetched (downloaded from target sites) per token per day for POST /Crawl.	17,179,869,184 (16 GB)
`max_bytes_fetched_per_hour`	Maximum bytes fetched (downloaded from target sites) per token per hour for POST /Crawl.	2,147,483,648 (2 GB)
`max_depth_cap`	Maximum crawl depth (levels) for POST /Crawl.	100
`max_fetch_workers_cap`	Maximum crawler fetch worker concurrency for this tier.	16
`max_pages_cap`	Maximum total pages fetched during POST /Crawl.	5,000
`max_pages_per_level_cap`	Maximum pages enqueued per depth level during POST /Crawl.	500
`max_requests_per_day`	Maximum authenticated requests per token for POST /Crawl per day.	100
`max_requests_per_hour`	Maximum authenticated requests per token for POST /Crawl per hour.	50
`max_requests_per_minute`	Maximum authenticated requests per token for POST /Crawl per minute.	5
`max_requests_per_month`	Maximum authenticated requests per token for POST /Crawl per month.	1,000
`max_requests_per_second`	Maximum authenticated requests per token for POST /Crawl per second.	1
`max_requests_per_week`	Maximum authenticated requests per token for POST /Crawl per week.	250
`max_response_bytes`	Maximum bytes read from a single crawler fetch response.	20,971,520 (20 MB)
`max_retries`	Maximum retries per URL fetch during crawl.	3
`min_interval_per_host_sec`	Minimum delay between requests to the same host (seconds).	0.35
`respect_robots_txt`	Whether the crawler respects robots.txt rules.	Yes
`retry_backoff_sec`	Base backoff used between retries (seconds).	1
`retry_http_status_codes`	HTTP status codes that trigger a retry during crawl.	429, 500, 502, 503, 504
`retry_jitter_ratio`	Random jitter ratio applied to retry backoff (e.g. 0.25 adds up to +/-25%).	0.25
`robots_fetch_timeout_sec`	Timeout for fetching robots.txt (seconds).	30
`robots_txt_max_bytes`	Maximum bytes read from a robots.txt file.	2,000,000 (2000000 bytes)
`wall_clock_sec`	Maximum wall-clock time allowed for this endpoint request (seconds). For POST /Scrape and POST /Crawl, the server may return partial results when the cap is hit; other endpoints return HTTP 429.	60

Support

For product support, contact us at support@siterows.com. For payment, billing, or refund questions handled by our merchant of record, you may also contact Paddle buyer support.

Privacy policy

SiteRows respects your privacy. This policy describes what we collect and how we use it when you use our website and create an account.

Account information

When you register, we store your email address and a bcrypt password hash. We do not store your password in plain text. Password verification uses industry-standard one-way hashing.

Payment information

PRO subscriptions are processed by Paddle, our payment provider and merchant of record. SiteRows does not collect or store your credit card, debit card, or other payment instrument details. Paddle handles checkout, tax, invoicing, and payment data in accordance with their own privacy policy.

Service usage data

When you use Scrape or Crawl, we process the URLs and queries you submit in order to run the service. We apply rate limits and abuse protections described in our terms. We do not sell your personal information.

Contact

Privacy questions or data requests: support@siterows.com.

Refund & cancellation policy

Cancelling PRO

You may cancel your PRO subscription at any time. Signed-in PRO users will see an Unsubscribe button in the app to cancel future billing. Alternatively, you may contact us at support@siterows.com to request cancellation.

When you cancel, your account reverts to the FREE tier unless you subscribe again.

Refunds

Refund requests for charges processed by Paddle may be submitted through Paddle buyer support or by contacting us at support@siterows.com. We will work with Paddle to resolve eligible refund requests in line with applicable consumer protection rules.

Billing disputes

Because Paddle is the merchant of record, payment receipts and tax invoices are issued by Paddle. If you do not recognize a charge, contact Paddle or us promptly so we can help resolve the issue before initiating a chargeback.