Legendary Messenger CRM's and Legendary Connector's use of information received from their users complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
This disclosure covers both extensions. Section 1 sets out what Legendary Messenger CRM handles; Section 1b sets out what Legendary Connector handles. The commitments in Section 3 apply to both.
This page is the disclosure that policy requires. It supplements, and does not replace, our full Privacy Policy.
1. What the extension handles
Legendary Messenger CRM is a customer-relationship tool that runs on facebook.com and messenger.com. It handles the following categories of data, all of which are written to a database inside your own browser on your own device:
| Category | Specifically | Why the feature needs it |
|---|---|---|
| Conversation identifiers | The thread identifier of a conversation you have open. | It is the key that attaches your notes, stage and follow-up to the correct record. Without it the extension cannot tell one conversation from another. |
| Personal communications metadata | The display name and avatar shown on the open conversation, and where present its profile link. | So your pipeline shows a person's name and face rather than an opaque identifier, and so duplicate records for the same person can be reconciled. |
| Personal communications | The text of messages visible in the conversation you have open, read transiently to compute a 32-bit fingerprint of the most recent incoming message. The fingerprint is stored; the text is not. | It is the only way to tell a new reply from one already seen, which is what advances a contact from New Lead to Replied and what attributes a reply to the script that earned it. A fingerprint cannot be reversed into the message. |
| User-authored content | Notes, tags, pipeline stage, follow-up reminders, contact details you type in, your script, image and link libraries, the products you sell, and the Facebook groups you save with any posts you note against them. | This is the product. It is your CRM data. |
| Website content | Only what is already rendered on the Facebook or Messenger page you have open, read at the moment you have it open — including the position of message bubbles, and your own first name from your account. | To place the context bar, the stage labels and the script picker into the interface, to identify the open conversation, and to tell incoming messages from outgoing ones (their bubbles sit left, yours sit right — nothing in the markup says which is which). |
Message text is never stored and never transmitted. The extension does not collect friend lists, group member lists, or information about people you are not already in a conversation with.
1b. What Legendary Connector handles
Legendary Connector is a prospecting tool that runs on facebook.com only. It sends friend requests to people you have targeted, and one intro message to those who accept. It handles these categories, all written to a database inside your own browser on your own device:
| Category | Specifically | Why the feature needs it |
|---|---|---|
| Website content | What is already rendered on a group member list, a post's comments, or a profile you have opened — a person's name, their profile link, the short lines Facebook shows about them, the public "Lives in" line, publicly shown gender, and whether a friend-request control is present. Read at the moment the page is open. | These are the values your filters run on. A person is screened on the card first, and on their profile second, because the card carries a place on only a small minority of rows. |
| Personally identifiable information (people you contacted) | Only for a person a friend request was actually sent to: name, profile link, an internal key derived from that link, the group they came from, timestamps, request status, and which of your message variants was used. | To stop the same person being requested twice, to detect an acceptance, to send the intro message once, and to produce your own acceptance figures. Everyone screened out is counted and dropped without being recorded. |
| User-authored content | Your saved groups, campaigns, filters, keyword sets, and the intro messages you write. | This is your configuration. The extension ships with no messages of its own. |
No member list is ever assembled, exported or transmitted. The extension does not collect friend lists, and it builds no database of people you did not contact.
2. Where the data goes (both extensions)
It stays on your device. The extension writes to your browser's local storage and local database — including the images you add to the image library, which are stored locally as encoded data so they can be handed to Facebook's own upload control later. None of your contact records, notes, images or conversation data is transmitted to us, and no server-side copy of your pipeline exists. We do not receive it, and we could not produce it if we were asked to.
One thing does leave your computer, and only when you ask it to: signing in sends your email address and password to Google's Identity Platform, which is what proves your subscription is active. That is an account credential, not conversation data — nothing about your contacts or your messages travels with it. The Privacy Policy sets out exactly what is sent and to whom.
Legendary Connector transmits nothing at all beyond that sign-in. Friend requests and the intro message are performed inside your own browser, in your own Facebook session, by clicking the same controls you would click yourself — nothing about the people involved is sent to us.
Two features move data, and only because you asked them to:
- Export and backup. A CSV or JSON file your browser writes to your own computer, when you press the button.
- Sending a contact to your own CRM — Legendary Messenger CRM only; Legendary
Connector has no such feature. If you connect a webhook address, a contact record can be sent from your
computer to that address: the name, email, phone, business, website, address, pipeline
stage, tags and custom fields on that person's card. Message text and note bodies are not in
it — the extension holds only a fingerprint of a message, never the message. By default a
record goes only when you press a button on that person's page; the two automatic triggers are off until
you switch them on. The extension asks for permission to reach that one address at the moment you connect
it and hands the permission back when you disconnect, and only
httpsaddresses are accepted.
That destination is yours, not ours. We do not choose it, we are not sent a copy, and no server of ours sits in the path — the request goes from your browser to the address you entered. It is the same distinction drawn in Section 3 below: we are not transferring your data to a third party, you are moving your own data into your own system.
3. Our Limited Use commitments
In accordance with the Chrome Web Store User Data Policy, we affirm the following about all data the extension obtains:
- Use is limited to providing or improving the user-facing features that are prominent in the extension's interface and listing. Data is not used for any unrelated purpose.
- We do not transfer the data to third parties, except where necessary to provide or improve those user-facing features, to comply with applicable law, or as part of a merger, acquisition or sale of assets with notice and consent as required. Sending a record to a webhook address you connected is not a transfer by us: it never reaches us, and it goes only where you pointed it.
- We do not use or transfer the data for serving advertising, including personalized, retargeted or interest-based advertising.
- We do not use or transfer the data to determine creditworthiness or for any lending purpose.
- We do not allow humans to read the data, except with your affirmative consent for a specific instance (for example, if you send us an export while asking for support), where necessary for security purposes such as investigating abuse, to comply with applicable law, or where the data has been aggregated and anonymized.
- We do not sell the data, and we do not use it to train machine-learning or generative-AI models.
4. Remotely hosted code
The extension does not execute remotely hosted code. Its logic ships inside the extension package and is reviewed as part of the Chrome Web Store submission. The extension may fetch a versioned configuration file consisting of selector strings, which it needs because Facebook changes its page markup without notice; that file contains data only — no executable logic, and nothing that changes what the extension is permitted to do.
5. Deleting the data
You can clear your data from the extension's settings at any time, or remove all of it by uninstalling the extension. Because the data is local, uninstalling deletes it and we cannot recover it for you — export a backup first if you want to keep it.
For the separate account and billing information we hold as a subscription business, see Sections 4, 7 and 8 of the Privacy Policy, or email support@trijohnson.com to request deletion.
6. Not affiliated with Facebook or Meta
Legendary Messenger CRM is an independent product of Tri-Johnson Marketing Solutions, LLC. It is not a part of, endorsed by, certified by, or affiliated with Facebook, Meta Platforms, Inc., or Google LLC. FACEBOOK and MESSENGER are trademarks of their respective owners.
7. Questions
Email support@trijohnson.com or write to Tri-Johnson Marketing Solutions, LLC, PO Box 12, Waverly, IA 50677.