This policy explains what information Peg ("Peg," "we," "us") handles when a financial firm's advisor connects an email account to Peg, and how we protect it. Peg's website is pegcompliance.com. The operator of Peg is [LEGAL ENTITY NAME], [ADDRESS].
Peg is a compliance routing service. A firm gives us a list of people (clients, prospects and staff) whose communications it must retain. An advisor of that firm connects an email account. When a message is sent or received in that account, Peg checks whether the sender and the recipient are both on the firm's list. If they are, Peg forwards a copy of that message to the firm's compliance archive. If they are not, Peg takes no further action and keeps nothing.
From the advisor's email account (through Google or Microsoft). With the advisor's permission, Peg is granted read access to the account. For every message, Peg first reads only the sender and recipient addresses and the message's technical identifier. Peg does not request the subject, the body or the attachments at this stage. Only if the sender and the recipient both match the firm's list does Peg then download the full message so it can be delivered to the firm's archive.
From the firm. The firm's list of names, email addresses and phone numbers, and the names and email addresses of the advisors and administrators who use Peg.
Sign-in information. The advisor's account email address and the access tokens Google or Microsoft issue to Peg. Peg never receives or stores the advisor's password.
We use information only to provide the routing service to the advisor's firm: to decide whether a message must be forwarded, to deliver it to the firm's archive, and to show the firm that it was delivered. We do not sell information. We do not use information received from Google or Microsoft for advertising, and we do not use it to develop or train generalized AI or machine learning models.
Peg's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In particular, Peg requests read-only Gmail access (the gmail.readonly permission) and uses it only to provide the routing service described in this policy. No human at Peg reads an advisor's email, except where needed for security purposes, to comply with law, or with the advisor's explicit consent.
Matched messages are delivered to the compliance archive the firm has chosen. The firm is responsible for that archive. Peg's service providers (cloud hosting, database and email delivery) process information on our behalf under confidentiality and security obligations. We will disclose information where required by law.
Information is encrypted in transit. Access tokens and any queued messages are encrypted before they are stored, with keys held in a managed key service. Access to systems is limited to what is needed. If we learn of an incident that affects a firm's information, we will notify the firm promptly, within the time its agreement with us requires.
Advisors can disconnect their account at any time, from Peg or from their Google or Microsoft account settings. When an account is disconnected, Peg revokes its access and deletes the stored token. Firms can ask us to delete their data when they stop using Peg. Routing records may be kept for as long as the firm's agreement requires, because they support the firm's own recordkeeping.
Advisors can withdraw Peg's access at any time. Individuals who are on a firm's list can contact that firm about their information. Questions to Peg can be sent to the address below.
If we change this policy we will post the new version here and update the date above.
[LEGAL ENTITY NAME]
[ADDRESS]
privacy@pegcompliance.com