Last updated: 22 July 2026
This Cookie Policy explains how FiatBear uses cookies and similar browser technologies on fiatbear.com, app.fiatbear.com, and the services available through them. It should be read together with our Privacy Policy.
A cookie is a small text file stored by your browser. We also use browser storage for limited functions such as remembering whether a consented analytics milestone has already been reported. Some technologies last only for a session; others remain for the period described below unless you delete them earlier.
1. Your choices
Essential technologies are used where they are required for security, authentication, consent storage, and services you explicitly request. Optional analytics, advertising, and support-chat technologies are denied by default until you make a choice.
When the consent banner appears, you can Accept all, Reject optional, or choose categories individually. You can change or withdraw your choices later using Change cookie choices on this page. Withdrawing a category removes the first-party cookies we can remove and prevents that category from loading again. Third-party data already received before withdrawal remains subject to the relevant provider’s retention policy.
2. Essential cookies
These cookies support security, sign-in, consent storage, or a service you request. They are not used for advertising and cannot be disabled through FiatBear’s optional-cookie controls.
| Name | Purpose | Owner | Duration |
|---|---|---|---|
| fb_consent_v1 | Stores your analytics, advertising, and support-chat choices across FiatBear subdomains. | FiatBear | 1 year |
| fiatbear.uid | Keeps you signed in to the FiatBear application. | FiatBear | 2 days, with sliding renewal while active |
| fiatbear.af | Protects forms and authenticated requests against cross-site request forgery. | FiatBear | Session |
| fiatbear.corr, fiatbear.ext | Temporarily preserves state while completing an external sign-in flow. | FiatBear | Short-lived / session |
3. Analytics and first-party attribution
If you allow analytics, FiatBear uses Google Analytics 4 to understand visits, registrations, and confirmed product-activation milestones. For signed-in customers, FiatBear may provide Google Analytics with a pseudonymous internal customer identifier so activity can be understood across sessions. We do not send email addresses, wallet addresses, or payment details as analytics event parameters.
FiatBear also stores limited first-party attribution when either analytics or advertising is allowed. This helps us understand which campaign, advertisement, or external page introduced a visitor.
| Name | Purpose | Owner | Duration |
|---|---|---|---|
| _ga | Distinguishes browsers for Google Analytics 4 reporting. | Up to 2 years | |
| _ga_<measurement-id> | Maintains session state for the configured Google Analytics 4 property. | Up to 2 years | |
| fb_utm | Stores campaign parameters and advertising click identifiers supplied in the landing-page URL. | FiatBear | 30 days |
| fiatbear.ref | Stores the external referring page URL reported by the browser. | FiatBear | 30 days |
| Analytics milestone keys | Uses local browser storage to avoid reporting the same one-time activation milestone repeatedly. | FiatBear | Until browser data is cleared |
Google Consent Mode is configured so analytics and advertising storage remain denied until you choose otherwise. When storage is denied, Google tags may send limited cookieless consent-status or measurement signals, but they are not permitted to read or write analytics or advertising cookies.
4. Advertising measurement
If you allow advertising, FiatBear uses Google Ads and the X/Twitter website tag to measure campaign performance and attribute conversions. These tools are used for measurement and campaign optimisation; FiatBear does not sell personal data.
| Name | Purpose | Owner | Duration |
|---|---|---|---|
| _gcl_* | Stores Google Ads click and conversion attribution information. | Up to 90 days | |
| fb_utm, fiatbear.ref | Provides first-party campaign and referrer attribution as described above. | FiatBear | 30 days |
| X/Twitter technologies | Measures visits and conversions from X campaigns. The exact cookies or browser storage used can vary according to X’s implementation and your existing X session. | X Corp. | Set by X according to its policy |
5. Support chat
If you allow support chat, FiatBear loads ClickConnector so you can contact support from the website or application. ClickConnector may use cookies or browser storage whose names begin with cc_ or clickconnector to maintain the chat session and widget state. The widget is not loaded when support consent is denied.
6. Payment cookies
FiatBear uses Stripe for active payment flows such as residential-proxy purchases. Stripe’s fraud-prevention technologies are loaded where needed to provide the payment service you request; they are not evidence of a copy-trading subscription.
| Name | Purpose | Owner | Duration |
|---|---|---|---|
| __stripe_mid | Helps Stripe prevent fraud and assess the risk associated with an attempted payment. | Stripe | Up to 1 year |
| __stripe_sid | Provides short-lived fraud-prevention and payment-session signals. | Stripe | Approximately 30 minutes |
7. Third-party providers
Third-party providers process information under their own terms and privacy policies. Their technology and cookie names can change independently of FiatBear. You can learn more from:
- Google Privacy Policy
- Google Business Data Responsibility
- X Privacy Policy
- Stripe Privacy Policy
- ClickConnector
8. Browser controls
You can also delete or block cookies through your browser settings. Blocking essential cookies may prevent sign-in, security protections, payments, or other requested features from working correctly. Browser controls do not replace the FiatBear consent choices for optional technologies.
9. Changes and contact
We may update this policy when our services, providers, or legal obligations change. The date at the top shows the latest revision.
Questions about this Cookie Policy or FiatBear’s handling of personal data can be sent to [email protected].