Sign in Sign up
Privacy Policy

Privacy Policy

This Privacy Policy explains how user information, order details, payment records, support tickets, cookies, and no-password safety are handled on fbpanel.org. When users place orders through a Facebook service dashboard, privacy should be clear, practical, and based on public order details rather than private login access.

Privacy Ledger

What This Policy Covers

This policy explains what information may be collected, why it is used, how support records are handled, and what users should never share. The goal is to keep order processing and support review clear without asking for private account access.

01
Account information Email, username, dashboard activity, login records, and account settings may be used for account operation.
02
Order details Public links, page URLs, post links, profile links, usernames, order IDs, and selected services may be stored.
03
Payment records Balance activity, payment references, billing review notes, and transaction-related details may be used for review.
04
Support tickets Ticket messages, screenshots, replies, and issue summaries may be kept to review customer requests.
Privacy Control Board

How Your Information Is Used

Information is used to operate the website, process orders, review payments, respond to tickets, prevent abuse, and improve the dashboard experience.

Order Processing

Public order details help identify the target.

Submitted links, usernames, page URLs, post URLs, profile URLs, service names, and quantities may be used to process and track orders without requiring private account access.

Information We May Collect

Types of Information Used by the Website

The website may collect practical information needed for account access, order handling, billing review, support, and technical safety. Data collection is focused on service operation rather than unnecessary private access.

A
Account details Email address, username, account settings, dashboard usage, and login-related records.
B
Order records Selected services, quantities, submitted links, order IDs, status, and delivery history.
C
Payment data Balance records, payment method references, transaction IDs, and billing review information.
D
Ticket messages Support requests, screenshots, user explanations, replies, and review notes.
E
Technical logs IP address, browser type, device data, cookies, session logs, and security signals.
F
Usage patterns General dashboard activity may help improve service clarity, navigation, and support flow.
No Password Required

What You Should Never Share

Standard orders should not require private login access. Users should never send sensitive access details through order forms, notes, or support tickets.

!
Account password Do not send account passwords, login sessions, or private profile access.
!
Two-factor codes Do not share login approval codes, OTPs, SMS codes, or two-factor authentication details.
!
Recovery information Do not send backup codes, reset links, recovery keys, or private email access.
!
Payment login details Payment review never requires card PINs, bank passwords, or private financial account access.
Simple rule: If the information gives someone private access, do not send it. Read No Password Required before sharing any sensitive detail.
Why Information Is Used

How Data Supports Orders and Help

Collected information helps the website process orders, track status, review payments, prevent abuse, and provide support through the ticket system.

✓
Order handling Public links and selected service details help identify where delivery should be processed.
✓
Support review Tickets help support compare order ID, submitted link, status, and user explanation.
✓
Payment checks Payment and balance records help review missing balance, duplicate payment, and billing issues.
✓
Security protection Technical logs may help reduce spam, fraud, duplicate abuse, and suspicious account activity.
Cookies, Payments, and Third Parties

Technical and Payment-Related Privacy

The website may use cookies, session tools, security systems, hosting providers, payment processors, and analytics or performance tools to keep the dashboard functional, safer, and easier to use.

01
Cookies and sessions Cookies may help keep users logged in, remember preferences, and protect account sessions.
02
Payment providers Payment processors may handle transaction data according to their own policies and payment rules.
03
Security systems Security tools may detect suspicious activity, abuse patterns, duplicate actions, or payment risk.
Related operating rules may also appear in Terms of Service, Service Policy, and Support Standards.
Data Retention and User Questions

How Long Information May Be Kept

Some information may be kept as long as needed for order history, support records, payment review, fraud prevention, security logs, legal obligations, and business operations. Retention time can vary by data type and account activity.

A
Order history Order records may be kept so users and support can review past service activity.
B
Support history Ticket records may be kept to understand previous replies, decisions, and unresolved issues.
C
Security records Technical logs may be retained to reduce abuse, misuse, fraud, and account risk.
Users can contact support through tickets for privacy-related questions. Support requests are handled through the ticket system so account records and messages stay organized.
Responsible Platform Use

Privacy and Platform Awareness

Users are responsible for submitting correct public links, avoiding private access sharing, and understanding that platform behavior can affect service results. The website cannot guarantee account outcomes, long-term retention, reach, ranking, or business results.

For responsible use guidance, read Platform Awareness and Service Limitations.

Have a privacy or account question?

Open a support ticket from your account and explain the question clearly. Do not send passwords, two-factor codes, recovery keys, or private account access details.

Contact Support