Legendary Messenger CRM's use of information received from its users complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
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, and your script, image and link libraries. | 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.
2. Where the data goes
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. There is no transmission of your contact records, notes, images or conversation data to us or to any third party by default, and no server-side copy of your pipeline exists.
Two features move data, and only because you direct them to:
- Export and backup. A CSV or JSON file your browser writes to your own computer, when you press the button.
- Outbound webhook. If — and only if — you configure a webhook URL in settings, record changes are sent to the destination you chose. We are not that destination and we do not receive a copy.
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.
- 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@legendaryleads.co 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@legendaryleads.co or write to Tri-Johnson Marketing Solutions, LLC, PO Box 12, Waverly, IA 50677.