Privacy Policy for the HPP Chrome Gateway

Who we are

Human Presence Protocol (HPP) is operated by Agile On Target LLC. Contact for privacy questions: privacy@humanpresenceprotocol.com.

These Chrome test pages are the public demo for the Chrome Gateway. They are not a claim that every relying website is production-ready. The iPhone app remains the prover. The HPP verifier remains the cryptographic authority.

Core privacy principle

HPP provides cryptographic evidence that a human was physically present at a device at the time an action was authorized. HPP does not prove identity merely because it proves presence. HPP does not store biometric templates.

The Chrome test page asks for one Boolean result: true or false for the claim human_presence. The page is architecturally not given biometric data, keys, location, date of birth, advertising identifiers, or a verifier session token.

What this Chrome path collects

On the test page

The static pages at /Dev/Chrome do not create accounts, do not set first-party cookies, and do not run analytics, advertising, or tracking pixels. They load only their own HTML, CSS, images, and the small HPP.verify() script.

If you click Verify Human, the page sends a same-origin message asking the extension for a Boolean. It does not read your browsing history. It does not receive a receipt.

In the Chrome extension, on your computer

The extension uses chrome.storage.local only. It does not use chrome.storage.sync. Local storage holds:

• Optional verifier settings that stay on this computer.

Those values stay on the device. They are not your name, email, or browsing history. Uninstalling the extension deletes them.

What the extension sends to the HPP verifier

When a participating page calls HPP.verify({ claim: "human_presence" }), the extension asks the allowlisted HPP verifier to create a short-lived relay slot, then shows a QR code for the HPP iPhone app. The QR payload is JSON of the form the iPhone app already scans:

• Verifier URL
• Site host (for example, humanpresenceprotocol.com)
• Protocol version
• Session duration
• Relay identifier
• Requested claim

The QR does not contain biometric data, Face ID templates, private keys, public keys, nonces minted by Chrome, signatures, or session tokens. Chrome does not mint HPP nonces. The iPhone app and the existing HPP verifier remain the cryptographic authority.

The extension then polls relay status. If the verifier response includes a session token, the extension strips that token before anything reaches the page. The page receives only whether verification succeeded.

What happens on the iPhone

Face ID or Touch ID is handled by Apple. HPP receives a pass or fail from the platform, not a biometric template. The Secure Enclave holds the private key. The verifier receives the minimum attestation material described in the product privacy policy: a public key that is not tied to your name or Apple ID, a one-use signature, a timestamp, and the site identifier.

What this Chrome path does not collect

• Name or real-world identity
• Email address, phone number, or Apple ID
• Location or GPS data
• Browsing history, page content, or form fields from the sites you visit
• Device fingerprinting for advertising
• Biometric templates (Face ID / Touch ID stay in the Secure Enclave)
• Date of birth
• Advertising identifiers
• Contacts, photos, or other on-device content

The extension does not sell data. It does not include advertising SDKs. It does not use the content script to scrape pages for any purpose other than receiving the page's HPP.verify() request and showing the verification panel.

Why Chrome permissions exist

How data is used

• Purpose. Answer one question: was a human present for this request?
• No secondary use. We do not use Gateway traffic for advertising, profiling, or sale.
• No cross-site tracking graph. A true result on one origin says nothing about another origin. The page SDK accepts results only from the same window and the same origin that asked.

A Boolean shown in the browser is a user-experience gate, not authorization by itself. A page script can forge a true in developer tools. Anything of value must be gated on the operator's own server against the HPP verifier. This policy discloses that limit so it is not mistaken for a hidden data collection.

Retention

• Extension settings: until you change them or uninstall the extension.
• Verifier challenges: purged on the HPP verifier after 300 seconds (5 minutes), as described in the product privacy policy.
• Session tokens: expire and are purged on the verifier. The Chrome page is never given the token.
• Attestation receipts on the verifier: chain-linked cryptographic records with no name, email, or biometric template. See the product privacy policy.
• GitHub Pages request logs: this static site is hosted by GitHub. GitHub may process ordinary web request metadata under GitHub's privacy policy. We do not run a separate analytics pipeline on these pages.

Third-party services

• GitHub Pages hosts these static test pages. Subject to GitHub's privacy policy.
• Render hosts the HPP verification server used for live attestations. Subject to Render's privacy policy.
• Apple provides the App Store, Secure Enclave, and Face ID / Touch ID. Subject to Apple's privacy policy. HPP does not receive biometric templates from Apple.
• Google Chrome runs the extension APIs. Subject to Google's privacy policy for Chrome.

We do not use analytics, advertising, or tracking services on the Chrome Gateway test pages.

Claims this version does not fulfill

The request schema can name age_over, geofence, or location-region claims so later adapters can be added. Version 0.1 of this Chrome Gateway returns false for those claims. It does not fabricate age or location results. Date of birth, when used by the iPhone app for other HPP features, stays on the phone as described in the product privacy policy.

Children

These Chrome test pages do not knowingly collect personal information from children under 13. HPP is designed so a presence check does not require a name, email, or account. This policy does not claim that every possible deployment is automatically COPPA or KOSA compliant. That depends on how a relying site uses the Boolean, in which jurisdiction, and for what purpose.

Your choices

• Do not click Verify Human, and no relay is created.
• Close the verification panel to cancel.
• Remove the Chrome extension to delete local mode and endpoint settings.
• Uninstall the HPP iPhone app to delete on-device HPP data, as described in the product privacy policy.
• Email privacy@humanpresenceprotocol.com with questions, including requests about verifier-side receipts (those receipts contain no personal information).

Legal positioning

The Chrome Gateway is designed around data minimization and purpose limitation. We do not market this package as automatically GDPR compliant, COPPA compliant, or compliant with every age-assurance or privacy law. Preferred language is privacy by design, data minimization, and designed to support minimal-disclosure verification.

Changes

We may update this policy when the Chrome Gateway or the HPP verifier changes. Material changes will be noted on this page with a new last-updated date.