Skip to content
Ride On HØVIKWORKSHOP & ONLINE SHOP
Menu

Cookies and privacy choices

Last updated 14 November 2026

Open cookie settings

Necessary storage supports the cart, login, requested payment, security and remembering your privacy choice. Our first-party ro_privacy cookie lasts up to 180 days and holds a signed random receipt ID, version, timestamp and purpose choices. It is not linked to your account or advertising. The self-hosted CookieConsent library uses cc_cookie for up to 180 days on butikk.ride-on.no to display your settings. No choices are sent to an external consent platform. This cookie alone cannot enable booking or statistics; a valid, server-verified Ride On choice is still required. The WooCommerce cart cookies last for the session; wp_woocommerce_session_* normally lasts up to 2 days. A saved account cart expires after 30 days of inactivity and is cleaned on use. Login cookies normally last for the session, or up to 14 days with “remember me”; WordPress settings cookies for logged-in users may last one year. Security/access cookies depend on the Cloudflare configuration.

Storage at checkout

The Svea payment window loads from checkoutapi.svea.com at the address step. Svea sends the session cookies persistance and TS01268479 without a fixed expiry date. Your browser may block them in the payment window. Checkout stores the street address, postcode, town and Posten address reference in the browser session so it can restore your address draft. If you are signed in, checkout may remember your last delivery method in your browser. This preference has no automatic expiry and can be removed by clearing site data.

Optional booking: the BikeDesk iframe stays off until permission is given. It can load Google reCAPTCHA and a Reepay/Flatpay component and share your IP address, browser/device information and security signals, including possible transfers outside the EEA. These providers control storage within their window. You can also open the booking form directly from the workshop page or book by phone or email. Withdrawal removes the window here but cannot remotely delete third-party cookies or an existing booking.

When you open BikeDesk booking, the form may use Google reCAPTCHA to assess abuse risk. In our English booking test, Google set _GRECAPTCHA for about 180 days and used the browser storage keys rc::a (local storage) and rc::c (session storage). The form also contacted Reepay before any payment was selected. The providers manage these components.

Optional search statistics: with separate consent, Ride On stores daily search/product-click totals for 30 days, without account, IP or device identifiers. Common contact-detail patterns are filtered out. No additional analytics cookie is set. Rejecting statistics does not affect product search.

WooCommerce order attribution is disabled. The online store uses Svea Checkout. iizy transfers sales and payment information to Tripletex for bookkeeping. This system-to-system transfer does not set a cookie in your browser. Necessary payment/shipping storage is assessed separately when a customer requests those services.

Use “Cookie settings” at the bottom of any page to reject, change or withdraw optional choices. Both optional purposes start off. GPC/DNT signals keep optional services off. You can separately allow BikeDesk booking using “Accept and show booking”; statistics stay off. A new choice is needed after 180 days or a material policy change. No JavaScript or a saving failure means optional services stay blocked. Our minimal receipt log stores no IP, email, browser profile or account and is cleaned daily after 180 days. Read the English privacy notice.

Cookie settings