Draft — pending legal review. This document has not yet been reviewed by counsel and may change before Irisend is generally available.
Cookie Policy
Effective date: 2026-11-10
This Cookie Policy explains how Irisend ("Irisend") uses cookies and similar technologies (local storage, pixels) on irisend.com (marketing site and dashboard), and your choices.
1. What Are Cookies
Cookies are small text files placed on your device when you visit a website. Similar technologies include local/session storage and tracking pixels. We use these terms interchangeably below to mean any technology that stores or accesses information on your device.
2. Categories of Cookies We Use
| Category | Purpose | Consent required (EU/UK ePrivacy)? | Examples |
|---|---|---|---|
| Strictly necessary | Required for the site/dashboard to function: authentication/session, load balancing, security, cookie-consent preference storage | No — exempt under ePrivacy Art. 5(3) | session cookie, consent-preference cookie |
| Functional | Remember preferences (e.g., theme, language) that are not strictly required — not currently set as cookies (theme preference is stored in browser local storage, not a cookie) | Yes, if and when a functional cookie is introduced | — |
| Analytics | Understand aggregate usage of the marketing site/dashboard to improve the product — no analytics tool is integrated yet | Yes (unless configured as genuinely strictly-necessary, privacy-preserving analytics, which we treat as still requiring consent to stay on the safe side) | [to be completed: ANALYTICS_TOOL] cookie/local storage |
| Marketing | Not currently used for third-party advertising; reserved for future use, would require separate consent | Yes | — |
We do not currently use third-party advertising or cross-site tracking cookies.
3. Consent Mechanism
Where you are in the EEA, UK, or another jurisdiction requiring prior consent for non-essential cookies:
- On first visit, we present a cookie banner allowing you to accept all, reject non-essential, or customize by category. Accepting and rejecting are equally prominent, and no non-essential cookie is set before you choose.
- Strictly necessary cookies are set regardless, as permitted under ePrivacy Art. 5(3) and equivalent laws (e.g., UK PECR).
- You can change your choice at any time via the "Cookie preferences" link in the site footer, or by clearing cookies in your browser. Withdrawing is as easy as consenting: the same dialog, one click.
- We log each choice — the categories you allowed, the policy version you saw, and the time — against a random identifier stored in your
cookie_consentcookie. We do not log your IP address or browser details with it. - When we change what a category covers (for example, if we start using an analytics tool), we update this policy's version and ask you again.
Today, no non-essential cookies are set, whatever you choose: the categories below are listed so your choice is already recorded if that ever changes.
4. Specific Cookies
| Name | Set by | Category | Duration | Purpose |
|---|---|---|---|---|
better-auth.session_token | irisend.com | Strictly necessary | 7 days | Authenticates logged-in dashboard users (set by better-auth) |
better-auth.two_factor | irisend.com | Strictly necessary | 10 minutes | Holds the half-finished sign-in between entering your password and entering your two-factor code (set by better-auth, only if you have two-factor authentication enabled) |
better-auth.trust_device | irisend.com | Strictly necessary | 30 days | Lets you skip the two-factor prompt on this browser — set only if you tick "Trust this device" when entering a two-factor code (set by better-auth) |
better-auth.better-auth-passkey | irisend.com | Strictly necessary | 5 minutes | Carries the one-time challenge while you register or sign in with a passkey (set by better-auth) |
cookie_consent | irisend.com | Strictly necessary | 12 months | Remembers your cookie choice (categories allowed, policy version, and a random identifier linking it to our consent log) |
[{{ANALYTICS_COOKIE_NAME}}](irisend-missing-placeholder:ANALYTICS_COOKIE_NAME) | [to be completed: ANALYTICS_TOOL] | Analytics | [to be completed: ANALYTICS_COOKIE_DURATION] | Aggregate product/site usage analytics — not yet implemented; no analytics tool is integrated today |
__cf_bm / cf_clearance | Cloudflare | Strictly necessary | Up to 30 minutes / 1 year | Bot mitigation, security (set by Cloudflare when proxying the site) |
This table lists the cookies currently set by the application itself (the better-auth session, two-factor, trusted-device and passkey cookies, and the cookie_consent preference cookie) plus Cloudflare's own cookies. There is no separate CSRF cookie — better-auth enforces CSRF protection via trusted-origin checks, not a cookie token. The analytics row describes planned, not-yet-built functionality; update this table, and the policy version, when an analytics tool actually ships — an inaccurate cookie table is itself a compliance gap under ePrivacy/GDPR transparency rules.
5. Browser Controls
Most browsers let you block or delete cookies via settings. Blocking strictly necessary cookies may break dashboard login and core site functionality.
6. Third-Party Cookies
Some cookies (e.g., Cloudflare security cookies, analytics) are set by third parties providing services on our behalf; see Subprocessors for the vendors involved and their own privacy/cookie policies.
7. Changes
We will update this policy as our cookie usage changes and reflect the current effective date above.
8. Contact
This document is a draft template and does not constitute legal advice. See research/legal.md for review recommendations before publishing.