Important notice
This Cookie Policy explains how “PRE-ORDER Europe” EOOD (“PRE-ORDER”, “we”, “us” or “our”) uses cookies and similar technologies on the PRE-ORDER website and, where relevant, on web-based parts of the PRE-ORDER Platform. It also explains how users can make choices about non-essential technologies.
The public website is intended primarily as an information and access point for the PRE-ORDER mobile application and related services. The Platform may also use local storage, session identifiers, device or app identifiers, software development kits (SDKs), pixels, tags or comparable technologies. Where a technology performs a function comparable to a cookie, the principles in this Policy apply to the extent appropriate.
The exact list of active cookies, providers, purposes and retention periods depends on the configuration actually deployed. Where a consent-management interface or cookie settings panel is available, the live list shown there is the most specific record for the current website configuration. PRE-ORDER will not intentionally place non-essential cookies before obtaining consent where applicable law requires consent.
1. Operator and scope
1.1 The website and Platform operator is “PRE-ORDER Europe” EOOD, UIC/EIK 208904127, registered at Arthur Residential Complex, Block C, Floor 3, Apartment C44, 8229 Sveti Vlas, Nessebar Municipality, Burgas District, Bulgaria.
1.2 This Policy applies to pre-ordera.com and related PRE-ORDER web pages that link to this Policy. It should be read together with the PRE-ORDER Privacy Policy, Terms of Service and any privacy or consent notice displayed in a specific feature.
1.3 The mobile application may rely on SDKs, device permissions, push-notification identifiers and local storage rather than browser cookies. Those technologies are addressed in this Policy where their function is materially similar, but app-specific processing is also described in the Privacy Policy and the relevant iOS or Android settings.
1.4 Third-party websites or services reached through external links are governed by their own cookie and privacy practices. PRE-ORDER does not control technologies placed by a third party after a user leaves the PRE-ORDER environment.
2. What cookies and similar technologies are
2.1 A cookie is a small text file or data element stored on a browser or device when a user visits a website. Cookies can be “session” technologies that expire when the browser session ends or “persistent” technologies that remain for a defined period or until deleted.
2.2 First-party cookies are set or controlled for PRE-ORDER’s own domain. Third-party cookies or comparable identifiers may be set by an external service integrated into the site, for example a payment, analytics, security, embedded-content or advertising provider.
2.3 Similar technologies may include browser local storage, session storage, pixels, tags, scripts, server-side identifiers, device identifiers, SDKs, cache entries and comparable technical mechanisms used to remember settings, measure use, maintain sessions or protect transactions.
3. General principles
- PRE-ORDER will use technologies proportionately to their purpose and will avoid collecting information that is not reasonably needed for the relevant function.
- Strictly necessary technologies may operate without an optional consent choice where permitted by law because they are required to provide a service requested by the user or to maintain security and core functionality.
- Analytics, advertising or other non-essential technologies will be activated only in accordance with the consent requirements applicable to the user.
- Where consent is relied upon, refusing or withdrawing consent must not disable the core website unless the relevant technology is genuinely necessary for the requested feature.
- Consent choices should be as easy to withdraw as they are to give and should be recorded for accountability.
4. Categories of technologies we may use
| Category | Typical purposes | Consent approach |
|---|---|---|
| Strictly necessary | Security, session continuity, load balancing, fraud prevention, consent choices, form submission, essential language or interface state, and features explicitly requested by the user. | Used without optional consent where legally permitted because necessary for the service or security. |
| Preferences and functionality | Remembering language, region, accessibility, display or other non-essential preferences. | Consent where required; otherwise used only where a valid legal basis and ePrivacy rule permits. |
| Analytics and performance | Understanding traffic, page use, errors, performance, conversion paths and aggregated interaction patterns. | Enabled only after consent where required. |
| Advertising and campaign measurement | Measuring campaigns, attribution, audience building, frequency control or personalised advertising. | Enabled only after valid consent where required. |
| Security and anti-abuse | Bot detection, account protection, rate limiting, suspicious-traffic analysis, payment security and fraud prevention. | May be necessary; any non-essential tracking component remains subject to consent rules. |
| Embedded and third-party content | Video, maps, social content, support widgets, payment interfaces or other third-party features. | Non-essential third-party content may be blocked until consent where required. |
5. Strictly necessary technologies
5.1 These technologies support functions that users reasonably expect when requesting the website or a particular feature. Examples may include session management, load balancing, security controls, remembering cookie-consent choices, maintaining form integrity, preventing duplicate submissions, protecting sign-in or transaction workflows and enabling technically required language routing.
5.2 Because these technologies are necessary for the requested service or for security, they may not appear as an optional category in the consent banner. Users may still block them through browser settings, but doing so can cause parts of the website or Platform to stop working correctly.
5.3 Strictly necessary does not mean that unlimited tracking is permitted. PRE-ORDER will limit these technologies to the purpose that makes them necessary and will not repurpose them for advertising without the required consent.
6. Preferences, language and localisation
6.1 PRE-ORDER provides an English and Ukrainian website and may remember the selected language or related display choice so that users do not need to select it on every page.
6.2 A language or preference technology may be strictly necessary where it is required to deliver a user-selected setting for the current session. Longer-term preference storage may be treated as functional or preference storage depending on the implementation and applicable law.
6.3 PRE-ORDER will not infer sensitive characteristics merely from a language choice and will not use a language preference for advertising unless a lawful, transparently disclosed basis exists.
7. Analytics and performance technologies
7.1 PRE-ORDER may use analytics to understand how visitors reach and use the website, which pages are viewed, whether technical errors occur, how quickly pages load and whether key journeys are completed. Project documentation also anticipates behavioural interaction data and aggregated analytics for service improvement and demand-related analysis.
7.2 Analytics information may include page or screen views, approximate time of access, referring source, device or browser characteristics, truncated or general network information, session events and similar interaction data. Where possible, PRE-ORDER should configure analytics to reduce unnecessary identifiers and use aggregated reporting.
7.3 Analytics used for the public website is distinct from PRE-ORDER’s demand-forecasting functions. Website analytics should not automatically be treated as AI-training data. If analytics data is later used for a materially different purpose, PRE-ORDER will assess the legal basis and transparency requirements before doing so.
8. Advertising and campaign measurement
8.1 PRE-ORDER may in the future use advertising or campaign-measurement technologies to understand whether an advertisement or social-media campaign led to a website visit, app download, registration or other relevant conversion.
8.2 Such technologies can involve identifiers shared with or received from advertising platforms. Where they are not strictly necessary, they will not be activated for EU/EEA users before valid consent where consent is required.
8.3 PRE-ORDER will not describe advertising technologies as “necessary” merely because they are commercially useful. If personalised advertising or audience matching is used, the purpose must be specifically explained in the consent interface and Privacy Policy.
9. Security, bot prevention and fraud controls
9.1 PRE-ORDER may use security technologies to protect forms, accounts, payment-related interfaces and infrastructure against automated abuse, malicious traffic, credential attacks, suspicious transactions and other cybersecurity threats.
9.2 Security data may include IP-derived network information, device or browser signals, request timing, session characteristics, failed attempts, risk indicators and security logs. Project documentation expressly anticipates technical and security logs for security, troubleshooting and performance.
9.3 Where a third-party security or anti-bot provider is used, PRE-ORDER will configure the integration to the extent reasonably possible so that tracking unrelated to security is not enabled without the appropriate consent.
10. Payment and checkout technologies
10.1 Stripe is the selected payment provider for B2C payments where enabled. B2B payments may use a separate licensed provider for conditional holding and release of funds, if and when that service is activated. Providers integrated into the website or Platform may use cookies or similar technologies for authentication, fraud prevention, payment security, regulatory compliance and transaction processing.
10.2 Payment-related technologies are governed by the actual payment flow, the PRE-ORDER Payment & Prepayment Policy, applicable payment-provider terms and privacy notices. PRE-ORDER does not use full card numbers or card security codes as analytics or advertising data.
10.3 A provider’s payment-security technology may be necessary for a requested transaction, even where another technology from the same provider is non-essential. Classification depends on the actual purpose and configuration, not merely on the provider’s name.
11. Embedded content and external services
11.1 The website may include external content or tools, such as video, social-media content, maps, support widgets, app-store links or other embedded services. Loading such content can allow the external provider to receive device, browser or interaction information.
11.2 Where an embedded service is not necessary to display the basic page, PRE-ORDER may use a consent-based placeholder so that the service loads only after the user chooses the relevant category.
11.3 Merely linking to an external website does not mean that PRE-ORDER controls the cookies placed on the destination website.
12. Mobile application technologies
12.1 The PRE-ORDER mobile application may, as features become available, support user accounts, payment interfaces, push notifications, analytics, order tracking and messaging. The SRS anticipates app/session data, analytics and push notifications as part of the service.
12.2 Mobile technologies may include app instance identifiers, notification tokens, local storage, SDK-generated identifiers, crash logs and device-level permissions. These are not always technically “cookies”, but similar consent and transparency principles apply when they are used for analytics, advertising or comparable non-essential purposes.
12.3 Users can also manage certain mobile permissions in the device operating-system settings. Disabling a permission may affect the feature that depends on it, such as push notifications.
13. Consent and legal basis
13.1 For cookies or similar technologies that require prior consent under applicable ePrivacy rules, PRE-ORDER will request consent before storing or accessing non-essential information on the user’s device.
13.2 Consent should be specific by purpose, informed, freely given and expressed through a clear affirmative action. Rejecting non-essential technologies should be available without forcing the user to accept them in order to access basic public information.
13.3 Personal data subsequently generated through a consented technology may be processed on the basis identified in the Privacy Policy. In some cases, consent to store or access a cookie and the GDPR legal basis for later processing are related but legally distinct assessments.
13.4 Project data-protection documentation states that consent will be used where appropriate and that another legal basis should be used where consent would not be freely given or another basis is more suitable.
14. Cookie banner and preference centre
14.1 Where required, PRE-ORDER will present a cookie banner or comparable consent interface that allows users to accept, reject or configure non-essential categories.
14.2 The interface should not rely on misleading design, pre-ticked consent, or an unnecessarily difficult rejection path. Consent records may include the consent version, timestamp, categories selected and a pseudonymous device or browser reference so that PRE-ORDER can demonstrate the user’s choice.
14.3 The preference centre should provide access to the current list of active technologies or providers, including purpose and expiry information to the extent available and relevant.
15. How to change or withdraw choices
- Use the “Cookie Settings”, “Privacy Settings” or comparable link made available on the website, if present.
- Clear or block cookies using browser settings. This may cause the website to ask for preferences again.
- Use device settings to control app permissions or reset relevant advertising or device identifiers where the operating system provides that functionality.
- Where a third-party provider offers its own opt-out mechanism, users may also use that mechanism; however, the PRE-ORDER consent interface remains the primary place for PRE-ORDER website choices.
15.1 Withdrawal of consent does not make prior lawful processing unlawful. It prevents future non-essential use to the extent the relevant technology can be disabled or removed.
16. Browser and device controls
16.1 Most browsers allow users to view, delete or block cookies. Users can also configure the browser to delete cookies when it closes or to block third-party cookies. The exact controls depend on the browser or device provider.
16.2 Blocking all cookies can prevent expected functions such as session continuity, language preferences, security checks or saved consent choices from working reliably.
16.3 Private browsing or similar modes may reduce persistence but do not automatically prevent all server-side logging, security processing or third-party network requests.
17. Data collected through cookies and similar technologies
17.1 Depending on the technology, PRE-ORDER or an integrated provider may process technical and interaction data such as browser or device type, operating system, general network information, page or screen viewed, session identifier, consent choice, referring source, timestamp, language, error information and interaction events.
17.2 PRE-ORDER does not require special-category personal data for ordinary website analytics or demand forecasting. Project documentation states that special-category data are not required for demand forecasting and should not be intentionally extracted from incidental free-text content for AI training.
17.3 Where identifiers can be reasonably reduced, pseudonymised or aggregated without defeating the relevant purpose, PRE-ORDER should use those measures in line with its data-minimisation approach.
18. Third-party providers
18.1 PRE-ORDER may engage service providers for hosting, content delivery, website security, analytics, communication, payments, support, anti-bot controls, embedded media, advertising or similar functions. A specific provider is considered active only if it is actually integrated and enabled in the relevant environment.
18.2 PRE-ORDER should not publish a static vendor list that is known to be inaccurate. The live cookie register or consent settings should identify active providers where technically and legally appropriate.
18.3 Third parties may act as processors, independent controllers or joint controllers depending on the service and data flow. Their role is assessed under the Privacy Policy, contractual arrangements and applicable law.
19. International data transfers
19.1 A provider receiving cookie or similar-technology data may process information outside the user’s country or outside the EEA. Where GDPR transfer rules apply, PRE-ORDER will use a lawful transfer mechanism and supplementary safeguards where required.
19.2 Users should consult the Privacy Policy and, where available, the live provider list for more information about recipients and transfer safeguards.
20. Retention and expiry
20.1 Session cookies generally expire at the end of the relevant session. Persistent cookies and similar identifiers have a defined expiry or remain until deleted. PRE-ORDER will not retain identifiers longer than reasonably necessary for the stated purpose.
20.2 Consent records may be retained for a reasonable period to demonstrate compliance, resolve disputes and avoid repeatedly requesting the same choice. Security logs may be kept for a period proportionate to the threat, incident, legal or audit purpose.
20.3 The specific expiry of an active cookie or comparable technology should be stated in the live cookie register or provider information where available.
21. Children
21.1 PRE-ORDER is not intended for children and its contractual services are intended for users who can lawfully enter the relevant agreements. PRE-ORDER does not intentionally use advertising cookies to profile children.
21.2 If PRE-ORDER learns that a non-essential technology has been used in a way that unlawfully tracks a child, it will take appropriate steps to stop the processing and delete or restrict the data where required.
22. Browser privacy signals
22.1 Some browsers or devices transmit signals such as “Do Not Track” or Global Privacy Control. The legal status and technical meaning of such signals can vary by jurisdiction and implementation.
22.2 PRE-ORDER will honour legally binding signals where required and technically applicable. Otherwise, users should use the PRE-ORDER cookie settings or browser controls described in this Policy to communicate their choices.
23. Changes to this Policy
23.1 PRE-ORDER may update this Policy when the website, Platform, technology stack, service providers or legal requirements change. Material changes affecting consent or user choices will be reflected in the consent interface where required.
23.2 The effective date at the top of the Policy will be updated when a revised publication takes effect. Previously given consent will be requested again where a material change means the earlier consent is no longer sufficiently specific or informed.
24. Relationship with the Privacy Policy
24.1 This Cookie Policy explains device-storage and similar technologies. The Privacy Policy provides the broader explanation of how PRE-ORDER processes personal data, including account, transaction, behavioural, communication, delivery, support and technical data.
24.2 If a cookie or similar technology collects personal data, both this Policy and the Privacy Policy apply. Mandatory law prevails if the documents cannot be reconciled.
25. Contact
Questions about cookies, consent or privacy can be sent to info@b2b-agency.cc. Please do not include passwords, payment-card details or other unnecessary sensitive information in a support request.
Schedule 1 – Category and implementation matrix
| Technology purpose | Examples of information | Typical duration | User choice |
|---|---|---|---|
| Essential security/session | Session ID, security token, consent state, load-balancing information | Session or limited persistent period | Not optional where necessary; browser blocking may break functionality. |
| Language/preferences | Selected language, interface preference | Session or limited persistent period | Optional where legally required; changeable through settings. |
| Analytics/performance | Page/screen events, device/browser data, referrer, timing, errors | Configured per provider and purpose | Consent required where applicable. |
| Advertising/attribution | Campaign ID, conversion event, pseudonymous advertising identifier | Configured per provider and purpose | Consent required where applicable. |
| Security/anti-bot | Network and browser signals, risk indicators, request patterns | Short or proportionate security period | May be necessary depending on function. |
| Payments | Payment-session identifier, risk and authentication signals | Transaction/security period under provider rules | Necessary for requested payment function; unrelated tracking remains separately controlled. |
Schedule 2 – Publication controls
- The website should provide a visible link to Cookie Settings or an equivalent preference control whenever non-essential technologies are used.
- The consent interface should block non-essential analytics and marketing technologies until consent where the applicable law requires prior consent.
- The live cookie register should be reviewed whenever WordPress plugins, analytics tools, advertising pixels, embedded media, anti-bot tools, payment components or other third-party scripts are added or materially reconfigured.
- The Privacy Policy and Cookie Policy should be reviewed together so that provider roles, international transfers, retention and contact information remain consistent.
- The production website should be scanned before launch and periodically thereafter to confirm that the live cookie register matches the technologies actually set or read.