Trust & security

What this site holds, and who sees it.

Written for the security or procurement review a tax function runs before buying software. Every answer describes how the site actually works, and each control can be checked from outside.

Updated 18 November 2026
Noneclient figures stored
Nonecookies
Nonepasswords stored
Nevercard data on this site

What is held, exactly

WhatExactly what is heldWhyWhereKept
Licence recordThe email you bought with, the licence code, the organisation name, the issue and expiry dates, and how often the code has been checkedTo issue the licence and confirm it when you use itNetlify (licence store)The licence term, then as long as tax records require
Change-alert subscriptionEmail, and optionally your role and the jurisdictions you choseTo send the alerts you asked forNetlify (subscriber store)Until you unsubscribe
Contact messageName, work email, company if given, and the messageTo replyNetlify FormsUntil no longer useful
Figures you type into the toolsNothing — they stay in your browser—Your browser only—
Access register entriesNothing — holders, dates and notes stay in your browser—Your browser onlyUntil you clear them

Who else touches it

  • Netlify — Hosting, serverless functions, the licence and subscriber stores, form handling.
  • None for complimentary licences — No payment is taken, so no payment provider receives anything.
  • Resend — Sends the licence email and change alerts.

That is the complete list. In your browser, a page may contact no outside host at all: there are no analytics scripts, and the Content Security Policy blocks every outside host.

Controls

  • HTTPS only, with HTTP Strict Transport Security for two years across all subdomains.
  • A Content Security Policy that allows no inline script and names every outside host a page may contact; there are none, so no analytics scripts and nothing from outside this site loads.
  • Pages cannot be framed by other sites; referrer data is trimmed; camera, microphone, location and similar browser features are switched off.
  • Fonts and scripts are served from this site. No Google Fonts, no tag manager, no advertising or tracking scripts.
  • Licence codes are checked on the server. The licensed content of the access register is served only after that check and is never published as a file.
  • Payment notifications are verified by signature (HMAC-SHA256) before any licence is issued.
  • Administrative functions are protected by a secret key held only in the hosting environment.
  • There are no user accounts, so there are no passwords to leak. The access register refuses to save anything that looks like a password or PIN.
  • Every build runs an automated audit and browser tests, including a check that no licensed content leaks into a public page, and an accessibility test of every page.
  • Email from this domain is authenticated: SPF and DKIM are published, and the DMARC policy is reject, so mail that only pretends to come from saurabhsatija.com is refused by receiving servers rather than delivered.

Checks you can re-run yourself

AreaResultLast run
Security headersGraded A+ by securityheaders.com17 October 2026Re-run ↗
HTTPSSubmitted to the HSTS preload list, so browsers can refuse plain HTTP outright16 October 2026Re-run ↗
Email spoofingDMARC policy "reject" published for the domain17 October 2026Re-run ↗

How the data itself is sourced, graded and corrected is set out separately: method and corrections. Accessibility: statement.

Certification, stated plainly

The site holds no ISO 27001, SOC 2 or Cyber Essentials certificate. It processes almost no data — no client figures, no accounts — so those frameworks would certify very little. The controls above are what protects you, and each can be verified directly.

Reporting a vulnerability

Email saurabh@saurabhsatija.com. The contact is published in security.txt. Reports are acknowledged within five working days. If an incident affects personal data, the people affected are told by email without undue delay.

Questions procurement asks

Do you store our tax figures or group data?

No. The safe harbour test, the scoping tool and the access register run in your browser. Figures, holders, dates and notes are not transmitted to this site or stored by it.

Which third parties process data?

Netlify (hosting and storage), none (no payment is taken for complimentary licences) and Resend (email). There are no analytics scripts. No others.

Do we need a data processing agreement?

For the tools, nothing of yours is processed on your behalf — it stays in your browser. The licence record is held under the privacy policy, as for any software purchase. If your procurement process still requires a document, ask and it will be provided.

Is there single sign-on or user management?

No. There are no accounts. A licence is a code entered in the browser, covering the tools and the number of users named in the quotation.

Do you hold ISO 27001, SOC 2 or Cyber Essentials?

No. The site holds almost no data — no client figures and no accounts — so those frameworks would certify very little. Each control listed on this page can be checked directly instead.

How do we report a security issue?

Email saurabh@saurabhsatija.com. The contact is also published in /.well-known/security.txt.

See also: Privacy policy · Terms · Refunds