Explore our collection of 200+ Premium Webflow Templates
Need to customize this template? Hire our Webflow team!
Last updated: 11 October 2026
This policy explains what this website stores on your device, why, for how long, and how you can change your mind. It sits alongside our Privacy Policy, which covers personal data more broadly. It is issued by Sealink Technology B.V., Dalweg 3B, 3233 KK Oostvoorne, the Netherlands.
We have kept it specific. Rather than a generic list of everything a website might use, it names what this site actually sets today. When that changes, this page changes with it.
A cookie is a small text file a website asks your browser to store, and which your browser sends back on later requests. It lets a site recognise a returning request — to keep you logged in, to remember a preference, or to tell a human visitor from a bot.
Other technologies do the same job by different means. Local storage and session storage keep data in the browser without sending it on every request. A pixel or web beacon is a tiny image or script whose loading tells a server that something was viewed. European rules treat these the same way as cookies: what matters is that information is stored on, or read from, your device — not the technical means.
Only the first category is active on this website today. The other two appear in the banner so that the choice is yours in advance, and so that nothing can start quietly later.
These cannot be switched off. They are used on the basis of our legitimate interest in operating a secure, functioning website, and under the ePrivacy exemption for storage strictly necessary to provide the service you requested.
None in use. We currently run no website analytics: no Google Analytics, no Google Tag Manager container, no self-hosted measurement. If we introduce analytics, it will be listed here with its provider, purpose and duration, and it will load only after you have agreed to the analytics category in the banner.
None in use. We run no advertising pixels, no remarketing tags, no conversion tracking and no cross-site profiling on this website. We do not sell or share personal data for advertising, and we have no interest in doing so for a business that sells bridge equipment to fleet operators.
Some scripts, stylesheets and fonts used by this site are delivered from external content delivery networks rather than our own servers. They set no cookies on your device, but requesting a file from them means your IP address, your browser details and the page you are on are visible to the network serving it, because that is how any web request works.
The networks involved are Webflow’s own CDN, Cloudflare, jsDelivr, cdnjs and unpkg. Each acts as a technical delivery provider; the data is used to serve the file and to protect the service from abuse. How we treat the personal data involved, and the safeguards that apply when it leaves the European Economic Area, are set out in the Privacy Policy.
On your first visit a banner appears in the corner of the screen. Nothing in the analytics or marketing categories runs before you answer it — not on a delay, not after a scroll, not if you ignore it. Continuing to browse is not treated as agreement, because under the GDPR consent has to be an active choice.
The banner offers Accept all, Decline and Choose. Accept and Decline are given the same size and prominence on purpose: a banner that makes refusal harder than acceptance does not collect valid consent. Choose opens the categories so you can agree to some and not others.
Your answer is stored in the sl_consent cookie described above and is sent to no one. Separately, a consent signal is set in the page so that any future measurement tool starts in a denied state and is only released if you have agreed.
Open Cookie settings from the link in the footer of any page. The banner reopens with your current choice shown, and you can change it or withdraw it entirely. Withdrawal takes effect immediately and does not affect anything that was lawful while your consent was valid.
Every major browser lets you see which cookies are stored, delete them, block them for a specific site, or block them in general, usually under Settings → Privacy. Your browser’s own help pages explain exactly where, and they stay more current than anything we could copy here. Browsers also offer a private or incognito window, which discards site data when the window is closed.
Deleting the sl_consent cookie resets your choice, so the banner will ask again on your next visit.
Nothing breaks. Because every non-essential category is currently empty, declining changes nothing about how this site behaves for you. It does mean that if we later add analytics, it will not run for you unless you change your answer.
Blocking strictly necessary cookies through your browser is a different matter: the contact form and the site’s abuse protection may stop working as intended.
Browsers can send a Do Not Track or Global Privacy Control signal. There is still no agreed standard for how a site must respond to DNT, so most sites, including this one, do not act on it. This has no practical effect here: we run no tracking for such a signal to switch off, and the consent banner already governs everything that is not strictly necessary.
We revise this page whenever we add, remove or change a cookie, or change the purpose one serves. The date at the top shows the version in force. Where a change introduces a new non-essential cookie, we ask for consent again rather than relying on an answer you gave about something else.
If anything here is unclear, or you want to know more about a specific item, write to support@sealink.co or use our contact page.