Two cookies, both needed to run the dashboard. No analytics, no advertising, no tracking.
Last updated: October 1, 2026
UPKira only sets cookies the service needs in order to work. We do not use analytics, advertising, social media or cross-site tracking cookies, and we do not use third-party tracking scripts. All our cookies are strictly necessary, so they do not need consent under the ePrivacy rules, and we do not show a cookie banner.
| Name | Purpose | Duration | Flags |
|---|---|---|---|
| __Secure-upkira.session_token | Keeps you signed in to the dashboard. It holds a random session token, not your password. | 30 days, renewed as you use the app. Removed when you sign out. | HttpOnly, Secure, SameSite=Lax |
| upkira_once | Carries a one-time message from a dashboard action to the next page, such as an invitation link that is shown only once. | Up to 2 minutes. Deleted as soon as the message is shown. | HttpOnly, Secure, SameSite=Lax |
Both are first-party cookies set by upkira.com. Page scripts cannot read them. They are sent only over HTTPS, and only with requests from our own site.
Public status pages and status badges do not set cookies for visitors, and subscribing to updates does not set one either. A status page may show a logo loaded from the workspace owner's own server, and that server may log the request or set its own cookies under its own policy.
Checkout and the billing portal run on Stripe's own pages. When you go there, Stripe may set its own cookies for fraud prevention and to keep the payment working. Its cookie policy covers them.
Your browser settings can block or delete cookies. If you block the session cookie, you cannot sign in to the dashboard. The public marketing site and status pages still work.
If we add a cookie, we will update this page first. If a new cookie is not strictly necessary, we will ask for your consent before setting it. Questions go to hello@upkira.com. Our privacy policy explains how we handle personal data more broadly.