Privacy Policy
Last updated 16 November 2026.
This policy explains what personal data Reply Manager processes, why, and what you can do about it. Reply Manager is operated by MM LLC ("we", "us"). Contact: social@flirtfordate.com.
What Reply Manager does
Reply Manager answers, on behalf of a business, people who comment on that business's Facebook Page or who write to the Page in Messenger — in public, with a reply under the comment, and in private, in Messenger. It can also moderate the comments on the Page: hide or delete a comment, like it, or block its author from the Page, following the rules the business sets. For the people who interact with such a Page, the business decides why and how Reply Manager is used, and we process their data on its behalf.
Data about people who interact with a business's Page
- Comments on the business's posts and ads that Meta delivers to the Page: the text, when it was written, the post it is under and that post's text (read so that an answer fits it), and the commenter's name and the ID Meta uses for them on that Page. Where the business has chosen it, the earlier comments of the same thread are read with a comment, for the same reason.
- What was done about a comment: the category it was given, a rendering of its words in English (so that the business can read it), and what was done — a public reply under it with that reply's words, a hide or an unhide, a delete, a like, a block — with Meta's answer; and, for each Page, how many of a person's comments fell into a category the business moderates, when the last of them came, and whether and when they were blocked from the Page.
- Messenger conversations with the Page: the messages exchanged, their times, how far you have read the Page's messages (the time Messenger reports, nothing else), and your Page-scoped ID — the number Messenger uses for you on that Page.
- Your name, from your comment or, if you write to the Page first, from the profile information Meta makes available: your name, first name and last name. Nothing else from your profile — no photo, no friends, no location.
- What you tell the conversation — for example a size or a choice you give in answer to a question.
- Whether the conversation reached its goal: whether you opened a link it sent, and which one when it sent several, and, where the business's own website reports it, whether you completed a named step there, such as signing up.
- A request not to be messaged, if the business puts you on its "Do not message" list — for example because you asked it by e-mail or by phone. Reply Manager then also asks Meta for the ID that identifies you on the Pages that business owns, and keeps it, like your other IDs, only as a one-way fingerprint — never the ID itself — so that the request holds on all of those Pages. While a business keeps such a list, that ID may be asked of Meta for anyone who comments or writes, only to compare it with the list; it is not kept.
Data about businesses using Reply Manager
- Account details: e-mail address, role, and a password stored only as a one-way hash.
- When a Page is connected, the list of Pages the person connecting it manages is read so that they can choose; only the Pages they choose are kept.
- The Facebook Pages a business connects, and the access tokens Meta issues for them, stored encrypted. Each Page's profile picture is shown beside it: Reply Manager fetches it from Facebook when it is shown, keeps it in memory for a few hours at most, and never stores it.
- For each Page, who connected it: the Facebook ID that Meta gives Reply Manager for that person, and their name, shown to the business beside the Page, with their profile picture. The picture is fetched from Facebook by that ID when it is shown, kept in memory for a few hours at most, and never stored. Nothing else from their Facebook account is used, and the access token they sign in with is used only while connecting and then discarded.
- The business's settings, categories, conversation scenarios and the facts it provides.
Why we use it
Only to provide the service the business has set up: to receive the Page's new comments and messages as they happen (Reply Manager subscribes to the Page's events, and checks that the subscription is still active); to tell whether a comment was written by a person or by another Page; to decide whether a comment or a message should be answered; to write and send the answers, in public under a comment and in private in Messenger; to hide, delete or like comments, or block their authors from the Page, where the business has chosen to; to hand a conversation to the business's staff; to follow Messenger's rules — one private reply per comment, the 24-hour window, stopping when asked; to show the business its conversations; and to measure whether conversations reached their goal and how they ended. We do not sell personal data, we do not use it for advertising, and we do not use it to train artificial intelligence models.
How replies are written
Replies, public and private, are written automatically by a large language model, used through its provider's API (currently Anthropic's Claude), following the business's instructions and using only the facts the business has provided. Before anything is done about a comment, a language model reads it once to tell which of the business's categories it belongs to; that decides whether it is answered or moderated, and how. When a person asks for a human, the conversation is handed to the business's staff; when anything suggests that a person may be under 18, the messages stop.
Who else receives data
- Meta Platforms — messages, public replies and moderation travel through Facebook and Messenger, under Meta's own terms and privacy policy.
- Anyone who can see the post — a public reply is a comment of the Page, shown under yours like any other.
- Our language-model provider (currently Anthropic) — processes the text of comments and messages to produce the answers, as our service provider.
- Our hosting provider — stores the data on our behalf.
- Our network provider (currently Cloudflare) — carries every request to Reply Manager and its answers, as our service provider.
- The business whose Page you interacted with — it sees your comments, what was done about them, and your conversation with its Page.
We do not share personal data with anyone else, except where the law requires it.
How long we keep it
We delete a person's conversations, messages, comments and what a conversation noted 90 days after that person's last message or comment, automatically, once a day — or sooner, on request (see Data deletion). If you replied STOP, we keep only a one-way fingerprint of your Facebook IDs for that Page — not the IDs, no name and no words — so that we never message you again; it is deleted when the business removes that Page from Reply Manager, or when you ask us to delete your data. If the business put you on its “Do not message” list, the same kind of fingerprint is kept until the business takes you off it or you ask us to delete your data.
Your choices and rights
- Ask to stop at any time, in any words — STOP is enough — or write to us at social@flirtfordate.com, and Reply Manager will not message you again.
- You can ask for a copy of your data, for it to be corrected, or for it to be deleted — see Data deletion, or write to social@flirtfordate.com. You may also contact the business whose Page you interacted with.
- A hide or a block is the business's decision: to have one lifted, ask the business. Deleting your data from Reply Manager does not undo what was done on Facebook — a public reply stays under your comment, and a block stays, until the business removes them.
- Depending on where you live, you may have further rights, including the right to complain to a data protection authority.
Security
Access tokens and secrets are encrypted, each business can see only its own data, and passwords are stored only as one-way hashes.
Children
Reply Manager is not intended for anyone under 18. When a conversation suggests that a person may be under 18, the assistant stops.
Changes
We publish any change to this policy on this page, with the date it was last updated.