1. Scope and contact
This policy covers lifuproxy.com, the dashboard, API and LiFu Proxy support channels. Processing on the service’s behalf is organised by its Administration, the person actually operating the service. Contact admin@lifuproxy.com about your data and rights.
LiFu Proxy is a service name and does not replace mandatory information identifying the person determining processing purposes and means. That information must be disclosed as required by applicable law. This policy does not claim a registered company, a particular registration country or compliance with every legal regime simultaneously.
2. Data used
Data depends on the features you choose. The service does not request access to your mailbox content or Google Drive. Do not send support passwords, login codes or unnecessary documents.
- Account and security: email, internal ID, a password hash for password login, email verification, sessions and login-check records. Google login uses a verified email and Google account identifier.
- Transactions: balance, purchases, credits, used and remaining traffic, promo codes, amounts, dates and operation records. Full payment card credentials are not required to maintain a service balance.
- Connections: proxy credentials, configured location and rotation, usage figures, technical errors and information needed for network operation and abuse prevention.
- Referrals: referral or promo code, visitor identifier, registration source and redemption history. Technical logs may include IP, request time and browser information.
- Support: messages and email if supplied; for Telegram, ID, name, username and submitted photos, files, stickers, voice and video messages. These materials are stored to handle the request.
- Browser preferences: theme, language, referral code, visitor identifier and credentials for accessing your own web support conversation.
3. Purposes and legal bases
Data is used for registration and login, code delivery, providing and metering proxies, transactions, promo codes, referral attribution, support, fraud prevention and legal duties.
The relevant basis depends on the purpose and applicable law: entering into and performing a contract, a legal obligation, a permissible legitimate interest in security and service operation, or separate consent where required. Accepting this policy is not unconditional consent to all future processing.
Code emails and ticket updates support account operation. Marketing requires a separate legal basis and an opt-out; registration alone does not give marketing consent.
4. Cookies and localStorage
The sid cookie maintains login on the website and associated subdomains; its current lifetime is up to 7 days. Short-lived login_browser and oauth_browser cookies bind login verification and Google authentication to your browser, for up to 10 minutes. A session may end sooner upon logout, a block or security changes.
localStorage saves your theme and language. A referral code is used for up to 30 days and then no longer applied. A visitor identifier supports unique referral click counting. Web support data lets you return to your conversation. Local records can remain until browser storage is cleared even after their period of use expires.
You can remove this data using browser settings. Disabling necessary cookies may prevent login and dashboard use. Optional technologies requiring legal consent must not be used before that consent is obtained.
We use Google Analytics 4 on the website and in the dashboard for visitor statistics, sign-ups, payments, traffic purchases, and support interactions. When measurement is enabled, Google receives the event type and the page URL without query parameters. For a confirmed payment, Google also receives the amount, currency, and a random transaction identifier for deduplication. We do not send payment credentials, email addresses, passwords, or support messages.
For visitors in the EEA, United Kingdom, Switzerland, or with an unknown country, Google cookies are disabled until a choice is made in the banner. Measurement may be enabled by default in other locations. When analytics is disabled, advanced Consent Mode sends limited signals to Google without cookies, payment amounts or payment identifiers, for statistical modeling. You can change your choice or opt out using Analytics preferences at the bottom of the page.
When analytics is enabled, GA4 may set _ga and _ga_* cookies. Their lifetime is configured to up to 180 days after the latest refresh. Google Ads measures confirmed payments. When advertising is permitted, it receives the amount in USD and a random transaction identifier for deduplication and may use advertising cookies such as _gcl_au. When advertising is disabled, Google Ads receives a limited signal without cookies, the amount, or the transaction identifier. The site looks up your country from your IP address using a local DB-IP database and keeps the country code in a lifu_cc cookie for up to 24 hours. Your choices are stored in your browser.
5. Third parties and recipients
The service uses server infrastructure, email delivery and the external proxy network. The network operator receives a technical user identifier and data needed to configure access and meter traffic. Routing through proxies involves the network operator processing connections; this policy does not promise that the network operator keeps no network logs.
Google processes data under its own rules for Google login, website measurement and advertising features. Cloudflare Turnstile processes information needed for security checks in forms using it. Telegram also processes data when you contact support through Telegram. Payment services, if a payment method uses one, are disclosed before the transaction.
Authorised support staff and administrators access data for their work. Data may also be disclosed to competent authorities under a lawful requirement or to defend rights where permitted by law. The service does not sell personal data. Using a contractor does not remove the Administration’s duty to ensure lawful disclosure.
6. Retention and deletion
Account, transaction and traffic data is retained while necessary for account operation, contract performance, handling claims and mandatory retention periods. Support records and technical logs are retained only as needed for their purpose, security and disputes. Blanket indefinite retention is not specified.
Request account and data deletion at admin@lifuproxy.com. After verification, data is deleted or anonymised except where legally required or necessary for a substantiated defence of rights. Backups may retain data until replacement or the end of their retention period; they are not used for normal operation of a deleted account.
Expiry of a code or session does not mean that all check records immediately disappear from logs or backups. You can request information about relevant retention periods and recipients at the contact above.
7. Security and international transfers
HTTPS, password hashing, restricted administrative access and login checks are used. Users must also protect their email, devices and proxy credentials. No storage or transmission method provides absolute security.
The network operator, Google, Cloudflare, Telegram and infrastructure contractors may process data in different countries. International transfers require the legal basis and safeguards mandated by applicable law. This policy does not replace necessary notifications, consents, contractual safeguards or localisation requirements.
8. Your rights
To the extent provided by applicable law, you may request processing information and a copy of your data, correction, deletion, restriction or portability, object to processing and withdraw consent. Withdrawal does not invalidate earlier lawful processing or prevent processing on another lawful basis.
Email admin@lifuproxy.com from your account email with your request. Proportionate identity verification may be needed to protect data. Responses follow mandatory legal deadlines. You may contact a competent data protection authority or court regardless of whether you contacted support.
9. Policy updates
The revision date appears on this page. Material changes to purposes, data or processing bases are communicated through an available channel. New consent is requested separately when required; publishing an update does not replace it. Previous versions may be requested by email.