BriteVerify

BriteVerify

BriteVerify scripts embed real-time email address validation on form fields. When a user enters an email, scripts transmit it to BriteVerify servers to verify deliverability and detect invalid or disposable addresses before the form submission is accepted.

Overview

BriteVerify is an email verification service (now part of Validity) that validates email addresses in real time as users type them into web forms. The verification check happens server-side, but it is triggered by client-side JavaScript that intercepts form field blur or submission events and dispatches the email address to BriteVerify's API before the form proceeds. This prevents invalid, mistyped, and disposable email addresses from entering marketing and CRM databases.

What This Script Does

The BriteVerify JavaScript integration performs the following on forms where it is installed:

  • Field monitoring: Attaches event listeners to email input fields, typically firing on blur (when the user moves focus away from the field) or on form submission
  • API transmission: When an email address is entered, it is transmitted to BriteVerify's verification API (api.briteverify.com) in a real-time request; the email address itself constitutes the request payload
  • Response handling: BriteVerify returns a verdict (valid, invalid, accept_all, unknown, disposable) that the integration uses to display inline validation feedback or block form submission
  • No persistent cookies: BriteVerify's core verification function does not set tracking cookies; it is a synchronous request-response verification call
  • Data logging: BriteVerify logs verification requests on its servers, meaning every email address entered into a verified form is transmitted to and logged by BriteVerify's infrastructure

Consent & Compliance

  • Consent Category: Functional
  • GDPR/ePrivacy: Each email address transmitted to BriteVerify for verification constitutes personal data processing under GDPR. The processing is functionally motivated (preventing form errors) and can be argued as necessary for the legitimate interest of maintaining data quality, but the transmission occurs before the user has completed any consent action. Disclose BriteVerify as a data processor in your privacy notice and ensure a signed DPA is in place.
  • ePrivacy: BriteVerify's verification mechanism does not set cookies, so the ePrivacy Directive cookie requirements do not directly apply.
  • CCPA: Email addresses transmitted for verification are personal information under CCPA. BriteVerify acts as a service provider; verify their CCPA compliance documentation.

Should You Block This Without Consent?

No. BriteVerify serves a direct functional purpose initiated by the user's own form interaction. It does not set tracking cookies or build behavioral profiles. However, because it transmits personal data (email addresses) to a third-party server, include it as a data processor in your privacy policy and ensure a DPA is executed with Validity/BriteVerify.

Visit website

Consent Categories

Functional

Also Known As

briteverify email validationbriteverify email verifyreal-time email checkvalidity briteverifyemail verification privacybriteverify cookies

Industries

Computers Electronics and TechnologyProgramming and Developer SoftwareBusiness and Consumer ServicesMarketing and Advertising

Tracked Domains (1)

briteverify.comFunctional

Frequently Asked Questions

Is consent required for BriteVerify?

Yes. BriteVerify transmits email addresses to its validation API in real time as visitors type, before the form is even submitted. Under GDPR, this constitutes processing personal data requiring a lawful basis. The ePrivacy Directive applies because the script intercepts form field events and sends data to external BriteVerify servers.

What data does BriteVerify collect?

BriteVerify's JavaScript intercepts form field events and sends each entered email address to its validation API in real time. The API checks deliverability, detects disposable and invalid addresses, and returns a verdict before the form proceeds. The script does not set persistent cookies but does transmit email addresses to Validity's servers.

How does ConsentStack manage BriteVerify?

ConsentStack identifies BriteVerify validation scripts and classifies them under the functional consent category. When functional consent has not been granted, ConsentStack blocks the script, meaning email validation occurs only after form submission via server-side methods. Once consent is granted, real-time client-side validation resumes.

Related Vendors

Google Maps
Google Maps
Google Maps is the dominant web mapping service used for embedded maps and location features on websites. Scripts load interactive map tiles, geocoding, and Places API functionality through the Maps JavaScript API. May set cookies to remember map preferences and manage API quota.
Google Search
Google Search
Google Search appears on websites through the Programmable Search Engine, enabling custom site-specific search functionality. Scripts load the search widget from Google's servers to render search bars and display results within the host website. Sends search queries to Google's index and may set cookies for search personalization and query history.
Google
Google
Google is the dominant provider of web analytics, advertising, and infrastructure tools. Scripts like Google Analytics, Tag Manager, Ads, and reCAPTCHA collect behavioral data, manage tag firing, serve targeted ads, and detect bots. Sets persistent cookies to track users and correlate activity across sites.
Microsoft Teams
Microsoft Teams
Microsoft Teams is a workplace communication and collaboration platform that can be embedded on websites for chat, meetings, and document sharing. Embedded widgets load from Microsoft's servers to enable real-time messaging, video calls, and file collaboration. Sets authentication and session cookies to verify participant identity and maintain connection state.
Apple Maps JS
Apple Maps JS
Apple Maps JS is Apple's JavaScript mapping framework for embedding interactive maps on websites. Scripts load map tiles, location pins, and routing data from Apple's MapKit servers to render navigable maps within web pages. Requires a MapKit JS token for authentication but does not set tracking cookies or collect behavioral analytics data.
Apple Business Chat
Apple Business Chat
Apple Business Chat enables direct customer messaging between websites and Apple's Messages app. Scripts load chat buttons and conversation interfaces that connect visitors to business support agents through iMessage. Sets minimal session cookies to maintain conversation context but does not track browsing behavior or collect analytics data.

Manage consent for BriteVerify

ConsentStack automatically detects and manages BriteVerify trackers so your site stays compliant with global privacy regulations.