SiteTools Cookie and Browser Storage Policy
Effective date: 6 November 2026
Operator: CloudServe Solutions Ltd, registered in England and Wales, company number 17554555
Privacy contact: privacy@cloudserveuk.com
1. Scope and meaning
This policy covers the public SiteTools website at sitetools.uk, SiteTools Main Management at accounts.sitetools.uk, and the SiteTools Engineers Hub operated by CloudServe. A customer that adds its own tracking or third-party content to a separately managed website or product environment must explain that additional use to its users. CloudServe remains responsible for the SiteTools technologies described here.
Cookies are small browser records. Similar technologies include local storage, IndexedDB and PWA Cache Storage. These can remain on a device after a browser tab closes. This policy explains what the current SiteTools services use and how to clear them.
2. What we currently use
| Service and technology | Purpose | Duration or clearing |
|---|---|---|
| Public sitetools.uk website | The static marketing pages currently set no first-party cookies and use no browser storage for analytics, advertising or preferences. | Not applicable. Ordinary server access logs are described in the Privacy Policy. |
| Main Management STMAINSESSID session cookie | Keeps a Management session and its server-side form protection together. This is required for sign-in, account administration and secure checkout. | Browser-session cookie. Signing out ends the server session. |
| Restricted Management installer STMAININSTALL session cookie | Protects the separate installer route while an authorised operator uses it. | Browser-session cookie scoped to the installer path. Not used for ordinary browsing. |
| Management PWA Cache Storage | Stores the offline notice and public static files such as styles, logo and app icons. It does not store customer, billing, account or admin pages for offline access. | The browser retains the installed app's static cache until it is replaced, the app/site data is cleared, or the browser removes it. |
| Engineers Hub session cookie, with a name beginning sitetools_fahub | Keeps a signed-in Hub session and server-side security state together. The precise suffix can vary by installation. | Browser-session cookie. Sign-out or expiry ends access. |
| Optional Engineers Hub remembered-device cookie | Restores a signed-in session on the selected device. The Hub revokes previous remembered devices when the same company user signs in elsewhere. | Up to 30 days under the current Hub setting, unless revoked or cleared earlier. |
| Engineers Hub local storage | Saves user-entered scratchpad notes, checklists and certain in-browser working values. | Until the user clears the relevant item, signs out where the Hub clears local data, or clears browser site data. |
| Engineers Hub IndexedDB and PWA Cache Storage | Provides requested offline working: static files, permitted page/file snapshots, drafts and queued changes that sync on reconnection. Private snapshots are scoped to the signed-in company/user/device and expire after up to seven days; queued changes may remain until synced or cleared. | Hub sign-out requests a local purge. Browser site-data controls can also remove it. A device that remains offline cannot receive a remote sign-out until it reconnects. |
The Management and Hub session cookies are set with Secure on HTTPS, HttpOnly and SameSite protections. Form tokens are held in the server session and submitted with forms; there is no separate cs_csrf_token cookie in the current Management implementation. A PWA can also use its browser cache without setting a cookie.
3. Payments and other providers
When you move to GoCardless's hosted pages to authorise a Direct Debit, GoCardless may use its own cookies and similar technologies. Its notice applies there. SiteTools does not currently load Stripe card-payment cookies or an optional analytics library on the public website or Main Management.
Server-side sign-in rate limits, transaction records and ordinary web-server logs are not browser cookies. See the Privacy Policy for how personal information is handled.
4. Consent and choices
The current services use the storage above for secure account access or an offline feature the user chooses to use. The public website has no optional analytics or advertising cookies to switch on, so it does not display a consent banner or a “Cookie Settings” control. We will assess consent requirements and provide a choice before adding non-essential tracking or storage. Technologies that are essential to deliver a service requested by the user can be used without prior cookie consent, but must still be explained.
You can block or clear cookies and site data in your browser's privacy settings. Blocking session cookies will prevent sign-in and protected forms from working. Clearing the Engineers Hub's site data will also remove offline drafts and changes that have not yet synced. Connect and sync those changes before clearing its data. Signing out of the Hub triggers its offline-data cleanup; you can also remove an installed PWA through your device or browser settings.
5. Changes and contact
We will update this page when the deployed technologies or their purposes change. For questions or data protection requests, contact privacy@cloudserveuk.com. See the Privacy Policy for further rights and contact information.