Privacy

What Huma keeps, and who sees it.

Last updated November 6, 2026

Data Used to Track You

None.

Data Linked to You

  • User Content · documents, proofs and writing replays
  • Contact Info · the email you sign in with, and the name you choose
  • Identifiers · wallet address, account ID, passkey public keys
  • Usage Data · once you sign in: which Huma pages you open, steps you take, and replays of how you move through a page, with every word hidden

Used for App Functionality and Analytics.

Data Not Linked to You

  • Usage Data · before you sign in: which Huma pages you open, steps you take like Start Recording or Share, and replays of how you move through a page, with every word hidden

Used for Analytics only.

Data Shared With Others

  • User Content · on the web’s free plan only: finished documents’ text and edit times, without your name or account

Licensed to AI companies, after you agree.

Data Not Collected

Your fingerprint or face, location, contacts, browsing and diagnostics.

What Huma Keeps

Typing checks run on your computer.

Shared Links

From Other Sources

Privy runs sign-in and makes your wallet. Huma gets your wallet address and an account ID. Your email is shown, not saved.

How Huma Uses It

No ads. On Plus, nothing you write is shared or sold.

Free and Plus

On the free plan, documents aren’t end-to-end encrypted, and documents you finish may be used, without your name, to help train AI models. Plus, coming soon, adds end-to-end encryption for all documents, and your writing is never used to train AI. See the Terms.

Service Providers

Cloudflare stores documents and shared pages. Google Cloud runs huma.social. Privy runs sign-in. Dodo Payments sells Plus and keeps your payment details; Huma gets only your subscription’s status. Cloudflare Turnstile checks the browser is used by a person. PostHog counts visits and steps and keeps page replays.

Your Choices

On Your Device

Huma keeps your documents, sign-in and writing keys in your browser’s storage. Writing keys can’t be exported. No ad or analytics cookies. To count steps, your browser keeps a random number. Once you sign in, your steps and replays count under your account instead, including the ones from this browser before you signed in, and PostHog gets the email you signed in with. Signing out starts a new random number. Steps never include your text, titles, links or IP address. Replays show clicks, scrolling and the screens you open, with every word shown as stars; shared pages are never replayed. Both go through huma.social, so PostHog never sees your IP address. With Global Privacy Control or Do Not Track on, nothing is sent. Our servers may keep IP addresses for a short time for security. The Mac app checks for updates once a day and sends only its version.

Huma for Chrome

The Huma extension reads nothing until you press Start Recording in a document, and stops when you finish, pause or close it. While it records, it sees the keys you press, what you paste and the document’s text in that one tab, and records and proves them inside the extension, on this computer, as the web app does. The only thing it asks huma.social for is the session’s start time. In Google Docs it reads the document’s edit history and plain-text export, through your own access. Proofs stay in the extension until you press Share; then huma.social takes that document in, and from there it’s kept and shared exactly as a document you write on huma.social. A red Recording chip shows on the document, and REC on the toolbar button, the whole time it records. It never reads other tabs, passwords or forms, and has no analytics.

Children

Huma isn’t meant for children under 13.

Changes

When this policy changes, the date at the top changes too.

Questions

Email team@huma.social. See also our Terms.

Credits

Faces are DiceBear “Dylan” drawings by Natalia Spivak, used under CC BY 4.0.