Deprecated: GuzzleHttp\Promise\queue(): Implicitly marking parameter $assign as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/guzzlehttp/promises/src/functions.php on line 24

Deprecated: GuzzleHttp\Promise\each(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/guzzlehttp/promises/src/functions.php on line 260

Deprecated: GuzzleHttp\Promise\each(): Implicitly marking parameter $onRejected as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/guzzlehttp/promises/src/functions.php on line 260

Deprecated: GuzzleHttp\Promise\each_limit(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/guzzlehttp/promises/src/functions.php on line 285

Deprecated: GuzzleHttp\Promise\each_limit(): Implicitly marking parameter $onRejected as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/guzzlehttp/promises/src/functions.php on line 285

Deprecated: GuzzleHttp\Promise\each_limit_all(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/guzzlehttp/promises/src/functions.php on line 307

Deprecated: Google\Client::fetchAccessTokenWithAssertion(): Implicitly marking parameter $authHttp as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/Client.php on line 282

Deprecated: Google\Client::authorize(): Implicitly marking parameter $http as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/Client.php on line 414

Deprecated: Google\AccessToken\Revoke::__construct(): Implicitly marking parameter $http as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/AccessToken/Revoke.php on line 42

Deprecated: Google\AccessToken\Verify::__construct(): Implicitly marking parameter $http as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/AccessToken/Verify.php on line 67

Deprecated: Google\AccessToken\Verify::__construct(): Implicitly marking parameter $cache as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/AccessToken/Verify.php on line 67

Deprecated: Google\AuthHandler\Guzzle6AuthHandler::__construct(): Implicitly marking parameter $cache as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/AuthHandler/Guzzle6AuthHandler.php on line 23

Deprecated: Google\AuthHandler\Guzzle6AuthHandler::attachCredentials(): Implicitly marking parameter $tokenCallback as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/AuthHandler/Guzzle6AuthHandler.php on line 29

Deprecated: Google\AuthHandler\Guzzle6AuthHandler::attachCredentialsCache(): Implicitly marking parameter $tokenCallback as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/AuthHandler/Guzzle6AuthHandler.php on line 46

Deprecated: Google\AuthHandler\Guzzle5AuthHandler::__construct(): Implicitly marking parameter $cache as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/AuthHandler/Guzzle5AuthHandler.php on line 23

Deprecated: Google\AuthHandler\Guzzle5AuthHandler::attachCredentials(): Implicitly marking parameter $tokenCallback as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/AuthHandler/Guzzle5AuthHandler.php on line 29

Deprecated: Google\AuthHandler\Guzzle5AuthHandler::attachCredentialsCache(): Implicitly marking parameter $tokenCallback as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/AuthHandler/Guzzle5AuthHandler.php on line 46

Deprecated: Google\Http\REST::decodeHttpResponse(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/Http/REST.php on line 121

Deprecated: Google\Http\REST::decodeBody(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/Http/REST.php on line 150

Deprecated: Google\Http\REST::determineExpectedClass(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/Http/REST.php on line 160

Deprecated: Google\Http\REST::isAltMedia(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/Http/REST.php on line 187

Deprecated: Google\Service\Exception::__construct(): Implicitly marking parameter $previous as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/Service/Exception.php on line 39

Deprecated: Google\Task\Composer::cleanup(): Implicitly marking parameter $filesystem as nullable is deprecated, the explicit nullable type must be used instead in /home/farha197/smm.farhan.iampro.top/vendor/google/apiclient/src/Task/Composer.php on line 31

Warning: session_start(): Session cannot be started after headers have already been sent in /home/farha197/smm.farhan.iampro.top/app/init.php on line 3
Terms

Terms and Conditions

Before using Smm Panel BD's services, it's crucial to carefully read and comprehend the terms outlined herein. Your utilization of Smm Panel BD.com implies agreement to these terms.

✅ Acceptance of Terms

When accessing and using Smm Panel BD, you are bound by the provided terms. Discontinuation of service use is advised if any part of these terms is disagreeable.

✅ Service Description

Smm Panel BD offers diverse social media marketing panels, varying in scope, delivery, and price.

✅ Registration and Security

Users must furnish accurate registration details and safeguard login credentials. Unauthorized account usage should be promptly reported to Smm Panel BD.

✅ Payment and Refunds

Advance payment for Smm Panel BD services is mandatory. Refunds, subject to deductions for rendered services, are processed case by case.

✅ Termination

Smm Panel BD reserves the right to suspend or terminate accounts for misuse, term breaches, or malicious activities.

✅ User Conduct

Users agree not to deploy Smm Panel BD services for illegal or unauthorized purposes, risking service termination.

✅ Limitation of Liability

While striving for quality service, Smm Panel BD doesn't guarantee uninterrupted service or specific outcomes. It disclaims liability for direct or indirect losses or damages.

✅ Intellectual Property

All content on Smm Panel BD, including text, graphics, logos, and service names, is exclusively owned. Unauthorized use or reproduction is prohibited.

✅ Changes to Terms

Periodic updates to terms will be communicated to users. The latest version is always available on this page.

✅ Governing Law

Terms are subject to Bangladeshi laws, and disagreements will be settled in Bangladesh's jurisdiction.

✅ Feedback and Reporting

Users are encouraged to report issues or provide feedback through the support team.

✅ Contact Information

For term-related inquiries, contact us immediately.

✅ Liabilities

Smm Panel BD isn't liable for social media platform actions, such as account suspension or content deletion.