Cookie Policy
Last updated 10 August 2026
OpenIssues sets four cookies. All of them exist to keep you signed in, protect forms, or remember an interface preference. None of them track you.
1. Cookies we set
| Name | Purpose | Type | Lifetime |
|---|---|---|---|
openissues-session | Keeps you signed in and carries an in-progress submission between the form and the email step. | Strictly necessary | 120 minutes |
XSRF-TOKEN | Protects every form submission against cross-site request forgery. | Strictly necessary | 120 minutes |
sidebar_state | Remembers whether the application sidebar is open or collapsed. | Functional | 7 days |
appearance | Remembers your light, dark or system theme choice so the page renders correctly on first paint. | Functional | 1 year |
2. What we don't set
No analytics cookies. No advertising or retargeting cookies. No third-party trackers, social widgets or pixels. Nothing on OpenIssues follows you to another site, and no cookie is shared with anyone.
If that ever changes, this page changes with it and non-essential cookies will only be set after you agree to them.
3. Your choice
The first time you visit, a short banner tells you we use only the essential cookies above and set no trackers. There is nothing optional to accept or decline — every cookie in the table is needed for the app to work or to remember an interface preference you set — so the banner is a notice, not a consent gate.
Dismissing it records that you have seen the notice in your browser's local storage under cookie_consent — not in a cookie — so it does not reappear on your next visit. If we ever introduce an optional cookie, we will ask for your agreement first and this banner will change accordingly.
You can bring the notice back by clearing this site's data in your browser. You can also block or delete cookies entirely in your browser settings — but signing in will stop working, because the session cookie is what keeps you signed in.
4. Related information
What personal data we process, why, and for how long is described in the Privacy Policy. For questions about either document, write to roman.szymanski@shortcodes.pl.