{"id":54143,"date":"2026-02-01T12:22:49","date_gmt":"2026-02-01T18:22:49","guid":{"rendered":"https:\/\/heartbeat.ai\/healthcare\/data-ethics-acceptable-use\/"},"modified":"2026-10-19T13:50:57","modified_gmt":"2026-10-19T18:50:57","slug":"data-ethics-acceptable-use","status":"publish","type":"post","link":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/","title":{"rendered":"Data ethics acceptable use for recruiting outreach (boundaries, do\/don\u2019t, provenance)"},"content":{"rendered":"<section class=\"aeo-key-takeaways\">\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_89 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\r\n<div class=\"ez-toc-title-container\">\r\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">What\u2019s on this page:<\/p>\r\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\r\n<nav><ul class='ez-toc-list ez-toc-list-level-1' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Key_takeaways\" >Key takeaways<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Who_this_is_for\" >Who this is for<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Quick_Answer\" >Quick Answer<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Acceptable_use_in_6_rules\" >Acceptable use in 6 rules<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Framework_the_%E2%80%9Cdont_be_a_creep%E2%80%9D_standard\" >Framework: the &#8220;don&#8217;t be a creep&#8221; standard<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#What_acceptable_use_is_not\" >What acceptable use is not<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Do_dont_fast_reference\" >Do \/ don&#8217;t (fast reference)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Step-by-step_method\" >Step-by-step method<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Step_1_write_a_one-page_acceptable-use_SOP_your_team_will_actually_follow\" >Step 1: write a one-page acceptable-use SOP your team will actually follow<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Stop-rule_examples\" >Stop-rule examples<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Step_2_separate_identity_sources_from_contact_channels_provenance\" >Step 2: separate identity sources from contact channels (provenance)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#What_to_say_if_asked_%E2%80%9Cwhere_did_you_get_my_info%E2%80%9D\" >What to say if asked &#8220;where did you get my info?&#8221;<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Step_3_build_opt-out_and_suppression_into_the_workflow\" >Step 3: build opt-out and suppression into the workflow<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Step_4_set_channel_rules_that_protect_deliverability_and_reputation\" >Step 4: set channel rules that protect deliverability and reputation<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Step_5_track_metrics_that_show_youre_staying_within_bounds\" >Step 5: track metrics that show you&#8217;re staying within bounds<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Diagnostic_table\" >Diagnostic table<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Weighted_checklist\" >Weighted checklist<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Outreach_templates\" >Outreach templates<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Email_template_initial\" >Email template (initial)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#SMS_template_only_where_policy_supports_it\" >SMS template (only where policy supports it)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-21\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Voicemail_template\" >Voicemail template<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Common_pitfalls\" >Common pitfalls<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-23\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#How_to_improve_results\" >How to improve results<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-24\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#1_Fix_targeting_before_you_fix_copy\" >1) Fix targeting before you fix copy<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-25\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#2_Reduce_wasted_touches_with_verification_and_ranking\" >2) Reduce wasted touches with verification and ranking<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-26\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#3_Run_a_weekly_outreach_health_review\" >3) Run a weekly outreach health review<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-27\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#4_Tighten_stop_rules\" >4) Tighten stop rules<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-28\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Legal_and_ethical_use\" >Legal and ethical use<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-29\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Evidence_and_trust_notes\" >Evidence and trust notes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-30\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#FAQs\" >FAQs<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-31\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#What_does_acceptable_use_mean_for_recruiting_contact_data\" >What does acceptable use mean for recruiting contact data?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-32\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#What_counts_as_an_opt-out\" >What counts as an opt-out?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-33\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Can_I_contact_clinicians_by_text\" >Can I contact clinicians by text?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-34\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#How_fast_should_opt-outs_be_applied\" >How fast should opt-outs be applied?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-35\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Is_it_acceptable_to_call_a_clinicians_workplace_line\" >Is it acceptable to call a clinician&#8217;s workplace line?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-36\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#What_should_I_say_if_a_candidate_asks_where_I_got_their_information\" >What should I say if a candidate asks where I got their information?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-37\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#How_do_I_keep_outreach_ethical_without_killing_speed\" >How do I keep outreach ethical without killing speed?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-38\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#Next_steps\" >Next steps<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-39\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#About_the_Author\" >About the Author<\/a><\/li><\/ul><\/nav><\/div>\r\n<h2><span class=\"ez-toc-section\" id=\"Key_takeaways\"><\/span>Key takeaways<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li>Use contact data for relevant recruiting outreach, identify yourself and your purpose, and make it easy to opt out.<\/li>\n<li>Centralize opt-outs in a suppression list and apply them across outreach tools and channels.<\/li>\n<li>Set frequency caps and stop rules, and stop immediately after an opt-out or explicit negative response.<\/li>\n<li>Keep recruiting outreach separate from patient information, care events, and clinical context.<\/li>\n<li>Document identity sources, contact channels, data transformations, refresh practices, suppression governance, and audit records.<\/li>\n<li>Track outreach metrics and audit suppression enforcement to identify problems and improve targeting.<\/li>\n<\/ul>\n<\/section>\n<p class=\"article-last-updated\"><strong>Last updated:<\/strong> August 30, 2026<\/p>\n<p><strong>By Ben Argeband, Founder &amp; CEO of Heartbeat.ai<\/strong> \u2014 Concrete do\/don&#8217;t examples; no moralizing.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Who_this_is_for\"><\/span>Who this is for<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Recruiters and recruiting ops leaders can use this guide to set clear, auditable outreach boundaries that protect deliverability, brand, and candidate relationships. It is designed to be practical for teams sharing policies with leadership, compliance, or procurement.<\/p>\n<p>One non-negotiable: <strong>you own compliance<\/strong>. Tools can help you execute, but they can&#8217;t own your policies, training, or judgment calls.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Quick_Answer\"><\/span>Quick Answer<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<dl>\n<dt>Core Answer<\/dt>\n<dd>Use contact data only for relevant recruiting outreach, with clear identity context, limited retention, an <strong>easy opt-out<\/strong>, and strict opt-out enforcement via a <strong>suppression list<\/strong>.<\/dd>\n<dt>Key Insight<\/dt>\n<dd>Ethical outreach is operational: provenance, relevance, frequency caps, and opt-out enforcement matter more than which channel you use.<\/dd>\n<dt>Best For<\/dt>\n<dd>Recruiters and ops teams that want clear, enforceable boundaries<\/dd>\n<\/dl>\n<blockquote>\n<p><strong>Compliance &amp; Safety<\/strong><\/p>\n<p>This method is for legitimate recruiting outreach only. Always respect candidate privacy, opt-out requests, and local data laws. Heartbeat does not provide medical advice or legal counsel.<\/p>\n<\/blockquote>\n<h3><span class=\"ez-toc-section\" id=\"Acceptable_use_in_6_rules\"><\/span>Acceptable use in 6 rules<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Be relevant:<\/strong> only contact people who plausibly match the role (specialty, setting, location, seniority).<\/li>\n<li><strong>Be transparent:<\/strong> say who you are, why you&#8217;re reaching out, and what the next step is.<\/li>\n<li><strong>Be restrained:<\/strong> use frequency caps and stop rules; don&#8217;t pile on across channels.<\/li>\n<li><strong>Make it easy to stop:<\/strong> every message includes an <strong>easy opt-out<\/strong>.<\/li>\n<li><strong>Honor opt-outs everywhere:<\/strong> centralize and enforce via a <strong>suppression list<\/strong> across all tools and channels.<\/li>\n<li><strong>No patient data:<\/strong> recruiting outreach never uses or implies access to patient information.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Framework_the_%E2%80%9Cdont_be_a_creep%E2%80%9D_standard\"><\/span>Framework: the &#8220;don&#8217;t be a creep&#8221; standard<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Before sending outreach, check it against a quick filter for respect, relevance, transparency, control, restraint, and separation from patient care:<\/p>\n<ul>\n<li><strong>Respect:<\/strong> treat the person like a professional, not a lead. No pressure, no guilt trips.<\/li>\n<li><strong>Relevance:<\/strong> the message should make sense given their specialty, licensure, geography, and career stage.<\/li>\n<li><strong>Transparency:<\/strong> say who you are and why you&#8217;re reaching out.<\/li>\n<li><strong>Control:<\/strong> give a clear <strong>easy opt-out<\/strong> and honor it immediately across channels.<\/li>\n<li><strong>Restraint:<\/strong> frequency caps and quiet hours. If you wouldn&#8217;t want it done to you on personal time, don&#8217;t do it to them.<\/li>\n<li><strong>Separation:<\/strong> recruiting outreach is not patient outreach \u2014 no patient data, no clinical context, no insinuations.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"What_acceptable_use_is_not\"><\/span>What acceptable use is not<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Not<\/strong> permission to spam \u2014 volume doesn&#8217;t replace relevance.<\/li>\n<li><strong>Not<\/strong> a reason to ignore gatekeepers or keep pushing after a &#8220;no.&#8221;<\/li>\n<li><strong>Not<\/strong> patient outreach \u2014 don&#8217;t reference care events, cases, or anything implying clinical surveillance.<\/li>\n<\/ul>\n<p>Use these examples to train recruiters:<\/p>\n<ul>\n<li><strong>Acceptable:<\/strong> &#8220;Dr. Patel \u2014 I recruit hospitalists in the Midwest. Are you open to hearing about a 7-on\/7-off role in Dayton? If not, reply &#8216;no&#8217; and I&#8217;ll stop.&#8221;<\/li>\n<li><strong>Not acceptable:<\/strong> &#8220;I saw you treated a patient at X hospital\u2026&#8221;<\/li>\n<li><strong>Acceptable:<\/strong> one follow-up after no response, then stop or switch to a single lower-friction touch.<\/li>\n<li><strong>Not acceptable:<\/strong> calling, texting, emailing, and messaging the same day with escalating language.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Do_dont_fast_reference\"><\/span>Do \/ don&#8217;t (fast reference)<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li><strong>Do<\/strong> lead with relevance: role, location, and why them. <strong>Don&#8217;t<\/strong> send generic blasts that force the candidate to guess.<\/li>\n<li><strong>Do<\/strong> identify yourself and your organization. <strong>Don&#8217;t<\/strong> use deceptive subject lines or fake familiarity.<\/li>\n<li><strong>Do<\/strong> include an <strong>easy opt-out<\/strong> in every channel. <strong>Don&#8217;t<\/strong> bury opt-out language.<\/li>\n<li><strong>Do<\/strong> treat any &#8220;stop\/remove\/unsubscribe&#8221; as an opt-out and enforce it via a <strong>suppression list<\/strong>. <strong>Don&#8217;t<\/strong> rely on individual recruiters to remember.<\/li>\n<li><strong>Do<\/strong> set frequency caps and stop rules per role. <strong>Don&#8217;t<\/strong> pile on across channels within 24\u201348 hours.<\/li>\n<li><strong>Do<\/strong> keep content strictly recruiting-related. <strong>Don&#8217;t<\/strong> reference patient care or anything implying clinical tracking.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Step-by-step_method\"><\/span>Step-by-step method<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_write_a_one-page_acceptable-use_SOP_your_team_will_actually_follow\"><\/span>Step 1: write a one-page acceptable-use SOP your team will actually follow<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Keep the SOP short and enforceable. At minimum, specify:<\/p>\n<ul>\n<li><strong>Purpose:<\/strong> &#8220;We use contact data to communicate about employment opportunities and career conversations.&#8221;<\/li>\n<li><strong>In-scope audience:<\/strong> who you recruit and what &#8220;relevant&#8221; means for your org.<\/li>\n<li><strong>Allowed channels:<\/strong> email, phone, SMS, voicemail, professional social \u2014 and who can use each.<\/li>\n<li><strong>Frequency caps:<\/strong> max attempts per person per role, plus quiet hours.<\/li>\n<li><strong>Stop rules:<\/strong> when to stop after no response, and when to stop immediately.<\/li>\n<li><strong>Opt-out enforcement:<\/strong> how opt-outs are captured and applied via a <strong>suppression list<\/strong>.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Stop-rule_examples\"><\/span>Stop-rule examples<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Immediate stop:<\/strong> any opt-out language (&#8220;stop,&#8221; &#8220;remove,&#8221; &#8220;unsubscribe,&#8221; &#8220;don&#8217;t contact&#8221;).<\/li>\n<li><strong>Immediate stop:<\/strong> any explicit negative response.<\/li>\n<li><strong>Stop and correct:<\/strong> wrong person, specialty, or location \u2014 fix targeting, don&#8217;t keep trying.<\/li>\n<li><strong>Stop and route:<\/strong> a gatekeeper requests a different channel \u2014 follow it once, then stop if declined.<\/li>\n<li><strong>Stop after cap:<\/strong> no response after your defined attempt limit for that role.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_separate_identity_sources_from_contact_channels_provenance\"><\/span>Step 2: separate identity sources from contact channels (provenance)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Procurement and compliance teams need more than an answer to \u201cwhere did you get the data?\u201d Document what establishes identity, what enables contact, and what transformations are applied between those steps.<\/p>\n<p><strong>Provenance one-pager outline:<\/strong><\/p>\n<ul>\n<li><strong>Identity sources:<\/strong> what establishes professional identity (name, specialty, license\/NPI context).<\/li>\n<li><strong>Contact channels:<\/strong> email\/phone\/SMS endpoints used for outreach \u2014 acknowledge these decay over time.<\/li>\n<li><strong>Transformations applied:<\/strong> verification, refresh, deduping, and suppression enforcement, described at a high level.<\/li>\n<li><strong>Refresh reality:<\/strong> how often you re-check contactability and remove bad endpoints.<\/li>\n<li><strong>Suppression governance:<\/strong> where the <strong>suppression list<\/strong> lives, who owns it, and how it propagates to tools.<\/li>\n<li><strong>Audit artifacts:<\/strong> opt-out logs, campaign settings, template versions.<\/li>\n<\/ul>\n<p>This structure helps you answer due-diligence questions while limiting disclosure of sensitive sourcing details.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_to_say_if_asked_%E2%80%9Cwhere_did_you_get_my_info%E2%80%9D\"><\/span>What to say if asked &#8220;where did you get my info?&#8221;<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Identity context:<\/strong> &#8220;We recruit in [specialty\/region] and use professional registries to confirm identity and credentials.&#8221;<\/li>\n<li><strong>Contact channel:<\/strong> &#8220;We use business contact channels to reach out about roles.&#8221;<\/li>\n<li><strong>Control:<\/strong> &#8220;If you&#8217;d like, I can remove you from outreach \u2014 just reply &#8216;stop&#8217; and I&#8217;ll add you to our suppression list.&#8221;<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_build_opt-out_and_suppression_into_the_workflow\"><\/span>Step 3: build opt-out and suppression into the workflow<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>Every outbound email includes an <strong>easy opt-out<\/strong> instruction.<\/li>\n<li>Every SMS includes a clear stop instruction, and you honor it.<\/li>\n<li>Any opt-out request updates your <strong>suppression list<\/strong> and applies across all sequences and tools.<\/li>\n<li>Ops audits suppression enforcement weekly with spot checks across campaigns.<\/li>\n<\/ul>\n<p>For details on implementation and failure modes, see suppression lists and opt-out management for recruiting ops.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_set_channel_rules_that_protect_deliverability_and_reputation\"><\/span>Step 4: set channel rules that protect deliverability and reputation<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Email:<\/strong> role-relevant messaging, no deceptive subject lines, stop after a small number of attempts.<\/li>\n<li><strong>Phone:<\/strong> call during reasonable local hours, leave one short voicemail, don&#8217;t hammer the same number.<\/li>\n<li><strong>SMS:<\/strong> use sparingly and only where policy supports it, include stop language, avoid long multi-part texts.<\/li>\n<\/ul>\n<p>More outreach attempts may produce short-term activity, but aggressive contact can also lead to blocks, complaints, and brand damage. Improve targeting and follow the team&#8217;s frequency caps and stop rules instead.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_5_track_metrics_that_show_youre_staying_within_bounds\"><\/span>Step 5: track metrics that show you&#8217;re staying within bounds<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use documented controls and audits to assess outreach practices. Track a small, consistent set of metrics to monitor whether outreach is respectful and effective:<\/p>\n<ul>\n<li><strong>Connect Rate<\/strong> = connected calls \/ total dials.<\/li>\n<li><strong>Answer Rate<\/strong> = human answers \/ connected calls.<\/li>\n<li><strong>Deliverability Rate<\/strong> = delivered emails \/ sent emails.<\/li>\n<li><strong>Bounce Rate<\/strong> = bounced emails \/ sent emails.<\/li>\n<li><strong>Reply Rate<\/strong> = replies \/ delivered emails.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Diagnostic_table\"><\/span>Diagnostic table<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><strong>Use this to check whether your outreach program is operating inside acceptable use.<\/strong><\/p>\n<div class=\"table-scroll\" style=\"overflow:auto;-webkit-overflow-scrolling:touch;width:100%\">\n<table class=\"separated-content\">\n<thead>\n<tr>\n<th>Area<\/th>\n<th>What acceptable use looks like<\/th>\n<th>Red flag<\/th>\n<th>What to do next<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Relevance<\/td>\n<td>Role + geography + specialty match is explicit in the first message<\/td>\n<td>Generic blast copy; unclear why they were selected<\/td>\n<td>Require a relevance line in templates; tighten list inclusion rules<\/td>\n<\/tr>\n<tr>\n<td>Opt-out handling<\/td>\n<td>Opt-outs captured same day and applied across tools via a <strong>suppression list<\/strong><\/td>\n<td>They opt out but still get contacted<\/td>\n<td>Centralize suppression; audit sequences and dialer queues weekly<\/td>\n<\/tr>\n<tr>\n<td>Frequency<\/td>\n<td>Documented caps; stop rules after no response<\/td>\n<td>Multi-channel pile-on in 24\u201348 hours<\/td>\n<td>Set caps by persona; enforce in CRM\/sequence tool<\/td>\n<\/tr>\n<tr>\n<td>Transparency<\/td>\n<td>Clear sender identity, company, and purpose<\/td>\n<td>Misleading subject lines or fake familiarity<\/td>\n<td>Rewrite templates; require sender signature block<\/td>\n<\/tr>\n<tr>\n<td>Content boundaries<\/td>\n<td>No patient data; no clinical insinuations; no sensitive inferences<\/td>\n<td>Any mention of patient care events or protected contexts<\/td>\n<td>Immediate stop; retrain; add approval gate for new templates<\/td>\n<\/tr>\n<tr>\n<td>Provenance (procurement-friendly)<\/td>\n<td>Documented separation: identity sources vs contact channels vs what Heartbeat adds (verification, ranking, refresh)<\/td>\n<td>&#8220;It&#8217;s all public&#8221; with no structure<\/td>\n<td>Publish a provenance one-pager; review quarterly with ops + procurement<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2><span class=\"ez-toc-section\" id=\"Weighted_checklist\"><\/span>Weighted checklist<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><strong>Score each campaign before launch.<\/strong> Under 80 points, fix it before you hit send.<\/p>\n<ul>\n<li><strong>(25 points)<\/strong> Relevance is explicit: specialty\/role + location + why them.<\/li>\n<li><strong>(20 points)<\/strong> Opt-out is clear and simple across email and SMS, and routes into a centralized <strong>suppression list<\/strong>.<\/li>\n<li><strong>(15 points)<\/strong> Frequency caps are set per person and per role, and enforced in tooling.<\/li>\n<li><strong>(10 points)<\/strong> A provenance one-pager exists: identity sources vs contact channels vs transformations.<\/li>\n<li><strong>(10 points)<\/strong> No sensitive content \u2014 no patient data, no clinical event references, no insinuations.<\/li>\n<li><strong>(10 points)<\/strong> Sender transparency: real name, company, and a direct reply path.<\/li>\n<li><strong>(10 points)<\/strong> A metrics plan exists with thresholds and stop rules.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Outreach_templates\"><\/span>Outreach templates<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><strong>These are intentionally plain.<\/strong> They&#8217;re built to be respectful, relevant, and easy to stop. Replace bracketed fields and keep your frequency cap consistent with your SOP.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Email_template_initial\"><\/span>Email template (initial)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Subject:<\/strong> Quick question about your next role<\/p>\n<p>Hi Dr. [Last Name] \u2014 I&#8217;m [Name], a recruiter with [Org]. I&#8217;m reaching out because we&#8217;re hiring a [Role\/Specialty] in [City\/Region] and your background in [relevant signal] looks aligned.<\/p>\n<p>Would you be open to a 5-minute call this week to see whether a longer conversation makes sense? If not, reply \u201cno\u201d and I&#8217;ll stop reaching out.<\/p>\n<p><em>Follow-up rule:<\/em> if I don&#8217;t hear back, I&#8217;ll only follow up up to [YOUR CAP] times for this role.<\/p>\n<p>\u2014 [Name], [Title], [Org] | [Phone] | [Email]<\/p>\n<h3><span class=\"ez-toc-section\" id=\"SMS_template_only_where_policy_supports_it\"><\/span>SMS template (only where policy supports it)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Hi Dr. [Last Name] \u2014 [Name] recruiting for [Org]. Are you open to hearing about a [Role] in [Location]? Reply STOP to opt out.<\/p>\n<p><em>Follow-up rule:<\/em> if no response, I&#8217;ll stop after [YOUR CAP] attempts for this role.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Voicemail_template\"><\/span>Voicemail template<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Hi Dr. [Last Name], this is [Name] with [Org]. I&#8217;m calling about a [Role] opportunity in [Location]. If you&#8217;re open to a quick chat, call me back at [Number]. If not interested, no problem.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Common_pitfalls\"><\/span>Common pitfalls<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li><strong>Assuming a list equals permission.<\/strong> Static purchased lists decay quickly. The more defensible standard combines access, refresh, verification, and suppression.<\/li>\n<li><strong>Opt-out that doesn&#8217;t actually stop outreach.<\/strong> If someone opts out and still gets contacted, you&#8217;ve proven you can&#8217;t be trusted.<\/li>\n<li><strong>Over-contacting across channels.<\/strong> Multi-channel is fine; pile-on isn&#8217;t. Set caps and stop rules.<\/li>\n<li><strong>Using sensitive context.<\/strong> Even material that seems public shouldn&#8217;t reference patient care, cases, or anything implying clinical tracking.<\/li>\n<li><strong>Confusing identity with contactability.<\/strong> A stable identifier, like a registry record, doesn&#8217;t mean the email or phone number you found is current or appropriate for outreach.<\/li>\n<li><strong>Policy without enforcement.<\/strong> If ops can&#8217;t audit it, it&#8217;s not a policy \u2014 it&#8217;s a hope.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"How_to_improve_results\"><\/span>How to improve results<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Ethical outreach can also be effective. When results fall short, avoid compensating with more volume or pressure. Improve performance by tightening relevance and channel hygiene instead.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"1_Fix_targeting_before_you_fix_copy\"><\/span>1) Fix targeting before you fix copy<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Define a clear inclusion rule for every outreach list, such as specialty, geography, setting, or seniority. If you can&#8217;t explain in one sentence why someone is on the list, revisit the targeting before increasing outreach volume.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"2_Reduce_wasted_touches_with_verification_and_ranking\"><\/span>2) Reduce wasted touches with verification and ranking<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Verifying contact details and prioritizing them can help reduce attempts to dead inboxes or wrong numbers. Heartbeat.ai describes its workflows as ranking mobile numbers by answer probability; verify that this capability and its performance claims match the current product.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"3_Run_a_weekly_outreach_health_review\"><\/span>3) Run a weekly outreach health review<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Email:<\/strong> Deliverability Rate, Bounce Rate, and Reply Rate, tracked by campaign and sender domain.<\/li>\n<li><strong>Phone:<\/strong> Connect Rate and Answer Rate, tracked by time-of-day and list category.<\/li>\n<li><strong>Opt-out enforcement:<\/strong> confirm requests land in the centralized <strong>suppression list<\/strong> the same business day, and spot-check opted-out records against active sequences and dialer queues.<\/li>\n<li><strong>Complaint signals:<\/strong> track spam complaints, negative replies, and &#8220;stop contacting me&#8221; messages. A spike triggers a template and targeting review.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"4_Tighten_stop_rules\"><\/span>4) Tighten stop rules<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Set a maximum number of attempts per person per role and define a cool-down period before any future outreach. Apply those limits consistently to protect your brand and keep recruiters focused on relevant candidates.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Legal_and_ethical_use\"><\/span>Legal and ethical use<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This page covers acceptable-use boundaries and operational controls, not jurisdiction-specific legal advice. Consult your counsel about requirements that apply to your organization and outreach channels. For a broader view of recruiting compliance topics, start with recruiting compliance resources.<\/p>\n<p>Requirements vary by jurisdiction, channel, and organizational policy. Use counsel to determine which obligations apply, and build operational controls to address relevant requirements, including:<\/p>\n<ul>\n<li><strong>TCPA:<\/strong> especially relevant for calling and texting practices and consent requirements \u2014 treat SMS as higher-risk than email and govern it accordingly.<\/li>\n<li><strong>CAN-SPAM:<\/strong> accurate sender information, no deceptive subject lines, and a clear opt-out mechanism for commercial email.<\/li>\n<li><strong>Opt-out:<\/strong> if someone opts out in any channel, honor it across all channels using a centralized <strong>suppression list<\/strong>.<\/li>\n<li><strong>No patient data:<\/strong> recruiting outreach should never involve patient information or imply access to it.<\/li>\n<\/ul>\n<p>For information about Heartbeat&#8217;s stated data boundaries, see: Not HIPAA: no patient data.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Evidence_and_trust_notes\"><\/span>Evidence and trust notes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Professional registries and licensing bodies can help establish identity and credentials, but they do not guarantee that a contact detail is current or appropriate for outreach.<\/p>\n<ul>\n<li><a href=\"https:\/\/nppes.cms.hhs.gov\/\">NPPES NPI Registry<\/a> (identity and NPI context)<\/li>\n<li><a href=\"https:\/\/www.cms.gov\/medicare\/regulations-guidance\/administrative-simplification\/national-provider-identifier-npi\">CMS: National Provider Identifier (NPI) overview<\/a><\/li>\n<li><a href=\"https:\/\/www.fsmb.org\/\">Federation of State Medical Boards (FSMB)<\/a> (licensure context)<\/li>\n<\/ul>\n<p>Channel requirements vary by jurisdiction and use case. Consult official sources for primary references, including:<\/p>\n<ul>\n<li><a href=\"https:\/\/www.ftc.gov\/business-guidance\/resources\/can-spam-act-compliance-guide-business\">FTC: CAN-SPAM Act compliance guide<\/a><\/li>\n<li><a href=\"https:\/\/www.fcc.gov\/general\/telemarketing-and-robocalls\">FCC: Telemarketing and robocalls (TCPA-related overview)<\/a><\/li>\n<\/ul>\n<p>For more information about Heartbeat&#8217;s stated approach to trust, see: Trust methodology.<\/p>\n<section class=\"aeo-faq\">\n<h2><span class=\"ez-toc-section\" id=\"FAQs\"><\/span>FAQs<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"What_does_acceptable_use_mean_for_recruiting_contact_data\"><\/span>What does acceptable use mean for recruiting contact data?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>It means you use contact data for relevant recruiting outreach with transparency, reasonable frequency, and a clear opt-out, and you enforce opt-outs through a centralized suppression process.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_counts_as_an_opt-out\"><\/span>What counts as an opt-out?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Any message that reasonably indicates \u201cstop\u201d (for example: \u201cremove me,\u201d \u201cdon&#8217;t contact,\u201d \u201cunsubscribe,\u201d \u201cSTOP\u201d). Treat it as immediate and apply it across channels via your suppression list.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Can_I_contact_clinicians_by_text\"><\/span>Can I contact clinicians by text?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>SMS can be higher-risk than email. If your organization allows it, keep it minimal, identify yourself, include STOP language, and honor opt-outs immediately. Align your process with policies reviewed for TCPA considerations.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_fast_should_opt-outs_be_applied\"><\/span>How fast should opt-outs be applied?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Operationally, same business day is the standard you should enforce so you don&#8217;t re-contact someone who already told you to stop. Make it automatic via a centralized suppression list, not dependent on individual recruiters.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Is_it_acceptable_to_call_a_clinicians_workplace_line\"><\/span>Is it acceptable to call a clinician&#8217;s workplace line?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>It can be acceptable when the outreach is relevant and respectful, and you follow your stop rules. Expect gatekeepers, keep the message short, and don&#8217;t keep calling if you&#8217;re told to stop or route elsewhere. If the clinician opts out (directly or through their office), capture it and enforce it via your suppression list.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_should_I_say_if_a_candidate_asks_where_I_got_their_information\"><\/span>What should I say if a candidate asks where I got their information?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Keep it factual and brief: you recruit in their specialty\/region, you use professional identity context to confirm you&#8217;re contacting the right person, and you use business contact channels for outreach. Offer an easy opt-out and enforce it via your suppression list.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_keep_outreach_ethical_without_killing_speed\"><\/span>How do I keep outreach ethical without killing speed?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Make relevance and suppression automatic: tight targeting rules, short templates, frequency caps, and centralized opt-out enforcement. That reduces wasted touches and keeps recruiters focused on reachable candidates.<\/p>\n<\/section>\n<h2><span class=\"ez-toc-section\" id=\"Next_steps\"><\/span>Next steps<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li>Operationalize opt-outs: implement or fix your suppression list and opt-out management workflow.<\/li>\n<li>Standardize templates and guardrails: pull from recruiting templates and scripts, and enforce relevance and stop rules.<\/li>\n<li>Document trust: align your internal policy with the Heartbeat trust methodology so ops can audit it.<\/li>\n<li>If you want verification, refresh, and suppression handled in one workflow, <a href=\"https:\/\/heartbeat.ai\/signup\">create a Heartbeat account<\/a>.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"About_the_Author\"><\/span><b>About the Author<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><a href=\"http:\/\/heartbeat.ai\/resources\/author\/ben-argeband\"><span style=\"font-weight: 400;\">Ben Argeband<\/span><\/a><span style=\"font-weight: 400;\"> is the Founder and CEO of Swordfish.ai and Heartbeat.ai. With deep expertise in data and SaaS, he has built two successful platforms trusted by over 50,000 sales and recruitment professionals. Ben&#8217;s mission is to help teams find direct contact information for hard-to-reach professionals and decision-makers, providing the shortest route to their next win. Connect with Ben on <\/span><a href=\"https:\/\/www.linkedin.com\/in\/ben-m-argeband-2427a8a3\/\"><span style=\"font-weight: 400;\">LinkedIn<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><br \/>\n<script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"Article\",\"author\":{\"@type\":\"Person\",\"jobTitle\":\"Founder & CEO of Heartbeat.ai\",\"name\":\"Ben Argeband\"},\"description\":\"Operational acceptable-use boundaries for recruiting outreach: relevance, restraint, easy opt-out, suppression list enforcement, and procurement-friendly provenance. Includes do\/don\u2019t, templates, metrics, and stop rules.\",\"headline\":\"Data ethics acceptable use\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/\",\"@type\":\"WebPage\"},\"publisher\":{\"@type\":\"Organization\",\"name\":\"Heartbeat.ai\"}}<\/script><\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"It means you use contact data for relevant recruiting outreach with transparency, reasonable frequency, and a clear opt-out, and you enforce opt-outs through a centralized suppression process.\"},\"name\":\"What does acceptable use mean for recruiting contact data?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Any message that reasonably indicates \u201cstop\u201d (for example: \u201cremove me,\u201d \u201cdon\u2019t contact,\u201d \u201cunsubscribe,\u201d \u201cSTOP\u201d). Treat it as immediate and apply it across channels via your suppression list.\"},\"name\":\"What counts as an opt-out?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"SMS can be higher-risk than email. If your organization allows it, keep it minimal, identify yourself, include STOP language, and honor opt-outs immediately. Align your process with policies reviewed for TCPA considerations.\"},\"name\":\"Can I contact clinicians by text?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Operationally, same business day is the standard you should enforce so you don\u2019t re-contact someone who already told you to stop. Make it automatic via a centralized suppression list, not dependent on individual recruiters.\"},\"name\":\"How fast should opt-outs be applied?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"It can be acceptable when the outreach is relevant and respectful, and you follow your stop rules. Expect gatekeepers, keep the message short, and don\u2019t keep calling if you\u2019re told to stop or route elsewhere. If the clinician opts out (directly or through their office), capture it and enforce it via your suppression list.\"},\"name\":\"Is it acceptable to call a clinician\u2019s workplace line?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Keep it factual and brief: you recruit in their specialty\/region, you use professional identity context to confirm you\u2019re contacting the right person, and you use business contact channels for outreach. Offer an easy opt-out and enforce it via your suppression list.\"},\"name\":\"What should I say if a candidate asks where I got their information?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Make relevance and suppression automatic: tight targeting rules, short templates, frequency caps, and centralized opt-out enforcement. That reduces wasted touches and keeps recruiters focused on reachable candidates.\"},\"name\":\"How do I keep outreach ethical without killing speed?\"}]}<\/script><\/p>","protected":false},"excerpt":{"rendered":"<p>Operational acceptable-use rules for recruiting outreach: relevance, opt-out enforcement, suppression lists, provenance, templates, and stop rules.<\/p>","protected":false},"author":5,"featured_media":54142,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_custom_permalink":"trust-methodology\/data-ethics-acceptable-use","footnotes":""},"categories":[1],"tags":[],"class_list":["post-54143","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\r\n<title>Data ethics acceptable use (recruiting outreach do\/don\u2019t + provenance)<\/title>\r\n<meta name=\"description\" content=\"Practical acceptable-use boundaries for recruiting outreach: relevance, easy opt-out, suppression list enforcement, provenance, stop rules, and metrics. Includes do\/don\u2019t and templates.\" \/>\r\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\r\n<link rel=\"canonical\" href=\"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/\" \/>\r\n<meta property=\"og:locale\" content=\"en_US\" \/>\r\n<meta property=\"og:type\" content=\"article\" \/>\r\n<meta property=\"og:title\" content=\"Data ethics acceptable use (recruiting outreach do\/don\u2019t + provenance)\" \/>\r\n<meta property=\"og:description\" content=\"Practical acceptable-use boundaries for recruiting outreach: relevance, easy opt-out, suppression list enforcement, provenance, stop rules, and metrics. Includes do\/don\u2019t and templates.\" \/>\r\n<meta property=\"og:url\" content=\"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/\" \/>\r\n<meta property=\"og:site_name\" content=\"Heartbeat.ai\" \/>\r\n<meta property=\"article:published_time\" content=\"2026-02-01T18:22:49+00:00\" \/>\r\n<meta property=\"article:modified_time\" content=\"2026-10-19T18:50:57+00:00\" \/>\r\n<meta property=\"og:image\" content=\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/data-ethics-acceptable-use-5d49dc32.png\" \/>\r\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\r\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\r\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\r\n<meta name=\"author\" content=\"Ben Argeband\" \/>\r\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\r\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ben Argeband\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"14 minutes\" \/>\r\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/\"},\"author\":{\"name\":\"Ben Argeband\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/person\\\/e9bcffa7dc47cac9f2379e4449e98207\"},\"headline\":\"Data ethics acceptable use for recruiting outreach (boundaries, do\\\/don\u2019t, provenance)\",\"datePublished\":\"2026-02-01T18:22:49+00:00\",\"dateModified\":\"2026-10-19T18:50:57+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/\"},\"wordCount\":2794,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/data-ethics-acceptable-use-5d49dc32.png\",\"articleSection\":[\"News\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/\",\"url\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/\",\"name\":\"Data ethics acceptable use (recruiting outreach do\\\/don\u2019t + provenance)\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/data-ethics-acceptable-use-5d49dc32.png\",\"datePublished\":\"2026-02-01T18:22:49+00:00\",\"dateModified\":\"2026-10-19T18:50:57+00:00\",\"description\":\"Practical acceptable-use boundaries for recruiting outreach: relevance, easy opt-out, suppression list enforcement, provenance, stop rules, and metrics. Includes do\\\/don\u2019t and templates.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/#primaryimage\",\"url\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/data-ethics-acceptable-use-5d49dc32.png\",\"contentUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/data-ethics-acceptable-use-5d49dc32.png\",\"width\":1024,\"height\":1024},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/trust-methodology\\\/data-ethics-acceptable-use\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Data ethics acceptable use for recruiting outreach (boundaries, do\\\/don\u2019t, provenance)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#website\",\"url\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/\",\"name\":\"Heartbeat.ai\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#organization\",\"name\":\"Heartbeat.ai\",\"url\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/Heartbeat.ai-logo.png\",\"contentUrl\":\"https:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/Heartbeat.ai-logo.png\",\"width\":704,\"height\":126,\"caption\":\"Heartbeat.ai\"},\"image\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/person\\\/e9bcffa7dc47cac9f2379e4449e98207\",\"name\":\"Ben Argeband\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g\",\"caption\":\"Ben Argeband\"},\"url\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/author\\\/ben-argeband\\\/\"}]}<\/script>\r\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Data ethics acceptable use (recruiting outreach do\/don\u2019t + provenance)","description":"Practical acceptable-use boundaries for recruiting outreach: relevance, easy opt-out, suppression list enforcement, provenance, stop rules, and metrics. Includes do\/don\u2019t and templates.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/","og_locale":"en_US","og_type":"article","og_title":"Data ethics acceptable use (recruiting outreach do\/don\u2019t + provenance)","og_description":"Practical acceptable-use boundaries for recruiting outreach: relevance, easy opt-out, suppression list enforcement, provenance, stop rules, and metrics. Includes do\/don\u2019t and templates.","og_url":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/","og_site_name":"Heartbeat.ai","article_published_time":"2026-02-01T18:22:49+00:00","article_modified_time":"2026-10-19T18:50:57+00:00","og_image":[{"width":1024,"height":1024,"url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/data-ethics-acceptable-use-5d49dc32.png","type":"image\/png"}],"author":"Ben Argeband","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ben Argeband","Est. reading time":"14 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#article","isPartOf":{"@id":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/"},"author":{"name":"Ben Argeband","@id":"https:\/\/heartbeat.ai\/resources\/#\/schema\/person\/e9bcffa7dc47cac9f2379e4449e98207"},"headline":"Data ethics acceptable use for recruiting outreach (boundaries, do\/don\u2019t, provenance)","datePublished":"2026-02-01T18:22:49+00:00","dateModified":"2026-10-19T18:50:57+00:00","mainEntityOfPage":{"@id":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/"},"wordCount":2794,"commentCount":0,"publisher":{"@id":"https:\/\/heartbeat.ai\/resources\/#organization"},"image":{"@id":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#primaryimage"},"thumbnailUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/data-ethics-acceptable-use-5d49dc32.png","articleSection":["News"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/","url":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/","name":"Data ethics acceptable use (recruiting outreach do\/don\u2019t + provenance)","isPartOf":{"@id":"https:\/\/heartbeat.ai\/resources\/#website"},"primaryImageOfPage":{"@id":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#primaryimage"},"image":{"@id":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#primaryimage"},"thumbnailUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/data-ethics-acceptable-use-5d49dc32.png","datePublished":"2026-02-01T18:22:49+00:00","dateModified":"2026-10-19T18:50:57+00:00","description":"Practical acceptable-use boundaries for recruiting outreach: relevance, easy opt-out, suppression list enforcement, provenance, stop rules, and metrics. Includes do\/don\u2019t and templates.","breadcrumb":{"@id":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#primaryimage","url":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/data-ethics-acceptable-use-5d49dc32.png","contentUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/data-ethics-acceptable-use-5d49dc32.png","width":1024,"height":1024},{"@type":"BreadcrumbList","@id":"https:\/\/heartbeat.ai\/resources\/trust-methodology\/data-ethics-acceptable-use\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/heartbeat.ai\/resources\/"},{"@type":"ListItem","position":2,"name":"Data ethics acceptable use for recruiting outreach (boundaries, do\/don\u2019t, provenance)"}]},{"@type":"WebSite","@id":"https:\/\/heartbeat.ai\/resources\/#website","url":"https:\/\/heartbeat.ai\/resources\/","name":"Heartbeat.ai","description":"","publisher":{"@id":"https:\/\/heartbeat.ai\/resources\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/heartbeat.ai\/resources\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/heartbeat.ai\/resources\/#organization","name":"Heartbeat.ai","url":"https:\/\/heartbeat.ai\/resources\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/","url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2021\/04\/Heartbeat.ai-logo.png","contentUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2021\/04\/Heartbeat.ai-logo.png","width":704,"height":126,"caption":"Heartbeat.ai"},"image":{"@id":"https:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/heartbeat.ai\/resources\/#\/schema\/person\/e9bcffa7dc47cac9f2379e4449e98207","name":"Ben Argeband","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g","caption":"Ben Argeband"},"url":"https:\/\/heartbeat.ai\/resources\/author\/ben-argeband\/"}]}},"permalink_manager":null,"_links":{"self":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54143","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/comments?post=54143"}],"version-history":[{"count":4,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54143\/revisions"}],"predecessor-version":[{"id":66890,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54143\/revisions\/66890"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media\/54142"}],"wp:attachment":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media?parent=54143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/categories?post=54143"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/tags?post=54143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}