BIG-FLYTX by MAS Privacy Disclosure

When enabled by a site administrator, BIG-FLYTX may collect first-party tracking data such as visitor IDs, URLs, referrers, UTM parameters, click IDs, event names, event IDs, ecommerce product/order data, value/currency, and safe lead/customer fields from forms or orders.

Raw name, email, and phone storage is disabled by default. Administrators can enable raw PII storage or keep hashed values only where possible.

External server-side delivery is disabled by default. If enabled and configured, event payloads may be sent to the selected services such as Meta, Google/GA4, Microsoft/Bing, TikTok, LinkedIn, Pinterest, Snapchat, X/Twitter, Reddit, Quora, Telegram, a license endpoint, or a custom endpoint.

Site owners should disclose enabled destinations in their own privacy policy and obtain appropriate consent where required.

Authorization and consent: BIG-FLYTX remains paused until a site administrator explicitly authorizes the configured data collection and external services. The administrator may optionally enable strict visitor-consent mode, which waits for the bftx_consent=granted cookie or the bftx_mas_tracking_consent_granted filter. The site owner remains responsible for visitor notices, legal basis, and consent required for the enabled services.

External providers: If enabled, data may be sent to configured advertising and analytics providers. The complete provider list, transmitted-data description, terms links, and privacy links are included in the plugin readme.txt under External Services.
