Cookie Policy
Last updated 1 October 2026
litesuite.dev sets three strictly necessary cookies and nothing else. The website loads no optional analytics scripts, advertising pixels, session recording, or third-party trackers. Desktop launch counting is separate and is described below. We do not sell or share personal information.
What we set
| Name | Purpose | Retention | Provider |
|---|---|---|---|
__Secure-ls_session | Keeps you signed in. A signed token that carries your account identity — no server-side session store. | Expires when the signed token expires, or immediately on sign-out. | litesuite.dev (first-party) |
__pkce | Holds the one-time PKCE verifier during Google sign-in. Without it the sign-in handshake cannot be completed securely. | Minutes — deleted as soon as sign-in finishes. | litesuite.dev (first-party) |
litesuite:cookie-consent | Remembers your choice on this banner. Stored in your browser's local storage, not as a cookie. | Until you clear site data or change your preferences. | litesuite.dev (first-party, local storage) |
Why you still see a banner
Strictly necessary cookies do not require consent under the GDPR or the ePrivacy Directive, and we could lawfully set them with no banner at all. The banner exists to disclose them plainly, to satisfy the CCPA/CPRA notice-at-collection requirement, and to hold your choice about optional analytics in advance of us ever adding any.
Optional analytics
The website analytics switch controls optional browser analytics scripts. None are loaded today, regardless of the switch. If we add them, only visitors who turn the switch on will have them run. This switch does not control desktop launch counting.
Desktop launch counting
The desktop app always sends a best-effort launch observation. Before sign-in, it sends only a hashed random install identifier and a random launch identifier, not your email, hardware identifier, or the install secret. Our servers still receive normal network metadata for security and rate limiting. Unclaimed launch rows are deleted after 90 days.
The app proves possession of its install secret over HTTPS. Launches counted before sign-in are attached to the account whose sign-in is first to complete successful launch reporting. This is best-effort: a sign-in that fails to report does not count. Later launches are linked to the account signed in at that time. Launches already counted for one account never move to another account. Linked launch records are retained to prevent duplicate counting; these are best-effort counts, not exact usage records.
There is no opt-out for desktop launch counting. Cookie preferences, the website analytics switch, and browser Global Privacy Control do not govern it. Desktop launch counting does not use website cookies.
Global Privacy Control
If your browser sends a Global Privacy Control signal we treat it as an opt-out from optional cookies, we record that opt-out, and we do not show you the banner. A browser that has already answered should not be asked again.
Changing your mind
Your choice is stored in your browser's local storage, not in a cookie, so asking you about cookies does not itself set one. You can change it at any time:
Clearing your site data also clears the choice, and you will be asked again on your next visit.
Questions
Email ryan@litesuite.dev.