Specifications for Obtaining Consent to Store Profile Data

You must make it transparent to the member that you intend to store their Profile Data. This can occur either by (1) a written statement or (2) by pre-filling a member editable form with their Profile Data as further described below.  You must also give the member an opportunity to review and agree to your privacy policy.

1. Written Statement

  • a. If you choose to use a written statement, your intent to store (vs. cache) Profile Data must be obvious to the vast majority of members through the use of clear, unambiguous language, such as "By clicking Sign in with LinkedIn, you agree to let [Your Company or Application Name] store your LinkedIn profile" or "I agree to let [Your Company or Application Name] store my LinkedIn profile."
  • b. Such clear, unambiguous language must appear next to the link, button, or other object clicked by the member to trigger the action which stores their Profile Data, and must be in a font size and color that would be noticeable to a member going through this process.
  • c. Alternatively, your written statement can appear in your privacy policy. If you choose to include such written statement in your privacy policy, (i) each applicable member must accept your privacy policy prior to or in conjunction with any action that saves their Profile Data, (ii) your intent to store (vs. cache) Profile Data must be obvious to the vast majority of members through the use of clear, unambiguous language, and (ii) you must prominently identify and link to your privacy policy at those locations where members may download or access your Application or where consent to store Profile Data is otherwise obtained.
  • d. If we believe the language used is insufficiently transparent to a member that his or her Profile Data is being stored, we may require you to adjust the text and/or its display.

2. Pre-Fill

  • a. If you choose to use a pre-filled member editable form, such as a site registration or job application, (i) your intent to store (vs. cache) Profile Data must be obvious to the vast majority of members through the display of all fields you wish to store (with the exception of their Member ID, the API standard profile request URL, and audit timestamps) and (ii) the member must be allowed the opportunity to edit or delete the pre-filled Profile Data as desired.
  • b. If a member edits any of the pre-filled Profile Data, you may only store the data as edited by such member, and not the data originally populated in such pre-filled fields. You may not store any Profile Data that a member deletes from the pre-filled editable form.
  • c. If we believe the pre-filled member editable form is insufficiently transparent to a member that his or her Profile Data is being stored, we may require you to adjust the form and/or its display.