Privacy notice
Inquiry forms and contact data
This notice describes inquiry forms, Telegram contact and notifications, site analytics and attribution.
Contact details support inquiry follow-up
Saved forms and support clicks are separate
Telegram messages are not read by this site
Inquiry forms and notifications
The form collects your email and requirements; name and Telegram username are optional. Submitted details, time, privacy-notice version, page path, available campaign parameters and an external referring hostname are stored in a private inbox on Bifu's server for authorized administrators to review and follow up. Only the referring hostname is kept, not its path, query or fragment. A source with no available clues remains unknown.
A notification bot may forward your name, email, Telegram username and requirements to our team's Telegram inbox. Telegram processes that information under its own privacy rules. Form contents are not sent as Google Analytics or Google Ads event parameters.
Short-lived submission tokens and one-way rate-limit identifiers help prevent duplicates and abuse. Raw IP addresses are not stored in inquiry records. Do not include passwords, verification codes, private keys or API keys.
When you submit requirements, the server uses offline DB-IP country data to decide whether extra verification is needed; it does not send your IP to DB-IP. Submissions outside the Philippines or with an uncertain location may use Cloudflare Turnstile, which processes network, device and browser signals needed for verification. Bifu sends only a one-use verification response and a random submission ID to the verification endpoint, not your name, email, Telegram username or requirements. Verification responses are not stored in inquiry records. Ordinary browsing does not trigger this verification.
Site visits and interaction data
- Analytics services may process device and browser type, approximate location, referrer, page path, time and page-interaction events when you visit this site.
- When a URL contains UTM, gclid, gbraid or wbraid attribution parameters, the site may keep them in browser session storage to distinguish organic, direct and advertising visits.
- A Telegram support click, channel click or support-ID copy records only the event, page location and destination. The site does not read Telegram messages and does not count a normal page view as an inquiry.
Telegram contact
Online support buttons open Telegram and do not send messages for you. Account information, messages or attachments you send there are handled by Telegram and the support participant under their respective privacy practices.
Do not send account passwords, verification codes, private keys or API keys through Telegram.
How data is used
- Understand which pages and payment topics are useful and improve the contact path.
- Separate organic, direct and advertising sources and measure support clicks, channel clicks and support-ID copies.
- Maintain site security and diagnose unusual traffic or analytics failures.
- Reply to requirements you submit through the form or Telegram. Saved forms, support clicks and manually confirmed qualified inquiries are recorded separately.
Analytics services and browser storage
The site may use Google Analytics, Google Ads and Baidu Analytics. These services may process device, network, visit and event information under their own privacy rules. Browser settings, blocking tools and consent controls may affect that processing.
During browsing, campaign parameters and an available external referring hostname are held in browser session storage. These source clues are also saved with an inquiry when you submit the form; they do not independently prove advertising attribution or customer qualification. Clearing local site data or blocking analytics does not delete previously submitted inquiries; contact support to query or request deletion of those records.
Retention and data requests
Analytics retention depends on the current account settings and each service's rules. You may contact the primary Telegram support account about data controlled by this site. Data held within Telegram should also be managed through Telegram's own controls or support channels.
Contact us
Contact the primary Telegram support account about data controlled by this site.