YOUR INFORMATION
Privacy, in plain language.
This notice describes how the CrawlPatch operator handles information when you use this website. Use our private support channel to ask a privacy question, request access or corrections, or ask us to remove your information. You can contact us without an account. We may need to verify ownership before changing or releasing account data.
What we collect and why
Clerk handles account registration, verified email addresses, sign-in credentials and session cookies. CrawlPatch uses your Clerk user ID to keep your sites and saved reports associated with your account. We do not store your password in the CrawlPatch database.
For saved checks, we store the site name and origin, a public ownership-verification value, verified status, watched URLs, timestamps, check results, errors and activity history. Checks fetch public pages and robots.txt, and extract search-related signals such as titles, canonicals and indexing directives. URLs and extracted text can contain personal information; use public pages and avoid URLs with private tokens or personal data.
The public checker processes the URL you submit. Its recent baselines are kept in your browser’s local storage, up to 20 entries, rather than saved as your account history. Clear this website’s browser data to remove them. Infrastructure providers can still process request metadata.
We use a keyed hash derived from your IP address to enforce request limits. This is a security measure, not a promise of anonymity. Hosting and service providers may process IP addresses, request paths, browser information, error details and other operational logs to deliver and protect the service.
If you contact support, we store your topic, subject, messages, reply status and timestamps. A hash of your private link controls access; anyone holding the link can read and reply. We do not require an email address for support. The operator may review requests using OpenAI’s Codex, so messages may be processed by OpenAI for that support work. Do not send credentials or sensitive personal information.
Usage and reliability measurements
To understand whether the service is useful, we keep your opaque Clerk user ID and original account-creation time, the times of your first ownership verification and successful saved manual check, repeat-use timing, and a count of verified sites. Known operator test accounts are separated from customer measurements. We also keep aggregate counts of completed checks, failures and quota use. These measurement records do not include checked URLs, email addresses, ownership tokens, page content or full referrers; your saved reports remain separate as described above.
We reconcile signup timestamps from Clerk hourly and when an owner first uses a measured feature. We do not currently collect visitor attribution or store a marketing tracking cookie. Missing source and audience information stays unknown.
Email and payments
Automatic monitoring and application email are currently paused. When alerts are enabled in a future release, they will require opt-in and use your verified primary account email. Delivery records can include the recipient, subject, message content, provider message ID and delivery status. Suppression records help prevent further mail after a bounce or complaint.
Payments are disabled in this free preview. CrawlPatch does not collect a card or automatically convert your account to a paid plan. AI Visibility is planned and unavailable; customer pages and questions are not currently being sent to an AI visibility provider.
Services that help us operate
We use Cloudflare for hosting and security, Clerk for authentication, Convex for application data and scheduled jobs, and Resend for transactional email when enabled. OpenAI provides the operator’s AI-assisted support tools. Their processing and retention can differ from the application’s. Information may be processed outside your country. These links describe the providers’ own practices; this notice describes CrawlPatch’s use of your information.
We do not sell your information. We do not currently run advertising trackers or a marketing analytics SDK. If we add marketing visitor attribution or change the service’s data use, we will update this notice before using the new collection.
How long information stays
Saved check history, activity, email queue records and receipt metadata have a 30-day cleanup threshold. Daily maintenance removes bounded batches, so physical deletion may happen later. Site and account settings, including a target’s latest saved result, remain until removed or an ownership-verified removal request is handled. Suppression records remain to prevent unwanted email. Request-limit records have a three-day cleanup threshold.
Per-owner measurement records have a cleanup threshold of 366 days after account creation, or first observation while a timestamp is pending. Aggregate signup cohorts have a 400-day threshold and daily operating counters a 90-day threshold. Bounded maintenance can delay physical deletion. The original Clerk creation time may also remain with account settings until removal. Contact support for ownership-verified access, correction or deletion requests.
Support conversations become inaccessible 30 days after their last message, then enter daily cleanup. Browser baselines stay until replaced by newer entries or cleared by you. Our application cleanup does not promise immediate deletion from provider logs, backups or legally required records.
Your choices
You can remove watched pages and sites in your dashboard and manage sign-in details through account settings. Use support for access, correction, deletion and privacy questions. Account deletion is currently handled by the operator after verification; it is not an automatic self-service process. Keep your private support link to read our reply.