Cookie Policy
Last updated Oct 24, 2026
This Cookie Policy explains how Progma ("Progma") uses cookies and similar technologies on our platform and websites (the "Service"). It should be read together with our Privacy Policy.
1. What are cookies?
Cookies are small text files placed on your device when you visit a website. Similar technologies include local storage and session storage. They are widely used to make websites work, to keep you signed in, and to remember preferences.
2. How we use cookies
We use cookies primarily to operate core functionality. Our use falls into the following categories:
- Strictly necessary cookies. Required for the Service to function. These include authentication and session cookies set by our authentication system (Better Auth), which keep you signed in and protect your session. The Service cannot function properly without these.
- Preference cookies. Remember choices about how the interface is displayed, such as whether the admin sidebar is expanded, your default list layout, and your reduced-motion setting.
We do not use analytics or advertising cookies, and we do not use cookies to track you across other websites. Some interface preferences, such as your light/dark theme choice, are stored in your browser's local storage rather than in cookies. A message you have typed to the AI assistant but not yet sent is also kept in your browser's local storage, so it is not lost if you reload the page or switch conversations. It never leaves your device until you send it, and it is deleted from that browser when you sign out, or when the browser next opens the Progma sign-in page or home page after your session has ended.
To avoid repeating What's new highlights you have acknowledged, we also keep a small account-specific record of release-note identifiers you have dismissed or completed in your browser's local storage, together with that response. Your highlight preference and delivery status are saved to your account. You can turn off these popups in your preferences and still read the public release notes.
3. Cookies we set
| Cookie | Type | Description | Duration |
|---|---|---|---|
better-auth.session_token | Strictly necessary | Stores the session token that keeps you signed in and secures your session | Until you close your browser; 7 days, renewed as you use the Service, if you choose "Remember me" or sign in with Google |
better-auth.session_data | Strictly necessary | Holds a short-lived, signed copy of your session details so pages load without re-checking the session on every request | 1 minute; until you close your browser if you did not choose "Remember me" |
better-auth.dont_remember | Strictly necessary | Records that you chose not to stay signed in ("Remember me" not selected) | Session |
better-auth.two_factor | Strictly necessary | Identifies a pending two-factor authentication challenge between entering your password and entering your code. Signed, and holds only an opaque identifier | 10 minutes |
better-auth.state | Strictly necessary | Protects a Google sign-in against forgery while you are redirected to Google and back. Signed, and holds only a random value | 5 minutes |
progma.admin-sidebar-open | Preference | Remembers whether the admin sidebar is expanded or collapsed | Persistent (up to 1 year) |
progma.default-list-view | Preference | Remembers your default layout for lists (cards or table), tied to your account | Persistent (up to 1 year) |
progma.reduced-motion | Preference | Remembers your interface animation setting (follow your device, full, or reduced) | Persistent (up to 1 year) |
On our secure (HTTPS) site, the names of the better-auth. cookies begin with __Secure-, which tells your browser to send them only over encrypted connections.
4. Third-party cookies
When you sign in using a third-party identity provider (for example, Google), that provider may set its own cookies subject to its own policies. We do not control third-party cookies.
5. Managing cookies
Most browsers let you view, manage, and delete cookies through their settings. Blocking strictly necessary cookies will prevent you from signing in or using core features. Because the Service relies on authentication cookies to function, it is not designed to operate without them.
6. Changes to this Policy
We may update this Cookie Policy from time to time. Material changes will be indicated by updating the "Last updated" date.
7. Contact
Questions about this Cookie Policy may be sent to support@progma.app.