SDK Demo
Try not.bot Verify: Request information from a human and review the response.
This page is a thin wrapper around the not.bot™ Verify Web SDK. Choose what to ask for, write the message the signer will see, respond in the not.bot app, and view the response data not.bot Verify receives.
Live demo. No personal data is stored, except for alias identifiers (DIDs) and site passes.
Step 1Permalink to Step 1
Build the request.
Step 2Permalink to Step 2
Respond in the app
Scan with your phone’s camera.
Opens the app on this device.
Why that address is not a link
The button above opens the same request through notbot://. Tap an https://not.bot link from a page already on not.bot and the phone keeps you in the browser: iOS and Android both read it as navigation inside this site and skip the hand-off to the app.
That applies to not.bot’s own pages. Your site should use the https:// address. It opens the app for anyone who has it, and shows the rest what to install.
Using Brave on iOS? Brave shows a “Cannot Open Page” alert when you return from the app. Your signature arrived anyway, and the response is on this page behind the alert. Brave opens the app and also tries to load notbot:// as a page, which no browser can render. Safari and Chrome skip that second step.
Request data
The request this page sent to the signature server, as sent. requested_message travels as UTF-8 bytes and expires as Unix seconds; both are shown decoded.
Step 3Permalink to Step 3
Response data
Claims
Signature metadata
Response payload
The VerifySignatureResponse as returned, with the presentation bytes shown base64-encoded for legibility.
None of this personal data has been stored, except the alias identifier (DID) and the Site Pass. The claims above live in this page and in the demo server’s memory, which drops them thirty minutes after the request; they are never written to disk.
Why not.bot VerifyPermalink to Why not.bot Verify
About this demo.
For not.bot Verify operators:
- Only humans can have a not.bot, so only humans can respond to not.bot Verify requests.
- Only request the information you need, like proof of human or age.
- Site Passes let you distinguish unique humans, without requesting any other information.
- Billing is based on MAUs reported only as aggregate data. There is no additional cost to re-verify users at every login.
- not.bot Verify runs in your cloud, under your control.
- No network connections are made from your site to Julia Social during user interaction. Except for this demo running at Julia Social.
For not.bot users:
- The app is free for users to download and prove they’re human.
- No biometric data is ever collected.
- There is no minimum age. A parent or guardian must accept the Terms of Service for a minor.
- Julia Social gathers no personal information at enrollment.
- Users can create aliases to avoid being tracked between sites.
- Once a user enrolls in not.bot, they do not need to enroll again no matter how many sites they access.
- The user sees exactly what information is requested and can refuse to share it.
- Enrolling today needs an NFC-enabled passport and a US app store account. We are adding in-person enrollment.
Law Enforcement
User information is encrypted and stored with our independent data escrow provider, Praxis Escrow. Praxis does not have access to the decryption keys. When presented with a valid demand from a US-based law enforcement agency, Julia Social can request the encrypted enrollment data for a specific signature from Praxis Escrow. Praxis will confirm the demand and charges a significant fee per record to release data. Julia Social can decrypt the data and provide it to law enforcement. The process takes 9-14 days per signature.
Want this on your own site?