This Cookie Policy explains how BidFinance uses cookies and similar browser storage technologies to support secure sign-in, session continuity, functional preferences, and core platform operation.
Cookie Policy
This Cookie Policy explains how BidFinance uses cookies and similar browser storage technologies to support secure sign-in, session continuity, functional preferences, and core platform operation.
1. Cookies And Similar Technologies
1.1.On the BidFinance website and platform we use cookies and similar browser storage technologies, including localStorage and sessionStorage. These technologies are used mainly to keep users securely signed in, maintain authenticated sessions, remember user preferences, and operate platform features correctly.
1.2.This Policy has been updated for the current BidFinance platform. It does not describe historical tools used by previous website versions, such as Tilda, embedded Google Docs, or third-party marketing tools, unless those tools are reintroduced in the current production environment.
1.3.Capitalised terms not defined in this Policy have the meanings given to them in the applicable BidFinance terms and conditions.
2. What Cookies Are
2.1.Cookies are small text files stored on a user's device when using a website or web application. Similar technologies include localStorage, sessionStorage, session identifiers, technical scripts, and other mechanisms that allow information to be stored in or accessed from the browser.
2.2.These technologies do not adversely affect the device on which they are stored and do not change device or software configuration beyond ordinary storage of information needed or useful for platform use.
3. Information Processed
3.1.The scope of information depends on the specific technology. In the current BidFinance platform, the information is primarily technical and functional data used for authentication, session protection, user preferences, and marking selected interface items as read or seen.
3.2.Depending on the feature used, information may include authentication identifiers; session creation, activity and expiry times; IP address and browser information recorded on the server; interface language and the source of that preference; theme and compact-view preferences; sound and action-confirmation settings; auction read/preparation indicators; search text, filters and sort order; VDR folder expansion and document column widths; and temporary navigation or panel-state markers. Server-side records are distinct from browser storage and are addressed in the Privacy Policy.
4. Categories Of Technologies
4.1.Necessary technologies enable core functions such as login, session continuity, protection against unauthorised access, CSRF protection, and secure navigation in protected platform areas. Without them, the platform cannot operate correctly.
4.2.Functional technologies remember user preferences such as language, theme, compact view, sound settings, selected one-click confirmations, and interface read-state markers.
4.3.The browser technologies listed in Section 5 support authentication, platform functions or interface preferences. They are not used by BidFinance to build advertising profiles or track activity across unrelated websites. The website’s LinkedIn links are ordinary external links. If optional analytics, advertising or social-media tracking technologies are introduced, this Policy and the applicable consent arrangements must be updated before activation.
5. Technologies Used On The Platform
The table describes names and key patterns used by the current website and platform. An asterisk identifies a variable suffix, such as a company, user, auction, workspace or page identifier. Entries are created only where the relevant function operates; not every entry appears for every visitor. BidFinance is the first-party provider. Production and staging use separate website origins and browser storage.
| Name or pattern | Storage | Purpose | When used | Browser lifetime |
|---|---|---|---|---|
__Host-bf_session | cookie | Secure sign-in and authenticated session continuity; HttpOnly, Secure, host-only, SameSite=None. | After successful sign-in or registration establishing a session; separate cookie for each host. | Until logout or expiry. The current inactivity timeout is 30 minutes; valid activity renews the server session and cookie renewal follows the authentication/prolong flow. This is not the retention period of server records. |
bidfinance-languagebidfinance-language-preference | localStorage | Interface language and whether the preference was chosen manually or supplied through an invitation. | Language on localized pages; the preference record after manual selection or invitation handling. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance-themebidfinance-marketing-theme | localStorage | Light/dark appearance and continuity between the public website and platform login. | Read when the page starts; written after theme selection or the relevant navigation from the marketing site to login. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance-compact-view:* | localStorage | Compact view preference for the relevant interface. | When the user selects the compact-view option. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance:*auctions-seen:* | localStorage | Auction indicators already seen, scoped to company, role or internal user. | On the relevant authenticated auction screens. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance:*transaction-attention-seen:* | localStorage | Transaction updates already seen. | On the relevant authenticated transaction/auction screens. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance:auction-communications:* | localStorage | Read state for announcements and public questions and answers. | When the relevant auction communication area is viewed. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance:auction-viewed:*bidfinance:auction-documents:*bidfinance:auction-calendar:* | localStorage | Auction preparation and document/calendar action indicators. | After the relevant view, document or calendar action. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance:seller-live-bid-sound:*bidfinance:buyer-live-bid-sound:*bidfinance:admin-commission-sound:* | localStorage | Sound preferences for live bidding or internal commission notifications. | After choosing sound settings in the relevant customer or internal screen. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance:progressive-one-click-accept:*bidfinance:english-one-click-bid:* | localStorage | Chosen confirmation behaviour for supported auction actions. | After selecting the corresponding one-click option. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance:buyer-auctions-filters:v1:*bidfinance:seller-auctions-filters:v1:* | localStorage | Auction search text, country filter and sort order. | In authenticated buyer/seller lists where the filter toolbar is available; may include its initial defaults. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance:admin:*:companies:hide-testbidfinance:admin:*:users:hide-test | localStorage | Internal user preference for hiding test companies/users in a directory. | After an internal user changes this filter; not restricted to staging. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance:docs-workspace-column-widths-v2 | localStorage | Document workspace column widths. | When the document workspace loads or its column widths change. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance:transaction-workspace-vdr-tree:v1:* | localStorage | Expanded VDR folders for the relevant workspace and viewer. | When VDR folders are expanded; the entry is removed when no folders remain expanded. | No fixed expiry. Until overwritten/reset by the feature or the browser site data is cleared. |
bidfinance:post-logout-redirect | sessionStorage | Language-specific public destination after logout. | When logout navigation is scheduled; removed when consumed. | For the tab’s page session, unless cleared earlier; browser session restoration may restore it. |
bidfinance:deployment-refresh-pending | sessionStorage | Complete a page refresh after a platform version change. | Only when a version mismatch requires a refresh; removed after handling. | For the tab’s page session, unless cleared earlier; browser session restoration may restore it. |
bidfinance:partnership-program:view-preference:v2 | sessionStorage | Remembers your explicit choice to minimise or expand the Partnership Program panel. | Saved only when you activate the minimise button or expand the collapsed launcher. Automatic minimisation after five seconds changes only the current in-memory display state. | Current browser-tab session, subject to browser session restoration or earlier clearing. |
If a browser contains the former bf_session cookie or bidfinance-ai-chat:v1:{locale} storage key, these are legacy entries. The current production/staging authentication cookie is __Host-bf_session. The current website does not mount the former support-chat widget and does not actively create that widget’s storage. Legacy browser data may remain until it expires or is cleared. A historic application-level validity period does not itself remove localStorage from an inactive or closed page.
Earlier versions could automatically save bidfinance:partnership-program:minimized-session:v1. This legacy key may remain in an existing tab session, but the updated component does not read or use it as a user preference.
6. Legal Basis And Managing Technologies
6.1.Access to or storage of information on a device is governed separately from the GDPR basis for processing personal data. Under Article 399 of the Polish Electronic Communications Law, the consent exception concerns storage/access necessary to transmit a communication or provide a service requested by the user. A legitimate interest under the GDPR does not by itself replace consent required for device storage/access. Describing an entry as functional does not automatically place it within that exception; each purpose must be assessed. Consent required for optional technologies must be obtained before their use.
6.2.Users can delete cookies and browser storage data or change browser settings at any time. Blocking or deleting necessary technologies may prevent login, session continuity, protected navigation, or remembering preferences.
7. International Transfers
7.1.The configuration described above does not include third-party advertising, social media, or analytics cookies that by themselves transfer cookie information outside the European Economic Area.
7.2.If BidFinance uses technical, hosting, infrastructure, support, or security providers and cookie or browser-storage information is transferred outside the EEA, the transfer will take place only under mechanisms required by data protection law, such as an adequacy decision, standard contractual clauses, or another permitted safeguard.