LEGAL BLOCK · Effective Date: 2026-04-20 · Last Updated: 2026-04-20 · LEGAL BLOCK
← HOME
COOKIE // CONTROL

COOKIE POLICY

Effective Date: 2026-04-20Last Updated: 2026-04-20GDPR // KVKK

Websites use cookies to store data about you. We are stingy with them; we load as few as possible. No third-party analytics, ad tags, social pixels or behavioral trackers are in use. The full list is below.

§01

1. What is a Cookie?

A cookie is a small text file a website places on your browser. Cookies are used for session memory, saving preferences, security and analytics.

Cookies are classified by duration as "session cookies" (deleted when the browser closes) or "persistent cookies" (kept until an expiration date), and by purpose as "strictly necessary", "functional", "analytics" and "marketing".

§02

2. Why We Use Cookies

We currently use two functional (preference) cookies: pg.lang (remembers language preference) and pg.theme (remembers theme preference). Both are for personalization and do not authenticate or track you.

Once Wave 2 ships accounts, we will add a "strictly necessary" Firebase Auth session cookie. Without it you cannot sign in or access the dashboard; for that reason it is loaded without consent, in accordance with KVKK and the ePrivacy Directive (2002/58) strictly-necessary exemption.

§03

3. Third-Party Cookies

We do not currently use third-party cookies, analytics cookies or advertising cookies. Google Analytics, Meta Pixel, TikTok Pixel, Hotjar, Cloudflare bot management and similar trackers are not installed.

If we later introduce an analytics tool (for example, a privacy-friendly option such as Plausible), this policy will be updated and a consent panel (cookie banner) will be introduced where required.

§04

4. Cookie Banner Status

Because only preference and strictly necessary cookies are used, we do not show a pop-up "Accept Cookies" banner. This approach is defensible under KVKK Art. 5/2(f) (legitimate interest in operating the service) and the "strictly necessary" carve-out in the ePrivacy Directive.

When analytics or marketing cookies are added, we will display a clear, separable, easily withdrawable consent panel, where rejection is as visible as acceptance.

§05

5. How to Manage Cookies

You can reject all cookies or delete them selectively from your browser settings. Chrome, Firefox, Safari, Edge and Brave all offer per-site cookie control. Rejecting pg.lang or pg.theme means your language and theme preferences will not be remembered.

Once your account is active you can also delete the Firebase Auth session cookie; this will sign you out, and you'll need to sign in again.

// INVENTORY

Active Cookie Inventory

CookiePurposeDurationCategory
pg.langRemembers language preference (tr / en)1 yearFunctional
pg.themeRemembers theme preference (dark / light / acid)1 yearFunctional
__session (planned)Firebase Auth session token — once accounts go live14 daysStrictly Necessary
CONTACT

To exercise your rights, ask a question, or report an incident, reach us through the channels below. Our response window is 30 days at most (KVKK Art. 13 and GDPR Art. 12).

DATA CONTROLLER
Pixelgang Collective (an informal collective — no registered legal entity at this time).
EMAIL
[email protected]
POSTAL ADDRESS
{{ADDRESS_PLACEHOLDER}}
// LEGAL BLOCK
TERMS OF SERVICEPRIVACY POLICYCOOKIE POLICYCODE OF CONDUCTCOMMUNITY RULESREFUND POLICY