Facebook Integration Documentation for chatbot_practika

1. Overview of the Application

chatbot_practika is a SaaS platform that enables verified Page Admins and Business Managers to manage Facebook Pages, automate Messenger conversations, respond to messages via Human Agent mode, manage comments, schedule posts, and analyze audience engagement.

The platform only accesses Page data after the Page Admin explicitly logs in using Facebook Login and grants the required permissions.

We do NOT collect, sell, or share user data with any third party. All data is used solely to deliver the features requested by the Page owner.

2. Data Collection and Use

The application collects the following categories of data only after the Page Admin grants access:

• Page name, Page ID, Page access token
• Page posts, comments, and messages
• User profile fields allowed by Meta (first name, last name, profile picture, gender, locale, timezone)
• Page insights and analytics
• Webhook events (messages, comments, feed events)

Purpose of data processing:

• Managing Messenger conversations (AI bot + Human agent)
• Managing Facebook Page posts
• Responding to comments
• Generating insights and analytics
• Automating replies and workflows
• Subscriber management
• Delivering Page-admin–requested services inside chatbot_practika

We do NOT use Page data for:

• Advertising or selling user data
• Creating or selling third-party audiences
• Sharing data with external platforms unrelated to the Page owner’s use of chatbot_practika

3. Data Storage & Retention

• Data is stored securely in encrypted databases hosted on our controlled servers.
• Only the Page Admin and authorized users in the application can access their Page data.
• We never store user passwords or Facebook access tokens in plaintext.
• All access tokens are encrypted.

Retention policy:

• Page data is kept only as long as the Page remains connected to chatbot_practika.
• When a Page Admin disconnects their Facebook account or deletes their chatbot_practika account, all connected Page data is permanently deleted within 30 days.

4. Data Deletion Policy

Users can request deletion through:

• The in-app “Delete Account” option (where available).
• Disconnecting their Facebook account from chatbot_practika.
• Sending an email request to: support@practika.jo

Once requested, all of the following are fully erased within 30 days:

• Facebook Page data
• Messenger conversations
• Page analytics and insights stored by the app
• Automation settings and subscriber lists

5. Data Security

• All communication uses HTTPS (TLS) encryption.
• Access tokens are encrypted in storage.
• Databases are access-controlled and firewalled.
• Only authorized support staff can access data, and only with the Page owner’s consent for troubleshooting.
• We follow standard security practices to prevent unauthorized access, disclosure, alteration, or destruction of data.

6. Permissions and Justification

Below is every permission requested, including the exact use case and the steps to reproduce the functionality inside chatbot_practika.

A. pages_manage_engagement

Why we need it: To allow Page Admins to write and reply to comments on posts directly from chatbot_practika.

Steps to reproduce:

• Log into chatbot_practika using username and password.
• Navigate to “Connect Accounts”.
• Click “Login with Facebook” and import the Page list.
• Click “Enable Bot Connection”.
• Open “Comment Manager → All Post List”.
• Select a Page from the left panel.
• Click the Gear icon next to any post.
• Click “Leave a Comment Now”.
• Type a comment and click Submit.
• A comment is posted on the Page using this permission.

B. pages_read_user_content

Why we need it: To read public comments made by users on Page posts and display them to the Page Admin.

Steps to reproduce:

• Log in and go to “Connect Accounts”.
• Click “Login with Facebook” and select a Page.
• Click “Enable Bot Connection”.
• Go to “Comment Manager → All Post List”.
• Select a Page from the left panel.
• Click the Gear icon → “Latest Comments”.
• User comments from the Page posts are displayed.

C. pages_manage_posts

Why we need it: To allow Page Admins to publish or schedule posts from chatbot_practika.

Steps to reproduce:

• Login → “Connect Accounts” → “Login with Facebook”.
• Click “Enable Bot Connection”.
• Navigate to “Social Posting → Multimedia Post”.
• Click “Create New Post”.
• Create text/image/video/link post.
• Click Publish or Schedule.
• The post is published or scheduled on the Page.

D. pages_manage_metadata

Why we need it: To subscribe the Page to Messenger Webhooks and Feed Events for bot automation and event handling.

Steps to reproduce:

• Login → “Connect Accounts”.
• Click “Login with Facebook”.
• Click “Enable Bot Connection”.
• The app subscribes the Page to relevant webhook events (Messenger and Feed).

E. pages_read_engagement

Why we need it: To retrieve Page posts and engagement metrics to help Page Admins analyze performance.

Steps to reproduce:

• Login → “Connect Accounts” → “Login with Facebook”.
• Click “Enable Bot Connection”.
• Go to “Comment Manager → All Post List”.
• Select a Page and see the list of posts and engagement indicators.

F. pages_show_list

Why we need it: To load and display the list of Pages a person manages, so they can choose which Page to connect.

Steps to reproduce:

• Login → “Connect Accounts”.
• Click “Login with Facebook”.
• The app retrieves and displays the list of Pages that the user manages.

G. business_management

Why we need it: To import Facebook Business Pages and connect them to chatbot_practika for management.

Steps to reproduce:

• Go to the website and log in.
• Navigate to “Connect Accounts”.
• Click “Login with Facebook”.
• The app imports Business Pages and shows them to the user.

H. read_insights

Why we need it: To display Messenger Insights such as daily conversations, messaging connections, blocked conversations, and reported conversations.

Steps to reproduce:

• Login → “Connect Accounts”.
• Click “Login with Facebook” and then “Enable Bot Connection”.
• Go to the Page list and click the “Analytics” button for a Page.
• The Messenger analytics and insights are displayed.

I. pages_messaging

Why we need it: To send automated messages and BOT replies to users who message the Page.

Steps to reproduce:

• Login → “Connect Accounts” → “Login with Facebook”.
• Click “Enable Bot Connection”.
• Open “Bot Manager” and click “Create new flow”.
• Configure an automation flow.
• Send a message (e.g., "Hi") to the Page from a test user.
• The Page BOT replies automatically using this permission.

J. human_agent

Why we need it: To allow human agents to respond to user messages within the 7-day human_agent window.

Steps to reproduce:

• Login → “Connect Accounts” → “Login with Facebook”.
• Click “Enable Bot Connection”.
• Open the “Live Chat” menu.
• From Messenger, a user sends a message to the Page.
• The Page Admin replies from the Live Chat interface using human_agent.

K. Business Asset User Profile Access

Why we need it: To display user first name, last name, and profile picture for personalized bot and human replies.

Steps to reproduce:

• Login → “Connect Accounts” → “Login with Facebook”.
• Click “Enable Bot Connection”.
• Navigate to “Subscriber Manager”.
• View the list of subscribers: first name, last name, and profile picture are displayed.

L. pages_user_genders

Why we need it: To personalize recommendations and content based on user gender (for example, showing more relevant product categories or using correct pronouns).

M. pages_user_locale

Why we need it: To detect the user’s locale and send messages in a relevant language or dialect whenever the Page owner configures multilingual messages.

N. pages_user_timezone

Why we need it: To schedule and send messages at appropriate times in the user’s local time zone, avoiding late-night or intrusive notifications.

7. Human-Agent and BOT Test Script (for Meta Review)

The following simple flow can be used by the Meta Review team to test the Messenger BOT:

• If a user sends “Hi”, the BOT replies: “Hi, how can we help you?”
• If a user sends “Info”, the BOT replies: “We are a software firm. We develop web applications.”
• If a user sends “Support”, the BOT replies: “Please put your question here, one of our team members will help you.”

Additionally, from the “Live Chat” interface, a human agent can reply manually using the human_agent tag within the allowed 7-day window.

8. Contact Information

Company: Akadimia Al-Reyada Al-Fikria Lil-Maharat Al-Ilmia

Business Name Used on Meta: Art inpa Manager

Address: Wasfi Al-Tal, Tla’ Al-Ali, Amman, Jordan (11182)

Phone: +962785800582

Email: support@practika.jo

Website: https://practika.jo

App URL: https://chat.practika.jo

9. Legal and Compliance

This document describes how chatbot_practika uses Meta (Facebook) Platform data in compliance with:

• Meta Platform Terms
• Meta Developer Policies
• Facebook and Instagram Platform Policies
• Privacy, Data Protection and Data Handling Standards

For additional information, please refer to:

• Terms of Use
• Privacy Policy