Skip to content
UK SRSThe UK Sustainability Reporting Standards, ESOS, SECR and TCFD, read against the published text.HUBUK SRS GuideAn independent reference guide to UK SRS, ESG, TCFD, SECR, ESOS and the global standards.Global Reporting StandardsSustainability reporting standards worldwide: ISSB, the EU CSRD after Omnibus I, California SB 253 and SB 261, and UK SRS.UK SRS StandardsUK SRS S1 and S2 at the provision: reliefs, comply or explain, and the FCA statements.ESOS QuestESOS Phase 4 in depth: qualification, the audit, sign-off, action plans and penalties, read against the Regulations.SRS EngineeringThe data build behind a UK SRS report: metrics, owners, controls and timing.SRS ReportWhat a UK SRS report contains, how it is assembled, and how to read one.UK SRS ReportAnalysis and commentary: CDP, the DESNZ emission factors, SECR and ESOS, with every figure cited.UK SRS NewsThe cluster's news publication, and what a UK SRS report contains.UK SRS DeliveryTemplates, costs, ESOS delivery guides and readiness assessment.UK SRS FinanceFinanced emissions, PCAF and IFRS S1/S2 for banks, insurers and asset managers.YOU ARE HERESECRStreamlined Energy and Carbon Reporting: deadlines, thresholds, eligibility and guidance.Carbon CreditsCarbon credit ratings, risk analysis, valuation and market structure.Environmental RegimesThe eight UK environmental reporting regimes, their thresholds, deadlines and regulators.UK SRS ServicesThe services arm: ESOS, SECR, net zero and sustainability consultancy.

Legal

Privacy policy: what we measure, and nothing more

This page describes exactly what UK SRS Finance measures and stores.

Last updated 1 October 2026.

Analytics

Analytics, and cookies only after you say yes

This site uses Plausible Analytics to measure aggregate traffic, under the site domain uksrs.finance.

The Plausible script is not loaded at all unless you accept the banner.

If you reject it, or never answer, nothing is fetched from Plausible and no visit is counted.

Plausible sets no cookies and no cross-site identifier; it receives your IP address with the request, as any server does, and uses it only to count a visit without storing it.

This site also loads Snitcher on every visit: it uses your IP address to identify the organisation you are visiting from, and records which pages that visit viewed.

Until you accept the banner, Snitcher stores nothing on your device and sends no persistent identifier; if you accept, it sets its cookies and a persistent visitor ID so it can recognise a returning visit.

If you accept and later change your mind, clearing the stored choice stops the script loading on your next page view; a script already running on the page you are on cannot be recalled.

WhatWhenWhere it lives
Plausible analyticsOnly after you accept the bannerPlausible’s servers, aggregate only
Snitcher organisation lookupEvery visit; its cookies only after you acceptSnitcher’s servers
Your banner answerWhen you answerYour browser’s local storage
Cal.com booking widgetOnly on the booking pageCal.com
Your emailIf you write to usOur inbox

Local storage

One entry, on your device

Your answer to the banner is saved in your browser’s local storage under the key cookie-consent, not in a cookie.

That entry stays on your own device, is never sent to us, and contains no personal data — only whether you accepted or declined.

The cookie notice, word for word

We count page views with Plausible and Snitcher. Snitcher sets cookies only if you accept. Until you do, Snitcher still loads but stores nothing on your device and sends no persistent identifier, though it can see your IP address. Snitcher also identifies the organisation you are visiting from, using your IP address, and records which pages it viewed, so we can see which organisations are interested in our work. Plausible does not load at all unless you accept. Whichever you choose, your answer is kept in your browser, so we do not ask again. Signing in happens on uksrs.org.uk, where an account holds your name and surname, email address and organisation, and your activity and conversations in the member app.

Booking a call

The booking page runs Cal.com

The book a call page embeds a scheduling widget from Cal.com, a third-party booking service.

Loading that page runs Cal.com’s own script, which can set its own cookies to operate the booking calendar.

That is separate from, and not covered by, the analytics above; Cal.com’s own privacy policy says what it collects.

Accounts

There is no account on this site

UK SRS Finance has no sign-in, no registration and no member area, so nothing here creates an account and we hold no database of visitor details.

The account for this family of sites lives on uksrs.org.uk, and what an account holds is set out in that site’s policy: uksrs.org.uk/privacy-policy, and summarised in the next section.

Sign-in cookies are set by uksrs.org.uk on its own domain; none of them is set on, or read by, this site.

If you email us, we hold that email in order to answer it; no fixed period is set for deleting it, and we will delete it if you ask.

Signing in

If you sign in on uksrs.org.uk

This site has no sign-in of its own.

The sign-in link in the header takes you to uksrs.org.uk, where the one account for this family of sites is made and held by Fractional Quest Ltd.

Signing in there does not sign you in here: no cookie crosses from uksrs.org.uk to this site.

If you make an account, it holds your name and surname, your email address, your organisation, and your activity and conversations in the member app, including what its assistant remembers.

Your sign-in

Your email address, the name you gave when you signed up (your email address stands in for it if you left it blank, or the name on your Google account), whether your address is verified, how you sign in (with a password or with Google), and your signed-in sessions, which the sign-in service records with the IP address and browser each came from.

Who processes it. Neon, which hosts the sign-in service and sends the codes. Google, only if you choose to sign in with Google.

How long. Until you delete your account.

Your profile

Your first name, your surname, the name you want to be called, and your photo if you upload one.

Who processes it. Neon, which hosts the database.

How long. Until you delete your data or your account.

Your organisation

The organisation you belong to and your role in it, requests to join, and invitations you send (which hold the colleague's email address). The organisation's own record holds its name, Companies House number, email domain and logo.

Who processes it. Neon. Companies House, when you search for your company: that sends the company's name or number to the public register, and nothing about you.

How long. Your membership until you delete your data. An invitation nobody answered is deleted 90 days after it was sent, and a revoked one 30 days after it was revoked; an accepted one is kept as the record of how that person joined.

Your company record

The company you confirmed and the figures you give or tap to confirm (headcount, turnover, balance sheet, year end and others), with the history of every change, and which version of the workspace terms you ticked.

Who processes it. Neon. If you ask the assistant to read your company's filed accounts, Interfaze reads that public document from Companies House to pull out the figures; nothing about you is sent. If your organisation switches on its API or a webhook, the organisation's record (not your name) goes to whoever holds its key, or to the address it sets.

How long. Until you delete your data or your account.

Your activity and conversations

Your messages to the assistant and its replies, your threads and their titles, what you kept in your working file, your plan board and its history, the steps behind each reply, and the text of any tender you upload (never the file itself).

Who processes it. Neon stores it. Vercel hosts the workspace and Railway runs the assistant. Each message, with the context the assistant needs, goes through the Vercel AI Gateway to the model that writes the reply (by default Anthropic's Claude).

How long. Until you delete your data or your account.

What the assistant remembers

Your own words, and the values you confirmed, held as a memory graph so the assistant can recall them in a later conversation. The assistant's replies are not sent to it, and neither is the text of a tender.

Who processes it. Zep, our memory provider.

How long. Until you delete your data or your account; it is erased first, before anything else.

Company look-ups and Slack

When the assistant looks your company up in public sources, the company's name and website, which go to a search provider; nothing else about you is in the search. If your organisation connects Slack, the link between your Slack user and your account, and the Slack threads the assistant answers in.

Who processes it. Exa and Tavily, the search providers. CopilotKit, which relays Slack messages to the assistant and holds those threads. Slack holds the messages under your organisation's own agreement with Slack.

How long. The Slack link and the relayed threads until you delete your data or your account.

Service records

Traces of what the product did (timings, which tool ran, errors, and your account and thread IDs, but not the content of your messages), request logs (IP address, browser, page and time), counters of how many messages your account sent in a minute and in a day, and, if your organisation uses the API, a log line and a counter per request with its IP address.

Who processes it. Pydantic Logfire (traces), Vercel and Railway (request logs), Neon (the counters and the API log).

How long. API request lines for 90 days. Traces and request logs for the periods Logfire, Vercel and Railway set. The counters have no deletion period set yet. None of these is deleted with your account.

That is a summary of the account; the full notice, with the purpose and lawful basis of each item, is the uksrs.org.uk privacy policy.

You can do each of these yourself, in Settings on uksrs.org.uk:

  • See and correct: every figure on your company record can be edited, and the old value stays in the history.
  • Export: Settings → Privacy → Export as JSON downloads your email, profile, organisation and company record. It does not include your conversations or the assistant's memory; ask us for those and we will send them.
  • Delete your data: Settings → Privacy → Delete everything we hold about you erases every store in the account, the assistant's memory first. It leaves your sign-in, so signing in again gives you an empty account.
  • Delete your account: Settings → Account → Delete account does all of that and then removes your sign-in. If the sign-in service refuses that last step, the screen says so and you can ask us to finish it.

For anything else about your account, write to hello@uksrs.org.uk.

Your rights

Your rights, and how to use them

Plausible, and Snitcher’s cookies and visitor ID, rest on your consent (UK GDPR Article 6(1)(a)), which you give or refuse on the banner; Snitcher’s organisation lookup from your IP address on every visit, and hosting logs, bookings and emails rest on our legitimate interests in knowing which organisations read the site, running a secure site and answering what you asked us for (Article 6(1)(f)).

You can ask to see, correct or delete what we hold about you, or object to how we use it, by emailing hello@uksrs.org.uk.

If you are unhappy with our answer, you can complain to the Information Commissioner’s Office.

Controller

Who the controller is

Fractional Quest Ltd, company number 17322105, 71–75 Shelton Street, London WC2H 9JQ.

Questions about this policy can be sent to hello@uksrs.org.uk.

Book a free consultation