Email Inbox Permissions FAQs

  1. What does Lusha do with Email Inbox API permission?

    1. Lusha extracts business contact details within signature blocks and other information from business email inbox accounts (“Email Account”) of consenting Email Account holders who are employees or personnel otherwise authorized to enter into agreements on behalf of their employers (“Lusha Users”) (where those employers are Lusha’s customers (“Customers”)).
    2. Lusha Users provide permission (on behalf of their company) for Lusha to access their Email Account by enabling the feature and agreeing to Lusha’s standard terms.

  2. What is the legal basis for such processing?

    1. The processing is necessary for the performance of a contract in terms of which Lusha will deliver a new product feature that monitors job changes (“Feature”) by extracting and scanning message contents for the purpose of detecting and recording changes (against existing information in Lusha’s customer-facing service (“Service”)) about the professional contact information of individuals (names, email addresses and phone numbers) as well as job title, seniority, role and location of that individual (“Business Profile Information”).
    2. If a Lusha User activates this Feature, Lusha will record their assent to the relevant terms and DPA, and configure its tools to extract message contents from messages in the Lusha User’s Email Account inbox (as a service provided to such Customers).
    3. Lusha will then be permitted to create a copy of the message contents and extract and scan the message to:
      1. determine which individuals the Lusha User has interacted with;
      2. query and match those individuals’ details in the signature block of the message (as well as received from fields) to existing Business Profile Information about the sending party in the Service. Please note that Lusha will only scan the signature block, and will not scan the content of the “body” of the message for any contact details contained therein; and
      3. where a position change is detected, alert the Lusha User (e.g., “your business contact now has a different title”).
    4. Lusha will also use this information for accuracy scoring and to create a ‘shopping list’ of potential Business Profile Information that it does not hold in the Service. This Feature performs this function on all messages stored in the inbox that have been sent or received in the past year, not merely messages where the Lusha User “matches” an entry in the Service (as technically, there is no way to limit this prior to scanning the message). In other words, all senders are deemed to be persons to whom the Customer or Lusha User would value job change updates.

  3. Is Lusha a Processor or Controller?

    1. Lusha intends to provide the Feature in its capacity as a data processor on behalf of the Customer (i.e., the Lusha User’s employer). The Feature enables Customers to be made aware of any job changes of their contacts so that they can unlock sales or marketing opportunities.