[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fGgmadKganNp40rChfD8rGiUmWD7VkCXIrM_oczv_JQA":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"brekam","https:\u002F\u002Fprofiles.wordpress.org\u002Fbrekam\u002F",1,0,100,30,94,"2026-05-20T01:25:44.010Z",[13],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":7,"num_ratings":7,"last_updated":20,"tested_up_to":21,"requires_at_least":22,"requires_php":23,"tags":24,"homepage":30,"download_link":31,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":32,"fetched_at":33},"borderage-core","Borderage Core","0.1.0","\u003Cp>Borderage Core protects your WordPress site by requiring age verification for visitors. Unlike traditional ID-based systems, BorderAge uses \u003Cstrong>hand gesture recognition\u003C\u002Fstrong> – no selfie, no ID document required.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Protect entire site or specific pages\u003C\u002Fli>\n\u003Cli>Hand gesture verification (no facial recognition)\u003C\u002Fli>\n\u003Cli>Visitor account system for returning users\u003C\u002Fli>\n\u003Cli>Unified login form (WordPress account first, then visitor account fallback)\u003C\u002Fli>\n\u003Cli>Credit alert system – Automatic email notifications when credits run low\u003C\u002Fli>\n\u003Cli>Rate limiting – Prevent brute force verification attempts\u003C\u002Fli>\n\u003Cli>Login brute-force protection – Rate limiting on account login attempts\u003C\u002Fli>\n\u003Cli>Health logging system – 24-hour internal monitoring with export\u003C\u002Fli>\n\u003Cli>Statistics dashboard – View verification metrics (total, adults, minors)\u003C\u002Fli>\n\u003Cli>Customizable verification page styling\u003C\u002Fli>\n\u003Cli>Multi-language support (EN, FR, DE, ES)\u003C\u002Fli>\n\u003Cli>Developer tools – Testing utilities and data reset\u003C\u002Fli>\n\u003Cli>Debug mode with logging and export functionality\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Requirements:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>BorderAge API credentials (site_id and site_secret_key)\u003C\u002Fli>\n\u003Cli>Credits for new verifications (existing verified users can still access)\u003C\u002Fli>\n\u003Cli>Pretty permalinks enabled in WordPress Settings\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For more information, visit \u003Ca href=\"https:\u002F\u002Fborderage.com\u002F\" rel=\"nofollow ugc\">borderage.com\u003C\u002Fa> or contact us at \u003Ca href=\"contact@needemand.com\" rel=\"nofollow ugc\">contact@needemand.com\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Admin Pages\u003C\u002Fh3>\n\u003Cp>Borderage Core provides 8 configuration tabs accessible via \u003Cstrong>BorderAge\u003C\u002Fstrong> in the WordPress admin menu:\u003C\u002Fp>\n\u003Cp>  Tab\u003Cbr \u002F>\n  Description\u003Cbr \u002F>\n  Purpose\u003C\u002Fp>\n\u003Cp>  Configuration\u003Cbr \u002F>\n  API credentials and basic settings\u003Cbr \u002F>\n  Enter your site_id, secret_key, enable\u002Fdisable plugin, set debug mode\u003C\u002Fp>\n\u003Cp>  Protection\u003Cbr \u002F>\n  Protection mode and protected pages\u003Cbr \u002F>\n  Choose to protect all pages or specific pages, configure rate limiting\u003C\u002Fp>\n\u003Cp>  Appearance\u003Cbr \u002F>\n  Form styling customization\u003Cbr \u002F>\n  Customize verification page colors, button styles, and layout\u003C\u002Fp>\n\u003Cp>  Statistics\u003Cbr \u002F>\n  Verification metrics dashboard\u003Cbr \u002F>\n  View total verifications, adult\u002Fminor breakdown, monthly statistics\u003C\u002Fp>\n\u003Cp>  Guide\u003Cbr \u002F>\n  User documentation\u003Cbr \u002F>\n  Complete usage guide and setup instructions\u003C\u002Fp>\n\u003Cp>  Developers\u003Cbr \u002F>\n  API documentation\u003Cbr \u002F>\n  Technical reference for developers integrating with BorderAge\u003C\u002Fp>\n\u003Cp>  Debug\u003Cbr \u002F>\n  Health logs viewer\u003Cbr \u002F>\n  View system health logs, export debug information\u003C\u002Fp>\n\u003Cp>  Dev Tools\u003Cbr \u002F>\n  Testing utilities\u003Cbr \u002F>\n  Reset visitor data, clear logs, testing functions (debug mode only)\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Navigation:\u003C\u002Fstrong> Click on the “Borderage” menu item in WordPress admin to access all tabs. Each tab provides a specific set of configuration options and tools.\u003C\u002Fp>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>This plugin connects to the \u003Cstrong>BorderAge API\u003C\u002Fstrong> at \u003Ccode>pool.borderage.com\u003C\u002Fcode> for age verification services.\u003C\u002Fp>\n\u003Ch4>When data is transmitted\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\u003Cstrong>During age verification\u003C\u002Fstrong> – When a visitor clicks “Verify now”\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Credit balance check\u003C\u002Fstrong> – When admin pages load to display remaining credits\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Statistics retrieval\u003C\u002Fstrong> – When the Statistics dashboard loads to display verification metrics\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Health logging\u003C\u002Fstrong> – Internal monitoring events (not transmitted to external API)\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Data transmitted\u003C\u002Fh4>\n\u003Cp>  Data\u003Cbr \u002F>\n  Description\u003Cbr \u002F>\n  Purpose\u003C\u002Fp>\n\u003Cp>  site_id\u003Cbr \u002F>\n  Your site identifier\u003Cbr \u002F>\n  Identify your site\u003C\u002Fp>\n\u003Cp>  user_id\u003Cbr \u002F>\n  SHA256 hashed visitor ID\u003Cbr \u002F>\n  Pseudonymized visitor tracking\u003C\u002Fp>\n\u003Cp>  age\u003Cbr \u002F>\n  Age threshold\u003Cbr \u002F>\n  Verification requirement\u003C\u002Fp>\n\u003Cp>  hash\u003Cbr \u002F>\n  Security signature\u003Cbr \u002F>\n  Request validation\u003C\u002Fp>\n\u003Cp>  is_over_age\u003Cbr \u002F>\n  Boolean (true\u002Ffalse)\u003Cbr \u002F>\n  Age verification result\u003C\u002Fp>\n\u003Cp>  result_hash\u003Cbr \u002F>\n  Callback validation hash\u003Cbr \u002F>\n  Verify callback authenticity\u003C\u002Fp>\n\u003Cp>  reference_id\u003Cbr \u002F>\n  Attempt reference for rate limiting\u003Cbr \u002F>\n  Track verification attempts\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Hash Generation:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Credits check: \u003Ccode>hash('sha256', timestamp . site_id . secret_key)\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Callback verification: \u003Ccode>hash('sha1', result . user_id . age . secret_key)\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Privacy note:\u003C\u002Fstrong> This plugin and the BorderAge API store only pseudonymized data: a hashed visitor ID and a boolean indicating whether the age threshold was met. \u003Cstrong>Zero Personally Identifiable Information (PII)\u003C\u002Fstrong> is stored or transmitted – no names, emails. Unlike competitors, BorderAge uses \u003Cstrong>no biometric fingerprinting\u003C\u002Fstrong>, \u003Cstrong>no selfies\u003C\u002Fstrong>, and \u003Cstrong>no ID documents\u003C\u002Fstrong>. This eliminates any risk of personal data leaks, as such data simply doesn’t exist in our system.\u003C\u002Fp>\n\u003Cp>For more details about BorderAge’s technology and privacy-first approach, visit \u003Ca href=\"https:\u002F\u002Fborderage.com\u002Ftechnology\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fborderage.com\u002Ftechnology\u002F\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Service links\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Privacy Policy:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fborderage.com\u002Fpolitique-confidentialite\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fborderage.com\u002Fpolitique-confidentialite\u002F\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Technology information:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fborderage.com\u002Ftechnology\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fborderage.com\u002Ftechnology\u002F\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Service website:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fborderage.com\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fborderage.com\u002F\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Terms of Service:\u003C\u002Fstrong> 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.\u003C\u002Fp>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Data processed by this plugin:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Visitor verification status\u003C\u002Fstrong> – Stored in browser cookies to remember verified visitors (expires after 24 hours)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Visitor accounts\u003C\u002Fstrong> – Optional accounts for returning visitors (email, hashed password)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Verification logs\u003C\u002Fstrong> – Records of verification callbacks for debugging (24-hour retention)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Health logs\u003C\u002Fstrong> – Internal system monitoring logs (24-hour retention, JSON format)\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Data sent to the external BorderAge API:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>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\u002Ffalse). Additional metadata includes site_id, age threshold, and security hashes for validation.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What makes BorderAge different:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Zero PII storage\u003C\u002Fstrong> – Neither this plugin nor the BorderAge API store any Personally Identifiable Information\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No biometric fingerprint\u003C\u002Fstrong> – No biometric data is collected, stored, or transmitted\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No data leak risk\u003C\u002Fstrong> – Impossible to leak personal data that doesn’t exist\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Privacy by design\u003C\u002Fstrong> – Hand gesture verification without selfies, ID documents, or facial recognition\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rate limiting protection\u003C\u002Fstrong> – Prevents brute force verification attempts\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Automatic cleanup\u003C\u002Fstrong> – Verification tokens and logs expire after 24 hours\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For complete privacy information, see the \u003Ca href=\"https:\u002F\u002Fborderage.com\u002Fpolitique-confidentialite\u002F\" rel=\"nofollow ugc\">BorderAge Privacy Policy\u003C\u002Fa>.\u003C\u002Fp>\n","Protect your WordPress pages by verifying visitor age via the BorderAge API using hand gesture recognition.",167,"2026-03-18T15:14:00.000Z","6.9.4","6.2","8.1",[25,26,27,28,29],"adult-content","age-gate","age-verification","compliance","hand-gesture","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fborderage-core.zip",null,"2026-04-16T10:56:18.058Z"]