Frequently asked questions

The store domain, its ecommerce platform, detected technologies and installed-app signals, payment gateways, public generic business contact availability, the source the record came from, and the date it was last verified.

OpenData discovers candidate stores from public web indexes and scans public storefront pages itself, including archived public captures of those pages. It does not purchase or copy another vendor's proprietary database.

The verified records published today come from archived public captures dated September 2026 (4 Sep 2026 – 17 Sep 2026), and every record carries its own last-verified date — we date our data instead of calling it live. The operating target is a monthly refresh of the published database, with more valuable segments prioritised.

The index covers 23,984,359 scanned domains today, and 1,504,744 stores have been fully verified with detected technology so far. Verified means OpenData fetched the store's own storefront — directly or from an archived public capture — and detected at least one ecommerce technology on it; every verified record carries its source URL and the date it was last observed. The index grows monthly, and the counts on this site are read from the live database when each page is generated.

Shopify stores are indexed and verified first. The wider index also holds Squarespace and BigCommerce stores and additional platforms whose verification is in progress. WooCommerce and Magento detection is part of the same fingerprint library and rolls out with the scan queue.

An address the business itself publishes for contact — a generic mailbox like sales@ or info@, or the store's own named contact address. OpenData records only addresses published as business contacts; private addresses are excluded.

Public samples are deliberately redacted. A “🔒 Available” marker shows that a business contact is present in the full record without exposing the address in a public demo file.

Detection reads the signals a public storefront page actually exposes: platform markers, app code, payment buttons, analytics and CDN fingerprints. Apps that run only inside a store's admin, checkout-only extensions and email tools leave no storefront trace — no outside tool can see them, and we never guess. Treat every record as dated evidence, not a guarantee.

Yes — every paid pull exports to CSV plus a formatted Excel twin, billed per row: $4 per 1,000 full records, $1 per 1,000 technology-only records. That is the main way OpenData differs from incumbents that lock exports behind a $250/mo tier.

Not yet. CSV export is the launch interface; API access is on the roadmap for paid customers once the export product is stable.

Yes — the detection library includes fingerprints for GCash, OVO, DANA, PromptPay, QRIS, Xendit and Midtrans alongside global rails like PayPal, Stripe, Klarna and Afterpay. Detections are published per store only when a public page actually exposes the signal.

Submit the form on the Data Removal page with the store domain. Verified requests are completed within 48 hours and the domain is added to permanent suppression so it is not re-added.

It runs a narrower self-serve product, lower overhead and a focused store dataset rather than decades of web-wide history and enterprise features. The trade-off is explicit: less historical depth and a smaller index today, but a lower price, exports included, and a stronger focus on ecommerce stores.

There is no subscription billing. Every OpenData list is a one-time purchase in USD at the price shown on the pricing page — pay once, download the file, and re-download the latest refreshed file free for 60 days. Nothing renews and there is nothing to cancel.