JustBrowser
← Back to Home

Cookie Policy

Last updated: October 2, 2026

This Cookie Policy explains which cookies the JustBrowser website and web dashboard at justbrowser.app set on your device, what they do, and how you can manage them. It also describes the cookieless analytics our website uses, and explains how cookies inside your JustBrowser browser profiles differ from ours.

1. Who we are and what this policy covers

JustBrowser is operated by Velocity Digital Labs LLC, 131 Continental Dr, Suite 305, Newark, DE 19713, USA ("we", "us", "our"). "The Service" means the JustBrowser website and web dashboard at justbrowser.app and the JustBrowser desktop application. "You" means the person visiting the website or using the Service.

A cookie is a small text file that a website asks your browser to store on your device and send back on later requests. Websites use cookies to keep you signed in, protect forms against forgery, remember choices you have made, and measure how a site is used.

This policy covers two different things. Sections 2 to 5 cover the cookies, cookieless analytics and local storage used when you visit justbrowser.app. Section 6 covers cookies that live inside the browser profiles you create in the JustBrowser desktop application. Those profile cookies are set by the websites you visit, not by us.

For how we handle personal data more generally, see our Privacy Policy at /privacy. For the terms that govern your use of the Service, see /terms.

2. Cookies our website sets

Our website and dashboard set three kinds of first-party cookie on justbrowser.app:

  • Sign-in cookies: strictly necessary, and listed below.
  • Analytics choice: one cookie that remembers your choice about Google Analytics (Section 2.2).
  • Google Analytics cookies: not strictly necessary, and set only where Google Analytics runs (Section 2.3). Nothing on the website depends on them.

The website and dashboard set three sign-in cookies during normal use, plus one short-lived cookie that exists only while a Google sign-in is in progress. All four are created by Auth.js, the sign-in library that runs our authentication, and all are strictly necessary: without them you cannot sign in or stay signed in. A fifth, jb_dg_nonce, is set by our own code only while a Google sign-in started from the desktop app is in progress, and is strictly necessary too. They are first-party cookies, set only by justbrowser.app.

The names carry standard browser security prefixes. A cookie starting with __Host- can only be set over HTTPS, only for justbrowser.app itself, and only for the whole site path. A cookie starting with __Secure- can only be set and sent over HTTPS. These prefixes are enforced by your browser, not by us.

  • __Host-authjs.csrf-token. Purpose: protects the sign-in and sign-out forms against cross-site request forgery by pairing each form submission with a token that only our site could have issued. Duration: session; deleted when you close your browser. Set by: Auth.js on justbrowser.app.
  • __Secure-authjs.callback-url. Purpose: remembers the page you were trying to reach so we can return you there after you sign in. Duration: session; deleted when you close your browser. Set by: Auth.js on justbrowser.app.
  • __Secure-authjs.session-token. Purpose: keeps you signed in to the dashboard. It holds a signed session token, not your password. Duration: 30 days after your last visit to the dashboard; the expiry is extended each time you use the dashboard while signed in, and the cookie is deleted when you sign out. Set by: Auth.js on justbrowser.app after a successful sign-in.
  • __Secure-authjs.pkce.code_verifier. Purpose: set only when you choose Continue with Google; holds a one-time code that proves the sign-in that returns from Google is the one you started, so the response cannot be replayed or hijacked. Duration: 15 minutes at most, and deleted as soon as the Google sign-in completes. Set by: Auth.js on justbrowser.app.
  • jb_dg_nonce. Purpose: set only when you sign in with Google from the JustBrowser desktop app; holds a one-time random value that ties the sign-in coming back from Google to the request the app started. Duration: 10 minutes at most, and deleted as soon as that sign-in completes. Set by: our website on justbrowser.app (our own code, not Auth.js), and sent only to the address that completes that sign-in.

2.1 What these cookies do not contain

None of the sign-in cookies above contains your password, your card details, or any identifier that is shared with another company. The session cookie identifies your sign-in session to us and nothing else. It is not used to track you across other websites.

2.2 Cookie that remembers your analytics choice

  • jb_consent. Purpose: remembers your choice about Google Analytics: whether you clicked Accept or Decline on our banner, or turned Google Analytics off in Cookie settings. It holds only that choice, the date you made it and a version number. Duration: 6 months from when you make your choice; some browsers delete it sooner. Set by: our website on justbrowser.app, when you make a choice.

This cookie is strictly necessary to respect your choice. If it expires or you delete it, we treat you as not having chosen yet: in the United Kingdom, Switzerland and the EEA the banner asks again, and elsewhere Google Analytics loads again by default.

2.3 Google Analytics cookies

We use Google Analytics 4 to measure how our website is used; section 2.11 of our Privacy Policy explains where it runs and what it receives. When Google Analytics runs, it sets the two cookies below. They are not strictly necessary. They are first-party cookies on justbrowser.app, but they are written by the Google Analytics script, not by our own code, and the identifier in _ga is sent to Google with each measurement.

  • _ga. Purpose: website analytics; holds a random identifier for your browser (for example, 12345.67890) so that Google Analytics can tell visitors apart and recognise the same browser on later visits. Duration: up to 2 years from your most recent visit; some browsers delete it sooner. Set by: the Google Analytics script on justbrowser.app.
  • _ga_TVZHQ99TZW. Purpose: website analytics; keeps track of your current session for our Google Analytics property (measurement ID G-TVZHQ99TZW). Duration: up to 2 years from your most recent visit; some browsers delete it sooner. Set by: the Google Analytics script on justbrowser.app.

When these cookies are set:

  • United Kingdom, Switzerland and the EEA: only after you click Accept on our banner (Section 4).
  • Everywhere else: when you visit, unless you have turned Google Analytics off in Cookie settings. There is no banner.
  • Everywhere: never if your browser sends a Global Privacy Control (GPC) or Do Not Track (DNT) signal, and never on the pages where Google Analytics does not run, which section 2.11 of our Privacy Policy lists.

These cookies contain no name, email address or account details. Google Analytics is not linked to Google Ads, Google signals is off, and its advertising signals are switched off. For how Google uses information from sites that use its services, see "How Google uses information from sites or apps that use our services" (https://policies.google.com/technologies/partner-sites).

3. Cookieless analytics, and cookies we do not set

Cloudflare Web Analytics: Cloudflare, the network provider that delivers justbrowser.app, adds its Web Analytics script to our pages. The script loads from static.cloudflareinsights.com and reports page views and page-load performance to Cloudflare without setting cookies. Cloudflare says the script does not store any data in your browser. Cloudflare also says Web Analytics does not log query strings, to avoid collecting potentially sensitive data. We have set Cloudflare not to add it for visitors who connect through its data centres in the European Economic Area, the United Kingdom or Switzerland. For everyone else it runs without asking; the banner, Cookie settings, Global Privacy Control and Do Not Track do not switch it off. It does not run on /check or /newtab, the pages the desktop application opens inside your browser profiles, or on /fingerprint-checker. Section 2.11 of our Privacy Policy lists what it receives.

The website sets no advertising cookies and no third-party cookies. It embeds no advertising pixels or social media widgets, and it runs no analytics scripts other than Cloudflare Web Analytics and Google Analytics (Section 2.3). The desktop application sends no usage telemetry or crash reports (it contacts our servers only for sign-in and session checks, licence validation, cloud sync and the features you use). No cookies other than those listed in Section 2 are set on justbrowser.app.

Our infrastructure providers (for example, the edge network that serves justbrowser.app) process requests to deliver the site. As of the date at the top of this page, none of them sets a cookie on justbrowser.app. If our edge network ever needs to set a security cookie to protect the site from automated abuse, that cookie would be strictly necessary; we will list it in Section 2 as soon as it is introduced. Rate limiting keys on your IP address transiently and does not use a cookie.

4. Cookie consent

Cookie consent rules under the EU ePrivacy Directive, the GDPR, and the UK equivalents require consent for cookies that are not strictly necessary for a service you have asked for. Cookies that are strictly necessary are exempt from that requirement.

The sign-in cookies in Section 2 are strictly necessary for signing in and staying signed in, which is a service you request when you use the dashboard. The cookie in Section 2.2 is strictly necessary to remember your analytics choice. Google Analytics and its cookies (Section 2.3) are not strictly necessary, so how we handle them depends on where you are:

  • United Kingdom, Switzerland and the European Economic Area (EEA): a banner asks you first. Google Analytics does not load, and sets no cookies, unless you click Accept. If you click Decline, it does not load. In this policy, the EEA includes EU territories that have their own country code, such as Réunion and the Åland Islands. If we cannot tell which country you are in, we treat you as being in this group.
  • Everywhere else: there is no banner. Google Analytics loads by default and sets its cookies when you visit, unless you have turned it off.
  • Everywhere: if your browser sends a Global Privacy Control (GPC) or Do Not Track (DNT) signal, Google Analytics does not load.

We work out which group applies on our server, from the country that Cloudflare, our network provider, associates with your IP address, so a VPN or proxy can change it. Wherever you are, you can turn Google Analytics off at any time with Cookie settings, in the footer of our website and at the bottom of the dashboard's sidebar. Cloudflare Web Analytics (Section 3) sets no cookies, and the banner and Cookie settings do not apply to it.

We commit to the following: if we ever decide to introduce another cookie or similar technology that is not strictly necessary, such as an advertising cookie, we will update this policy first, describe it here and, wherever you are, ask for your consent before it is set. The only exception is Google Analytics outside the United Kingdom, Switzerland and the EEA, described above. Cloudflare Web Analytics (Section 3), which our website already uses, sets nothing on your device; we have set Cloudflare not to add it for visitors who connect through its data centres in the EEA, the United Kingdom or Switzerland, and elsewhere it runs without asking. We will not add non-essential cookies silently.

5. Local storage on the dashboard

Besides cookies, browsers offer a storage area called localStorage that a website can use to keep small settings on your device. The dashboard does not currently store anything in localStorage. If it does in future, it will only be interface preferences, such as a chosen layout, and we will update this section.

Data in localStorage is never sent to us automatically. It stays in your browser, is not used for tracking or analytics, and contains no personal data beyond the preference itself. You can clear it at any time through your browser's site data settings (see Section 7); the dashboard will simply return to its default preferences.

Some pages keep a value in your browser's session storage, which belongs to a single tab and is cleared when you close it. The password-reset page (jb_reset_token) and the team-invitation page (jb_invite_token) keep the code from the link you followed while you finish; the code is sent to us only when you complete the reset or accept the invitation. The /check, /newtab and /fingerprint-checker pages keep a flag (jb_ga4_off) that keeps Google Analytics off in that tab.

6. Cookies inside your browser profiles

The JustBrowser desktop application creates isolated browser profiles, each with its own cookie storage. The cookies in a profile are set by the websites you visit inside that profile, in exactly the way any browser stores cookies. They are not set by us and are not our cookies.

  • Each profile has a completely separate cookie jar. Cookies from one profile are never shared with another.
  • Profile cookies are stored locally on your device in a per-profile user data directory. That directory is a local file under your control.
  • Profile cookies persist between sessions, so you stay signed in to websites across restarts of the application.
  • We never read, analyse, or access the content of cookies inside your browser profiles, and the desktop application does not report browsing history or page content to us.
  • If you enable cloud sync, the profile archive, which contains the profile's cookies, sessions, and browser storage, is uploaded over TLS and stored in Amazon Web Services S3 (us-east-1) with server-side AES-256 encryption at rest. We do not open or read synced archives. Alongside each archive we store a profile summary in our database so your other devices can list the profile before downloading it; section 2.3 of our Privacy Policy at /privacy describes what that summary contains. The archive is deleted from storage when you delete the profile, and when your account is deleted (see Section 10 for how to request account deletion). The profile summary is kept after the archive is deleted, so that your other devices learn the profile was deleted.
  • Separately from cookies, proxy credentials and saved logins stored by the Service are encrypted with AES-256-GCM using a per-account key issued after sign-in, so a synced profile works on another machine you sign in from. The local database as a whole is not encrypted. See our Privacy Policy at /privacy and our security page at /security for how that key is issued and what it does and does not protect.
  • You can delete the cookies inside any individual profile from that profile's own browser settings without affecting other profiles. Deleting a profile permanently removes its cookies.

7. How to manage cookies

7.1 Cookies on our website

You can manage or delete the cookies on justbrowser.app through your browser settings. Most browsers let you view, block, or delete cookies for a specific site. Blocking or deleting the sign-in cookies (Section 2) will sign you out and prevent you from signing in to the dashboard until they are allowed again. Blocking or deleting the Google Analytics cookies (Section 2.3) does not affect signing in or how the website works. If you delete the cookie that remembers your analytics choice (Section 2.2), we treat you as not having chosen yet: in the United Kingdom, Switzerland and the EEA the banner asks again, and elsewhere Google Analytics loads again by default.

To turn Google Analytics off, use Cookie settings, in the footer of our website and at the bottom of the dashboard's sidebar, or turn on Global Privacy Control or Do Not Track in your browser (Section 4). Google also offers a browser add-on that, according to Google, stops Google Analytics from being used in your browser (https://tools.google.com/dlpage/gaoptout). None of these switches off Cloudflare Web Analytics, which sets no cookies (Section 3); to stop it in your browser, block scripts from static.cloudflareinsights.com.

Common locations for cookie settings:

  • Chrome: Settings > Privacy and security > Cookies and other site data
  • Firefox: Settings > Privacy & Security > Cookies and Site Data
  • Safari: Settings (or Preferences) > Privacy > Manage Website Data
  • Edge: Settings > Cookies and site permissions > Cookies and site data

7.2 Signing out and sign-in sessions

Signing out of the dashboard deletes the session cookie from the browser you signed out in. The session cookie is a signed, self-contained token: it is not stored on our servers, so it cannot be cancelled remotely and remains valid in any browser that still holds it until it expires (see Section 2) or you sign out there. If you believe a browser you no longer control holds a valid session cookie, change your password and contact [email protected]. The Active Sessions list in your account settings shows the desktop applications signed in to your account; those use a separate sign-in token, not a cookie. Revoking a desktop session there signs that application out within about a minute, once it next contacts our servers.

7.3 Cookies inside browser profiles

You manage the cookies inside a JustBrowser profile from the desktop application:

  • Open the profile in the desktop application and find the Cookies row in the profile panel. From there you can import cookies into the profile or export the profile's cookies to a file.
  • To delete cookies from a profile, open the profile and use the browser's own Clear browsing data setting (Settings > Privacy and security > Delete browsing data); this affects only that profile.
  • Deleting a profile permanently removes all of its cookies, and its synced archive if cloud sync was enabled.

8. Links to other websites

Our website may link to other websites and services, for example our payment provider's checkout pages or a proxy provider's documentation. When you follow such a link, that site may set its own cookies under its own policy. We do not control those cookies, and we recommend reading the cookie policy of any site you visit.

Inside JustBrowser profiles, websites you visit set their own cookies as they normally would in any browser. Those cookies stay confined to the profile in which they were set.

9. Changes to this policy

We may update this Cookie Policy when our practices or the law change. When we do, we will post the updated version with a new date and, for changes that narrow what you may do or reduce your rights, notify account holders by email before they take effect. As stated in Section 4, any change that would introduce a non-essential cookie will be described here before it takes effect and put to you for consent before it is set, wherever you are, except Google Analytics as described in Section 4. We encourage you to review this policy from time to time.

10. Contact us

If you have questions about our use of cookies or about this policy, or want to exercise your privacy rights, contact us at [email protected]. To delete your account, email [email protected] from the address on the account; we delete your data within 30 days except where law requires retention.

To report a security vulnerability, email [email protected]; our security disclosure page at /security explains what to include. For legal notices, email [email protected].

Velocity Digital Labs LLC, 131 Continental Dr, Suite 305, Newark, DE 19713, USA.

We'd like to use Google Analytics, a Google service, to understand how our website is used. It sets two cookies in your browser and runs only if you click Accept. You can change your choice at any time with Cookie settings. Cookie Policy

Sign-in cookies and the cookie that remembers this choice are always on; the website needs them to work.

Google Analytics, a Google service, helps us understand how our website is used. It sets two cookies, _ga and _ga_TVZHQ99TZW. It is now onoff in this browser. If your browser sends a Global Privacy Control or Do Not Track signal, it stays off. Cookie Policy