Cookie Policy

Cookies are small text files that are placed on your device when you visit our website. They help us provide you with a better experience by remembering your preferences and understanding how you use our site.

Nothing beyond the strictly necessary cookies runs until you switch it on. Analytics, functional and marketing all start off, in every country, and nothing arrives pre-ticked. If you close the banner without choosing, all three stay off.

Not everything that loads is covered by the categories below. The sign-up form loads Google reCAPTCHA the moment the page opens, before you have an account and before any cookie choice of yours exists; the contact form loads the same script when you send the form. Loading it tells Google your IP address. We use it to stop bulk automated sign-ups, and there is no switch for it today. The CAPTCHA is not the only thing outside those categories. The map view on the Benefits page loads Google's map code from maps.googleapis.com the moment you open it. If you read Cravora in Chinese, Japanese or Korean, your browser fetches the fonts for those characters from Google's font servers at fonts.gstatic.com, on every screen in those languages, signed in or not. And some help pages carry a tutorial video from YouTube or Vimeo: nothing is requested from either company when the page opens, because what you see is a still panel we draw ourselves, which names the company before you press anything. Press play and their player loads, which tells them your IP address and lets them set their own cookies; we use YouTube's youtube-nocookie.com address and ask Vimeo not to track, which reduces that without stopping it. The thumbnail pictures on the video, resource and community story lists are fetched by our servers and served from us, so opening one of those lists contacts nobody else. None of these has a switch here; for the video, the press is the choice. Our Privacy Policy sets them out in full.

We use cookies for the following purposes:

• To keep you signed in, to remember your cookie choice, and to hold the language you chose. Signing in sets a session cookie that lasts seven days, or thirty if you tick the box to stay signed in. Your cookie choice is stored in a cookie of its own for a year. The language you choose is stored in a cookie of its own for a year as well, set when you pick a language from the language switcher, on the welcome screen or in your settings, and when you sign in on a browser that carries no language cookie yet, from the language stored on your account. These are the strictly necessary ones. They have no switch. Without the sign-in and cookie-choice ones the product does not work; without the language one a page comes back in whatever language your browser asks for, and in English when your browser asks for one we do not offer.
• To measure how the site is used, and only if you switch the Analytics category on. That category decides whether Google Analytics and PostHog load in your browser; with it off, neither one loads. Where they are loaded, the address of each page you open is sent to both of them. That is not only our marketing pages: the same scripts run through the onboarding questionnaire, so the addresses of the pages where you record your health conditions, your medications, your insurance and your income go to Google and to PostHog as well.
• To record what you click, if you switch the Functional category on. That is the only thing this category does today. It turns on PostHog's automatic capture, which records the elements you click and the text written on them — on the conditions step of the onboarding questionnaire, that text is the name of each health condition you select. It only takes effect while Analytics is on as well, because PostHog is not loaded otherwise. It does not personalise anything you see.
• To record your answer on the Marketing category, and nothing more. No advertising or ad-network tag is loaded by the product today, so that category currently switches nothing on or off; we keep your answer so that it already applies if that ever changes. One thing we will not overstate: the app does not set Google's cross-device advertising signals either way, so whether the data Google Analytics receives is put to an advertising use is decided by the settings on our Google Analytics account rather than by anything in the product.

The cookie banner asks once. It appears only while you have not answered it, and the moment you answer — Accept All, Reject All or Save Preferences — it closes. It comes back only if that cookie is gone or the check that reads it fails. There is no button anywhere on the site that brings it back. The close button on the banner is not an answer: it hides the banner without saving anything, so it returns on your next page load. We store the answer you do give in a cookie in this browser for one year, and inside that year we do not ask again, even if we change this policy or add a category. The answer you already gave keeps applying until you change it or it expires.

If you have an account, that is where you change it. Open your settings, go to the Privacy tab, and use the Cookies & Tracking card. It has its own save button, separate from the rest of that page. You have to be signed in to reach it; the settings screen sends you to sign-in otherwise. If you answered the banner without an account, there is no route left inside the product.

The other route is your browser: clear this site's cookies. Your answer lives in one place, that cookie, and clearing it puts you back to everything non-essential being off. It used to live in two. We also kept a copy in this site's local storage, and the scripts that load Google Analytics and PostHog read that copy before the cookie — so analytics could keep loading after you had deleted the cookie, and answering the banner again did not clear it, because the banner writes only the cookie. That second copy is gone, and a device that still has one has it removed the next time you open Cravora. Site data is still where we store which version of a homepage test you were shown, written the first time you load our homepage, before you have answered the banner, so clearing site data as well as cookies is what removes that.

Turning analytics, functional or marketing off does not change how the site works. Analytics decides whether Google Analytics and PostHog load at all. Functional decides whether PostHog records what you click automatically. Marketing switches nothing today, because the product loads no advertising or marketing script. The cookies that do carry functionality are the strictly necessary ones, and neither the banner nor the settings card can switch those off. Your browser can, and that route is different: blocking or deleting this site's cookies takes those out too, and signing in, our security checks and the cookie that holds your language all rely on them, so that route can stop parts of the site working.

These choices are not only about our marketing pages. With analytics on, Google Analytics and PostHog also load on the onboarding, welcome and payment screens, and the address of each step you visit is sent to both, including steps named for your conditions, your medications and your insurance. They do not load on the sign-in and sign-up screens, and not on the rest of the signed-in app.

Four scripts sit outside the categories above, and only one of them is affected by any choice you make here. The first is Google reCAPTCHA. Our sign-up form and our public contact form load it, from Google, whenever a site key is configured. It loads whatever you have chosen here, and before you have chosen anything.

The second is Google Maps. Switch the Benefits page to its map view and your browser loads Google's map code straight from Google, inside the signed-in app, whatever you have chosen here.

The third is Sentry, the company we use to catch crashes, and it is the one that runs everywhere. Where a Sentry connection is configured, Sentry loads on every page — our public pages and the signed-in app alike, not only the screens the analytics scripts reach. It sends Sentry the errors your browser hits, the console errors and warnings on the page, and the requests that come back a failure, whichever address they went to. It also records a replay of what is on your screen, and that half does follow your answer here. If you have not accepted the analytics category, or have made no choice at all, nothing is recorded. If you have accepted it, the recorder runs in every session you open and holds the last minute or so of it in memory, and nothing is sent from a session in which nothing goes wrong. Once something does go wrong, the part held in memory is sent to Sentry and the recording then continues, and keeps being sent every few seconds, for the rest of that session. Turning analytics off stops it in the page you are looking at, without waiting for a reload; what it was holding is discarded if nothing had gone wrong, and the last part is sent if something had. The replay masks the text and blocks images and video, but the layout of the page, what you click and where you go is recorded. One control does stop it, and it is not on this page: the Privacy tab of your settings has a Crash Reporting switch. It starts on, and turning it off stops the errors, the console messages and the failed requests described above, and the replay with them. Your answer is saved against your account and mirrored into a cookie in the browser you signed in on, so it applies on every Cravora page in that browser, this one included. Signing out removes that cookie, and in a browser with no such cookie — one nobody has signed in on, or one you have signed out of — there is no answer to read and the reporting goes on. Blocking Sentry's own address in your browser does not stop it either, because the recordings leave through our own domain. Our privacy policy sets it out in full.

The fourth is a video player. Some help pages inside the signed-in app carry a tutorial video hosted by YouTube or Vimeo. Nothing is requested from either company when the page opens: the panel you see before you press play is drawn by us and names the company. Press play and we load that company's player, which receives your IP address and can set its own cookies. No category here changes that; the press is the choice.

One thing that is not a script belongs here too. If you read Cravora in Chinese, Japanese or Korean, your browser fetches those fonts straight from Google's font servers, so Google receives your IP address. No category here changes that either.

Your cookie choice belongs to this browser, not to your account. It is written to a cookie and nowhere else: whether you answer the banner or save the Cookies & Tracking card, nothing records the choice against your Cravora account. Another browser, another device, or a private window has its own answer, and one that has never answered is treated as refusing everything except the strictly necessary cookies.