User responsibility
ParseShelf provides a dashboard and API for structured product-data workflows. Customers are responsible for deciding whether a planned use of exported data is lawful, permitted by applicable agreements and appropriate for their business context.
For sensitive deployments, route ParseShelf outputs through your normal legal, privacy and procurement review before the data enters a production system.
Allowed workflow shape
Use bounded jobs with explicit search URLs, category URLs, product URLs or ASIN lists. Keep job IDs, source URLs and export timestamps so a human can audit where a row came from.
Prefer listing_only for broad discovery and full_product for selected ASINs. This reduces unnecessary collection and keeps jobs easier to reason about.
Prohibited uses
Do not use ParseShelf for credential scraping, account takeover, paywall bypass, personal-data harvesting, abusive automation, security testing against third parties or any workflow that violates law or rights of others.
Do not present ParseShelf as a drop-in replacement for Amazon's licensed Product Advertising API content. It is an alternative workflow for product-data research and internal ecommerce operations.
Retention and deletion
Exports are retained according to the active plan and can be downloaded as JSONL, CSV, XLSX or Markdown while available. Teams should copy only the data they need into downstream systems and delete stale files when they are no longer useful.
If a workflow requires shorter retention, limited access or a written data-handling process, contact ParseShelf before scaling the job volume.
Production checklist
Start with one small input and compare the delivered fields with the report, catalog or pipeline you actually need.
Keep the job ID, source URL, mode and run date with downstream exports so operators and developers can audit the same result.