# STATIX — Cookie Policy > **DRAFT — NOT YET LEGALLY REVIEWED.** Professional drafting to be reviewed by a > qualified attorney / data-protection adviser before publication. Not legal advice. > Confirm the actual cookies and local-storage keys set by the live website and app, > and complete all `[bracketed]` items, before publishing. **Provider:** N. de Beer, trading as [legal entity], South Africa **Contact:** [privacy@statix.app] **Version:** Draft 0.1 · **Effective date:** [to be set] This Cookie Policy explains how the STATIX website and any hosted application use cookies and similar technologies (local storage, session storage). It should be read with the **Privacy Policy**. --- ## 1. What cookies and similar technologies are A **cookie** is a small text file stored on your device by your browser. **Local storage** and **session storage** are similar browser mechanisms that store data on your device. We refer to all of these collectively as "cookies" below. Cookies can be: - **First-party** (set by us) or **third-party** (set by a provider we use); - **Session** (deleted when you close the browser) or **persistent** (kept until they expire or you delete them). --- ## 2. The offline edition stores data on your device — not on us The offline single-file STATIX application uses your browser's **local storage** to make the tool work — for example to **autosave your model, remember your settings, theme, chosen design code, and onboarding state**. This data **stays on your own device** and is **not** sent to us. It is a technical necessity of an offline tool, not tracking. You can clear it via your browser settings (note: clearing it will remove your local autosave). Examples of local-storage keys the application may use on your device include: `autosave` (your latest model), preference/theme settings, selected design code, and "tour seen" / "what's new" flags. These contain **your** data and never leave your machine through the offline app. --- ## 3. Cookies we use on the website / hosted app | Category | Purpose | Consent needed? | Examples | |---|---|---|---| | **Strictly necessary** | Security, load-balancing, sign-in/session, remembering your cookie choices, basic functionality | No (exempt) | Session/auth cookie, CSRF token, cookie-consent record, CDN/security cookies (e.g. from [Cloudflare]) | | **Preferences / functional** | Remember settings such as language, region or display preferences | Yes, where not strictly necessary | Preference cookie | | **Analytics** | Understand aggregate, privacy-respecting usage to improve the Service | Yes | [Only if/when enabled — name the tool, e.g. a privacy-first analytics provider] | | **Payment / checkout** | Operated by our payment provider / merchant of record during checkout | Necessary for the transaction you requested | [Lemon Squeezy / Paddle / Paystack] cookies on their checkout | | **Marketing** | We currently do **not** use advertising/marketing cookies. If this changes, we will update this policy and obtain consent first. | Yes | — (none at present) | > The exact cookie names, providers, durations and purposes must be confirmed against > the live site before publication and listed in a cookie table here. --- ## 4. Your choices and consent 4.1 **Strictly necessary cookies** are set without consent because the Service cannot function without them. 4.2 For **non-essential cookies** (preferences, analytics, any future marketing), we will ask for your **consent** through a cookie banner/preference centre before setting them, and you can **change or withdraw your consent at any time** via [the "Cookie settings" link in the website footer]. 4.3 **Browser controls.** You can block or delete cookies and clear local storage through your browser settings. Blocking strictly necessary cookies may break parts of the Service; clearing local storage in the offline app will delete your local autosave and settings. 4.4 Our approach is intended to meet both POPIA expectations and the consent requirements that apply to EU/UK visitors (ePrivacy/GDPR). --- ## 5. Third-party cookies Some cookies are set by providers we rely on (for example hosting/CDN/security and, during checkout, our payment providers). Their use of cookies is governed by their own privacy and cookie policies. We list our sub-processors in the Privacy Policy. --- ## 6. Changes We may update this Cookie Policy. The latest version, with its effective date, is always available from the website footer. Material changes will be notified as described in the Privacy Policy. --- ## 7. Contact Questions about cookies: [privacy@statix.app]. --- *© [2026] N. de Beer. All rights reserved.* **Reminder: this is a DRAFT for attorney review. Audit the live cookies / storage keys and complete the cookie table before publishing.**