Update for IdP details - minor edit

templates/about/edi-policy.html

@@ -14,7 +14,7 @@
 <li><a class="link-dark rounded text-muted" href="#privacy-policy">Privacy policy</a><ul class="fw-normal">
 <li><a class="link-dark rounded text-muted" href="#definitions_1">Definitions</a></li>
 <li><a class="link-dark rounded text-muted" href="#why-and-how-we-collect-personal-data">Why and how we collect personal data</a></li>
-<li><a class="link-dark rounded text-muted" href="#third-party-identity-provider-user-information">Third-party identity provider user information</a><ul class="fw-normal">
+<li><a class="link-dark rounded text-muted" href="#third-party-identity-provider-customer-information">Third-party identity provider customer information</a><ul class="fw-normal">
 <li><a class="link-dark rounded text-muted" href="#github">GitHub</a></li>
 <li><a class="link-dark rounded text-muted" href="#google">Google</a></li>
 <li><a class="link-dark rounded text-muted" href="#microsoft">Microsoft</a></li>
@@ -99,7 +99,7 @@ <h3 id="why-and-how-we-collect-personal-data">Why and how we collect personal da
 <li>Customer email or other contact information. EDI customers may register contact information with EDI for the purpose of notification when the creation, addition, or modification of science data and metadata that is curated by EDI occurs within the EDI data repository. Notifications of this type serve to inform customers when new or updated science data are added to the system or to alert customers when science data are found to be suspect or erroneous post-publication. The collection of customer contact information is an option provided to EDI customers during an authenticated web browser session. Customer contact information includes only an email address.</li>
 <li>Web browser session cookies and authentication tokens. EDI websites utilize web browser session cookies and authentication tokens to maintain an authenticated state between the customer's web browser and EDI's website services. Session cookies are generated by the EDI website and authentication tokens are generated by the EDI authentication service at the point a customer self-identifies. EDI authentication tokens include the customer's unique identifier, a token time-to-live, and any membership in recognized roles or groups.</li>
 </ol>
-<h3 id="third-party-identity-provider-user-information">Third-party identity provider user information</h3>
+<h3 id="third-party-identity-provider-customer-information">Third-party identity provider customer information</h3>
 <p>The Environmental Data Initiative utilizes third-party identity providers, <a href="https://github.com" rel="noopener noreferrer" target="_blank">GitHub</a>, <a href="https://google.com" rel="noopener noreferrer" target="_blank">Google</a>, <a href="https://microsoft.com" rel="noopener noreferrer" target="_blank">Microsoft</a>, and <a href="https://orcid.org" rel="noopener noreferrer" target="_blank">ORCID</a>, to authenticate and uniquely identify customers who (1) require access to authentication controlled science data and metadata; (2) use EDI’s “ezEML” metadata editor web application, which requires a unique customer identifier for retaining application history; or (3) wish to create a unique customer profile within the suite of EDI web applications. This form of identity authentication relies on the OAuth2.0/OpenId Connect protocols used to communicate between your client browser, EDI, and the identity provider (IdP). EDI does not store customer authentication (“sign-on”) credentials on any EDI host server. However, in addition to securely verifying your identity, the IdP allows EDI access to minimal information they maintain about you: a string value that uniquely identifies you within their system (e.g., an email address) and your common name (if available). EDI may store this information in a web-based session cookie for customer identification on websites, in database applications maintained by EDI that are related to customer profiles or to match customer interactions with an EDI data product, or within an EDI authentication token that is used to convey customer identity information to one of EDI’s web services that implements access control. By selecting authentication through a third-party IdP, you consent to releasing this information for the above purposes. The following sections list detailed information that each IdP releases to EDI:</p>
 <h4 id="github">GitHub</h4>
 <p>The information released about you from GitHub includes:</p>