dhaga.

Privacy

The short version: self-hostable, user-triggered, receipts for everything, export anytime. The long version is the code — it's open source.

Your graph is yours

Dhaga stores your contacts, notes, and everything derived from them in your own database — the embedded local database by default, or a Postgres instance you control. There is no central Dhaga server reading your graph.

AI is opt-in and user-triggered

Cloud AI calls (extraction, search answers, drafts, briefs, enrichment, card scanning) happen only when you press the button and only using your own API key. Nothing runs in the background. Scanned card photos are kept in your own database as visual receipts — a setting you can turn off, with one-click deletion of everything already stored.

The browser extension reads nothing silently

The extension accesses the active tab only at the moment you click its icon, sends exactly what you selected, and only to the Dhaga instance you configured. No content scripts, no background scraping, no analytics.

Every AI fact keeps a receipt

Facts and relationships always link to the note they came from. Deleting a note removes everything derived from it; "Forget this person" removes the contact and every trace — notes, facts, connections, and search index entries.

You can always leave

Export your full graph as CSV, vCard, or JSON at any time. No lock-in is a feature.

Access request emails

If you request access we store your email address to send the invite once approved, and nothing else. One email confirms the request; unsubscribe by replying.