Scope and contact
This policy explains cookies and similar browser storage used by UpBastion at upbastion.com. Local storage is included because it saves information on your device even though it is not a cookie sent with each HTTP request. For questions, email [email protected] or use our contact page.
Read this policy together with the privacy policy, which explains the information processed by the monitoring application, authentication provider and website infrastructure.
Authentication cookies
UpBastion uses Clerk to authenticate accounts. Cookies used by the account screens and dashboard maintain and verify the authentication session. They are necessary to use those account functions and are not controlled by the optional analytics setting.
Clerk documents cookies including __session and __client_uat. Cookie names, domain scope and expiry can vary with the configured authentication flow and session state. See Clerk's cookie documentation for provider details, and inspect your browser's cookie panel for the cookies and expiry actually present in your session.
The public product, documentation, guide, legal and contact pages do not load Clerk's account interface. Opening sign-in, sign-up or the dashboard loads the authentication functionality. Blocking its necessary cookies can prevent sign-in or session continuity.
Saved website preferences
The upbastion:cookie-preferences local storage entry records the preference format version, that essential storage remains enabled, your optional analytics choice and the time you saved it. The entry is used to show your choice on later visits; it is not a monitoring result or a record of your account password.
A saved choice is valid for up to 180 days. The website disregards an expired, malformed or incompatible entry and asks again. Local storage does not automatically remove a value at its expiry time; the website applies this validity check when it reads the entry. Clearing site data removes the saved choice immediately.
If your browser blocks local storage, your selection applies to the current visit and cannot be remembered reliably across visits. Browser settings or privacy modes can also clear the entry earlier. Preferences are stored per browser and origin; changing one browser does not change another browser's choice.
Optional website analytics
When configured, UpBastion uses a self-hosted Umami instance to measure visits to public pages. Its tracker loads from UpBastion's own domain only after you allow website analytics. Selecting Use essential only leaves the tracker off. The optional choice does not affect access to the website or the monitoring service.
Umami operates without analytics cookies. Its website metrics can include page paths, page titles, referrers, visit times, browser and device information, screen size, language and approximate location. Umami derives a session identifier using request information including an IP address and user agent. The absence of a cookie does not mean there is no data processing. Umami's session documentation explains that identifier.
UpBastion excludes URL query strings and fragments from its tracked page paths. The tracker is limited to public pages and does not receive contact form field values or the signed-in dashboard's monitor data from the application. UpBastion does not enable session replay or pass account identifiers as analytics identities.
The tracker also respects the browser's Do Not Track setting. Advertising cookies and advertising pixels are not part of the current UpBastion application.
Change or withdraw your choice
Open Cookie settings in the footer, change Website analytics, and select Save preferences. Turning analytics off stops further tracker collection from that page; the website reloads when needed to stop an already loaded tracker. Withdrawal does not erase observations already collected before the change. To ask about those records, contact us.
Essential authentication storage cannot be turned off in this preference panel because the account features depend on it. You can block or delete cookies and local storage through your browser, subject to the effect on sign-in and saved preferences.
Infrastructure security cookies
Requests pass through Cloudflare. Cloudflare documents security cookies used by specific protection features, for example cookies associated with a challenge or bot protection. These are separate from UpBastion's optional Umami choice; which cookies are present depends on the protection applied to your request.
See Cloudflare's cookie reference for their purposes. We do not label every Cloudflare cookie as present on every visit or claim a fixed lifetime for a cookie your request did not receive.
Policy changes
The update date on this page identifies the published version. We will revise the policy when the website's storage or analytics behavior changes. A changed preference format can cause the website to ask for your choice again. For the wider rules governing the service, read the terms of service.