Who we are
CommaScale, LLC operates CrawlerLogs (a CommaScale product). We are based in the United States (Pittsburgh, PA area). Controller for account and service data: CommaScale, LLC.
CrawlerLogs is operated by CommaScale, LLC. This policy explains what we store and why. Last updated September 13, 2026.
See also Privacy first and Terms. Contact: Contact or inquiries@commascale.com.
CommaScale, LLC operates CrawlerLogs (a CommaScale product). We are based in the United States (Pittsburgh, PA area). Controller for account and service data: CommaScale, LLC.
Each accepted crawl event stores IP, User-Agent, URL, and Timestamp. Query strings are stripped from the URL before storage.
That is enough to check a crawler claim (UA plus published IP ranges) and to know when a path was last hit. Events are not joined into human visitor sessions or marketing profiles. The IP is typically a crawler or edge address, retained for verification — it can still be regulated personal data, so we call this data-minimized, not “no PII.”
No cookies or session IDs on the visit event, no request bodies, form data, auth headers, query strings, URL fragments, or full server-log dumps. No Google Search Console OAuth.
The Worker path captures at the edge. The JS tag sends the same four fields only when the tag runs; it does not match Worker coverage for all bots.
Signup stores first name, last name, email, and a password hash. We use that to run the workspace: sign-in sessions, domain tokens (ingest / browser / read API), team invites, settings, and — when enabled — billing and transactional email (resets, receipts).
Session cookies keep you signed in (including a shared cookie across www/app on .crawlerlogs.com in production). Those cookies are for your account session, not for tracking site visitors via CrawlerLogs.
If you create API or MCP read keys, those keys can read crawl data for domains on your account. You are responsible for who holds them.
Free workspaces: rolling 7 days of visible visit data. Paid / upgraded domains may keep a longer window as described in-product. We do not sell visit data.
You can ask us to delete an account or specific visit data via Contact. We will process reasonable requests; some records may remain in backups for a limited time or where we must keep them for security, abuse prevention, or law.
We use infrastructure providers to run the product (notably Cloudflare for Workers, DNS, and edge delivery; database hosting for stored events). When billing is enabled, Stripe processes payments — card data is handled by Stripe, not stored as full card numbers in CrawlerLogs.
Public demo views may show sample demonstration rows separate from your live ingest. Sample data is for product walkthroughs.
We do not sell personal data. We share data with processors needed to run the service, if required by law, or to protect CommaScale, users, or the public from fraud or abuse. Teammates you invite can see workspace data you grant them.
Privacy questions or deletion requests: Contact, inquiries@commascale.com, or commascale.com.
We may update this policy as the product changes. The “Last updated” date will change when we do. Continued use after an update means you accept the revised policy.