What we collect
We collect account email addresses, authentication and security records, product-search queries, requested markets and shop restrictions, extraction requests, source URLs, results, usage records, support messages and billing records. Our payment processor handles payment-card information; datawebot. receives payment status and transaction references rather than complete card details.
Product research and connected apps
When an authorized app calls our product-research tools, we process the tool arguments needed for that request. Searches send the query, requested market and optional shop restrictions to configured search-data providers. Offer lookups also use the requested product identifier and provider-issued product reference. We do not send these providers your datawebot. account email, access token or full conversation. Product research does not access private marketplace accounts or place orders. Avoid including passwords, payment details or other private information in search queries.
Tool results are returned to the app you connected. That app handles the results under its own terms and privacy policy. Source images and seller links can point to third-party domains; opening them or loading images may share your network information with those domains.
Measurement
Public pages use website analytics and experience-measurement providers to understand visits and improve the experience. The workbench sends limited analytics events for sign-in, extraction and purchase milestones. These events exclude email addresses, source URLs, run IDs and extracted results. The operations dashboard does not load measurement scripts. Your browser or network settings may block measurement.
When configured, server-side agent and API usage events are sent to product-analytics providers: sign-in steps, which agent or app connected, tool calls with result counts, errors and timing, the country of the request, the domain of the email address, and a random install ID that the setup script keeps on your computer. These events exclude email addresses, API keys, raw IP addresses and, by default, search text. Requests without an install ID are grouped by a salted hash of the IP address that changes daily. Search-text analytics requires a separate operator setting and a disclosure review before activation.
How information is used
We use information to provide and secure the service, retrieve requested product data, process payments where applicable, calculate usage, support customers, diagnose failures and improve reliability. We do not sell personal information or use connector conversations to train models.
Storage and providers
We use service providers for cloud hosting and application storage, email delivery, search data, checkout and payment processing, website analytics and experience measurement, and product analytics. These providers process information needed for the purposes described above. Information may be processed outside Singapore, including in the United States, where our providers operate, subject to their safeguards and applicable law. Contact [email protected] for information about the providers relevant to your use of the service.
Retention and choices
Completed extraction outputs are normally available for seven days. Product-search queries and results are processed for the response and are not saved as a product-search history in our account database. Search-data providers may retain requests and results under their own retention policies. One configured provider specifies a standard 31-day search-data retention period; other providers may use different periods. Contact [email protected] for provider-specific retention details. Authentication records have operational expiry periods, including ten-minute sign-in requests, one-day OAuth access tokens and thirty-day sliding refresh grants; revocation can end access sooner.
Account and usage records are retained while needed to operate the account and enforce usage limits, until deletion is requested, subject to security, dispute and legal-retention requirements. Transaction, security, support and provider-managed analytics records can require longer retention for those purposes. Contact [email protected] to request access, correction or deletion, or details of applicable retention. Some records may need to be retained. Disconnecting an app revokes its access; it does not by itself delete account records or copies already received by that app.
Contact
datawebot. is operated by Revenue Scaler Pte. Ltd. in Singapore. Privacy questions can be sent to [email protected].