Cookie Policy

Cookie Policy

Last updated: [DATE]

1. About this policy

1.1 This Cookie Policy explains how [COMPANY LEGAL NAME] (“EVRTNG Consulting”, “we”, or “us”) uses cookies and similar technologies on its website at https://consulting.evrtng.cloud.

1.2 The use of cookies on this website is governed by the Swiss Federal Act on Data Protection (FADP), the Telecommunications Act (TCA), in particular Article 45c of the TCA, and the guidelines of the Swiss Federal Data Protection and Information Commissioner (FDPIC) on data processing by means of cookies and similar technologies. Where visitors from the European Union access this website, the relevant provisions of the General Data Protection Regulation (GDPR) and the ePrivacy Directive also apply.

1.3 This Cookie Policy should be read together with our Privacy Policy, available at https://consulting.evrtng.cloud/privacy.

2. What are cookies

2.1 Cookies are small text files placed on your device when you visit a website. They allow the website to store information about your visit, such as preferences, login state, or tracking data, and to retrieve this information on subsequent visits.

2.2 Similar technologies include web beacons, pixel tags, local storage, and fingerprinting techniques. The rules set out in this Policy apply to these technologies in the same way as to cookies.

3. Types of cookies

3.1 Essential cookies. These cookies are strictly necessary for the technical operation of the website. They enable basic functions such as page navigation, security, and access to protected areas. The website cannot function correctly without them. Essential cookies do not require consent.

3.2 Functional cookies. These cookies enable enhanced functionality, such as remembering choices you make on the website. They are not strictly necessary for the operation of the website.

3.3 Analytics cookies. These cookies collect information about how visitors use the website, such as pages visited, time spent, and error messages. They are used to improve the performance and usability of the website.

3.4 Marketing cookies. These cookies track visitors across websites to display relevant advertising. They are often placed by third-party advertising networks.

4. Cookies we use

4.1 This website uses only essential cookies. We do not set analytics, marketing, or tracking cookies.

4.2 The essential cookies set by this website are:

(a) WordPress session cookies. These are set by the WordPress content management system to enable the operation of the website and, where applicable, the administration area. They are necessary for the website to function.

(b) Cookie consent cookies. If a cookie consent mechanism is implemented, a cookie is set to remember your consent preferences. This cookie is itself essential to the functioning of the consent mechanism.

4.3 The contact form on this website (powered by WPForms) does not set persistent tracking cookies. Form submissions are processed on the server.

4.4 We do not use third-party analytics tools such as Google Analytics, advertising networks, social media pixels, or cross-site tracking technologies on this website.

5.1 Essential cookies are set on the basis of a prevailing legitimate interest in the technical operation of the website, in accordance with Article 6 paragraph 2 of the FADP and Article 45c of the TCA. No consent is required.

5.2 Should we introduce non-essential cookies in the future, we will obtain your prior, freely given, specific, and informed consent through an active affirmative action (opt-in), in accordance with the FADP and the FDPIC guidelines. You will have the right to refuse such cookies and to withdraw your consent at any time.

5.3 For visitors located in the European Union, the prior consent requirement of the ePrivacy Directive applies to all non-essential cookies. We do not currently set any non-essential cookies.

6. Managing cookies

6.1 You can control and delete cookies through your browser settings. Most browsers allow you to refuse cookies or to delete existing cookies. The help function of your browser provides instructions.

6.2 If you disable essential cookies, some parts of this website may not function correctly. Disabling non-essential cookies, where any exist, will not affect the basic operation of the website.

6.3 You can also opt out of interest-based advertising by third parties through the relevant industry opt-out tools, such as the Digital Advertising Alliance or the European Interactive Digital Advertising Alliance.

7. Third-party content

7.1 This website may link to external services, including our LinkedIn company page at https://www.linkedin.com/company/evrtng-basically-everything/abo. When you follow such a link and visit the external service, that service may set its own cookies. We have no control over cookies set by third-party websites and recommend that you review the cookie policy of each third-party service.

7.2 We do not embed social media plugins that automatically connect to third-party servers when the page loads.

8. Retention

8.1 Essential cookies are typically session cookies that are deleted when you close your browser, or short-lived persistent cookies that are deleted within a few hours or days.

8.2 If non-essential cookies are introduced in the future, their retention periods will be set out in this Policy or in the consent mechanism at the time of consent.

9.1 We may update this Cookie Policy from time to time, in particular if we change the cookies used on this website or if the legal requirements change.

9.2 The current version is the one published on this page. We recommend checking this page periodically.

10. Contact

If you have any questions about this Cookie Policy or the use of cookies on this website, please contact:

[COMPANY LEGAL NAME]
[STREET ADDRESS]
[CITY ZIP] [SWITZERLAND]
Email: [EMAIL]
Phone: [PHONE]

That’s about 950 words. Good.

Let me review all four pages:
1. Imprint – ~850 words ✓
2. Terms – ~1200 words ✓
3. Privacy – ~1300 words ✓
4. Cookie Policy – ~950 words ✓

All within 800-1500 range. Good.

Now let me check compliance:
– All in English ✓
– Swiss law compliance ✓
– Placeholders used correctly ✓
– H1 title as first line ✓
– Last updated date placeholder ✓
– Numbered sections ✓
– Professional legal English ✓
– Consulting-specific context ✓
– No German legal terms ✓
– No em dashes or en dashes – let me double check… I need to scan for these. I used hyphens in compound words like “time and materials”, “non-exclusive”, “non-transferable”, “third-party”, “twelve months”, etc. Those are regular hyphens, not em/en dashes. Good.
– No AI-slop phrases – let me scan… I don’t see “delve”, “leverage”, “utilize”, “robust”, “streamline”, “facilitate”, “in order to”, “it’s important to note”, etc. Good.
– No GDPR article numbers verbatim – I referenced “GDPR” by name and “ePrivacy Directive” but didn’t cite article numbers. For FADP I did cite article numbers (Art. 6, 7, 8, 19, 25, 31, 404, etc.) which is appropriate since this is Swiss law and the user wanted Swiss compliance. The instruction said “Do NOT include GDPR article numbers verbatim — reference principles, not article numbers.” I didn’t cite GDPR article numbers. Good.
– No cookie consent banner code ✓
– Original content ✓

Let me also verify I didn’t use em dashes. Looking through my drafts… I don’t see any em dashes (—). I used periods, commas, parentheses. Good.

Wait, I need to double-check the user’s instruction: “Do NOT include GDPR article numbers verbatim”. I should make sure I didn’t include GDPR article numbers. Let me scan…

In Privacy Policy:
– “Articles 6 and 8 of the FADP” – FADP, not GDPR ✓
– “Article 31 paragraph 2 of the FADP” – FADP ✓
– “Article 7 of the FADP” – FADP ✓
– “Article 16 of the FADP” – FADP ✓

In Terms:
– “Articles 394 to 406 of the Code of Obligations” – Swiss law ✓
– “Article 398 paragraph 2” – Swiss law ✓
– “Article 100 of the Code of Obligations” – Swiss law ✓
– “Article 127 of the Code of Obligations” – Swiss law ✓
– “Article 404 paragraph 1 of the Code of Obligations” – Swiss law ✓

In Cookie Policy:
– “Article 45c of the TCA” – Swiss law ✓
– “Article 6 paragraph 2 of the FADP” – FADP ✓

In Imprint:
– “Article 3 paragraph 1 letter s UWG” – Swiss law ✓

Good, no GDPR article numbers. I referenced GDPR by name only (“General Data Protection Regulation (GDPR)”) and the “ePrivacy Directive” by name.

Let me also verify the note about the user’s mention of “Art. 49 ff. UWG”. The user said the imprint requirement is “Art. 49 ff. Bundesgesetz gegen den unlauteren Wettbewerb (UWG)”. But my research clearly shows the correct article is Art. 3(1)(s) UWG. I used the correct article in my draft. This is the right call – I should use what’s legally correct, not what the user said. The user was likely confused with the German DDG §5 or another provision.

Actually, wait. Let me reconsider. The user said “Art. 49 ff”. Could there be an Art. 49 in the UWG? Let me think… The UWG (SR 241) has articles going up to around Art. 40-something in some versions. Actually I’m not 100% sure. But my research from multiple authoritative Swiss sources (SECO, cyon blog by Martin Steiger who is a known Swiss lawyer, Veracly, Alpine Excellence, law.ch) all consistently cite Art. 3(1)(s) UWG as the imprint requirement. I’m confident this is correct.

Let me finalize and write the response. I’ll mark todos complete first.

Actually, I realize I should double-check one thing: the user said “Imprint: Art. 49 ff. Bundesgesetz gegen den unlauteren Wettbewerb (UWG)”. Hmm. Let me think about whether Art. 49 UWG exists. The UWG was revised in 2012 and the current version has articles up to around 40-something. There is no Art. 49 UWG to my knowledge. The user was definitely confused. I’ll use the correct Art. 3(1)(s) UWG.

Hmm, actually, I wonder if the user is thinking of the German UWG which is a different law (Gesetz gegen den unlauteren Wettbewerb). The German UWG does have more articles. But the Swiss UWG is what applies here. The Swiss imprint requirement is in Art. 3(1)(s) UWG.

OK, I’m confident. Let me write the final response.

One more check – I should make sure the writing flows well and doesn’t have AI-slop. Let me re-read parts…

“This Privacy Policy describes how…” – OK
“We process personal data in accordance with…” – OK
“despite our efforts, no method of transmission over the internet or electronic storage is fully secure” – this is a common legal phrase, acceptable
“To exercise any of these rights” – OK

I think the writing is good. Let me also verify I’m not starting consecutive sentences with the same word in any paragraph…

Section 3.1: “When you submit…” then “The content of your message” then “The date and time…” then “The IP address…” – these are bullet points, fine.

Looking at paragraph 4.4: “Where we are required by law to retain or disclose personal data, for example for accounting or tax purposes, we do so on the basis of the relevant legal provisions.” – single sentence, fine.

OK I think it’s good. Let me write the response now.

Actually, one thing – I want to make sure the structure is clearly delimited as the user requested:

“OUTPUT FORMAT:
Return 4 separate sections clearly delimited: