Cookie Policy

What Cookies and Local Storage Are

Cookies and local storage are both small pieces of data that a website asks your browser to keep. They are not the same thing, and the difference matters for what happens to the data afterwards.

Cookie A small file your browser stores and then attaches to every later request to the site that set it. Because it travels with the request, a cookie reaches a server.

Local storage A store that stays inside your browser. Nothing is attached to a request, so a value written to local storage is not a cookie and never leaves your device unless a script deliberately sends it. We do not send ours.

Some of this storage is needed for the site to behave the way you asked it to. The rest is optional, and we ask before we use it.

What This Site Stores

This is the complete list. There are three items, one of which is not a cookie.

The second Analytics cookie carries our measurement identifier in its name, so on this site it reads as _ga_ followed by that identifier. It is written by the Google Analytics tag rather than by our configuration, which is why the lifetime above is attributed to the tag rather than claimed as ours. If Google changes it, we update this page.

Analytics is not switched on yet. Until we enable it, the two Google Analytics cookies above are never set at all, whatever you choose in the banner. The table describes what happens once analytics is enabled and you have accepted it.

Our contact page embeds Cal.com so you can book a call. We did not see Cal.com set any cookie on the domain of this site, so there is no row for it above. Opening the scheduler loads Cal.com, and Cal.com may set its own cookies under its own domain and its own policy, which you can read at cal.com/privacy. If you would rather not load it at all, email us instead at hello@forma.marketing.

When you choose to pay an invoice by card, we redirect you to checkout.stripe.com. Stripe sets cookies on its own domain while you are there, under its own policy, which you can read at stripe.com/cookies-policy. We do not load Stripe on forma.marketing itself, so there is no row for Stripe in the table above. If you would rather not be redirected to Stripe at all, ask to pay by bank transfer instead and we will send the details.

One thing that is not storage but is worth stating plainly here: this site loads its typefaces from Google Fonts, and that happens on every page load, before and regardless of any consent choice. It sets no cookie, but your browser does contact Google to fetch the files, which means your IP address reaches Google. We intend to serve the fonts from our own server and remove that request.

We run no advertising, ad-targeting or cross-site tracking tags, so there is nothing of that kind to list. The advertising signals in the Google consent framework stay denied on this site at all times, including after you accept analytics.

How Consent Works Here

Analytics storage is denied by default. The instruction that denies it sits in the page itself, ahead of every other script, so it is in force before anything has a chance to store or read anything.

The Google Analytics tag is not requested at all until you accept. It is not loaded and then held back: the script is added to the page only once you have said yes.

If you reject, no analytics cookie is ever set and no request is made to Google Analytics. Nothing about your visit is measured, and the only thing stored is the record of your refusal, so that we stop asking.

Strictly necessary storage does not ask for consent, because it is what makes the choice you made stick. That is the one item in this category, and it holds nothing beyond your answer, the consent version and the time you answered.

What the analytics data is used for, how long it is kept, who it reaches and the legal basis we rely on are described in the Privacy Policy.

Changing or Withdrawing Your Choice

Open Cookie Settings in the site footer at any time and change your answer. Withdrawing is exactly as easy as giving consent, and it costs you nothing else on the site.

Turning analytics off updates the consent signal immediately and deletes the Analytics cookies already stored on your device.

It also reloads the page. A tag that has already loaded stays resident until the page is unloaded, and while it is resident it can keep sending requests even with storage denied. Reloading is what actually stops it, so withdrawal is real rather than cosmetic.

If you have the site open in more than one tab, withdrawing in one takes effect in the others as well.

Withdrawing does not undo measurement that already happened while your consent was in place. It stops everything from that point on.

Controls in Your Own Browser

Independently of anything on this site, your browser can block cookies, delete the ones already stored, or clear site data for a single site. Those settings live under privacy or site data in the preferences of your own browser, and they override whatever you told us.

One consequence is worth knowing about. Clearing or blocking storage for this site also removes the record of your consent choice, because that record is kept in your browser rather than in an account on our servers. When it is gone, we no longer know what you decided, so the banner asks again on your next visit.

A browser that blocks storage entirely is treated as undecided, which means analytics stays off. Nothing on this site breaks if you block it.

Changes to This Policy

The version number and effective date at the top of this page always identify the current version.

If we add or remove a cookie, or change what one is for, we update this page. Where the new use requires consent, we ask for it again rather than carrying over the answer you gave to an earlier version.

Questions about anything on this page go to privacy@forma.marketing.