Cookie Policy
Draft for legal review. Update this Policy and the consent interface whenever analytics, advertising, authentication, payment, or support vendors change their browser storage technologies.
1. Scope
This Policy explains how [Pijon legal entity] uses cookies, local storage, pixels, SDK storage, and similar technologies on the public website and authenticated studio services. It should be read with the Privacy Policy.
2. What these technologies are
Cookies are small text files stored by a browser. Local storage keeps information within the browser without necessarily sending it with each request. Similar technologies can include pixels, software-development-kit storage, device identifiers, and scripts that read information from a user’s device. Belgian and EU rules may apply to all of these technologies, not only traditional cookies.
3. Current public-site use
The current public Pijon site stores the user’s selected light or dark theme in local storage under pijon-theme. This preference is functional, remains on the device until cleared, and is not used for advertising or cross-site tracking.
The current static public site does not intentionally set advertising cookies or non-essential analytics cookies. If analytics or other optional technologies are introduced, they must remain disabled until the user provides valid consent where required.
4. Categories we may use
| Category | Purpose | Consent | Typical duration |
|---|---|---|---|
| Strictly necessary | Authentication, security, load balancing, fraud prevention, and checkout continuity | Not optional where required to provide the requested service | Session to [12 months] |
| Functional | Theme, language, accessibility, and interface choices | Depends on necessity and local law | Up to [12 months] |
| Analytics | Aggregated traffic, reliability, and product-usage measurement | Consent before placement where required | Up to [13 months] |
| Support and communications | Remember support sessions or communication preferences | Consent unless strictly requested or necessary | Provider dependent |
| Advertising | Cross-site advertising or behavioural profiling | Prior consent | Not currently planned |
5. Expected authenticated-service technologies
Before the studio console launches, the production inventory should identify each technology by name, provider, domain, purpose, category, data collected, legal basis, and expiry. Expected strictly necessary items may include:
- a secure session cookie marked
Secure,HttpOnly, and an appropriateSameSitevalue; - a CSRF or request-integrity token;
- load-balancing and abuse-prevention identifiers;
- a short-lived checkout or subscription-state token; and
- consent-choice storage where optional technologies are offered.
6. Consent and choices
Where consent is required, Pijon will provide a clear choice before optional technologies are used. Accept and reject controls should be equally accessible, optional categories should be off by default, and consent should be specific, informed, freely given, and withdrawable as easily as it was given.
Withdrawing consent does not affect processing that occurred lawfully before withdrawal. Necessary technologies cannot be disabled through the consent tool where they are required to provide a service explicitly requested by the user.
7. Browser and device controls
Users can clear or block cookies and site data through browser settings. Doing so may sign the user out, reset theme or language choices, or prevent authenticated features from operating. Browser “do not track” signals do not have a uniform legal or technical standard; Pijon will honour legally recognised preference signals where required.
8. Third parties
Payment, authentication, hosting, support, or analytics providers may place technologies when their services are used. The final production inventory and consent manager must name those providers and link to relevant notices. Pijon will contractually limit providers to agreed purposes and will not permit non-essential third-party tracking before required consent.
9. Updates
We may update this Policy when technologies, vendors, or law changes. Material changes will be reflected in the effective date and, where appropriate, through a renewed consent request.
10. Contact
Questions may be sent to privacy@pijon.example or [postal address].