Quarry Hosting cookie policy
- Last updated
- Oct 16, 2026
The short version
- We use only what is needed to keep you signed in and the site working.
- We set no advertising or tracking cookies, and no ads run today.
- Our visitor counter, if we switch it on, sets no cookies and asks you first.
- You can block or delete cookies in your browser. If you block the essential ones, you cannot sign in.
1. What we keep in your browser
In short: two cookies for sign-in, and a few small items on your device. All are essential.
Many of our players are young, so we keep this short. This is everything our site and panel keep in your browser, what it does and how long it stays. Essential means the site cannot work without it, so the law does not ask for your consent.
| Name | What it does | How long | Essential |
|---|---|---|---|
__Host-sh_session (cookie) | Keeps you signed in to your account and the panel. Only our own site can read it, and scripts on the page cannot | Up to 30 days. It ends sooner after 7 days without use, or when you sign out | Yes |
__Host-sh_oauth (cookie) | Only while you sign in with Discord, Google or GitHub: links their answer back to the sign-in you started, so nobody else can finish it | 10 minutes, and removed once you are signed in | Yes |
site.cookies (stored on your device) | Remembers that you closed the cookie notice, or your answer about the visitor counter, so we do not ask again | Until you clear your browser's site data, or press Cookie settings at the bottom of the page while the counter is on | Yes |
panel.console.history. and a server ID (stored on your device) | Your last commands in a server's console in the panel, so you can repeat them with the arrow keys. It never leaves your device | Until you clear your browser's site data. At most the last 100 commands | Yes, for the console you use |
srv-setup-hidden: and a server ID (stored on your device) | Remembers that you hid a server's setup checklist in the panel | Until you clear your browser's site data | Yes, for the panel you use |
srv-ai-feed-seen: and a server ID (stored on your device) | Remembers when you last looked at a server's AI activity, so new items stand out | Until you clear your browser's site data | Yes, for the panel you use |
panel.entered (stored in this tab only) | Remembers that the panel already took you into your one server after you signed in, so it does it once per visit | Until you close the tab | Yes, for the panel you use |
menu-editor.favourites and menu-editor.recent (stored on your device) | The items you starred and the ones you used last in the menu editor's item picker, so they are easy to find again. They never leave your device | Until you clear your browser's site data. At most 48 items in each | Yes, for the menu editor you use |
srvhost.menu-tabs. and a server ID (stored in this tab only) | The menus you opened in the menu editor, so you can switch between them with the tabs above it. Only the menus' short ids are kept, and they never leave your device | Until you close the tab. At most 8 menus | Yes, for the menu editor you use |
invite-link (stored in this tab only) | Keeps a team invite you opened while you sign in, so you land on it afterwards | Until you close the tab, or the invite is used | Yes, for the invite you opened |
sh-help-bot (stored in this tab only) | Your open chat with the help bot, at most the last 20 messages, so it survives moving between pages | Until you close the tab, sign out or start a new chat | Yes, for the help bot you use |
On a test machine the two cookies are called sh_session and sh_oauth. Our staff sign in to a
separate admin site with a cookie of their own.
Protection against forged requests uses no cookie of its own: the panel asks for a token that comes from your sign-in and sends it with every change.
The help bot uses your sign-in cookie to know who you are when you are signed in. It sets no
cookie of its own. Your open chat stays in this browser tab only (sh-help-bot above), and we keep
no copy of it.
2. What we do not use
In short: no tracking, no profiling, and no outside analytics.
- No advertising or tracking cookies, and no social media buttons that follow you.
- The visitor counter. We may count page visits on our public pages with our own counter, which runs on our own machine. It sets no cookies, collects no personal details and sends nothing to an outside analytics company. It is not essential, so when it is switched on the banner asks you first, with Accept and Reject buttons of the same size. It only runs after you press Accept. You can change your answer at any time with Cookie settings at the bottom of every page, which shows the banner again.
3. Ads
In short: no ads run today. If they ever do, this page will say so first, and you will get a choice.
A few public pages may show light ads one day. They would never be personalized, and they would never appear in the panel or in game. We would ask the ad company to treat the site as child-directed, which turns off interest-based ads. Before any ad runs:
- this page will list each cookie or identifier the ad company sets, its purpose and how long it stays;
- if you are in the EU, the UK or Switzerland, a consent tool will ask for your choice before any ad cookie is set, with Accept and Reject of equal weight, and refusing will not stop you using the site or the panel;
- the Privacy policy will name the ad company.
4. Other sites
In short: the sites we send you to set their own cookies.
- Payments: checkout runs on Link's own site (a Stripe company), which sets its own cookies under its own policy. We set none for it.
- Discord, Google and GitHub sign-in: signing in with them takes you to their own sites, which have their own cookies and policies.
- Our status history: the status page links to UptimeRobot's page, which has its own cookies and policy.
- Owners' own stores: an owner's Tebex store is Tebex's site, with its own cookies and policy.
- Pages from owners' web plugins (like maps) are served on a separate pages domain. Any cookie they set belongs to that server's owner, not to us, and our site cannot read it.
5. Your choices
In short: you can block or clear cookies any time. The essential ones are needed to sign in.
You can block or delete cookies in your browser's settings. If you block the essential ones, you cannot sign in and some pages will not work. Clearing your browser's site data for our site removes everything in the table above. The only optional thing we ever ask about is the visitor counter, and Cookie settings at the bottom of the page changes that answer. Saying no costs you nothing.
6. Changes and contact
In short: this page changes when a cookie or stored item is added, and it says so below.
If we add a cookie or a stored item, we update the table before it goes live, and any optional one asks you first. Questions: email [email protected]. See also the Privacy policy.
What changed
Updated 2026-10-15:
- The list now has the panel's setup checklist, AI activity, team invite, first-visit and menu editor items, and the help bot's open chat, which stays in your browser tab. The welcome tour item is gone with the tour.
- Google sign-in, Link's checkout and our status history are in the list of other sites.
The first public version of the three-page set checked the list against the code, said which items are essential, and said what we would do before any ad ran.