Cookies and Storage
Effective date: [EFFECTIVE DATE] Last updated: [EFFECTIVE DATE]
1. What this covers
This page lists everything [PRODUCT NAME] stores in your browser, and why. It covers the ordering site you sign in to at your distributor's address, and the separate console that [LEGAL ENTITY NAME] staff use to administer the service.
It does not cover your distributor's own website, marketing emails, or anything else they run. If you reached us from a link on their site, their notice covers that site and this one covers ours.
2. The short version
There is no advertising and no cross-site tracking here. Almost everything below is either what signs you in or a setting you chose yourself.
- We use one sign-in cookie on your distributor's site, and a separate one on our own operator console. It is what keeps you signed in; without it you cannot use the site.
- We save a copy of who you are signed in as, and a few of your own settings in your browser, such as the theme you picked and how many rows you want per page. You set each of the settings by using the app; we do not infer them.
- Once you are signed in we measure how the product itself is used — which screens you open and which controls you press — so we can tell whether something we built is working. Part of that goes to a product-analytics company, which stores a cookie and one browser storage entry so that a run of actions can be recognized as a single visit. It is not sent your email address, a price, or anything from an order, though it does record the wording on whatever you pressed, which on a distributor's staff screens can be a name their own staff typed in. If your browser sends a Global Privacy Control or Do Not Track signal we switch that company off for you, and only our own counting continues.
- There is no advertising, no tracking pixel, and no session recording. Nothing records your screen, and no advertiser or ad network receives anything from your browser as a result of using [PRODUCT NAME].
- The pages load no third-party fonts or stylesheets, and only two scripts from anywhere other than the site you are on: the public request-access form runs a Cloudflare Turnstile bot check on that screen only, and the billing screen a distributor's administrators use loads the payment provider's own script, which draws the card fields. Everything else the browser downloads comes from the same site you are visiting, the usage measurement included — it is sent through your distributor's own address rather than to the provider. [FACT NEEDED: whether Turnstile sets any cookie or storage, per Cloudflare's current documentation — if it does, it belongs in the tables below.]
The product-analytics company and the payment provider are named, with what each of them receives, on our Subprocessors page.
Consent banners exist to ask permission for the optional, non-essential things. The sign-in cookie and your saved settings are not that. The usage measurement is the one thing on this page that is not strictly necessary, and [FACT NEEDED: whether a consent banner or an opt-out control is required for it, and where — this page will be updated with the answer].
3. Cookies
The sign-in cookies are set by the site you are on and are sent back only to the address that set them — a sign-in cookie from one distributor's address is not sent to another's, or to our console. The measurement cookie in the last row is the exception, and its row says so.
| Cookie | Purpose | How it is protected | Lifetime |
|---|---|---|---|
__Host-boss_session |
Keeps you signed in to your distributor's ordering site. It identifies your account and your distributor. It is strictly necessary — sign-in does not work without it. | Sent only over HTTPS; not readable by scripts in the page; tied to the one address that set it, and the browser will not accept it from any other. | Customers: until 30 days without using the site, and at most 180 days. Distributor staff: until 32 hours without using the site, and at most 7 days. Ends immediately when you sign out, or when you sign that device out from your profile. |
__Host-boss_session (support sessions only) |
The same cookie, issued when a [LEGAL ENTITY NAME] operator opens your distributor's account to help with a support request. It is deliberately much shorter-lived. | As above. | About 30 minutes, and it does not extend with use. |
boss_platform |
Keeps a [LEGAL ENTITY NAME] operator signed in to our own console. It is not used on a distributor's ordering site. | As above. | About 2 hours, or until sign-out. |
ph_…_posthog |
Lets the usage measurement in section 2 recognize a run of actions as one visit, instead of counting every screen as a new person. It holds an identifier for your account in this service and a few technical values — not your name and not your email address. | Written by the page rather than by the server, so unlike the sign-in cookies it can be read by scripts on the page. Like them, it is written for the one address you are on: a visit to one distributor is not joined to a visit to another. | About a year, unless you clear it. Not set at all if your browser sends a Do Not Track or Global Privacy Control signal, or while one of our operators has your distributor's account open for support. |
Those are the cookies we set as of the date at the top of this page, apart from anything the Turnstile check on the request-access screen may set, and anything the payment provider's own script sets on the billing screen. [FACT NEEDED: what storage the payment provider's script sets on that screen, per its current documentation — if it sets any, it belongs in these tables.]
4. Browser storage
Alongside cookies, the app keeps a small amount of data in your browser's own storage
(localStorage, which persists between visits, and sessionStorage, which is discarded
when you close the tab). None of it is sent to us automatically the way a cookie is; the
app reads it locally to draw the screen the way you left it.
| Key | Purpose | When set | When cleared |
|---|---|---|---|
boss.session |
A copy of who you are — your name, your account and your distributor's branding — so a page reload shows the right screen immediately instead of a blank one. It is not the credential; the __Host-boss_session cookie is, and this copy proves nothing on its own. |
When you sign in | When you sign out |
boss.rowsPerPage |
Your saved rows-per-page choice for lists, so the first page you see is already the size you asked for. | When you change it in your profile, or when your saved profile setting is loaded | When you sign out |
boss.orderWindow |
For distributor staff: how far back the orders list should reach (3 months, 6 months, and so on). | When you change the date range | Not cleared automatically; removed when you clear site data |
boss.themeMode |
Whether you chose light, dark, or "follow my device". A per-device display preference. | When you use the theme switch | Not cleared automatically; removed when you clear site data |
boss.submitted.<order number> |
A short-lived confirmation that a specific order was submitted, so if you are interrupted and come back the page can still tell you it went through. Held in sessionStorage, not localStorage. |
When you submit that order | When the tab is closed, or when the order's status next changes |
boss.lastSupplier |
On our own home page only: the distributor you picked in the supplier finder (their name and sign-in address), so your next visit can offer a one-tap shortcut instead of another search. | When you pick a distributor in the finder | When you choose "not your supplier?", or when you clear site data |
boss.platform |
Vendor console only: a copy of the signed-in operator's identity, for the same reason as boss.session above. |
When an operator signs in to the console | When they sign out |
boss.visitId |
A random identifier standing for this one visit, so the usage measurement in section 2 can tell a single trip through the site from a later one. Held in sessionStorage, so it lasts as long as the tab. It says nothing about you. |
On your first screen after arriving | When the tab is closed |
ph_…_posthog |
The same values as the cookie of that name above. The measurement keeps a copy here as well, so it still works where cookies are unavailable. | When the usage measurement starts, shortly after you sign in | Emptied when you sign out; the entry itself goes when you clear site data |
One note on the table: some things you might expect to be saved deliberately are not. A search term you typed on an admin screen, or the sort order of a table, are kept in memory only and disappear on reload.
5. Clearing them, and what breaks
You can delete all of this at any time using your browser's "clear cookies and site data" control for the site, or by using a private/incognito window, which discards everything when you close it. You do not need to ask us.
What happens if you do:
- You are signed out. Deleting the
__Host-boss_sessioncookie ends your session, and you will be asked to sign in again. Nothing is lost — your orders, favorites and account live on the server, not in your browser. - Your display settings go back to the defaults. Theme, rows per page, and the orders list's date range reset. Rows per page is also stored on your account, so it comes back the next time you sign in; the others are per-device and you would re-pick them.
- Blocking cookies entirely means you cannot sign in. The sign-in cookie is how the site knows who you are; there is no alternative. Blocking only browser storage is survivable — the app keeps working for the visit and forgets your settings afterwards.
6. Your distributor's own site
[PRODUCT NAME] loads no third-party tags or embeds, and no script from anywhere other than the site you are on apart from the two named in section 2 — the Turnstile bot check on the request-access form, and the payment provider's card fields on a distributor's own billing screen. Nothing beyond the tables above is added by us on your distributor's ordering site. A distributor can upload their logo and colors, but not code.
Your distributor's separate marketing website, if they have one, is theirs and may use cookies and analytics of its own. That is outside our control and outside this notice.
7. Changes to this page
If we add, remove, or change anything in the tables above, we will update this page and the "last updated" date at the top. [FACT NEEDED: whether advance notice of changes to this notice is given to distributors, and how much]
8. How to contact us
Questions about anything on this page:
- Email: [NOTICE EMAIL]
- Support: [SUPPORT EMAIL]
- Post: [LEGAL ENTITY NAME], [PRINCIPAL ADDRESS]