Protect your WordPress pages by verifying visitor age via the BorderAge API using hand gesture recognition.

brekam

Borderage Core protects your WordPress site by requiring age verification for visitors. Unlike traditional ID-based systems, BorderAge uses hand gesture recognition – no selfie, no ID document required.
Features:
<ul>
<li>Protect entire site or specific pages</li>
<li>Hand gesture verification (no facial recognition)</li>
<li>Visitor account system for returning users</li>
<li>Unified login form (WordPress account first, then visitor account fallback)</li>
<li>Credit alert system – Automatic email notifications when credits run low</li>
<li>Rate limiting – Prevent brute force verification attempts</li>
<li>Login brute-force protection – Rate limiting on account login attempts</li>
<li>Health logging system – 24-hour internal monitoring with export</li>
<li>Statistics dashboard – View verification metrics (total, adults, minors)</li>
<li>Customizable verification page styling</li>
<li>Multi-language support (EN, FR, DE, ES)</li>
<li>Developer tools – Testing utilities and data reset</li>
<li>Debug mode with logging and export functionality</li>
</ul>
Requirements:
<ul>
<li>BorderAge API credentials (site_id and site_secret_key)</li>
<li>Credits for new verifications (existing verified users can still access)</li>
<li>Pretty permalinks enabled in WordPress Settings</li>
</ul>
For more information, visit <a href="https://borderage.com/" rel="nofollow ugc">borderage.com</a> or contact us at <a href="contact@needemand.com" rel="nofollow ugc">contact@needemand.com</a>
<h3>Admin Pages</h3>
Borderage Core provides 8 configuration tabs accessible via BorderAge in the WordPress admin menu:
 Tab 
 Description 
 Purpose
 Configuration 
 API credentials and basic settings 
 Enter your site_id, secret_key, enable/disable plugin, set debug mode
 Protection 
 Protection mode and protected pages 
 Choose to protect all pages or specific pages, configure rate limiting
 Appearance 
 Form styling customization 
 Customize verification page colors, button styles, and layout
 Statistics 
 Verification metrics dashboard 
 View total verifications, adult/minor breakdown, monthly statistics
 Guide 
 User documentation 
 Complete usage guide and setup instructions
 Developers 
 API documentation 
 Technical reference for developers integrating with BorderAge
 Debug 
 Health logs viewer 
 View system health logs, export debug information
 Dev Tools 
 Testing utilities 
 Reset visitor data, clear logs, testing functions (debug mode only)
Navigation: Click on the “Borderage” menu item in WordPress admin to access all tabs. Each tab provides a specific set of configuration options and tools.
<h3>External Services</h3>
This plugin connects to the BorderAge API at <code>pool.borderage.com</code> for age verification services.
<h4>When data is transmitted</h4>
<ol>
<li>During age verification – When a visitor clicks “Verify now”</li>
<li>Credit balance check – When admin pages load to display remaining credits</li>
<li>Statistics retrieval – When the Statistics dashboard loads to display verification metrics</li>
<li>Health logging – Internal monitoring events (not transmitted to external API)</li>
</ol>
<h4>Data transmitted</h4>
 Data 
 Description 
 Purpose
 site_id 
 Your site identifier 
 Identify your site
 user_id 
 SHA256 hashed visitor ID 
 Pseudonymized visitor tracking
 age 
 Age threshold 
 Verification requirement
 hash 
 Security signature 
 Request validation
 is_over_age 
 Boolean (true/false) 
 Age verification result
 result_hash 
 Callback validation hash 
 Verify callback authenticity
 reference_id 
 Attempt reference for rate limiting 
 Track verification attempts
Hash Generation:
<ul>
<li>Credits check: <code>hash('sha256', timestamp . site_id . secret_key)</code></li>
<li>Callback verification: <code>hash('sha1', result . user_id . age . secret_key)</code></li>
</ul>
Privacy note: This plugin and the BorderAge API store only pseudonymized data: a hashed visitor ID and a boolean indicating whether the age threshold was met. Zero Personally Identifiable Information (PII) is stored or transmitted – no names, emails. Unlike competitors, BorderAge uses no biometric fingerprinting, no selfies, and no ID documents. This eliminates any risk of personal data leaks, as such data simply doesn’t exist in our system.
For more details about BorderAge’s technology and privacy-first approach, visit <a href="https://borderage.com/technology/" rel="nofollow ugc">https://borderage.com/technology/</a>
<h4>Service links</h4>
<ul>
<li>Privacy Policy: <a href="https://borderage.com/politique-confidentialite/" rel="nofollow ugc">https://borderage.com/politique-confidentialite/</a></li>
<li>Technology information: <a href="https://borderage.com/technology/" rel="nofollow ugc">https://borderage.com/technology/</a></li>
<li>Service website: <a href="https://borderage.com/" rel="nofollow ugc">https://borderage.com/</a></li>
</ul>
Terms of Service: BorderAge’s Terms of Use are negotiated individually between each client and Needemand (creator of the BorderAge SaaS). Contracts are established on a case-by-case basis rather than using a generic public ToS. Please contact BorderAge to discuss your specific terms.
<h3>Privacy Policy</h3>
Data processed by this plugin:
<ol>
<li>Visitor verification status – Stored in browser cookies to remember verified visitors (expires after 24 hours)</li>
<li>Visitor accounts – Optional accounts for returning visitors (email, hashed password)</li>
<li>Verification logs – Records of verification callbacks for debugging (24-hour retention)</li>
<li>Health logs – Internal system monitoring logs (24-hour retention, JSON format)</li>
</ol>
Data sent to the external BorderAge API:
Only pseudonymized data is transmitted and stored: a hashed visitor ID (SHA256) and a boolean indicating whether the age verification was successful (is_over_age: true/false). Additional metadata includes site_id, age threshold, and security hashes for validation.
What makes BorderAge different:
<ul>
<li>Zero PII storage – Neither this plugin nor the BorderAge API store any Personally Identifiable Information</li>
<li>No biometric fingerprint – No biometric data is collected, stored, or transmitted</li>
<li>No data leak risk – Impossible to leak personal data that doesn’t exist</li>
<li>Privacy by design – Hand gesture verification without selfies, ID documents, or facial recognition</li>
<li>Rate limiting protection – Prevents brute force verification attempts</li>
<li>Automatic cleanup – Verification tokens and logs expire after 24 hours</li>
</ul>
For complete privacy information, see the <a href="https://borderage.com/politique-confidentialite/" rel="nofollow ugc">BorderAge Privacy Policy</a>.

Alternatives to Borderage Core

Top alternatives