Cookie PolicyCookie Policy

RideNova has not launched, so what follows describes intended use rather than an audit of what is running today. The website is being built to use cookies for four purposes and no others.

• Delivering the site: keeping pages working, protecting forms from abuse, and remembering that you have answered the cookie notice.
• Remembering preferences you set, so the site does not ask the same question every time you arrive.
• Counting visits in aggregate, to see which pages are read and where people give up.
• Measuring whether a campaign reached anyone, if and when RideNova advertises.

RideNova does not sell personal information and does not intend to. Nothing on this site is being built to assemble a profile of you across unrelated websites, and no cookie described here is shared for that purpose.

Cookies are grouped by what they are for rather than by who wrote them. Only the first category is set without asking; the other three are optional and stay off until you choose otherwise.

“Session” means the cookie is discarded when you close the browser. Anything longer is a persistent cookie, written with an expiry date that your browser enforces and that you can override by clearing your cookies at any time.

Where the real inventory will live

When the service launches, this page will carry a full inventory beside the table: the name of every cookie, the company that sets it, its exact purpose and its exact expiry, revised whenever the site changes. Publishing an invented inventory now would be worse than publishing none.

The intended design is written down here so that it can be held to when the site opens to the public.

• On a first visit, a notice explains the choice before any optional cookie is written.
• Refusing is as easy as accepting: one action for each, in the same place, carrying the same visual weight.
• Categories can be accepted one at a time rather than only all at once.
• Strictly necessary cookies are set regardless, because the site cannot be delivered without them, and the notice says so plainly instead of hiding it.
• Your decision is remembered in a strictly necessary cookie, so you are not asked again on every page.
• The choice can be reopened and changed later, from a control published alongside this policy.

Where a browser sends a privacy preference of its own — a do-not-track header, or a global privacy signal — RideNova intends to honour it wherever it can be read reliably. That is stated as an intention rather than a guarantee, because a signal the site cannot yet read is not a promise worth making.

Until launch, treat all of the above as intent rather than as a description of a control you can use today. Clearing this site’s cookies in your browser resets any record of a choice you have already made.

Several technologies sit next to cookies and are treated the same way here, under the same categories and the same consent.

Local and session storage

Browser storage that holds a little more than a cookie and is not attached to every request. Useful for an interface preference such as language or reduced motion. Session storage is cleared when the tab closes; local storage persists until you clear it.

Pixels and tracking images

A single-pixel image, or an equivalent request, embedded in a page or an email. Loading it tells the sender that the page was opened and roughly from where. Where they are used, they fall under the analytics or marketing categories and follow the same consent as the cookies in them.

Server logs

Requests to this site are recorded with an address, a timestamp and the page requested, to keep the service available and to investigate abuse. Logs are not cookies and are not governed by a cookie choice; the privacy policy describes how they are handled.

The apps do not use browser cookies. They use identifiers supplied by the operating system and by the app installation itself, for the same three jobs: holding a signed-in session, diagnosing crashes, and measuring use in aggregate.

Those identifiers are controlled by your device rather than by this website. Both major mobile platforms let you reset an advertising identifier, or refuse app tracking outright, from the privacy section of the device settings, and removing an app clears the storage it kept on the device.

Neither app has launched. This section describes how they are being built; the privacy policy covers the information they are designed to collect once they do.

A first-party cookie is set by the site you are looking at. A third-party cookie is set by another company whose service is embedded in the page — a map, a video player, a payment step, an analytics service — and is readable by that company under its own policy rather than this one.

RideNova has not launched and has not settled which providers it will use. This page therefore names none: listing a vendor we have not chosen would be a claim rather than a disclosure, and a cookie policy that guesses is worth nothing.

At launch, every third party that sets a cookie on this site will be named in the inventory published beside the table above, together with what it is for and where to read that company’s own policy. Providers that handle personal information on RideNova’s behalf are to be bound by contract to use it only for that work.

Blocking third-party cookies in your browser is a reasonable default and will not stop this site from working. Only the strictly necessary category is required, and that category is first-party.

Whatever choice a website offers you, your browser is the authority. Every major browser can block cookies, delete the ones already stored, or clear them automatically when it closes — and that setting applies to every site you visit, not only this one.

Menu names move between versions, so read the paths below as a direction rather than an exact route. In each case, look for the privacy section of settings.

Chrome

Settings, then Privacy and security, then the third-party cookie controls. Per-site permissions live under Site settings, and history clearing removes what is already stored.

Safari

Settings or Preferences, then Privacy, on the desktop. On iOS and iPadOS, open the Safari entry inside the system Settings app, where blocking and clearing are separate controls.

Firefox

Settings, then Privacy & Security, where the standard, strict and custom levels each apply a different default and can be adjusted per site.

Edge

Settings, then Cookies and site permissions, which covers both blocking and clearing on exit.

A private or incognito window keeps cookies only until the window closes, which is the quickest way to look at a site without leaving anything behind.

Blocking every cookie has consequences. Preferences such as language stop being remembered, a cookie notice reappears on each visit because the record of your answer cannot be stored, and anything that depends on a session may not complete at all.

This document will change. The first substantial change will be the launch version: dated, versioned, and published together with the cookie inventory that a draft cannot honestly contain.

When a change alters what is stored on your device, or what a category is used for, we will mark it on this page. Where the change is significant, we intend to ask for consent again rather than assume your earlier answer still applies.

Until that version exists, the status shown at the top of this page is the accurate one: a draft, not in force.

Questions about this policy, about a particular cookie, or about a choice that did not stick can be sent through the contact page. Mention which browser and version you were using — a cookie problem is almost always specific to one of them.

If you are reviewing this draft on behalf of a legal team, use the same channel and mark the message for the attention of the privacy team.