Content Stage

Cookie Policy

Last updated August 29, 2026 Effective from August 29, 2026

Last updated August 29, 2026. This is version 1 of this policy.

This policy explains what Content Stage stores on your device when you use www.contentstage.de or our platform, why we store it, and how you can change what you allow. It is published by Goodbrands Love GmbH, Stegner Strasse 2a, 79199 Kirchzarten, Germany — who decide how and why that information is processed.

Cookies, and everything like them

A cookie is a small file a website asks your browser to keep. Browsers offer other ways to store information too — localStorage among them — and the rules that apply to cookies apply equally to those. This policy therefore covers everything we store on your device, whichever mechanism is used. The table further down lists each item individually, including which mechanism it uses.

The two kinds of storage we use

Necessary storage is what the platform cannot work without: keeping you signed in, protecting forms against cross-site request forgery, holding a campaign you are part-way through creating so a reload does not lose it, and remembering the cookie choice you make below. We do not ask permission for these, because without them the service you asked for would not function. This is permitted under Section 25(2) of the German Telecommunications Digital Services Data Protection Act (TDDDG) and the equivalent provisions of the ePrivacy Directive.

Analytics storage is optional and we ask before using it. Today it is a single item, cs_utk: a random identifier that lets us recognise a returning visit as the same visit, so we can tell which channels bring people who go on to create an account. It contains no name, no email address and nothing about you personally — only a random string. We rely on your consent for this, under Article 6(1)(a) of the GDPR, and you can withdraw it at any time.

What we do without asking, and why it is not storage

Every website receives certain information simply because your browser sends it with each request: the page you asked for, the site that linked you to us, and your IP address. We record this to understand how people find us, and we convert the IP address into a country and then keep the reference rather than the address itself. None of this involves storing anything on your device, so it is not governed by the rules above — it is ordinary processing of personal data, carried out on the basis of our legitimate interest in understanding how our own service is found and used (Article 6(1)(f) GDPR). If you would prefer we did not, you can object using the contact details below.

We use no third-party cookies

This is worth stating plainly, because it is unusual. Content Stage sets no advertising cookies, embeds no tracking pixels, and runs no third-party analytics product. Nothing described in this policy is shared with anyone, sold, or used to build a profile of you across other websites. Every item in the table below is set by us, read only by us, and used only for the purpose stated beside it.

Your choice, and how to change it

The first time you visit, we ask whether you accept analytics storage. Declining is a single click and costs you nothing — the platform works identically either way, and we will not ask again.

You can change your answer whenever you like using the Change your cookie choice button on this page. That button asks you again; the identifier is removed from your device as soon as you confirm the new choice. Withdrawing does not affect anything that happened while your consent was valid.

You can also control storage through your browser, which lets you delete what is already stored and refuse anything new. Bear in mind that blocking necessary storage will stop you being able to sign in.

How long things are kept

Each item's lifetime is listed in the table below. Session storage disappears when you close your browser. The consent record and the analytics identifier both last twelve months, after which you will be asked again.

We also keep a record of the choice you made, when you made it, and which version of this policy was current at the time. We are required to be able to demonstrate that consent was given, and that record is how we do it.

Changes to this policy

This policy is versioned. When it changes materially we publish a new version, and the previous one remains available at the foot of this page so you can see what changed. If we ever add something that requires your consent, your existing choice stops applying to it and we will ask you again rather than assume.

Contact

Questions about this policy, or about any of the data described in it, can go to support@contentstage.de. You also have the right to complain to a data protection authority; for us that is the data protection authority of the German state in which we are established (Kirchzarten, Germany).

What we store on your device

NameStored asPurposeKept forNeeds consent
PHPSESSID cookie Keeps you signed in and protects forms against cross-site request forgery. Until the browser is closed No — required for the service
cs_consent cookie Remembers your cookie choice so you are not asked again. 12 months No — required for the service
campaignState localStorage Keeps a campaign you are part-way through creating, so a reload does not lose it. Until the campaign is saved or you clear it No — required for the service
queued_notification localStorage Carries a confirmation message across a page reload. Until shown, moments later No — required for the service
queued_modal localStorage Reopens a dialog after a page reload. Until shown, moments later No — required for the service
queued_method localStorage Resumes an action interrupted by a page reload. Until shown, moments later No — required for the service
org_tutorial_seen_type localStorage Remembers that you have already seen an introduction, so it is not shown again. Until you clear your browser storage No — required for the service
cs_utk cookie Lets us see that the same person returned, so we can tell which channels bring people who go on to sign up. First-party only — never shared. 12 months Yes