LeadShield privacy notice

Updated October 29, 2026

Moosh Works operates LeadShield. This notice covers LeadShield account connections, message screening, site rules, and blocked-message reports.

Information we process

Account records contain your email address, a password hash, and the sites you can access. When you connect an app, we record its name, callback address, requested permissions, and connection status. Passwords and connection tokens are stored as one-way hashes.

Connected forms can send names, email addresses, phone numbers, message text, company details, custom form fields, and site identifiers. Screening also uses technical details such as country, timezone, browser information, IP address, referring page, and time spent filling the form. The fields available depend on the form and integration.

How we use and share information

We use this information to screen messages, apply site rules, prevent abuse, deliver accepted inquiries where configured, and let authorized users review blocked messages.

• Cloudflare hosts LeadShield and stores its account, policy, and message records.
• When intent screening is enabled, TypeSafe receives message text and relevant form context. This can include company, website, town, service, timezone, country, and custom fields. Personal information entered in those fields may be included.
• Configured destinations, such as HighLevel, HubSpot, email through Resend, or an operator notification channel, receive the information needed for that integration.
• When you connect ChatGPT or another app, LeadShield returns the screening results, site rules, or report records that the app requests within your account's access.

The website receiving an inquiry and any connected app also have their own privacy practices. Their copies are separate from records held by LeadShield.

Previews and payments

The message-screening tool previews a decision. It does not save the message as a lead, deliver it to a customer, or process a payment. If intent screening is enabled, it can still send the message context to the classifier described above. Any price shown in the preview is an estimate, not a charge.

Retention and account access

Stored lead and blocked-message records are currently marked for deletion after 180 days. A scheduled cleanup removes expired records in batches, so removal may occur after that date. Account records and saved site rules have no automatic expiry.

Access tokens expire within one hour. A connection can renew access for up to 30 days before a new sign-in is needed. Expired connection records are removed by scheduled cleanup. Revoking a connection prevents further use of its tokens; it does not delete existing lead records or copies already returned to another app.

Site webhook keys let a connected workflow screen messages for one site. These keys are stored as one-way hashes and have no automatic expiry. Replacing or revoking a key stops its use. Changes to the account's access also invalidate existing keys.

Cookies and security

The connection page uses a temporary cookie to tie the sign-in form to your connection request. It expires after 10 minutes. LeadShield limits sign-in attempts and checks account permissions before returning protected records or saving site rules.

Questions and requests

Email support@mooshworks.com to request access, correction, deletion, or connection revocation. Include the site involved and the type of request. We may need to verify your authority before changing or disclosing records. If you submitted a form to another business, you can also contact that business about its copy.