Privacy Policy

Who we are#

Almujeb AI (the "Platform") lets owners of Facebook Pages and Instagram business accounts ("Clients") reply automatically to comments and direct messages sent to their accounts. It is operated by [Operating entity name] ([Country]) ("we", "us").

The Platform is not made by, affiliated with or endorsed by Meta. Facebook, Instagram and Messenger are trademarks of Meta Platforms, Inc.

This text addresses two groups: the Client who opens a business workspace and connects accounts to the Platform, and the person who comments on a Client's page or messages it, so that their words reach us through Meta.

Data we process#

Client and workspace data

• Name, email address and password. The password is stored hashed; we do not keep it in plain text.
• Session data: the IP address and browser type of each sign-in session, and its duration.
• The workspace name and time zone, its members and their roles.
• Subscription data: the plan and its period, gift codes redeemed, and partner-programme data for those who join it.
• Workspace actions in the dashboard (the audit log): who did what and when, by identifiers rather than message text.
• Support conversations: what a Client or a visitor to the public site writes in the support chat and the replies from the assistant and the support team, kept as an archive for review and for improving answers and not subject to the retention periods below.

Data of accounts a Client connects from Meta

• The Page or Instagram account ID and name (and the Instagram username) and a link to its picture.
• The access token Meta issues when connecting. It is stored encrypted in a separate table and never appears in logs.
• The account's posts: post ID, an excerpt of its text, its link, thumbnail and date, so the Client can pick a specific post for a reply rule.
• What the Client writes in the Platform: reply instructions, knowledge sources (texts and FAQs) and comment reply rules.
• The product catalogue the Client enters (product names, descriptions, prices, images and links): the Client's own business content, part of which is sent to the person who messages the account within the reply to them, and whose images are served from a public URL that anyone holding the link can view.

Data of people who comment on or message a connected account

When a comment or direct message reaches a connected account, Meta sends us the event data, and we store:

• The identifier Meta gives this person for the account concerned, and their name and username where Meta provides them.
• The text and time of the comment or message, and the post that was commented on.
• The replies we sent on the Client's behalf: their text, time and delivery result.
• A "once per person per post" record when the Client enables it in a comment rule.

We do not ask this person for anything and do not access their profile, friends or posts beyond what Meta puts in the notification. What they write themselves in a message may include other personal data, so we process the text as it arrives.

Operational data

• Incoming notifications as received and normalised, which include the comment or message text, and the log of their processing steps, results and error codes.
• The model-call log: model name, token counts, latency and outcome, without the texts.
• Usage counters and their ledger (numbers, not texts) and account-status alerts.
• Server logs: identifiers, statuses and error codes, without message texts, access tokens or email addresses. The entry gateway keeps an access log that includes IP addresses.

Why we process this data#

• To run the service: receive comments and messages, reply to them with the Client's rules or the smart reply, and send the reply through Meta.
• To manage the account, subscription and quotas, and to support the Client.
• To protect the Platform and its Clients: prevent abuse and fraud and trace faults.
• To meet our legal obligations.

We do not sell or rent data, do not use it for advertising, do not use message and comment texts to train AI models, and do not use Meta data for anything other than providing the service to the Client who connected the account.

Smart reply and the model provider#

The smart reply to direct messages uses a language model configured by the Platform operator: a model it hosts on its own servers, or a model service from an external provider. What is sent to the model for each reply: the latest messages of the conversation, the comment text and post excerpt when the conversation began with a comment, the Client's instructions, the knowledge passages closest to the question, and the account name and channel. The person's identifier and name are not sent.

If vector search is enabled for knowledge, the passages and the question text are sent to the vector server the operator configures. What reaches an external provider is subject to that provider's terms and privacy policy. Rule-based replies to comments do not use a model.

Smart replies can be wrong. The Client sets their instructions and knowledge and can switch them off for any account or conversation.

Who we share data with#

• Meta: we receive notifications from it and send replies to it, subject to its terms and data policy.
• The model provider and, if any, the vector provider: as described in the smart reply section.
• The infrastructure providers the Platform runs on (server hosting, database and backups): they process data on our instructions and only to run the Platform.
• Public authorities, where a law or a valid court order requires us to.

A Client sees in their dashboard the comments, messages and replies of their accounts, and workspace members see them according to their roles. One Client cannot see another Client's data.

Where data is processed#

Data may be processed and stored in a country other than yours, depending on where it is hosted and on the model provider. If your country's law requires specific safeguards for this, write to [Contact email].

Retention periods#

A daily automated task deletes what has expired. The periods in force on the Platform:

• Texts of comments and messages, our sent replies, conversations and the related people's data: 12 months from creation (a conversation from its last message).
• The model-call log: 12 months.
• Incoming notifications as received and their processing log: about 90 days. They are deleted in whole monthly partitions, so a notification may remain for up to four months.
• The usage ledger and the audit log: 24 months.
• Keys that prevent duplicate processing: 72 hours.
• The Client's account and workspace data: as long as the workspace exists, and deleted on request as described in "Deleting your data".
• Subscription, gift-code and commission records: not deleted with people's content because they are financial records.
• Backups: database backups are kept for 14 days and then deleted, so what was deleted from the Platform may remain in them until that period ends.

Deleting your data#

You can ask for your data to be deleted at any time in one of these ways:

• A Client: from the Accounts page, by disconnecting the account and choosing "Also delete this account's data".
• A Client who connected their account through Facebook or Instagram: by removing the Almujeb AI app from their account settings at Meta and requesting deletion of its data; the request reaches us from Meta and we carry it out.
• Anyone: by writing to [Contact email].

The Data Deletion page details what is deleted and what is kept, and how to follow your request with the confirmation code.

Protecting data#

• Each Client's data is isolated in the database itself by row-level policies, not in the application alone.
• Access tokens are encrypted with a key kept outside the database.
• Connections to the Platform are encrypted (HTTPS).
• Message texts and access tokens are not written to logs.
• Access to data is limited by role.

No system is completely secure. If a breach affects your data, we will notify those concerned as the law requires.

Your rights#

Depending on the law of your country, you have rights that include knowing what we hold about you, correcting it, deleting it, and objecting to or restricting its processing. Write to [Contact email] and we will reply after verifying your identity or your connection to the account concerned.

If you message a business page, its owner has a role in your data and we may refer your request to them. You may also complain to the data protection authority in your country.

Cookies#

• The session cookie: keeps you signed in, and is necessary for the dashboard to work.
• The referral cookie (almujeb_ref): set when you arrive through an approved partner's link, it stores only the partner's code so your sign-up can be credited to them, and is cleared after the workspace is created. Its lifetime is a Platform setting.

We do not use cookies for advertising or tracking, and no third-party analytics tools.

Children#

The Platform is aimed at businesses, and no one under 18 may open a workspace on it. If a child's data reaches us, write to [Contact email] and we will delete it.

Changes to this policy#

We publish any change on this page and update the last-updated date at the top. Continuing to use the Platform after publication means you accept the change.

Contact#

[Operating entity name], [Country].

For questions, rights requests and deletion requests write to [Contact email].