1. What we use
Triggerize keeps its use of cookies and browser storage deliberately minimal. We distinguish strictly necessary storage — required to run the service and exempt from consent — from optional storage, which we set only with your consent.
| Name | Purpose | Category | Retention |
|---|---|---|---|
| Session cookie (NextAuth) | Keeps you signed in; HttpOnly, Secure, SameSite | Strictly necessary | Session / expiry |
| Trusted-device token | Remembers a device you approved for MFA | Strictly necessary (security) | 30 days |
| Theme preference | Remembers light/dark mode | Functional | Persistent (local) |
| Consent choice | Stores your cookie preferences | Strictly necessary | 12 months |
| Pipeline cache | Local cache of your content board for responsiveness | Functional (local storage) | Until cleared |
| Analytics (if enabled) | Aggregate product usage to improve the service | Optional — consent required | Per provider |
2. Consent
On your first visit we ask whether you accept optional cookies. Strictly necessary storage is always active because the service cannot function without it. Optional cookies are set only if you choose “Accept”. You can change your choice at any time — declining leaves only the essential storage in place.
3. Managing cookies
You can withdraw or change consent using the cookie banner (it reappears when you clear the consent choice) and control cookies through your browser settings. Blocking strictly necessary cookies may prevent you from signing in.
4. More information
Cookies that involve personal data are also covered by our Privacy Policy. Questions? dpo@triggerize.io.