Skip to content
DH ConnectHelp

Account & privacy

Use DH Connect responsibly and protect private information

Understand public content, private workspace data, consent, and the limits of activity evidence.

5 min read For All membersReviewed
Full handbook

Before you start#

  • Review what you intend to publish before sharing.

Steps#

  1. Step 1: Separate public and private information#

    Published cards and active published Member Spotlights are public-facing content. Private drafts, lead information, and internal requests should not be pasted into them.

    Review each card's public-contact controls. If you share a social profile or community invitation, assume anyone who can view the published card may use that link.

  2. Step 2: Keep sign-in and editing private#

    Use your own DH Connect email/password account and sign out on shared devices. Studio and uploads require authentication; published-card viewing does not grant editing access.

    Never share passwords, verification codes, browser cookies, or secrets. Do not ask a prospect for sensitive information through a casual card question.

  3. A person asking for one response is not agreeing to an ongoing newsletter. A device notification permission is not email consent. A click is not permission for repeated unsolicited outreach.

    Use the consent and unsubscribe controls appropriate to the actual channel. Do not claim DH Connect grants a general legal right to contact someone.

  4. Step 4: Make accurate claims about activity#

    A visit, a submitted first name, a button click, a signup, and a delivered message are different things. Do not describe one as another or invent outcomes to make a report look better.

    Labels such as verified email do not establish verified identity, income, results, or membership in another program. Labeled demo content remains fictional even if it looks realistic.

  5. Step 5: Share help requests safely#

    Redact lead details, request messages, email addresses, phone numbers, and private links from screenshots. Describe a problem with the minimum information needed.

    The local checklists in this Help Center store only checklist progress on the current browser when storage is available. They do not modify your account, publish cards, or mark real follow-ups complete.

How you know it worked#

  • Published content contains only intended public information.
  • Contact and notification choices are deliberate.
  • Activity descriptions stay within what was actually measured.

Tips#

  • Use your own lawful privacy and business practices; this guide is not legal advice.
  • Before sharing a screenshot, inspect the entire image for private details.

Troubleshooting#

I published a contact method I did not intend to share.
Turn off the relevant card-level visibility, republish, and verify the public card signed out. Previously copied or cached information elsewhere may remain outside the app's control.

Related questions#

Account & privacy5 min readControl public contact details and contact buttons

Keep public visibility separate from private account information and test where messages actually go.

Account & privacy4 min readUnderstand announcements, email, and phone permissions

Keep communication channels separate and choose deliberately when a device asks for permission.

Pipeline5 min readFind and understand genuine leads in Pipeline

Review submissions and recorded actions without confusing activity with identity or confirmed delivery.