Cookie Policy

This policy explains how UptimeOwl, a SaaS monitoring platform operated by Blastup, uses cookies and similar browser technologies on uptimeowl.online, in the account dashboard and in embedded status widgets. Read it alongside our Privacy Policy at https://uptimeowl.online/privacy-policy.

What are cookies?

Cookies are small pieces of information stored on your computer or mobile device when you visit a website. They help a service recognise your browser, maintain a signed-in session and make features work across pages.

Similar technologies include browser session storage, which keeps information for a particular browsing tab. Although session storage is not a cookie and is not automatically sent with every request, it can support related functions such as remembering your workspace while you navigate.

What cookies do we use and why?

Essential sign-in cookie

Name: uptime_session Provider: UptimeOwl Purpose: Keeps you signed in and allows the platform to recognise your authenticated session when you access your account, monitors, widgets and other protected features. Duration: Up to 24 hours from sign-in. Signing out clears the cookie and revokes the associated session. Sessions may also be revoked earlier for security or access-management reasons.

The cookie contains a random session identifier rather than your email address or payment-card details. It is marked HttpOnly so page scripts cannot read it, uses SameSite=Lax, and is marked Secure when the service is accessed through a recognised HTTPS connection.

Essential verification cookie

Name: uptime_verification Provider: UptimeOwl Purpose: Binds your browser to a restricted authenticator enrollment or verification step after confirming an email sign-in link. It cannot access your workspace as a normal signed-in session. Duration: Up to ten minutes. Successful verification or cancellation clears the cookie.

The cookie contains random proof values, not your authenticator secret or backup codes. It is HttpOnly, SameSite=Lax and Secure on recognised HTTPS connections. Sensitive authenticator screens do not load our analytics or chatbot, and their setup QR codes are generated locally.

Mobile secure storage

The native app stores persistent, revocable sign-in credentials and temporary pending sign-in proof in the operating system’s Keychain or Keystore, rather than browser cookies. Pending verification expires after ten minutes; a verified mobile session does not expire after 24 hours. Signing out removes its local credentials and revokes the session when the service can be reached. Setup keys and newly displayed backup codes stay in app memory unless you explicitly save or share them to a destination you choose.

Temporary browser storage

UptimeOwl uses session storage to retain the workspace identifier while you navigate. Invitation flows may temporarily store an invitation reference so that you can continue after signing in. Authorised support visits use a separate temporary support-access reference.

These values support the feature you are using; they are not advertising identifiers. Session storage normally lasts for the browsing tab's session. Invitation and support references are also removed when their corresponding flows complete or end. Browser session-restoration behaviour may retain tab data, so you can clear site data through your browser settings when needed.

Third-party services

Some features connect to service providers that may use their own cookies or similar technologies:

• Stripe provides the payment interface used for billing and payment-card management. Its technology may use cookies and browser storage for payment functionality, authentication and fraud prevention. The exact cookies depend on the Stripe features you use. Stripe's cookie policy is available at https://stripe.com/legal/cookies-policy.

• Cloudflare helps deliver and protect UptimeOwl. Depending on the security features active for a request, it may set cookies to support functions such as bot protection or security challenges. Cloudflare documents these cookies and their purposes at https://developers.cloudflare.com/fundamentals/reference/policies-compliances/cloudflare-cookies/.

• Some pages load Font Awesome resources to display interface icons. Your browser connects to that provider to retrieve those resources. Loading a third-party resource does not, by itself, mean an advertising cookie has been set.

Third-party cookie names and lifetimes can change with provider configuration and the features used. Refer to the relevant provider's information for its current practices.

Analytics, advertising and social media cookies

On our production marketing, help, legal and signup pages, and limited plan events on the Billing tab of your account, we use optional Google Analytics to understand visits, signup steps and plan choices. Google Analytics is not loaded until you choose “Allow analytics”. “Essential only” leaves it disabled. You can change your choice through “Analytics preferences” in the footer. Your choice is stored in your browser for up to 180 days; clearing browser storage removes it.

With permission, Google Analytics may set _ga cookies to distinguish browser visits, configured here for up to 180 days. We send fixed signup and plan event names and sanitised page metadata, not your form entries, email address, username, workspace details, billing details or sign-in tokens. Analytics requests still involve Google receiving technical information such as your network address and browser information. Google describes its processing at https://policies.google.com/privacy.

Withdrawing permission stops our analytics, removes accessible _ga cookies and reloads a page if its Google tag was already loaded. It does not retrospectively erase information already received by Google. Apart from limited plan-choice and activation events on the Billing tab of your account, our platform analytics does not measure authenticated dashboard activity, tenant status pages or embedded widgets. A tenant can separately configure its own analytics on its public status page; that tenant is responsible for the associated notices and choices. This analytics preference does not disable essential sign-in, payment security or separately provided third-party features.

With analytics permission, plan events contain a standard plan label (Free, Starter, Team, Business or Enterprise), the activation category and an opaque event identifier. They never contain prices, card or invoice details, custom Enterprise revision identifiers or workspace identifiers. Paid activations are reported only after the application confirms the change. A minimal internal receipt prevents duplicates; essential billing records remain separate. No billing-page view is sent. Analytics remains optional and does not affect signup or billing.

Our Google tag disables Google signals and advertising personalisation. We do not add social-media tracking plugins through the social links in our footer.

Embedded status widgets

Public UptimeOwl status widgets can be viewed without signing in. Viewing a public widget does not create an UptimeOwl sign-in session. The website embedding a widget may independently use its own cookies, analytics or advertising technologies. Those practices are covered by that website's policies. Delivery and security services may still apply when a widget is loaded.

How long do cookies remain on my device?

A session cookie generally lasts for the browsing session, while a persistent cookie remains until its expiry or until you delete it. UptimeOwl's sign-in cookie has a maximum lifetime of 24 hours from sign-in. Third-party cookies follow their providers' settings and lifetimes. You can remove stored cookies and site data before they expire through your browser controls.

How can I control cookies?

Your browser settings allow you to inspect, delete or block cookies and other site data. These controls are usually found under Privacy, Security or Site settings. Consult your browser's help documentation for instructions.

Blocking or deleting the verification cookie prevents completion of the authenticator sign-in step. Blocking or deleting the sign-in cookie will prevent your existing session from working, and you may need to sign in again. Restricting third-party storage can also affect payment or security features. Signing out ends your UptimeOwl session, but does not necessarily clear data stored independently by another provider or by the website hosting an embedded widget.

Changes to this policy

We may revise this policy as the platform or its service providers change. The Cookie Policy page presents the current version, while previously archived document versions remain available through their versioned links.

Contact

If you have questions about UptimeOwl's use of cookies or browser storage, contact Blastup at [email protected].