Privacy Policy

Message checks

JevShield processes the message text, sender name and email supplied by the website using the service. The public AI demo and authenticated API checks send these inputs to TypeSafe for spam classification when configured. Non-blocked messages may also be sent to DeepSeek for lead-intent evaluation, including the supplied business context. If a provider is unavailable, local rules may supply the result. Provider processing is separate from the message-storage setting in your dashboard; that setting does not disable AI-provider requests. The public demo uses hashed IP-based counters to enforce rate limits. API responses identify the engine used. Do not submit passwords, authentication codes, payment-card details or information unrelated to the check.

Accounts and providers

Account email, credential hashes, subscription identifiers and usage counters are stored in PostgreSQL for authentication, service delivery and quota enforcement. Our VPS hosts the application, Cloudflare provides the public network entry, and Neon provides PostgreSQL database infrastructure. These providers may process connection metadata and operational logs. Creem processes payments and associated purchase information; JevShield does not receive full card numbers.

Sign-in uses a secure, HttpOnly session cookie. Google provides basic profile information and a verified email when you choose Google sign-in. Resend processes your email address and verification code to deliver sign-in messages. It also delivers service notices when your detection quota is exhausted. We retain a per-account, per-quota-period notification record, including the recipient and notice, to prevent duplicate sends and retry temporary delivery failures.

Optional lead notifications and booking

When you configure a notification destination, high-intent checks send submitted contact details, intent signals and the website identifier to that destination. Message text is excluded by default and can be enabled separately. Email notifications go through Resend to your verified account email; channel notifications go to your selected webhook service. These providers may retain their own copies under their policies. Test notifications use synthetic contact details. JevShield retains the latest attempt time, service, HTTP status and error category for connection diagnostics, without a copy of the notification body.

A configured booking URL is returned to your integration and may be included in notifications. Visitors decide whether to open the booking provider and enter their details there. JevShield does not connect to calendars, reserve meeting slots or confirm meeting attendance. Your booking provider handles availability and calendar invitations. Explain these destinations in your own website privacy notice before enabling them.

Plugin updates

The JevShield plugin uses the WordPress.org update system; the latest ZIP is also available from jevshield.com. The separate legacy FormShield plugin continues to check public update metadata and download its updates from jevshield.com. Those legacy update requests do not include API keys, submitted messages or account email addresses. Our hosting and network providers receive ordinary connection metadata, including IP addresses, and the legacy updater identifies its plugin version. Automatic installation follows the website administrator’s WordPress settings.

Optional website analytics

With the same consent, Microsoft Clarity provides masked session recordings and heatmaps, and PostHog receives fixed behavior events and server-verified purchase conversions. A random browser identifier links consented checkout to payment. PostHog uses its US region. Unknown paid amounts are never estimated. Use Analytics preferences to stop optional collection.

With your permission, Google Analytics uses cookies to measure website visits, referring sites, page navigation and selected actions such as trying the demo, creating an API key and opening checkout. It receives browser and connection information to provide these reports. We do not send account email addresses, API keys, message content, URL query strings or authentication codes to Analytics. Advertising personalization and Google signals are disabled.

Analytics is not loaded before you choose Allow analytics. Rejecting it does not limit the service. Use Analytics preferences at the bottom of any page to change your choice.

Retention and requests

For authenticated API checks, account-isolated detection records contain the time, verdict, category, score, engine, reason, optional website hostname/form identifier, and integration-reported action. A classification reason may contain details derived from the submitted message. Full message text is not retained by default; an account owner may explicitly enable it for future checks. Turning off message storage clears existing text in the active database. Detection records are hidden after 7 days and deleted by hourly cleanup.