Cookies
What SISC Suite keeps in your browser, why, and for how long. This list was made from the product’s code. We use no advertising or tracking cookies.
In effect since 1 November 2026 · Last updated: 11 November 2026
1. What we store
A cookie is a small piece of text a website asks your browser to keep. A website can also keep data in your browser’s local storage or session storage, or keep files for use offline. This page lists all of them, because they do the same job.
This public website sets no cookies. It keeps two short values, the language you pick and your answer to the cookie notice, and while you use the Ask SISC assistant, one value for that browser tab. The SISC Suite app sets two cookies, each only in one case, and keeps more in your browser so that it can work.
We use no advertising or tracking cookies, and nothing listed here is shared with an advertiser. Only with your agreement does this website also count page views, by country and page (section 5).
2. Strictly necessary
Without these, the product cannot sign you in, keep a till working offline, or finish a step you started.
| Name | What it is for | How long | Set by |
|---|---|---|---|
| sisc_trusted_device (cookie) | Remembers a browser you chose to trust at two-step sign-in, so it is not asked for a code every time. | 30 days | The SISC Suite app, only if you tick it |
| sisc_till_device (cookie) | Recognises a till your company registered for SISC POS. | 400 days | The SISC Suite app, on a registered till |
| sisc.refresh, sisc.expires, sisc.refresh.lease | Keeps you signed in on your workspace’s address, and stops two tabs renewing the sign-in at once. | Until you sign out | The SISC Suite app |
| sisc.pos.*, sisc.hr.timeClock.device, sisc.logistics.myRun.queue.v1, IndexedDB sisc-office | Sets up a device and keeps work done offline until it is sent: tills and the customer display, the time clock, deliveries, SISC Library documents. | Until it is sent, or the device is removed | The SISC Suite app |
| sisc.signup.*, sisc.install.wizard, sisc.calendar.oauth, sisc.mail.oauth, sisc.cloud.oauth, sisc.companyMail.oauth | Keeps a form or a sign-in step while you go to Google or Microsoft and come back. | Until the tab is closed | The SISC Suite app |
| sisc-saq-visit | Lets the Ask SISC assistant answer more questions after the first check. | Until the tab is closed | This website |
| Service worker cache | Keeps the app’s own files so that it opens quickly and can be installed. | Until the next update | The SISC Suite app |
3. Your settings
These remember choices you made, in this browser only. Nothing breaks if you clear them: the screens go back to their defaults.
| Name | What it is for | How long | Set by |
|---|---|---|---|
| sisc.locale, sisc.site.lang | The language you chose. | Until you clear it | The app, this website and the help centre |
| sisc.theme | Light or dark. | Until you clear it | The SISC Suite app |
| sisc.site.cookies | Your answer to the cookie notice at the bottom of this website: Accept all or Reject. | Until you clear it | This website |
| sisc.sidebar.collapsed, sisc.tableView.*, sisc.company.navGroups.*, sisc.recent-routes.*, sisc.mail.prefs.*, sisc.productFavourites.*, sisc.banner.*, sisc.boardroom.callDevices.*, IndexedDB sisc.boardroom.backgrounds | How your screens look: menus, table views, recent pages, favourites, notices you closed, call devices and your own call backgrounds. | Until you clear them | The SISC Suite app |
4. Other companies you may meet
On a few pages, another company’s code or page is involved. Any cookies they set are theirs, and their own policies apply. SISC cannot read or change them.
| Who | When | What happens |
|---|---|---|
| Stripe | When you pay by card in Billing | Stripe’s own script, from js.stripe.com, takes the card. Stripe may set its own cookies. |
| Meta (Facebook) | Only when a company administrator connects WhatsApp | Meta’s login window and script load from facebook.com. Meta may set its own cookies. |
| Google, Microsoft | When you connect a calendar, a mailbox or cloud files, or sign in with Microsoft | You sign in on their own pages. |
| PayPal, Stripe Checkout | When you choose to pay on their page | You leave for their page. |
| Cloudflare | Only where it is switched on: the contact form and the Ask SISC assistant on this website | Cloudflare’s check loads. It may keep its own data. |
5. Statistics (only with your agreement)
If you choose Accept all, this website counts each page you open: one count for the page and the country the visit comes from, kept as a total per day. It sets no cookie, stores nothing in your browser for this, and sends nothing that identifies you. Until you choose, and after Reject, nothing is counted.
6. Your choice
When you first open this website, a notice at the bottom of the page offers two buttons. Accept all switches on the page-view count in section 5. Reject keeps it off. Either answer closes the notice, and this browser remembers it (sisc.site.cookies, in section 3).
Neither button switches off what is in section 2 or your settings in section 3: the website and the product need them to work.
To change your answer, choose Cookie settings at the bottom of any page of this website.
7. How to clear them
- In most browsers, open Settings, then Privacy (or Privacy and security), then the option to clear cookies and site data, and choose this site.
- Clearing them signs you out of SISC Suite. On a till, it also removes the till’s registration and any sales not yet sent, so send offline sales first.
- A private window keeps nothing after you close it.
8. Questions
Our Privacy Policy explains what we hold and why. Questions go to [email protected].