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.
Is BriteVerify GDPR compliant?
BriteVerify typically loads functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So BriteVerify can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads BriteVerify, not on BriteVerify itself.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
briteverify.comFunctionalbriteverify.com is a functional domain operated by BriteVerify, used to run site features like chat, video, embeds, and preferences.
Frequently Asked Questions
Related Vendors
Manage consent for BriteVerify
ConsentStack automatically detects and manages BriteVerify trackers so your site stays compliant with global privacy regulations.