Who is responsible
Crawlhub is operated by [Legal operator name to be added], [Business address to be added], [Country to be added]. This operator is responsible for the personal information described in this notice. Contact hello@crawlhub.ai about privacy or your account.
This notice covers the website, account area, support and public proxy checker. Public proxy and scraping API products are not enabled yet. An internal, admin-only request generator uses a connected provider as described below.
Information we process
| Information | Purpose and handling |
|---|---|
| Account details | Your email address, account name, optional display name, authentication records, account timestamps and pending email changes. Authentication is handled by Supabase; support staff do not need your password. |
| Saved setup and preferences | Your timezone and the proxy or API drafts you choose to save, including queries, target URLs, country, protocol and session preferences. |
| Support correspondence | Your email, subject, message, submission reference and delivery/follow-up status. A message is stored in the application and sent to our support inbox. |
| Proxy checks | The proxy address, credentials if supplied, selected protocol, timeout and optional target URL are processed to run your check. The checker requests an IP-verification page and, if supplied, your target through the proxy. Proxy credentials are not written to the application database. |
| Internal request generator | For an authorized admin run, the target URL, options, supplied cookies and JavaScript are sent to ScrapingAnt for processing. Request bodies and responses are not saved in the application database. Saved drafts exclude cookies and JavaScript. |
| Security and operations | Network information needed to deliver requests and prevent abuse; salted network hashes and rate-limit counters; page paths, generic error categories and timestamps for fault reporting. Our client error reporter does not send form inputs, stack traces or URL query strings. |
Why we use it
We use account and draft information to provide the service you request. Support information lets us answer questions and investigate problems. Authentication, rate limiting and operational reporting help prevent misuse and maintain the service.
Where data-protection law requires a legal basis, we rely on providing the requested service or taking steps at your request, legitimate interests in security and reliable operation, and legal obligations where they apply. If we introduce processing that needs consent, we will ask before starting it.
We do not load advertising or audience-analytics scripts in the current application. Service messages and replies to support requests are not a marketing subscription.
Who receives information
| Information | Purpose and handling |
|---|---|
| ScrapingAnt | Processes requests from the internal admin-only generator, including selected target pages and any supplied cookies or JavaScript. The target receives the provider’s outgoing request. |
| Supabase | Account authentication, application database, private application backups and server-side processing. |
| Resend | Delivery of account confirmation, recovery, email-change, support and operational emails. |
| Website hosting and security | OpenAI Sites and its hosting infrastructure, including Cloudflare, deliver the public site and apply security checks. Infrastructure processes connection and request metadata. |
| Support inbox | Messages sent to hello@crawlhub.ai are handled through our email service and by the operator responsible for support. |
| Proxy and destination operators | A proxy check connects to the proxy you supply. Cloudflare’s verification endpoint and any target you request receive the outbound requests and the exit IP. Do not put personal data, credentials or access tokens into target URLs. |
Service providers can process information in countries outside your own. Contact us for the applicable processing locations and transfer arrangements. Where required, cross-border processing must use a recognized transfer mechanism and appropriate safeguards. We do not promise that all information stays in one country.
Retention and deletion
Account details and saved drafts remain while your account is active. The account deletion flow removes your authentication identity, account record, drafts and account notifications. It does not automatically delete earlier support correspondence or infrastructure logs.
Application snapshots are kept on a seven-day rolling schedule. Expired snapshots are removed by the scheduled cleanup. Infrastructure and email-provider logs are separate from these application snapshots.
Support records are kept while needed to handle the request, related follow-up, disputes or legal obligations. Operational records are kept for service maintenance and security investigation. Contact us to request deletion; we will assess what can be removed and explain any records that must remain.
Internal generator records contain the account ID, request identifier, a settings hash, status, credit count and elapsed time. Records older than seven days are cleaned during later requests. Raw requests and response bodies are not stored as execution history.
Checker rate-limit counters expire with their time window and are cleaned during later checks. Proxy input and results remain in your browser’s page memory until the page is reloaded or closed. Copying working proxies or downloading results creates a copy on your device that you control.
Your choices and rights
You can edit your profile, change your email, download draft configurations, sign out and delete your account from Settings. For other access, correction, deletion or portability requests, email hello@crawlhub.ai. We may need to confirm your identity before disclosing or changing account data.
Depending on the law that applies, you may also ask us to restrict processing, object to processing based on legitimate interests, or withdraw consent where we rely on it. These rights have conditions and exceptions. You may complain to your local data-protection authority. We respond within the time required by applicable law.
Security and updates
Access to internal account and support tools is restricted. Connections to account and support services use HTTPS. Keep your account credentials and proxy credentials private; do not include them in support messages.
We will update this notice when our processing changes. Material changes will be explained through the site or an appropriate account communication. See the cookies and browser storage notice for device storage.