Cookie Policy
Effective date: 27.10.2025
Last updated: 27.10.2025
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 we use (examples)
The exact cookies used may change over time. The table below shows common examples. An up‑to‑date list is available in Cookie Settings and may be supplemented in an appendix or help article.
| Category | Example cookie / storage | Who sets it | Purpose | Typical expiry |
|---|---|---|---|---|
| Strictly necessary | __Host-session, sid, csrf_token | First‑party | Secure login/session, CSRF protection | Session / 7–30 days |
| Strictly necessary | __cf_bm (or equivalent), challenge token | {{Security provider, e.g., Cloudflare/Turnstile}} | Bot mitigation, rate‑limiting | 30 minutes / as defined |
| Payments (necessary) | m, __stripe* / paypal* | {{Payment processor, e.g., Stripe/PayPal}} | Payment routing, fraud checks | Session / up to 1 year |
| Preferences | locale, ui_theme | First‑party | Remember language/UX preferences | 6–12 months |
| Analytics | _ga*, _gid (if used) | {{Analytics provider, e.g., Google Analytics}} | Usage stats, performance | 24 months / per provider |
| Analytics | ajs_* / segment* (if used) | {{Product analytics}} | Product usage analytics | 12–24 months |
| Security | token_fingerprint (hashed) | First‑party | Account integrity, anomaly detection | 30–90 days |
| Marketing (our service only) | fbp / *_utm / conversion tag (if used) | {{Attribution/measurement provider}} | Measure our own campaigns (no cross‑site ads) | 90 days / per provider |
Replace provider placeholders {{…}} with your actual vendors or remove rows you don’t use.
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]
Appendix A — Cookie list template (optional for publication)
Use this section if you prefer to publish a static list. Keep it synced with your CMP export.
Strictly necessary
- Name: __Host-session — Provider: First‑party — Purpose: Secure session — Expiry: Session
- Name: csrf_token — Provider: First‑party — Purpose: CSRF protection — Expiry: 2 hours
Payments (necessary)
- Name: __stripe_mid — Provider: Stripe — Purpose: Fraud prevention — Expiry: 1 year
Analytics
- Name: _ga — Provider: Google Analytics — Purpose: Usage stats — Expiry: 24 months
Marketing (our service only)
- Name: fbp — Provider: Meta — Purpose: Conversion measurement for our product — Expiry: 90 days
Add/remove lines to match your actual setup; if you later stop using a tool, remove it here and from Cookie Settings.