VulCode

Cookie Policy

Last updated: 24 October 2026

1.

What this document covers

1.1

This Cookie Policy describes what information vulcode.com stores in your browser, for what purpose, and how you can delete it.

1.2

It supplements the Privacy Policy, which describes how VulCode ("VulCode", "we", "us") processes personal data.

1.3

The vulcode.com website itself does not set any cookies. It uses browser storage (localStorage and sessionStorage), and counts visit statistics on the server without storing anything in the browser (point 3.3). The client panel, which runs at vulcode.com/panel, keeps what it needs for signing in and its settings in browser storage, and sets one cookie for members of the VulCode team once they open an administration session. All of this is first-party data: only VulCode stores and reads it. We use no advertising cookies and no third-party tracking tools. Because browser storage works similarly to cookies and is subject to similar rules, we describe it here in the same way.

2.

What cookies and similar technologies are

2.1

Cookies are small text files stored by a website on the user's device and sent back to the server with subsequent requests.

2.2

localStorage is browser storage bound to a specific domain. Data stored there remains on the device until removed by the user or by the website. It is not automatically sent to the server with every request.

2.3

sessionStorage works the same way as localStorage, except that the stored data is removed when the browser tab is closed.

2.4

First-party technologies are data stored by vulcode.com itself, including the client panel at vulcode.com/panel. Third-party technologies are data stored by external providers whose resources are embedded on the site - their scope is described in section 6.

2.5

The service worker cache (Cache Storage) holds copies of the site's files that the browser keeps on the device, so the site also opens without an internet connection. It holds no data about you, only files downloaded from vulcode.com.

3.

Categories used

3.1

Strictly necessary - required for core functions of the site, including signing in to the client panel and the admin panel. Without them the site cannot work correctly.

3.2

Functional - remember settings and data that improve the experience, such as the recently visited pages in the footer or the menu groups you collapsed in the client panel.

3.3

Analytics - allow us to count visits and understand how the site is used. Analytics neither stores anything in your browser nor reads anything from it: we count a visit on our server, and its identifier is a hash of your IP address and browser type with a random value that changes every day and is never stored. The hash cannot be reversed, and the next day it no longer matches the same person. We use our own analytics system only; we do not share this data with external analytics providers.

3.4

Marketing - in our case limited solely to remembering a referral code if you arrived through a referral link. We do not use advertising technologies, ad networks, remarketing or user profiling for marketing purposes.

4.

What exactly we use

4.1

The tables below are the complete list of data stored in the browser by the vulcode.com website and by the client panel at vulcode.com/panel. A name in angle brackets marks the part that changes with each entry, such as the address of an article.

The vulcode.com website

The client panel (vulcode.com/panel)

4.2

Apart from the items listed in the tables, the website and the client panel store no other data in the browser. The website sets no cookies, and the client panel sets only the vc_admin cookie, and only for members of the VulCode team.

5.

Legal basis

5.1

The table below indicates the basis for processing personal data associated with each category:

5.2

Storing information on, and accessing information stored in, the user's terminal equipment is also subject - independently of the GDPR - to electronic communications law.

5.3

Analytics neither stores nor reads information on your device, so it does not require consent. If the law requires consent for particular categories, we will ask for it before storing the data and allow it to be withdrawn at any time.

6.

Third parties

6.1

Google Fonts - the typefaces used on the site are loaded from Google servers (fonts.googleapis.com, fonts.gstatic.com). The provider does not store data in your browser under our domain on that account, but loading the files does disclose your IP address and browser information to it.

6.2

flagcdn.com - the flag icons in the language switcher are loaded from an external image service. This concerns only the download of the image file, which discloses the IP address and browser information.

6.3

Embedded portfolio previews - on pages presenting completed projects we embed a live preview of the site in a frame. The embedded site may store its own cookies and data in the browser in accordance with its owner's policy. This applies only to portfolio pages containing such a preview.

6.4

Links to external services (including social media and Discord) do not cause any data to be stored until they are clicked. Once you move to an external service, its own rules apply.

6.5

We do not use third-party analytics, advertising or tracking tools, in particular: Google Analytics, Google Tag Manager, Meta Pixel, TikTok Pixel, LinkedIn Insight Tag, Hotjar, Microsoft Clarity, Matomo, Plausible, or remarketing-type advertising systems.

7.

How to delete stored data and withdraw consent

7.1

You can delete all data stored by the site in your browser at any time using your browser settings - usually under privacy, site data or clearing browsing data. Clearing site data covers cookies, browser storage and the cache alike.

7.2

You can also use the site in private (incognito) mode - data stored in such a session is removed when the window is closed.

7.3

Deleting the data does not restrict access to the site. The effect is that the privacy notice is shown again and you are signed out of the client panel and the admin panel if you were signed in.

7.4

If you wish to object to analytics based on our legitimate interest or request deletion of data concerning you, write to hello@vulcode.com. Your remaining rights are described in the Privacy Policy.

8.

Storage period

8.1

The storage period in the browser is indicated in the tables in section 4.

8.2

The retention period for analytics data on the server side is described in the Privacy Policy.

9.

Changes to this Cookie Policy

9.1

We update this Policy when the technologies we use or the applicable rules change. We announce changes by updating the date at the beginning of the document.

9.2

We encourage you to review this document periodically.

10.

Contact

VulCode E-mail: hello@vulcode.com Website: https://vulcode.com

Form protection (Cloudflare Turnstile)

Apart from the embedded previews described in section 6.3, the only third-party mechanism that may store technical data in your browser is Cloudflare Turnstile - a tool that protects the site's forms (including the contact form) against spam, provided by Cloudflare, Inc. Turnstile may store a technical token needed to verify that you are not a bot. This token is not used for tracking, advertising or profiling and is limited to handling forms. Apart from these exceptions, what sections 1.3 and 4.2 describe stands: the website sets no cookies, and the client panel sets only one, for the VulCode team alone.