Cookie Policy
Last updated: July 29, 2026
This Cookie Policy explains how the mobile proxy marketplace (the “Platform”, “we”, “us”) uses cookies and similar technologies on our websites, web apps, and emails. It should be read together with our Privacy Policy and Terms of Service.
We do not sell your personal data and we do not use third‑party cookies for cross‑context behavioral advertising. We use cookies and similar technologies to operate the Platform, secure accounts and payments, perform analytics, and run our own service marketing (e.g., measuring campaigns for our product), as described below.
1. What are cookies and similar technologies?
- Cookies are small text files placed on your device when you visit a site. They can be session (deleted when you close your browser) or persistent (stored until they expire or you delete them).
- Similar technologies include local storage, SDKs, pixels/tags, web beacons, fingerprinting signals, and server‑side identifiers that achieve purposes comparable to cookies.
2. Who sets cookies?
- First‑party cookies are set by us on our domains.
- Third‑party cookies are set by our service providers (e.g., payment processors, analytics, security). These providers process data on our instructions and for our purposes; see the Privacy Policy for categories of recipients.
3. How we use cookies (purposes)
We categorize cookies by purpose. Some cookies are strictly necessary and do not require consent; others are non‑essential and require your consent where applicable law requires it (e.g., the EEA/UK).
- Strictly necessary — enable core features such as page navigation, secure login, account session, load balancing, fraud prevention, and checkout/payment flows. (Always on; cannot be disabled via the CMP.)
- Preferences — remember choices like language, region, UI settings.
- Analytics/Performance — measure usage (page views, events), improve reliability and speed, and understand product performance. We aggregate or pseudonymize data where feasible.
- Security/Anti‑abuse — detect anomalous activity, rate‑limit bots, and protect your account (e.g., challenge/response).
- Marketing (our service only) — measure the effectiveness of our own campaigns and communications about our product (e.g., conversion tracking for our signup flow). We do not permit these tools to sell your data or to build cross‑site advertising profiles.
4. Your choices: consent and control (CMP)
Where required, we display a consent banner/Consent Management Platform (CMP) that lets you accept all, reject non‑essential, or manage preferences by category. You may change your choices at any time via Cookie Settings (link in the footer or your account settings). We record your consent status (timestamp, country/region, preferences) for compliance and store it for up to 13 months. If you clear cookies, you may need to set your preferences again.
We also honor Global Privacy Control (GPC) signals where applicable. If we detect a valid GPC, we will treat it as an opt‑out of non‑essential cookies.
5. Managing cookies in your browser
You can block or delete cookies in your browser settings. Instructions are available from your browser provider (e.g., Chrome, Firefox, Safari, Edge). Blocking some cookies may impact essential features such as login, checkout, or security checks.
6. Cookies and Similar Technologies We Use
We use cookies and similar technologies only from the following providers:
-
OnlineProxy — to operate, secure, and improve the Platform, remember user preferences, and measure the effectiveness of our own marketing activities;
-
Google Analytics — to analyse website traffic, user interactions, conversions, and the performance of our marketing activities;
-
Google Ads — to measure advertising conversions and the effectiveness of campaigns promoting OnlineProxy;
-
Yandex Metrica — to analyse website traffic, user behaviour, campaign attribution, and conversions;
-
Cloudflare — to protect the Platform, prevent malicious traffic, manage requests, and ensure reliable service operation.
- Chatwoot — cookies are used only to provide and maintain customer-support functionality. They are not used by OnlineProxy for advertising or for selling personal data.
Strictly necessary cookies are set without consent where permitted by law. Analytics and marketing cookies are activated only after the user provides consent through our cookie banner, where such consent is legally required.
6.1 OnlineProxy Cookies
OnlineProxy uses the following first-party cookies to operate, secure, and analyse the Platform:
| Cookie name | Category | Purpose | Expiry |
|---|---|---|---|
onlineproxy_session |
Strictly necessary | Maintains the user’s session, enables account functionality, and preserves session-related information while the user interacts with the Platform | Session or as configured by the Platform |
XSRF-TOKEN |
Strictly necessary | Protects forms, requests, and account actions against cross-site request forgery and similar security threats | Session or as configured by the Platform |
gtm_session_start |
Analytics / Marketing | Records the beginning of a website session for internal analytics, event processing, and measurement of OnlineProxy marketing activities | Session |
gtm_page_view |
Analytics / Marketing | Records whether a page-view event has been processed during the current visit and helps prevent duplicate event tracking | Session |
The strictly necessary cookies onlineproxy_session and XSRF-TOKEN are required for the security and proper operation of the Platform and cannot be disabled through Cookie Settings.
The cookies gtm_session_start and gtm_page_view are used for analytics and marketing measurement relating exclusively to OnlineProxy. Where required by applicable law, these cookies are activated only after the user has provided consent.
OnlineProxy does not use these cookies to sell personal data or to create advertising profiles for unrelated third parties.
6.2 Google Analytics Cookies
Google Analytics cookies help us distinguish visitors, identify sessions, understand how users interact with the Platform, and assess website and campaign performance.
| Cookie name | Provider | Category | Purpose | Default expiry |
|---|---|---|---|---|
_ga |
Google Analytics | Analytics | Distinguishes individual users and browsers | 2 years |
_ga_<measurement-id> |
Google Analytics | Analytics | Maintains and persists the state of an analytics session | 2 years |
The exact suffix in _ga_<measurement-id> corresponds to the Google Analytics property used by OnlineProxy.
6.3 Google Ads Cookies
Google Ads cookies are used to record advertising interactions, attribute conversions, and measure the effectiveness of campaigns promoting OnlineProxy.
| Cookie name | Provider | Category | Purpose | Typical expiry |
|---|---|---|---|---|
_gcl_au |
Google Ads | Marketing | Supports conversion measurement and stores information about advertising interactions | Up to 90 days |
_gcl_aw |
Google Ads | Marketing | Stores information about a Google Ads click for conversion attribution | Up to 90 days |
_gcl_dc |
Google Ads | Marketing | Supports conversion attribution for Google advertising and campaign products | Up to 90 days |
IDE |
Google / DoubleClick | Marketing | Measures advertising performance and conversions; may also support ad delivery depending on configuration | Up to 13 months in the EEA/UK |
test_cookie |
Google / DoubleClick | Marketing | Checks whether the user’s browser supports cookies | Approximately 15 minutes |
Some Google Ads cookies are set only if the relevant conversion, remarketing, or DoubleClick features are enabled. Cookies that are not used in the current OnlineProxy implementation must be removed from this table.
6.4 Yandex Metrica Cookies
Yandex Metrica uses cookies and browser storage to provide statistics about traffic sources, visitors, sessions, user interactions, and conversions.
| Cookie name | Provider | Category | Purpose | Typical expiry |
|---|---|---|---|---|
_ym_metrika_enabled |
Yandex Metrica | Analytics | Checks whether Yandex Metrica cookies are operating correctly | 60 minutes |
_ym_isad |
Yandex Metrica | Analytics | Detects whether the visitor uses an advertising blocker | 20 hours |
_ym_uid |
Yandex Metrica | Analytics | Assigns an anonymous identifier to distinguish visitors | 1 year |
_ym_fa |
Yandex Metrica | Analytics | Supports visitor identification together with _ym_uid |
Provider-defined |
_ym_d |
Yandex Metrica | Analytics | Records the date of the visitor’s first session | Provider-defined |
_ym_ucs |
Yandex Metrica | Analytics | Records the source used to create or reset _ym_uid, where server-side cookie resetting is enabled |
Provider-defined |
_ym_visorc_* |
Yandex Metrica | Analytics | Enables Session Replay functionality, where this feature is activated | 30 minutes |
_ym_hostIndex |
Yandex Metrica | Technical | Helps limit and manage requests sent by the Metrica tag | 1 day |
gdpr |
Yandex Metrica | Technical | Identifies users who may fall within GDPR jurisdiction | Up to 2 years |
is_gdpr |
Yandex Metrica | Technical | Identifies users who may fall within GDPR jurisdiction | Up to 2 years |
is_gdpr_b |
Yandex Metrica | Technical | Supports identification of users who may fall within GDPR jurisdiction | Up to 2 years |
yabs-sid |
Yandex Metrica | Technical | Stores a session identifier | Browser session |
i |
Yandex Metrica | Analytics | Helps distinguish website users | 1 year |
yandexuid |
Yandex Metrica | Analytics | Assigns an identifier used to distinguish users | Usually 1 year |
yuidss |
Yandex Metrica | Analytics | Supports visitor identification | Provider-defined |
ymex |
Yandex Metrica | Analytics | Stores auxiliary information, including identifier creation dates and alternative values | 1 year |
usst |
Yandex Metrica | Analytics | Supports synchronisation of user identifiers between Yandex domains | Provider-defined |
The following cookies may also be created only when debugging or optional Yandex Metrica functionality is enabled: _ym_debug, _ym_sup_debug, _ym_debugger_state, and _ym_turbo_uid.
Yandex Metrica may additionally use localStorage or sessionStorage identifiers, including _ym<tag-id>_lastHit, _ym<tag-id>_lsid, _ym<tag-id>_reqNum, _ym_retryReqs, and _ym_uid. These technologies perform functions similar to cookies and are governed by this Policy.
6.5 Cloudflare Cookies
Cloudflare cookies are strictly necessary for website security, traffic management, fraud and bot prevention, availability, and reliable delivery of the Platform. The particular cookies created depend on which Cloudflare functions are triggered or enabled.
| Cookie name | Provider | Category | Purpose | Typical expiry |
|---|---|---|---|---|
__cf_bm |
Cloudflare | Strictly necessary | Helps identify and mitigate automated or malicious traffic | 30 minutes after inactivity |
cf_clearance |
Cloudflare | Strictly necessary | Stores evidence that a visitor has successfully completed a security challenge | Based on the configured challenge duration |
_cfuvid |
Cloudflare | Strictly necessary | Distinguishes visitors sharing the same IP address for rate-limiting purposes | Provider/configuration-defined |
__cflb |
Cloudflare | Strictly necessary | Maintains session affinity and routes requests to the appropriate origin server, where load balancing is enabled | Several seconds to 24 hours |
__cfseq |
Cloudflare | Strictly necessary | Helps assess the sequence and timing of requests for bot and security rules | Provider/configuration-defined |
__cfruid |
Cloudflare | Strictly necessary | Supports legacy Cloudflare rate-limiting functionality, where used | Provider/configuration-defined |
cf_ob_info |
Cloudflare | Strictly necessary | Stores information about an unavailable origin server for the Always Online feature | Approximately 30 seconds |
cf_use_ob |
Cloudflare | Strictly necessary | Instructs Cloudflare to retrieve content from the Always Online cache | Approximately 30 seconds |
__cfwaitingroom |
Cloudflare | Strictly necessary | Manages access to a Cloudflare Waiting Room, where enabled | Provider/configuration-defined |
cf_chl_rc_i, cf_chl_rc_ni, cf_chl_rc_m |
Cloudflare | Strictly necessary | Help Cloudflare identify technical issues affecting security challenges | Provider/configuration-defined |
Only Cloudflare cookies associated with functionality enabled or triggered on OnlineProxy are placed on a visitor’s device.
6.6 Chatwoot Cookies
We use Chatwoot to provide customer support through the live chat available on the Platform.
| Cookie name | Provider | Category | Purpose | Expiry |
|---|---|---|---|---|
_chatwoot_session |
Chatwoot | Strictly necessary | Maintains the Chatwoot session required for the operation of the customer-support system | Session or as configured by Chatwoot |
cw_conversation |
Chatwoot | Functional / Strictly necessary | Preserves the customer-support conversation when a user navigates between pages or returns to the Platform | As configured by Chatwoot |
cw_user_{identifier} |
Chatwoot | Functional | Stores limited contact information when a user is identified through the Chatwoot SDK | As configured by Chatwoot |
Chatwoot cookies are used only to provide and maintain customer-support functionality. They are not used by OnlineProxy for advertising or for selling personal data.
The cookie cw_user_{identifier} is set only where OnlineProxy identifies the user through the Chatwoot SDK. If this functionality is not enabled, this cookie is not used.
6.7 Maintaining the Cookie List
The cookies and similar technologies actually used may change when we update the Platform or the configuration of our service providers. We periodically review the Platform and update this Policy and the Cookie Settings interface to reflect the cookies that are currently in use.
The live Cookie Settings interface should be treated as the most current technical list. Any cookie that is no longer used must be removed from the published list, and any newly introduced non-essential cookie must not be activated for users subject to consent requirements until the relevant consent has been obtained.
7. Retention and expiry
- Session cookies expire when you close your browser.
- Persistent cookies have a fixed expiry set by us or the provider (see table/Settings).
- Consent records are retained up to 13 months. Analytics/marketing retention is described in the Privacy Policy.
8. Email pixels and similar technologies
Our emails may contain a tiny image (pixel) or trackable link to measure opens/clicks. You can disable image loading in your email client or unsubscribe from marketing emails at any time. Transactional emails are not subject to marketing opt‑out.
9. International transfers
If cookie‑related data is transferred internationally (e.g., to the U.S.), we rely on appropriate safeguards such as EU Standard Contractual Clauses (SCCs) and the UK IDTA/Addendum, plus additional measures as needed. See the Privacy Policy for details.
10. Updates to this Policy
We may update this Cookie Policy from time to time. Material changes will be signposted via the banner, Cookie Settings, or the Platform. Please check the “Last updated” date.
11. Contact
- Cookie/consent questions: [email protected]
- General support: [email protected]