Cookie Policy

Purpose

This Cookie Policy explains how Squillify uses cookies, local storage, session storage, software development kits, pixels, tags, and similar technologies on its website, dashboard, documentation, and related online services.

This policy should be read together with the Privacy Policy. Where cookies or similar technologies involve personal data, the Privacy Policy also applies.

What cookies and similar technologies are

Cookies are small text files stored on your device by a website or application. Similar technologies may store or access information on your device in other ways, including local storage, session storage, browser identifiers, device identifiers, embedded scripts, pixels, tags, or authentication tokens.

In this policy, "cookies" means cookies and similar technologies unless stated otherwise.

Squillify's launch position

At launch, Squillify permits only:

• cookies or similar storage strictly necessary to transmit communications or provide a service or feature the user expressly requested;
• authentication, session-integrity, CSRF, security, fraud-prevention, and tenant-access technologies used only for those purposes;
• first-party preference storage written when the user selects the corresponding interface, accessibility, or dashboard preference; and
• session-scoped idempotency values necessary to prevent duplicate money-moving or destructive commands.

Squillify does not enable advertising, behavioural profiling, cross-site tracking, or cookie-based analytics at launch. If a future technology is not strictly necessary, it must remain disabled until this policy is updated and valid prior consent is obtained where required.

Categories of cookies we may use

Strictly necessary cookies

Strictly necessary cookies are required to provide the website, dashboard, authentication, security, account access, load balancing, session integrity, fraud prevention, abuse prevention, or consent-management functionality.

These cookies are necessary for Squillify to work and cannot be disabled through the Squillify cookie preference tool. You may block them through your browser settings, but parts of the website or dashboard may not function correctly.

Examples may include cookies or storage used for:

• sign-in and session management;
• dashboard authentication;
• tenant and organization access;
• API account security;
• CSRF protection;
• abuse prevention;
• rate-limit or security checks;
• remembering cookie choices.

User-requested preference storage

Squillify uses first-party local storage to remember interface or accessibility choices that a user expressly makes, including theme, colour-vision mode, dashboard display preferences, and selected usage views. These preferences are not used for advertising, analytics, profiling, or cross-site tracking. The service remains usable with defaults if preference storage is blocked, except that the selected preference will not persist.

Cookieless website analytics

If enabled, Squillify uses Plausible Analytics to understand aggregate website usage. The approved Plausible configuration does not use cookies, local storage, browser cache, or persistent visitor identifiers. Plausible processes the page URL, referrer, IP address, and user agent to produce aggregate reports. Its published service states that raw IP addresses and full user agents are not stored, and that its daily visitor identifier cannot be linked across days.

Squillify must not send URL query strings, account identifiers, tenant identifiers, email addresses, payloads, file names, search terms, form values, or other customer-provided data to Plausible. Analytics must not determine access to the website or service.

Advertising and marketing cookies

Marketing cookies are cookies used for advertising, retargeting, cross-site tracking, behavioural profiling, or campaign attribution beyond basic operational measurement.

Squillify does not use marketing cookies at launch. If this changes, Squillify will update this policy and request valid consent before setting or reading the technology.

Authentication cookies

Access to the Squillify dashboard relies on authentication and session technologies. These technologies may be provided by Squillify or by an authentication provider acting on Squillify's behalf.

Authentication cookies are necessary to:

• sign users in;
• keep users signed in;
• protect accounts and sessions;
• enforce tenant and organization access;
• support security checks;
• prevent unauthorized account access.

If you block authentication cookies, you may not be able to access the dashboard or authenticated product features.

Local storage and session storage

Squillify may use browser local storage or session storage for necessary or functional purposes, such as maintaining session state, preserving interface preferences, supporting documentation navigation, or improving dashboard usability.

Squillify should not store API keys, secrets, raw submitted payloads, or sensitive authentication secrets in browser local storage unless expressly required, secured, and documented. API keys and credentials should be handled according to the Tenant and API Key Responsibility Policy.

Consent

Strictly necessary cookies and similar technologies do not require prior consent when they are used exclusively for transmission or to provide a service or feature expressly requested by the user. Squillify therefore does not display a consent banner merely to obtain consent for the essential technologies described in this policy.

This exception is purpose-specific and narrowly interpreted. A technology does not become essential merely because it is useful to Squillify. If any non-essential technology is introduced, Squillify must block it before use, provide clear information, obtain valid prior consent, and make refusal and withdrawal as easy as acceptance.

Blocking or deleting storage

You can block or delete cookies and similar storage through browser controls. Blocking authentication or security cookies can prevent sign-in or authenticated service use. Blocking preference storage should only reset the affected feature to its default. Plausible website analytics does not rely on browser storage.

Browser controls

You can control or delete cookies through your browser settings. Browser controls may allow you to block cookies, delete stored cookies, clear local storage, or configure tracking protections.

Blocking strictly necessary cookies may prevent Squillify from working correctly, especially for authentication, dashboard access, security, and session management.

Third-party providers

Clerk provides authentication and session technologies used for account access and security. Plausible provides cookieless aggregate website analytics if enabled. Material providers and their processing role, region, and transfer information are also listed in the Sub-processor List.

Browser technology register

Before activation, an automated production scan must replace the Clerk placeholder with the exact deployed names, domains, purposes, and lifetimes and must confirm that no undeclared storage or PostHog request occurs.

Microskill payloads and cookies

Squillify does not use cookies to store raw microskill payloads.

Cookies and similar technologies are used for website, dashboard, authentication, security, preference, analytics, or operational purposes. They are not intended to permanently store submitted microskill execution payloads.

Retention

Browser-storage lifetimes are listed above. Deleting browser storage removes first-party preferences but does not by itself delete account, security, or provider-side records governed by the Privacy Policy and Data Retention Policy. The exact Clerk session lifetime and Plausible server-side retention remain activation inputs and must be stated in the appropriate register before this draft becomes active.

Changes to this policy

Squillify may update this Cookie Policy when its website, dashboard, providers, analytics setup, authentication provider, consent mechanism, or legal obligations change.

Where required, Squillify will request consent again before using new optional cookies or materially changing the purposes of existing optional cookies.

Contact

Questions about this Cookie Policy can be sent to [email protected].

Security-related concerns can be sent to [email protected].