Transparency
Automation, bots, and HTTP identity
Effective date: May 1, 2026
FormReceipt uses real browser automation to run authorized tests against contact forms that customers configure in their accounts. This page explains how to recognize our traffic in logs and how we handle bot checks and CAPTCHAs.
Who operates this traffic?
Automated requests originate from FormReceipt’s worker infrastructure on behalf of a logged-in customer who configured monitoring for a specific public URL. Tests use synthetic data and include clear labeling (for example in the message body: “FormReceipt test … Not a real lead.”).
User-Agent and request headers
We send a Chromium-compatible User-Agent with an explicit product token and a machine-readable suffix pointing to this policy page and our contact address. We also set transparency headers on automated requests.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 FormReceiptBot-Run/0.0.1 (+https://formreceipt.com/bot; contact=support@formreceipt.com)
Examples of headers you may see:
- From: support@formreceipt.com
- X-FormReceipt-Bot: run (scheduled or manual test) or probe (form discovery)
- X-FormReceipt-Bot-Info: https://formreceipt.com/bot
- X-FormReceipt-Purpose: authorized_form_monitoring_test
- X-FormReceipt-Run-Id, X-FormReceipt-Public-Test-Id, X-FormReceipt-Workspace-Id, X-FormReceipt-Form-Id (for correlating logs with a specific test — IDs are internal/customer-scoped, not end-user PII)
Purpose and scope
Traffic is limited to testing customer-configured forms for deliverability and regression monitoring. We do not crawl the open web for indexing; we load configured pages and interact with the intended form.
CAPTCHAs, bot checks, and rate limits
We do not solve CAPTCHAs or bypass bot challenges. If a page requires manual verification, our run may end with a blocked or challenged outcome. If you believe FormReceipt traffic should be allowlisted for your environment, contact us and we can discuss options that respect your security policies.
Abuse, mistaken blocking, and contact
If you see traffic that claims to be FormReceipt but looks abusive, or you need to block or adjust handling for a legitimate reason, email support@formreceipt.com with timestamps, URLs, and request headers (including X-FormReceipt-Public-Test-Id if present). We take misuse of the service seriously and investigate reports.
Operators using FormReceipt
Configure only targets you own or are authorized to test. Our Terms of Service require this; misconfigured targets can inconvenience third parties and may violate law or site policies.