Bonani DOSH, Dhaka - 1230, Bangladesh
Privacy & Consent
1 / 1Consent, Personal Data and Privacy Controls
Learn when BIG-FLYTX collects data, how its consent modes work and what privacy controls administrators should review.
Paused by default
BIG-FLYTX does not collect or transmit visitor events merely because it is installed or activated. An administrator must authorize tracking, enable the plugin and configure a destination. If Strict visitor gate mode is selected, visitor consent is also required before collection or transmission.
Choose a consent approach
Site-owner managed mode: the site owner manages required visitor notice and consent through the site’s privacy process or its consent-management platform. BIG-FLYTX does not display its own consent banner.
Strict visitor gate mode: BIG-FLYTX waits for the documented bftx_consent=granted cookie or the bftx_mas_tracking_consent_granted filter before tracking. Make sure your consent platform sets the signal only after the visitor’s valid consent.
Data and storage controls
Depending on enabled features, event data can include visitor IDs, URLs, referrers, UTM values, advertising click IDs, browser/user-agent hashes, IP-address hashes, ecommerce data and safe lead/customer fields supplied by a form or commerce transaction. Raw name, email and phone storage is disabled by default; enable it only if your notice, legal basis and consent process permit it.
Review Do Not Track support, administrator data masking, event and delivery-log retention, WordPress personal-data export/erase support and the optional uninstall deletion setting. Set retention to match your operational and legal needs.
Site owner responsibility
The site owner is responsible for deciding whether tracking is lawful, maintaining an accurate privacy/cookie notice, configuring a consent platform where needed, and documenting each external provider and custom endpoint. This guide is technical information, not legal advice.
BIG-FLYTX does not collect or transmit visitor events merely because it is installed or activated. An administrator must authorize tracking, enable the plugin and configure a destination. If Strict visitor gate mode is selected, visitor consent is also required before collection or transmission.
Choose a consent approach
Site-owner managed mode: the site owner manages required visitor notice and consent through the site’s privacy process or its consent-management platform. BIG-FLYTX does not display its own consent banner.
Strict visitor gate mode: BIG-FLYTX waits for the documented bftx_consent=granted cookie or the bftx_mas_tracking_consent_granted filter before tracking. Make sure your consent platform sets the signal only after the visitor’s valid consent.
Data and storage controls
Depending on enabled features, event data can include visitor IDs, URLs, referrers, UTM values, advertising click IDs, browser/user-agent hashes, IP-address hashes, ecommerce data and safe lead/customer fields supplied by a form or commerce transaction. Raw name, email and phone storage is disabled by default; enable it only if your notice, legal basis and consent process permit it.
Review Do Not Track support, administrator data masking, event and delivery-log retention, WordPress personal-data export/erase support and the optional uninstall deletion setting. Set retention to match your operational and legal needs.
Site owner responsibility
The site owner is responsible for deciding whether tracking is lawful, maintaining an accurate privacy/cookie notice, configuring a consent platform where needed, and documenting each external provider and custom endpoint. This guide is technical information, not legal advice.
