Learn

About not.bot

Overview — How not.bot proves people and content are real without surveillance: the app, Verify, Signer, and the identity beneath them.
Content Provenance and Digital Signatures — Sign your authentic content so recipients can verify it. How not.bot signatures, QR and JAB codes, and visible provenance work.
Is not.bot Safe? — A plain-language safety walkthrough for anyone considering not.bot: what enrollment involves, what leaves your phone, who can see your activity, and what happens when something goes wrong.
Roadmap — Where Julia Social is taking not.bot and honest.bot: planned products, capabilities, and infrastructure beyond what ships today.
Evaluation Framework — A vendor-neutral framework for evaluating any human-verification or identity product, not.bot included: the criteria every buyer can apply across the category.
About Julia Social — The company behind not.bot: why we build identity that proves a person is real without learning who they are, how blind identity works, and who's on the team.

Human Verification and not.bot Verify — How businesses use not.bot Verify to confirm a user is a real, unique, age-qualified human without collecting identity data.
Content Signing and not.bot Signer — not.bot Signer lets verified people and brands sign what they publish, so audiences can confirm it's genuine and dismiss anything unsigned in your name as fake.
The not.bot App — Enroll by scanning your passport, create unlinkable aliases, sign content, and verify others. The not.bot app explained.
honest.bot: Verifiable Agent Identity — Verifiable, process-bound identity for AI agents, with every delegation chain tracing back to an accountable human.

not.bot Use Cases: Index — The top-level catalog of not.bot use cases, grouped by category, with the mechanism definitions each detail document draws on.
not.bot Use Cases: Enterprise — Enterprise authentication, authorization, hiring, and operations: binding permissions to a verified human at the authentication layer.
not.bot Use Cases: Content Signing — Content signing across creator types, content categories, and licensing models, so that unsigned content is fake by default.
not.bot Use Cases: Verified Humanness — CAPTCHA replacement, sybil defense, surveys, and catfishing prevention: telling real humans apart at the protocol layer, not by inference.
not.bot Use Cases: Credentials — Marks of distinction, qualifiers, self-attested claims, and age verification: cryptographically backed credentials presented selectively.
not.bot Use Cases: Trust Surface — Signed links, authorized-agent verification, and peer-to-peer commerce: turning 'is this real' into 'is this signer who I expect'.
not.bot Use Cases: Industry Verticals — Industry-specific applications across healthcare, finance, real estate, education, journalism, legal services, and consumer platforms.

The Problems not.bot Solves: Index — The public evidence behind the problems the not.bot family exists to solve: deepfakes, proof of personhood, age verification, digital ID, and unaccountable AI agents.
Problems: Deepfakes and Inauthentic Content — Fabricating anyone's face and voice now costs almost nothing, detection loses the arms race, and every authentic recording competes with the possibility it's fake.
Problems: Proof of Personhood — No system deployed at internet scale can tell whether an account belongs to a human without demanding to know which human — as bots become the majority of traffic.
Problems: Age Verification Without Surveillance — Age checks are now law across the major internet markets, and the systems used to comply collect identity data that gets retained, breached, and repurposed.
Problems: Non-Government Digital ID — Digital identity today means a record in someone else's database — a government portal or a platform login — and the costs arrive as breaches, surveillance, and exclusion.
Problems: Unaccountable AI Agents — AI agents now act across the internet with no verifiable identity and no human accountable for what they do.

Glossary — Alphabetical definitions of every term used across the not.bot documentation, each entry self-contained so an AI reader can retrieve one and have all it needs.