Cookie Policy
Last updated: [EFFECTIVE DATE]
[PLACEHOLDER] and have qualified counsel review it before you rely on it.
The short version
Lapseguard uses exactly one cookie, and it is strictly necessary to keep you signed in. We do not use any analytics, advertising, or tracking cookies. Because the only cookie is essential to provide a service you have asked for, no consent is required to set it — so we show a brief informational notice rather than a consent banner.
The cookie we set
| Name | Purpose | Type | Expiry |
|---|---|---|---|
db_session |
Keeps you signed in after you log in. It holds an opaque session identifier — no personal data is stored in the cookie itself. | Strictly necessary (first-party) | Up to 30 days, or until you log out |
The cookie is set with the HttpOnly, Secure, and SameSite=Lax attributes, so it cannot be read by JavaScript, is only sent over HTTPS, and is protected against cross-site misuse.
What we don't use
- No analytics or performance cookies.
- No advertising or re-targeting cookies.
- No third-party tracking pixels or social-media cookies.
- No cross-site profiling of any kind.
We do use your browser's local storage to remember that you have dismissed our cookie notice, so it doesn't reappear on every page. That is stored only in your browser and is not a cookie and not sent to us.
Managing the cookie
Because db_session is essential, there is no way to use the signed-in application without it. You can clear it at any time by logging out, or by clearing cookies in your browser settings — note that doing so will sign you out and you'll need to log in again.
Changes
If we ever introduce non-essential cookies (for example, analytics), we will update this policy and ask for your consent first. See also our Privacy Policy.
Contact
Questions about cookies? Email [CONTACT EMAIL].