Cookies Policy

Last Updated: July 7, 2026

This Cookie Policy explains how Kindilly ("Kindilly", "we", "us", or "our") uses cookies, tracking pixels, and web storage technologies on our web platform and applications.

We prioritize a technical architecture centered on data minimization. Consequently, we avoid invasive long-term tracking practices and configure cookies strictly to facilitate application security, core functionality, and stable user experiences.

1. Understanding Browser-Side Storage Controls

1.1 Traditional Cookies

Cookies are minute text-based data packages deployed to your client device's browser by a web host. They read states, security states, and layout settings during subsequent visits.

1.2 Modern Alternatives Disclaimer

Kindilly does not deploy, utilize, or access localStorage or sessionStorage arrays for any sensitive, user-identifiable, or tracking purposes. All client state management is handled through secure server-side session tokens and localized functional cookies.

2. Cookie Classification Framework

We organize our cookies into clear functional categories, allowing users to easily understand their operational intent and technical requirements.

A. Strictly Necessary Cookies (Essential Frameworks)

These elements are required for the essential technical operation of Kindilly. Without these configurations, basic application security, verification, and database routing are impossible.

  • Purpose: Secure user session authorization, maintaining profile routing across platform pages, and validating identity tokens during transactional API interactions.
  • Retention Period: Server-managed lifespans that automatically expire or clear upon browser tab closure or session logout events.
  • Consent Necessity: Because these cookies are strictly necessary to deliver the requested service, they do not require optional user opt-in under PIPEDA or GDPR baselines.

B. Functional Cookies (Preference Layouts)

These cookies improve the personal user experience by recording interface options you explicitly choose.

  • Purpose: Retaining specialized visual layouts (such as toggling between light and dark display modes) and keeping user preferences persistent across application re-entries.
  • Retention Period: Persistent expiration cycles designed to remain valid for up to twelve (12) months unless manually purged by the client browser maintenance tools.
  • Consent Necessity: Enabled by default to preserve selected user interface settings, but completely blockable via standard client-side browser settings.

C. Operational & Ad Management Tokens (Frequency Capping)

When ad integrations are enabled inside community frameworks, basic operational cookies monitor metrics to ensure stable layout behaviors.

  • Purpose: Capping ad impression frequencies to ensure individual users do not view repetitive or disruptive promotional banners, and validating correct layout generation.
  • Retention Period: Temporary lifespans that clear automatically within short operational windows.
  • Consent Necessity: Managed via our integrated Consent Management Platform (CMP).

3. Integrated Third-Party Technologies

Kindilly connects securely with reliable infrastructure providers via APIs (including single sign-on identity providers, file delivery networks, and payment gateways). While our custom application layer does not inject behavioral ad tracking scripts, these third-party integrations may drop technical cookies into your browser environment to secure their financial transactions, confirm identity validity, or monitor API delivery latency over HTTPS.

4. Consent Management Platforms (CMP) & Control Protocols

4.1 Banner Interaction

When first entering Kindilly from a unique browser or region, you will see our Cookie Consent Management Banner. This interface allows you to view active categories and choose whether to enable functional or non-essential categories.

4.2 Prior Consent Blocking

In compliance with GDPR and PIPEDA informed-consent guidelines, our platform blocks non-essential categories before you click "Accept."

4.3 Granular Browser Overrides

You can reconfigure your personal web browser settings (e.g., Google Chrome, Mozilla Firefox, Apple Safari) to refuse all cookies, remove cookies, or notify you when a cookie is deployed.

4.4 Operational Limitations Notice

If you fully block all cookies via your browser settings, you will disrupt our "Strictly Necessary" authentication session tokens. This will make it technically impossible to access your profile or use the Kindilly application.

5. Policy Updates

We may update this Cookie Policy from time to time to reflect changes in our technical setup or legal compliance requirements. Please review this document periodically to stay informed about how we use cookies.