Legal
Last updated: March 2026
This Cookie Policy explains which cookies and similar local storage technologies BIDGO uses, why they are used, how long they remain active, and which providers may place or read them during marketplace, payment, security, or support workflows.
BIDGO uses strictly necessary cookies and local storage identifiers for sign-in state, session continuity, fraud prevention, account security, checkout protection, language persistence, and core platform operation. These identifiers may include bidgo-access-token (up to 15 minutes), bidgo-refresh-token (up to 30 days), bidgo-authenticated (up to 30 days), bidgo-auth-session local storage, bidgo-language local storage, and bidgo-cookie-consent local storage. These technologies are required because the marketplace cannot securely operate, protect accounts, or preserve transaction state without them.
When you allow preference technologies, BIDGO may store optional settings that improve experience without being strictly required for core security or order completion. This can include remembered interface preferences, consent choices, or accessibility and display refinements. Preference technologies are disabled by default until you opt in and may remain active for up to 12 months unless you clear them earlier.
Analytics technologies are disabled by default unless you explicitly enable them. If BIDGO adds analytics providers in the future, they must only load after analytics consent is granted. Their purpose would be limited to measuring reliability, usage trends, conversion quality, performance, and product improvement in line with the privacy notice. Active analytics providers and durations must be listed here before production use.
Marketing technologies are disabled by default unless you explicitly enable them. BIDGO does not currently enable marketing or advertising cookies by default. If advertising, attribution, remarketing, social embed, or promotional audience tools are introduced later, they must remain blocked until marketing consent is granted and the relevant provider, purpose, and retention details are added to this policy.
BIDGO may connect users to third-party services only when needed for a requested workflow. For example, PayPal may place its own cookies or device identifiers when a user starts a PayPal checkout or payout onboarding flow. Those provider-controlled technologies are governed by the third party and may be necessary to complete the payment or seller onboarding service requested by the user. BIDGO minimizes third-party loading outside those flows and does not load optional analytics or marketing providers before consent.
You can accept all categories, keep only essential technologies, or reopen cookie preferences from the BIDGO footer. You may also clear browser cookies or local storage directly in your browser settings, although doing so can sign you out, interrupt transaction continuity, or reset saved preferences. Essential security and session technologies will still be used where necessary to provide the service you request.
BIDGO may update this Cookie Policy when providers, purposes, durations, or legal requirements change. Material changes should be reflected in the consent flow and this page. For privacy or cookie-related questions, contact compliance@bidgo.me. For formal legal notices, contact legal@bidgo.me.