1. Overview

This Cookie Policy explains how Licentio, operated by Zachary Cardoza doing business as Kaweah Tech ("Kaweah Tech," "we," "us," or "our"), uses cookies and similar technologies on both our web application and mobile applications. Our approach is minimal: we use only what is strictly necessary to operate the Service.

2. What Are Cookies and Similar Technologies

Cookies are small text files stored on your device by your web browser. Similar technologies include localStorage, sessionStorage, IndexedDB, and mobile SDKs that can store data on your device. These technologies serve various purposes, from remembering your login session to tracking usage patterns across websites.

3. Cookies We Use

We use a single category of cookies:

Strictly Necessary Cookies

These cookies are required for the Service to function. They cannot be disabled while still using the Service.

Cookie	Purpose	Duration	Type	Attributes
Session token	Authenticates your identity after login so you don't have to sign in on every page	If you do not select "Remember me" at login, the cookie expires when you close your browser session. If you select "Remember me," the cookie is set as a persistent cookie with a maximum lifetime of 90 days (and is refreshed on active use, subject to that 90-day ceiling).	First-party	HttpOnly, Secure, SameSite=Lax

4. Other Browser Storage

We may use localStorage for application functionality, such as storing UI preferences (for example, theme selection or sidebar state). We do not use localStorage for tracking or analytics purposes, and no personal information is stored in localStorage. We do not use sessionStorage or IndexedDB.

5. What We Do Not Use

Analytics cookies: our analytics tool (PostHog) is configured to operate in cookieless mode, which is intended to avoid setting cookies, local storage, or session storage on your device. In this mode, PostHog uses server-side mechanisms (including privacy-preserving hashing of connection metadata) to generate analytics without writing persistent identifiers to your device. Whether a specific event is fully anonymous depends on configuration choices we make, including whether we pass user identifiers through PostHog's identify() call, whether autocapture is enabled, and whether IP-based geolocation is enabled. Our standing configuration does not pass personally identifiable user IDs to PostHog, does not enable form-input autocapture, and does not enable IP geolocation. This description reflects PostHog's cookieless mode implementation and our configuration as of the effective date of this policy; we will update this policy if either changes in a way that affects your device.
Advertising or tracking cookies: we do not serve ads and do not use any advertising networks
Third-party tracking cookies: we do not allow third parties to place cookies through our Service
Social media cookies: we do not embed social media widgets that set cookies
Device fingerprinting: we do not use device fingerprinting, pixel tags, or web beacons for tracking

6. Mobile Applications

Our mobile applications (iOS and Android) integrate with the following identity and analytics capabilities:

Sign in with Apple (iOS only): we integrate with Apple's system-level Sign in with Apple capability for OAuth authentication. Sign in with Apple is provided by Apple at the operating-system level rather than as a third-party SDK we embed. It does not track users or collect advertising identifiers.
Google Sign-In SDK: used for OAuth authentication. Does not track users or collect advertising identifiers.
PostHog mobile SDK: used for product analytics, configured consistently with our web implementation as described in Section 5. We do not enable the SDK's device advertising identifier (IDFA/GAID) features, which are off by default in the SDK version we integrate; we will update this policy if we change that configuration.

Our mobile applications do not contain third-party advertising SDKs, do not collect device advertising identifiers, and do not participate in cross-app tracking. Because our standing data practices do not meet Apple's definition of "tracking" under its App Store guidance (which requires, among other things, linking user or device data collected in our app with third-party data for advertising or data-broker purposes), the Service does not trigger an App Tracking Transparency prompt. If our practices change, we will update this policy and implement the prompt before any tracking activity begins.

Because we only use strictly necessary cookies (required for authentication), we are not required to obtain consent under the ePrivacy Directive or the CCPA. Strictly necessary cookies are exempt from consent requirements.

If our cookie usage changes in the future (for example, if we add non-essential cookies), we will update this policy and implement a consent mechanism before setting those cookies.

8. Managing Cookies

You can manage or delete cookies through your browser settings. Note that if you block or delete the session cookie, you will need to log in again each time you visit the Service.

Instructions for common browsers:

Chrome: Settings > Privacy and Security > Cookies and other site data
Firefox: Settings > Privacy & Security > Cookies and Site Data
Safari: Preferences > Privacy > Manage Website Data
Edge: Settings > Cookies and site permissions

9. Changes to This Policy

We will update this Cookie Policy if we change our cookie or similar technology practices. Material changes will be communicated through the Service or by email.

This Cookie Policy is part of Licentio's legal framework. Please also review our Terms of Service, Privacy Policy, and Data Retention Policy.

11. Contact

For questions about this Cookie Policy, contact us at:

Inquiry Type	Contact
Privacy and cookie questions	legal@licent.io
General support	support@licent.io
Security concerns	security@licent.io