Cookies

No cookie on a short link, none from brv.js on your own site unless you turn one on, the ones the console sets, and none on this website.

On this page
  1. On people who click your links: no cookie
  2. On your own website, with brv.js
  3. On this website: none
  4. In the console
  5. Managing them

Brevily is operated by Psionic Ventures LLP ("we", "us"). Read this page with our Terms of service, Privacy policy and Acceptable use policy.

On your own website, with brv.js

If you add the brv.js script to your website to report events, it keeps the brv_click value that a tracked short link handed your page for the visit only, in the browser tab's session storage, with no cookie. It is gone when the tab closes.

A site that wants the click remembered across visits, and whose own consent covers it, can turn on a first-party cookie by adding data-remember-days to the script tag (at most 90):

Cookie What it does How long
brv_click Only when your script tag asks for it with data-remember-days. Holds the id of the click and of its link, so that an event on a later visit, or on your server, can be tied to that click. It is set on your site's own domain, by our script; it is your site's cookie. The script sends it nowhere unless your page reports an event, and window.brv.clear() removes it. The days you set, at most 90

If you turn it on, your site's own cookie notice, and any consent your visitors' law requires, should cover it.

On this website: none

This website sets no cookie. Your choice of light or dark theme is kept in your browser's local storage, which never leaves your device.

In the console

Cookie What it does How long
__Host-brevily_session Keeps you signed in. Set only when you sign in; your browser's scripts cannot read it. 12 hours, or until you close the browser, whichever comes first — or 30 days if you choose to stay signed in
csrf A token the console checks on every form it receives, so another site cannot submit one in your name. The console's own script reads it to send it back. Until you close the browser
brevily_verify, brevily_invite, brevily_mfa, brevily_mfa_enrol, brevily_pk_login, brevily_pk_register, __Host-brevily_oauth, __Host-brevily_link, __Host-brevily_signup Each holds your place in a step of signing up, accepting an invitation, signing in or setting up sign-in: a code sent to you, a second factor, a passkey, a sign-in through Google, GitHub, Microsoft or your organisation's single sign-on, linking one of those to your account, or creating your account from one of them. Set only during that step. 10 minutes at most
brevily_reset_to Holds the address you asked for a password reset for, so the next page can say where the link went. Sent only to that page (/reset/sent); your browser's scripts cannot read it. 10 minutes
brevily_rv Remembers your address once you enter the code emailed to you, on a shared report that names its viewers, so you are not asked again on each page. Set only there, and sent only to that report's address (/r/<token>). 12 hours

None of them is used for analytics or advertising. The console also keeps a few preferences in your browser's local storage, such as your theme and your recent searches; they never leave your device.

Managing them

Your browser can block or delete cookies. Blocking the console's will stop you signing in; this website and every redirect will carry on as normal.

Questions to privacy@brevily.com.