BridgeSync

Cookie policy – BridgeSync website

Introduction and Scope

This cookie policy informs you about the cookies used on the BridgeSync website (https://bridgesync.io) and how we\'ve written it to comply with Dutch and Belgian legislation (the General Data Protection Regulation (GDPR) and the Dutch Telecommunications Act in the Netherlands, and the GDPR and Belgian cookie legislation in Belgium).

Here, we tell you everything you need to know about cookies: what they are, which types we use, what we use them for, and how we comply with legal requirements.

Note: This policy sets out how we use cookies on our website. This does not apply to the use of the BridgeSync plugin or other BridgeSync services outside of this website.

We will show you a cookie banner on your first visit so that you can decide which cookies you want to allow. Here at BridgeSync, we respect your privacy. We will never install cookies on your computer without your permission, and we will always follow the law. You will find all the information you need about how we use cookies below.

What are cookies?

Cookies are small text files that websites put on your device when you visit their site. You can read these text files again on the website later.

This way, cookies remember information about your visit, such as your preferences or items in your shopping cart. This helps the website work better or faster next time you visit.

Note: In this policy, we also use the term cookies for similar techniques that store or read data, such as scripts, tracking pixels, local storage, and similar "trackers." It is clear that these technologies are subject to the same legal rules.

Cookies are essential for your device to be recognised when you return. Cookies are small and contain only limited information (such as a unique identifier). They enable useful functions, but some of them can track your online activity. Here, we explain the different types of cookies we use and why.

Types of cookies we use

We use the following categories of cookies: strictly necessary (functional), analytics (tracking), and marketing. We explain each category and its purpose below.

Strictly necessary (functional) cookies

Functional cookies are essential for the website to work properly. These cookies provide essential features such as navigation, access to secure areas, and remembering your input (e.g. products in a shopping cart, login status, or language preference). You must have these cookies to use the site properly.

Legal basis: These cookies don\'t affect your privacy, so we don\'t need to ask for consent under the Dutch Telecommunications Act or Belgian regulations. We will let you know when they\'re around.

We only use these cookies to process personal data (like a login ID) when we have to for the service you asked for, or if we have a legitimate interest in making our website work well (GDPR Art. 6(1)(b) and/or 6(1)(f)). You can\'t refuse them via the cookie banner because the website can\'t function correctly without them.

Here are some examples of functional cookies on our site:

WooCommerce cookies

Use these cookies to keep track of your shopping cart and make checkout easier. Use the codes woocommerce_cart_hash and woocommerce_items_in_cart to track cart contents. These are session cookies that expire when you close your browser. wp_woocommerce_session_* stores a unique code for up to two days to link your cart to your session.

WordPress cookies

You'll need cookies to use the website. For example, there's a cookie called "wordpress_test_cookie" (this checks if your browser accepts cookies, and it's a session cookie). There's also a cookie called "wordpress_logged_in_*" (this remembers that you're logged in). If it's relevant, it'll expire when you log out or the session ends, and there are also preference cookies (wp-settings-{UID}). These record your settings, which are valid for about a year. These are exclusively used for logged-in users and site administration.

Cloudflare security cookie

We use __cf_bm for security and bot management. This cookie helps distinguish legitimate users from automated traffic to keep the site safe and available. It is short-lived and typically expires after 30 minutes of inactivity. Cloudflare considers these cookies strictly necessary for its security service.

We only use functional cookies on our own website (first-party cookies), and we do not share the information in them for other purposes. It is clear that these cookies and similar technologies fall under the exception for "strictly necessary cookies" as outlined in the ePrivacy rules.

Analytics (tracking) cookies

Tracking cookies, or analytics cookies as they\'re also known, are used to collect information about how visitors use our website. These cookies allow us to measure key performance indicators such as the number of visitors, popular pages, user navigation and session duration. We need to find out how people use our site so we can keep making improvements.

Google Analytics is Google\'s web analytics service. The data collected via these analytics cookies includes your IP address (we anonymise IPs where possible), device and browser information, and click behaviour (e.g., which pages you visit). We use this combined/anonymous data to make the user experience and performance of the website better.

You must give us your consent: While analytics cookies in the Netherlands can, under certain conditions, be considered "limited privacy-impact" (and therefore not require consent), we are taking a cautious approach. In Belgium, analytics cookies are not strictly necessary and do require consent. We will always ask you first if it's OK before we put tracking/analytics cookies on your device.

These cookies will definitely affect your privacy by tracking (anonymous) user behaviour. You will only get them if you click on the cookie banner. You have the right to change your mind and cancel this at any time (see below).

Note: We have a data processing agreement with Google for Google Analytics, and we have strict privacy settings in place (such as masking IP addresses and not sharing data with other Google services) to minimise any potential privacy impact. Google as a vendor will certainly have access to the data collected. Google LLC is based in the United States, so any data collected through Google Analytics cookies will be sent over there for processing. Google must protect any transfers outside the EEA because of the Standard Contractual Clauses.

Marketing and profiling cookies

Marketing cookies are used to recognise you and track your behaviour across one or more websites. The aim is to build a profile of your interests. We and third parties (e.g. advertising networks) will show you more relevant content and ads that match your interests based on this profile.

Third parties usually put these cookies on our site (third-party cookies), such as cookies from YouTube or advertising platforms. Marketing cookies track which videos you watched, which products you viewed, and which website you arrived at ours from. They collect personal data such as your IP address, unique identifiers, browsing behaviour, and interactions with content.

We use marketing cookies on the BridgeSync website, mostly in connection with embedded content and advertising tools. When we display YouTube videos on our site, YouTube places cookies that track your video playback. These may be used for advertising purposes by YouTube/Google. These cookies (like the YouTube cookie, VISITOR_INFO1_LIVE) help Google build a profile about you so they can show you targeted ads.

You must always obtain consent: You will always have to agree to activate marketing cookies. When you first visit us, our banner will ask you to consent to "marketing" cookies. These cookies will only be placed if you provide a positive opt-in.

Marketing cookies are designed to last longer and link your activity across different sessions and websites. Google is a prime example of this.

Your rights: We will, of course, ask you to consent to this in advance, and we guarantee that we will be transparent about how we use your data. You are free to refuse this, of course — our website will still work, but you won't get personalised content or ads. You can still access the site if you choose not to accept marketing (or tracking) cookies. A "cookie wall" is out of the question. You can also take back your previously given consent at any time (see below on how to do this).

Our website uses third-party cookies.

Our website allows third parties to place or read cookies. BridgeSync does not set these "third-party cookies". They are set by service providers whose functionality or services we use. Here is a list of all the third parties that can place cookies via bridgesync.io, with an explanation of what they're for and whether data may be processed outside the EU:

Google Analytics (Google LLC)

Purpose: These cookies (e.g. _ga, _gid, _gat) measure how visitors use our site (e.g. page views, duration, referral sources). BridgeSync uses these statistics to improve the site.

Personal data: Anonymised IP addresses (where possible), unique identifiers, and aggregated usage data.

Retention period: The main cookie, '_ga', is valid for two years. Other Analytics cookies vary, from one minute to 24 hours or several months.

Third parties/Transfers: Google LLC is based in the U.S. Any data collected via Analytics will be stored on servers outside the EU (e.g., in the U.S.). Google must adhere to EU rules regarding data handling, or the EU–US Data Privacy Framework if applicable. This guarantees the protection of your data during transfer.

Google Tag Manager (Google LLC)

Purpose: It\'s a tag management system that allows us to load and manage other scripts and cookies on our site. Tag Manager does not collect personal data for analytics; it simply serves as a technical tool to activate tags like Google Analytics or pixels. Tag Manager sometimes uses a cookie to sort out the loading order, but it doesn\'t set tracking cookies on its own.

Retention period: This doesn\'t usually apply, or it\'s very short, like when it\'s in preview or test mode.

Third parties/Transfers: Google LLC (US) is also involved as a service provider. As with Analytics, technical information may be sent to Google\'s servers in the US.

Cloudflare (Cloudflare, Inc.)

Purpose: Cloudflare provides a Content Delivery Network (CDN) and security services (like DDoS protection and bot management). Cloudflare uses only the strictly necessary cookies to manage traffic and block malicious requests. The cookie __cf_bm helps to tell the difference between automated bot traffic and real users. This cookie contains a random identifier and some metadata used by Cloudflare for a bot score, which is encrypted (we can\'t read it).

Retention period: Cloudflare security cookies are short-lived: The __cf_bm cookie expires after 30 minutes of inactivity, and other Cloudflare cookies (such as load balancing session cookies) remain active for a few hours to 24 hours.

Third parties/Transfers: Cloudflare, Inc. is a US company. Cloudflare processes your cookie data in data centres in the US. We also use Standard Contractual Clauses for data transfers. Cloudflare asserts that all its cookies are "strictly necessary" for the security service. However, we have listed them here in case you want to know.

YouTube (Google LLC)

Purpose: Our site embeds YouTube videos. When you play a YouTube video on our site, YouTube sets various cookies. These help the video player work (e.g. remembering preferences or bandwidth) and may track what you watch and link it to your Google profile for advertising and recommendations. Examples include YSC (a session cookie that keeps your video player interactions in the same session) and VISITOR_INFO1_LIVE (which is valid for around six months). It can estimate bandwidth and optimise streaming, and may also use ad cookies (such as IDE via DoubleClick, 13 months in the EEA) for personalised ads.

Personal data: It will show you viewing history, device IP address, any Google account information if you\'re logged in, and demographic data as far as Google knows.

Third parties/Transfers: YouTube is a service by Google LLC (U.S.). When these cookies are active, Google will get data about what you watch on the video site. This data will be sent to their servers outside the EU, for example in the US. Google also uses this kind of data for YouTube Analytics and ad personalisation. Google has your back with contractual safeguards for these transfers, but be aware that U.S. authorities might be able to access your data under certain circumstances. Turn off marketing cookies to stop YouTube videos from loading. Our site might show a placeholder instead of the video.

WooCommerce (a plugin by Automattic Inc.).

Purpose: WooCommerce provides the e-commerce functionality on our site (e.g. shopping cart and checkout). WooCommerce uses functional first-party cookies (see the Functional Cookies section for more information) to ensure you have the best shopping experience. For example, cookies track items in your cart and a session ID links your order information on the server temporarily.

Personal data: These cookies do not store anything that can directly identify you, but they do link your browser to server-side information (like what\'s in your cart or your order status).

Retention period: Most WooCommerce cookies are just session-based, so they\'re removed as soon as you close your browser. There\'s just one cookie left, which will last for about two days. You can come back and restore your cart later if you need to.

Third parties/Transfers: WooCommerce cookies are first-party cookies on our own domain. We never send information to Automattic or anyone else; it\'s all processed on our own website/server here in the EU. You can be absolutely certain that this cookie information is not being transferred outside the EU.

WordPress (Automattic Inc.)

Purpose: Our website uses WordPress CMS. WordPress itself sets a few functional cookies to keep the site running well and to improve usability. The wordpress_test_cookie is used to check that cookies are working. It is clear that cookies for logged-in users must be applied (e.g. wordpress_logged_in_{hash} to track your login session) and that cookies that help visitors leave comments on blog posts must also be applied (e.g. comment_author_{hash}, which remembers your name/email for future comments for around 347 days).

Personal data: These cookies save your account IDs and other info you\'ve entered, like your name and email address, in your browser so you don\'t have to enter it again.

Retention period: When it comes to logged-in WordPress users, cookies are usually of the session variety (they expire on logout or when you close your browser). Comment cookies, on the other hand, are stored for around 347 days.

Third parties/Transfers: These cookies are on our own domain, just like WooCommerce. Rest assured, the data will not be automatically sent to Automattic or other outside parties. Automattic does not track us unless we use extra plugins that send data, which we do not use here. These WordPress cookies are functional and don\'t involve international transfers.

Note: We have data processing agreements in place with all the third parties listed above (Google, Cloudflare, Automattic) and have taken other steps where necessary to keep your data safe. Check the privacy and cookie policies of these third parties for more information. BridgeSync has no control over what these other parties do with the data collected via their cookies. They may act as independent data controllers for their own processing.

Cookie retention periods

Cookies have different lifespans. This is how long different types of cookies usually stick around on your device. There are two types of cookie: session cookies and persistent cookies.

Session cookies

These cookies only last as long as your browser session, so they\'re pretty much just a temporary thing. Many functional cookies fit into this category.

Here are some examples: Most WooCommerce and WordPress cookies are session cookies and are cleared when you close your browser. Examples include the YouTube YSC cookie and certain Cloudflare cookies.

We use persistent cookies here.

These cookies stay on your device even after you\'ve closed the browser, and they\'ll keep on there until they expire. All cookies have an expiry date, and their lifespan can vary from minutes to years, depending on their use. We don\'t keep things for too long.

These cookies are here to help you.

Some of these cookies, used for things like preferences and settings, can be stored for anywhere between a few days and a few months. Take WordPress comment cookies (name/email), for example. These expire after about 347 days (just under 12 months). Any site preferences will usually expire within a year.

Analytics cookies

Google Analytics cookies last longer. The main cookie, _ga, is kept for two years unless you delete it earlier. There are two Analytics cookies: _gid, which expires after 24 hours, and _gat, which expires after one minute. These are there to limit the number of requests. Google sets these fixed terms to measure trends over time.

These are the marketing cookies.

Third-party cookies typically persist from a few months up to a year. For example, Google\'s VISITOR_INFO1_LIVE persists for around six months, and the DoubleClick IDE cookie may persist for up to 13 months in the EEA.

Here\'s the latest info: The exact cookies and terms will change if we update our site or if third parties adjust their cookies. We have a complete and up-to-date list of all the cookies we use, their intended purpose and the duration of their validity. Look in our cookie banner and internal records. Get in touch now to see the current list of cookies and their validity.

Consent and changing your preferences

Consent

When you visit our website for the first time, you will see a clear cookie banner. It gives you a quick rundown of our cookies and asks for your consent to place non-essential (tracking and marketing) cookies. You have the option to either accept all non-essential cookies or to specify per category (tracking, marketing) whether you allow them.

We only install tracking and marketing cookies on your device after you have actively agreed to them, e.g. by clicking "Accept" or saving your preferences. You can put functional cookies on a site before you ask for consent, because the site can't work otherwise, and these are in the exception, so you don't need to ask for consent (we tell you about them in this policy).

The choice is yours: You don't have to accept all cookies — just untick the ones you don't want and then click "Save preferences." Rest assured that if you say no, we won't load any tracking or marketing cookies. Refusing to comply will not result in your access being blocked or reduced, as this would contravene the GDPR (the use of so-called cookie walls is not permitted).

Withdraw or change your consent

You can change your mind about cookies whenever you want (GDPR Art. 7(3)). You should be able to withdraw consent as easily as you gave it. Here are the options we\'ve got for you:

Via our website

Reset your cookie preferences via our website. Use the 'Cookie settings' link in the footer on every page to reopen the banner and adjust your choices. This option allows you to switch categories on or off and save your new setting. We will stop putting cookies on your computer immediately.

Via your browser

If your browser doesn\'t provide an automated settings button, delete all cookies from your browser (see below). The cookie banner will reappear on your next visit so you can make a new choice. If you delete or block cookies on your browser, it\'s the same as withdrawing consent.

If you need to withdraw your consent or have any issues, contact us (our contact details are at the end of this policy). Rest assured, we will make sure your preferences are respected.

The consequences of withdrawal are clear.

Be aware: withdrawing or refusing consent for certain cookies may result in functionality issues. Refuse our tracking cookies and we won\'t include your visit in our statistics. This won\'t affect your use of the site itself.

If you\'re not happy with the cookies, you will find that third-party content (like YouTube videos) doesn\'t load automatically and that you see more general (less personalised) ads. You\'ll still have full access to all the info on the site. You can choose to load certain external elements only after you\'ve interacted with them.

Manage cookies via your browser settings

You can also manage your cookies yourself via your web browser settings. You can view, limit, delete or block cookies in most browsers. For example, you can delete all cookies (useful for resetting your consent) or set third-party cookies to be blocked. Follow these tips for the most popular browsers:

Google Chrome

Go to Settings, then Privacy and Security, and then Cookies and other site data. You can remove cookies and set blocking preferences there (e.g. block all third-party cookies). Use the 'Clear browsing data' option to remove cookies (and cache, if you want) for a given period or permanently.

Mozilla Firefox

Go to Settings (or Preferences on a Mac) and select Privacy & Security. Delete your cookies by going to the 'Cookies and Site Data' section and clicking on 'Clear Data'. You can set specific rules (like blocking cookies from unvisited websites or managing exceptions) via Settings… next to Manage Cookies and Site Data.

Microsoft Edge (Chromium)

Go to Settings, select Cookies and site permissions, then Cookies and site data. Toggles allow you to either allow or block cookies. Under 'See all cookies and site data', you can view and remove individual cookies.

Apple Safari

If you're on a Mac, go to Preferences and then Privacy. Choose "Block all cookies" (this is not recommended for general use, as many websites will not work) or view which cookies are set per website (via Manage Website Data, where you can remove cookies). If you're on an iPhone or iPad, go to Settings > Safari > Privacy & Security.

Other browsers

Check the help section of your browser (like Opera, Brave or Samsung Internet) for more info. Cookie settings are usually found under 'Privacy' or 'History' settings.

Blocking cookies: consequences Blocking all cookies will cause parts of our website to malfunction. Logging in or using a shopping cart often requires cookies. You can also block third-party cookies only — most browsers have this option — so that only the site you\'re on can access your data. This will limit tracking across different sites.

You control your browser settings yourself, so you\'re in charge. You can delete all cookies when you close your browser or get a notification when a website wants to place a cookie.

Legal basis (GDPR)

The processing of personal data via cookies is covered by the GDPR. We will explain the legal basis for processing each type of cookie.

These are functional cookies.

We only use strictly necessary cookies to provide the service you requested (website functionality), and we rely on the exception in the Telecommunications Act and the legal basis necessary for the performance of a contract (GDPR Art. 6(1)(b) applies). When you put something in your shopping cart or log in, the system saves this information in a cookie to work properly. This is an integral part of BridgeSync.

For other functional cookies that aren\'t directly under contractual necessity, we rely on our legitimate interests (GDPR Art. 6(1)(f)). The website must work well for everyone who visits, and be secure and efficient. We\'ve thoughtfully balanced these interests against your right to privacy and are confident that using functional cookies doesn\'t unduly infringe on your privacy, as they aren\'t used for anything else.

Analytics and tracking cookies are used.

It is clear that for analytics cookies that don't fall under the "limited privacy impact" exception — and for all cookies that track individual user activities (tracking cookies), to be precise — consent is the appropriate legal basis (GDPR Art. 6(1)(a)). As I have already stated, we will ask you to consent to these cookies being placed.

You can change your mind at any time and refuse or withdraw this consent, and it won't affect your use of the website. We will use "limited analytics cookies" that meet strict privacy conditions (e.g. first-party analytics with anonymised data). We will rely on legitimate interests where allowed by law. BridgeSync relies on consent for all analytics/tracking cookies because of different legal interpretations (NL vs BE). This gives users maximum control and ensures compliance with all regulations.

These are the marketing cookies.

Marketing and profiling cookies are also based solely on consent (GDPR Art. 6(1)(a)). Before we start using cookies (usually from third parties like Google/YouTube), we\'ll ask you to opt in via the cookie banner. If you don\'t consent, the cookies won\'t be active and your personal data won\'t be processed for marketing purposes on our site.

If you do give consent, you can change your mind later (as we described earlier), and we\'ll remove the marketing cookies (as far as we can) or at least stop reading them, and stop new placement. Third parties that matter (like Google) base their ad personalisation on your consent given through our site. Manage your preferences in your Google Ads settings if you have an account.

Your GDPR rights: For all categories, if personal data are processed, you have certain rights under the GDPR (see also our Privacy Policy). You can request access to data collected about you, request rectification or erasure, request restriction of processing, object to processing based on legitimate interests, or (as relevant) exercise data portability. To the extent cookie data are not personally identifiable (e.g., purely anonymous analytics data), the GDPR may not apply to those data. Nevertheless, BridgeSync will, in the spirit of transparency, strive to accommodate your preferences regarding cookies and privacy as much as possible.

Contact BridgeSync

If you have any questions or requests regarding this cookie policy or how BridgeSync uses cookies and personal data, please contact us. Here is the lowdown on our company and how to get in touch:

BridgeSync

Address: Ben Essingstraat 15, 1695 CV Blokker, Netherlands

Email: compliance@bridgesync.io

Here's the VAT number: NL002203659B53

Chamber of Commerce (KVK): 73844004

IBAN: NL73 KNAB 0502 6079 71

Here are the updates to the policy: We will update this cookie policy when the law changes or when we change the cookies we use. Any major changes will be posted on the website. This policy was last updated on: The date is 10 June 2025.

If you have any questions about our cookie policy, please get in touch.

If you have any questions about how we use cookies or how to adjust your preferences, please get in touch. Contact us now.

Send an email to compliance@bridgesync.io