Cookie Policy

Cookies are small files a website asks your browser to keep. Related technologies do the same job by other means: local storage, pixels (a one-pixel image whose only purpose is to tell a company you loaded a page), and tags (a script a third party runs on our page). This policy covers all of them, and calls them all cookies for short.

This policy covers tore.ai and the Tore application. Help centers and portals we host on behalf of our customers are covered separately at the end.

What is actually running today

Right now this site loads no analytics and no advertising tags at all. Tore has not launched. The only things stored in your browser are the strictly necessary and preference items in the table below, and nothing about your visit reaches Google, Meta or LinkedIn.

We are telling you this because the rest of this page describes an advertising setup we have decided to run and have not yet turned on. We would rather publish the mechanism in advance and be held to it than describe a consent tool that is not yet doing anything and let you assume it is. The rows marked “Not yet switched on” in the table are the honest current state, and this page will be updated, with its date changed, before any of them start.

The four categories

How the consent choice works

Consent is worth nothing if it is collected by a banner that has already loaded the trackers behind it, so here is the mechanism in enough detail that you can check we are doing what we say.

Before you choose anything

Analytics and advertising start in a denied state. Our tag setup uses Google’s consent signals, and all four of them, analytics_storage, ad_storage, ad_user_data and ad_personalization, are set to denied before any tag is allowed to run. Nothing loads quietly in the background while you read the banner, and declining is not treated as “ask again on the next page.”

What you are asked

You are asked once, on your first visit, in a dialog that does not block the page. Accepting and declining are presented as equally weighted choices: declining is one click, not a hunt through a settings panel, and there is no pre-ticked box anywhere in it.

Being clear about a limitation: the current control is a single choice covering all non-essential cookies, so accepting turns on both analytics and advertising together and declining turns off both. It does not yet let you accept analytics while refusing advertising. Per-category choice is something we intend to add, and until it exists we will not describe this page as offering it. If the distinction matters to you, decline, and email us if you want a category enabled individually.

Where your choice is recorded

Your answer is stored in your browser’s local storage under the key codas_consent_v1, together with the four signals above and a timestamp of when you chose. Two consequences worth knowing: declining does not itself set a tracking cookie, and your choice never leaves your browser, so we hold no central record tying a consent decision to you personally.

Because it lives in your browser, the choice is per browser and per device. Clearing your site data, or using a different browser, means we ask again.

Changing your mind

You can withdraw consent at any time, and it must be as easy to withdraw as it was to give. A footer link that reopens the choice is not built yet. Until it is, clearing this site’s data in your browser settings removes the stored choice and we will ask again on your next visit, or you can email privacy@codaslabs.com and we will action it. That link ships before the advertising tags do, and this paragraph gets replaced when it does.

Withdrawing later does not undo the past

Turning something off stops it collecting from that point. It does not erase what was already collected while consent was in place. To have that deleted as well, ask us under the privacy policy.

Where you are changes what we do

United Kingdom, European Economic Area and Switzerland: nothing beyond the strictly necessary and preference categories is set until you say yes. No analytics, no advertising, nothing preloading while you decide. This is what the UK Privacy and Electronic Communications Regulations and the EU ePrivacy Directive require, and it is the reason a consent gate has to exist here at all.

Everywhere else, including the United States, analytics and advertising are on by default once they launch, and you turn them off rather than turning them on. Your right to opt out is set out in the next two sections.

Global Privacy Control

We treat a Global Privacy Control signal as an opt-out of both analytics and advertising for that browser, with no further action needed from you. Global Privacy Control is a setting your browser or a browser extension can send automatically, so you do not have to make the same choice on every site you visit. Several US state laws require us to honor it, and we would honor it regardless.

Where a signal reaches us, it takes precedence over an earlier “accept” on this site, and we will not ask you to confirm it or nag you to change it back.

In the interest of not describing a control we have not written yet: the automatic listener that reads this signal in the browser ships alongside the advertising tags. Since nothing is currently being collected, there is nothing for it to switch off today, and it is in place before that stops being true.

US state opt-out rights

If you live in a US state with a consumer privacy law, that law gives you the right to opt out of targeted advertising, of the sale of personal information, and of sharing for cross-context behavioral advertising. Those states currently include California, Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Delaware, Iowa, Nebraska, New Hampshire, New Jersey, Tennessee, Minnesota, Maryland, Indiana, Kentucky and Rhode Island. If your state has such a law and is not on that list, we will honor it anyway.

We do not sell personal information and never have. However, when an advertising tag lets Google, Meta or LinkedIn receive an identifier for your browser so we can show you our own ads elsewhere, several of those state laws count that as sharing for cross-context behavioral advertising and as targeted advertising. We disclose it plainly rather than argue about the definition.

You can exercise the opt-out in any of these ways:

• Send a Global Privacy Control signal from your browser.
• Decline on the consent dialog, or clear this site’s data.
• Email privacy@codaslabs.com, which works whether or not a dialog is showing.

We will not treat you differently, charge you more, or give you a worse version of the site because you opted out. You may use an authorized agent to opt out for you. If we refuse a request, you can appeal it, and the privacy policy explains how.

This section is about our marketing website only. It never applies to anything inside the product. Support conversations, bug captures and customer content are never used for advertising, never sent to an advertising provider, and never used to target anyone.

Advertising, and who gets what

Once switched on, we will run advertising tags from Google, Meta (Facebook and Instagram) and LinkedIn so we can tell which advertisements bring people here, and so we can show advertisements to people who have already visited. This is commonly called retargeting. In practice those companies set a cookie and receive a record that a browser loaded a page on this site.

These are used to advertise Tore, our own product. We do not let those providers use what they learn here to advertise anyone else’s products to you, and we do not sell your information to them.

You can also opt out directly with each provider, which works across every site rather than just this one: Google through its ads settings, Meta through its ad preferences, and LinkedIn through its advertising preferences. Your browser’s own tracking-prevention feature will block most of them too, and blocking third-party cookies entirely will block all of them.

What we set, and for how long

The analytics and advertising rows describe what will be set once those categories are switched on and you have agreed to them. They are not being set today, and the specific cookie names will be listed here before they go live. A table of vendor cookie names we have not yet deployed would be a guess rather than a disclosure.

Refusing or removing cookies

Every browser lets you block or delete cookies and clear local storage in its settings, usually under privacy or site data, and most offer tracking prevention that blocks third-party advertising cookies by default. Deleting this site’s data also deletes your consent choice, so we will ask again next time.

Blocking the strictly necessary category will stop you from signing in. That is not us being awkward: those cookies are how the site knows the request is yours.

Help centers and portals we host for customers

When one of our customers runs their help center or feedback portal on Tore, those pages use only the strictly necessary and preference categories: enough to keep a session and remember a small choice. We do not run our own analytics or advertising tags on a customer’s portal, and we do not use visitors to a customer’s help center to advertise anything, to them or to anyone else. If a customer adds their own analytics to their portal, that is their decision, disclosed under their own privacy policy, and this policy does not cover it.

Changes to this policy

We will update this page when what we set changes, and always before a new category or a new provider starts, not after. The date at the top changes with it. If a change means we need consent we do not already have, we will ask again rather than carry your old answer forward onto something you did not agree to.

More

For everything else we do with information, see the privacy policy, and for the companies involved in running Tore, the subprocessor list. Questions to privacy@codaslabs.com.