Review the controls and evidence behind ParseShelf before you put an Amazon data workflow into production.
ParseShelf processes the Amazon URLs, product URLs, keywords or ASINs you submit and the normalized rows returned by a job. Authentication uses Google OAuth when configured or a one-time email link; the email address is used for account access and delivery notifications.
The free first-input step does not ask for an email or card. A sign-in is requested only when the downloadable job is ready to start.
Dashboard access is session-authenticated. API jobs require a Bearer API key and the public API rejects unauthenticated job creation. Keep keys on a server-side integration, rotate them when a team member or vendor changes, and never expose them in browser code.
Job results remain tied to the authenticated workspace. Public Market Intelligence is read-only observed data; saved actions and exports belong in the authenticated workflow.
The Pricing page is the current source of truth for plan retention: Free 7 days, Starter 30 days, Pro 60 days and Growth 90 days. Download only what the workflow needs and delete stale downstream copies.
To request account or job-data deletion, email info@parseshelf.com with the account address and job IDs. We confirm the scope before acting; legal, billing and abuse-prevention records may require separate handling.
Funnel telemetry stores bounded product events for activation analysis. URLs are reduced to safe paths, customer email addresses are not sent to analytics, and synthetic test traffic is marked and excluded from growth reporting.
Server-side funnel events are retained for 180 days by default and purged by the worker maintenance loop. Set PARSESHELF_FUNNEL_RETENTION_DAYS only within the documented 30 to 730 day bounds when a deployment needs a different operational window.
Every live intelligence surface labels observation dates, coverage and lower-bound semantics. Missing fields remain missing, partial rows are labeled, and unavailable or stale datasets use explicit states instead of invented values.
Customer jobs expose queued, running, succeeded, failed and partial-delivery states with row counts and export actions. Capacity can be limited by the available parser/proxy pool; the workspace quality banner is the source of truth for the current collection state.
The API contract, OpenAPI JSON, sample exports, acceptable-use guidance and extension privacy policy are public. A written procurement packet can be requested for a specific deployment and should be reviewed before a team scales volume.
ParseShelf does not publish SOC 2, ISO 27001, DPA or a subprocessors register on this page. Ask for the current documents if your procurement process requires them; no certification or contractual commitment is implied here.
Read the controls that apply to your workflow, then ask for the deployment-specific documents your process requires.
Public evidence - API contract: /docs/amazon-api/ and /amazon-api-openapi.json - Sample schema: /amazon-product-data-sample/ - Retention and pricing: /pricing/ - Acceptable use: /acceptable-use/ - Extension privacy: /amazon-scraper-chrome-extension/privacy/ Procurement request Email info@parseshelf.com with your use case, expected row volume, marketplaces and required documents. Do not send API keys or customer data in the first message.