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:
Requirements:
For more information, visit borderage.com or contact us at [email protected]
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.
This plugin connects to the BorderAge API at pool.borderage.com for age verification services.
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:
hash('sha256', timestamp . site_id . secret_key)hash('sha1', result . user_id . age . secret_key)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 https://borderage.com/technology/
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.
Data processed by this plugin:
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:
For complete privacy information, see the BorderAge Privacy Policy.