Cookie Policy
Version 1.3 · Effective 2026-09-27
This Cookie Policy explains how Smartilabs razvoj in svetovanje d.o.o. ("Closetforge", "we") uses cookies and similar technologies on the closetforge.com marketing website. For information about how we process Personal Data more generally, see our Privacy Policy at closetforge.com/privacy.
This Cookie Policy applies to the closetforge.com marketing website and to the Closetforge admin dashboard (each Customer's own /admin area, and admin.closetforge.com). The Configurator running on a Customer's own domain is governed by that Customer's cookie and privacy notice, with Closetforge acting as a processor under the DPA.
What are cookies?
Cookies are small text files that a website stores on your device. Similar technologies include local storage, session storage, pixels, and SDKs. We refer to all of them as "cookies" in this Policy for simplicity.
We use cookies to make the product work and to remember your preferences. We do not use them for advertising. One first-party local-storage entry — described below — is used to count visits to the marketing website.
Cookies we use
The closetforge.com marketing website sets no cookies at all — no HTTP cookie is written by any page on it. It does store one entry in your browser's local storage, which this Policy counts as a cookie (see the definition above), and it is the only thing it stores:
| Entry | Provider | Purpose | Retention |
|---|---|---|---|
cf_analytics_sid | Closetforge (first-party) | A randomly generated identifier with no personal data in it, used only to count a visit as one visit rather than as a series of unrelated page views | Rotates after 30 minutes of inactivity, and in every case after 12 hours |
What that entry is, precisely, because the distinction is the whole basis of the position below: it is first-party (readable only by closetforge.com, never sent as a request header and never shared with another site), random and non-identifying (it contains no name, no email, no account and no device fingerprint, and we do not join it to anything that would identify you), short-lived (it rotates on its own; it cannot follow you from one week to the next), and never used for advertising or profiling. If your browser blocks local storage, the site works exactly as it does otherwise.
The admin dashboard — where a Customer's staff sign in — sets only strictly necessary cookies:
| Cookie | Provider | Purpose | Retention |
|---|---|---|---|
authjs.* | Closetforge (first-party) | Sign-in session and cross-site request forgery protection. Set only after you sign in. | Session / until sign-out |
locale | Closetforge (first-party) | Your explicit choice in the language switcher | 12 months |
tenant_locale | Closetforge (first-party) | The default language configured for that workspace | 12 months |
admin_locale | Closetforge (first-party) | The language of the admin interface, which an administrator may set independently of the customer-facing language | 12 months |
omara_browser_id | Closetforge (first-party) | An anonymous browser marker that lets an unsigned-in visitor return to a design they saved without creating an account | 12 months |
Legal basis: necessity for the service you have requested. None of these cookies profile you or follow you across websites.
Analytics
We measure audience, and cf_analytics_sid above is how. We count page views, how far down a
page people read, and which buttons are pressed, so that we can tell which parts of our own site
are useful. That is the entire purpose. We run no session recording, no cross-site
tracking, no advertising or remarketing, and we do not build a profile of you — the
identifier exists so that one visit is counted once, and it is thrown away and replaced on its
own schedule.
We honour Do Not Track as a hard opt-out: with DNT on, nothing is sent and nothing is measured. Product usage inside the Configurator is measured server-side, without cookies, for the Customer whose data it is. Any measurement tool we introduce that reaches further than the above — anything identifying, cross-site, or shared with an advertising network — is covered by the Updates section: we ask for consent before setting it.
Advertising
We set no advertising cookies on closetforge.com or in the admin dashboard. We are not running LinkedIn or Meta campaigns, and no pixel from either is loaded. If that changes, this Policy is updated and consent is requested before any such cookie is set.
On a Customer's Configurator — the consent banner and the Customer's own tags
This Policy's scope paragraph applies: the Configurator on a Customer's own domain is governed by that Customer's notice, with Closetforge as its processor. What the platform does there is this:
- If the Customer has enabled Google Ads conversion measurement or Google Analytics 4 in its Closetforge settings, the Configurator shows a consent banner at the bottom of the page with two equally prominent choices, Accept all and Reject, and per-category settings that are never pre-ticked. Nothing that needs consent loads before the visitor chooses, and Google's tag is loaded only for a category the visitor accepted (Google Consent Mode v2, basic mode). A Customer that has enabled neither shows no banner.
- The visitor's choice is remembered in one first-party cookie, which is strictly necessary — it exists only so the question is not asked on every page:
| Cookie | Provider | Purpose | Retention |
|---|---|---|---|
cf_consent | Closetforge (first-party, for the Customer) | Which categories the visitor accepted, and when. Set only when the visitor makes a choice in the banner; carries no identifier | 12 months |
- If the Customer has enabled Google Ads and the visitor accepted Advertising, Google's tag measures whether an ad led to a confirmed enquiry, and Google sets:
| Cookie | Provider | Purpose | Retention |
|---|---|---|---|
_gcl_au | Google Ireland Limited | Links a visit to an ad click for conversion measurement | 90 days |
_gcl_aw | Google Ireland Limited | The ad click the visitor arrived from | 90 days |
- If the Customer has enabled Google Analytics 4 and the visitor accepted Analytics:
| Cookie | Provider | Purpose | Retention |
|---|---|---|---|
_ga | Google Ireland Limited | Distinguishes visitors for audience measurement | 13 months (set below Google's two-year default) |
_ga_<ID> | Google Ireland Limited | Keeps session state for audience measurement | 13 months |
Personalised advertising and remarketing are never enabled by the platform. Google may transfer data to Google LLC in the United States under the EU–US Data Privacy Framework. The visitor can change or withdraw the choice at any time through Cookie settings in the site footer or on the Customer's cookie policy page, as easily as it was given, without reloading the page.
How to manage cookies
No banner. Apart from the audience-measurement identifier described above, only strictly necessary cookies are set. We do not show a consent banner, on the basis that the one non-essential entry is first-party, contains no personal data, rotates on its own, is used solely to count visits to our own site, and is never used for advertising, profiling or cross-site tracking. If you would rather it were not stored at all, turn on Do Not Track, block local storage for this site, or clear it — each works, and none of them breaks the site.
Through your browser. Most browsers let you block or delete cookies and local storage. Doing so will sign you out of the admin dashboard and may break parts of it. See your browser's help pages.
Global Privacy Control. We set no advertising cookies and we sell no personal data, so there is no sale or sharing for a GPC signal to refuse. We honour Do Not Track, which stops the audience measurement described above outright.
Third parties
None of the cookies on closetforge.com or in the admin dashboard is a third-party cookie — all of them are set by Closetforge itself. The only third party that can set cookies through the platform is Google, on a Customer's own Configurator, and only when that Customer enabled its tag and the visitor accepted it (see above). The vendors Closetforge relies on to run the Service are listed at closetforge.com/legal/subprocessors.
Updates
We update this Policy when we add, remove, or change cookies. The version number and effective date at the top reflect the current version. If we ever introduce a cookie that requires consent, we will ask for it before setting the cookie.
Contact
Email privacy@closetforge.com for any cookie-related questions.