dhaga.docs
Using Dhaga

Share a contact with another person

Send one of your contacts to another Dhaga user, choose exactly which details go, and see what they receive and what stays private.

You can send a contact from your book to another person. You choose which details go with it, they decide whether to accept, and what they accept is a copy that is theirs.

Where this stands

Sharing is built on the web and covered by automated tests. It has not yet been checked end to end in a browser with a real email delivery, and there is no mobile app screen for it yet.

Sending a contact

Open the contact, choose Send a copy (next to Forget at the bottom of the page), and enter the recipient: a Dhaga user or an email address. Then tick what to include.

  • Always included: name, company and role, and links.
  • Only if you tick them: phone numbers, email addresses, notes, facts and tags.

The invite email and the notice the recipient sees contain no text that you wrote. They say that someone sent a contact, never who the contact is.

If the recipient has no Dhaga account, they get an emailed link that works for 14 days. They must sign up with that same, verified email address to claim it. If email is not set up on your deployment, or you have reached the hourly email limit, Dhaga shows you the link so you can pass it on yourself.

What the recipient sees

Pending shares wait in a list, with a notice in their inbox. They can accept or decline. Nothing is added to their book until they accept.

On accept, the contact appears in their book as an ordinary contact, marked as 2nd degree. If your verified address is on exactly one of their own contacts, it is shown one step beyond that person instead. If they already have someone with the same phone number or email address, the shared details are added to that contact rather than creating a duplicate. A matching name on its own never merges two people.

Privacy and what changes later

  • It is a one-time copy. What was sent is a snapshot taken when you shared. If you edit the contact afterwards, the other person's copy does not change, and neither does yours if they edit theirs. There is no live sync.
  • Revoke stops a share that is still pending. It is marked revoked on your side and can no longer be accepted.
  • Revoking does not take back an accepted copy. Once accepted, it belongs to the recipient until they delete it. After they do, your record shows removed by recipient.
  • The details are held only until the share is settled. Third-party details in a pending share are not shown to anyone but the intended recipient.
  • Deleting a contact removes its shares. Forgetting a contact deletes the shares you sent for it.

Your export

Everything you sent leaves with you. In the full JSON export, the sent_contact_shares section lists each share with who it went to, its status, which fields were chosen and the relevant dates. It never includes the snapshot of details or the link credential. Contacts you received are ordinary contacts and export with the rest of your book; the JSON export also carries their degree and where they came from, while CSV and vCard leave those two columns out.

On this page