Age gate data paths
Where WordPress age verification plugins send visitor data
An age gate can run before a cookie banner, because it is built to show first. Some plugins check age on your site and use a cookie to remember that the visitor passed. Other plugins send the visitor, and sometimes an ID photo, to an outside age-check service. On alcohol, cannabis, or adult sites, the visit itself can signal that someone is looking at age-restricted content. This table describes the setups below; your settings can change where requests go.
Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.
Scan your site for third-party requestsHow we group age verification plugins
We compare the age-gate setups named below. A plugin that hosts the overlay on your WordPress site and stores a remember-me cookie there is different from a plugin that loads an outside age-check script or asks for an ID photo at a vendor. The local setups described here do not document sending a date of birth to an outside age-check service. An overlay that shows first can still run before a cookie banner. We have not tested consent timing or how long age-check logs are kept.
Age verification plugins
No paid placement. Gate hosted on your site first, then outside age-check services, then plugins not yet reviewed. Names are alphabetical within each group.
| Plugin | Documented behavior | Documented service domains | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Age Gate This row covers Age Gate when the overlay asks for a date of birth or a yes/no confirm. The overlay scripts are hosted on your site. The local setups described here do not document sending a date of birth to an outside age-check service. The overlay can still show before a cookie banner. Consent timing is not tested here. | Gate hosted on your site | No outside age-check service documented for this setup. Other page requests are not covered. | Not assessed | Not tested |
| |
| Age Verify This row covers Age Verify when visitors confirm their age on your site. Passing the gate sets an age-verified cookie on your domain to remember that the visitor passed. That cookie is not a birth date. The local setups described here do not document sending a date of birth to an outside age-check service. Consent timing is not tested here. | Gate hosted on your site | No outside age-check service documented for this setup. Other page requests are not covered. | Not assessed | Not tested |
| |
| Easy Age Verify This row covers Easy Age Verify when the overlay is enabled. The overlay scripts are hosted on your site. The local setups described here do not document sending a date of birth to an outside age-check service. The overlay can still show before a cookie banner. Consent timing is not tested here. | Gate hosted on your site | No outside age-check service documented for this setup. Other page requests are not covered. | Not assessed | Not tested |
| |
| AgeChecker.Net This row covers AgeChecker.Net when checkout age check is enabled. The page loads a popup script from cdn.agechecker.net. Visitors who cannot be matched may be asked to upload an ID photo to AgeChecker.Net. That is a checkout check, not the same as a site-wide overlay that only stores a cookie on your domain. Consent timing is not tested here. | Outside age-check service | cdn.agechecker.net | Not assessed | Not tested |
| |
| AgeVerif This row covers AgeVerif when a site key is saved. The page loads an age-check script from www.ageverif.com as an early page script. That vendor call is not documented as waiting for a cookie banner. Date of birth or ID handling at the vendor is not assessed here. Consent timing is not tested here. | Outside age-check service | www.ageverif.com | Not assessed | Not tested |
| |
| Yoti We have not reviewed this plugin's age-check data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
|
What this table does and does not prove
This table describes the named age-gate setups. It does not show what loads on your site. Where no outside age-check service is documented, that applies only to the setup described. Other page requests are not covered. The local setups described here do not document sending a date of birth to an outside age-check service. An overlay that shows first can still run before a cookie banner. We have not tested consent timing, and we have not assessed how long age-check logs are kept. This table does not rate whether a visit is a sensitive-category signal. The site scan linked below checks for third-party requests; it does not access your WordPress database.
Documentation snapshot: Oct 1, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-age-verification-plugin-privacy