Privacy
This page has to be checkable too.
Two different things are described below, and conflating them is how privacy pages usually go wrong: what this website does with visitors, and what the product does with customer data. The website part is short, because the website does almost nothing.
What this site collects
- Request logs
- The server that serves these pages records the request: IP address, user agent, path, timestamp. Kept for at most thirty days, used for security and capacity, and never joined to anything else.
- Appearance preference
- If you switch between light and dark, the choice is written to localStorage under the key fs-theme, in your browser, on your device. It is never transmitted. Clearing site data removes it.
- Subscription form
- The Bulletin form collects a work email and an organisation type. The delivery endpoint is not connected yet, and until it is, the form tells you on screen that nothing was sent anywhere. When it is connected, this page names the provider first.
- Cookies
- None. Not for analytics, not for preferences, not for a consent banner about cookies we do not set.
What is never collected
- No analytics of any kind, first-party or third-party.
- No third-party scripts, fonts, stylesheets, CDN assets or embeds. Fonts are self-hosted and served from this origin.
- No fingerprinting, no cross-site tracking, no advertising identifiers.
- No sale, rental or brokerage of anything about you, to anyone, in any form.
- No account required to read anything on this site, including the public record.
Verify it yourself
The footer of every page claims this site loads no third-party resources. That claim is checkable in about fifteen seconds, so check it: open the network panel of your browser and reload. Every request should be to this origin. That origin is delivered through Cloudflare's network, which carries the connection and is listed under sub-processors below; it adds nothing to the page. There is no beacon, no deferred loader and no second wave after paint, because the page is static and there is nothing to defer.
Customer data
Applies to institutional customers. The security page describes the mechanisms; this is what they mean for the data itself.
- Address books
- Encrypted under a per-customer key, matched through an HMAC index without decryption, and structurally unable to reach the public record pipeline. In a self-hosted deployment they never leave your environment at all.
- Decision and evidence records
- Written for every verdict, content-addressed, append-only, retained for at least five years because that is what an audit needs. Yours to export at any time, in the format we store them in.
- KYC and identity data
- We do not perform KYC and do not want the underlying documents. Where a decision references your KYC outcome, it references your own record identifier.
- Aggregate statistics
- Customer data is not used to improve our models by default. Where a customer opts in explicitly and in writing, the scope is written into the agreement and compensated with a pricing discount. It is never a condition of service and never a default.
Where data lives
For self-hosted deployments, in your environment, under your keys, in the region you chose, with no copy on our side. For managed deployments, in the region fixed at onboarding and named in the contract. This site is served as static files with no database behind it.
Retention
| Data | Kept for |
|---|---|
| Website request logs | Thirty days, then deleted |
| Bulletin subscription | Until you unsubscribe, one click, no login |
| Decision and evidence records | At least five years, contractual, exportable throughout |
| Audit log | Append-only for the life of the agreement, exportable for your own rows |
| Support correspondence | Twenty-four months from last contact |
Sub-processors
The complete list of third parties that can see anything related to you. A provider is named here before it processes anything, not after, and customers get thirty days notice of an addition.
| Role | What it can see | Status |
|---|---|---|
| Static site hosting | Request metadata for this website: IP, user agent, path, timestamp | In use |
| Network delivery and TLS for this website (Cloudflare) | Every request to this website and the page returned: IP, user agent, path, timestamp | In use |
| Email delivery for the Bulletin | Subscriber address and delivery events | Not engaged; named here before the first issue is sent |
| Managed deployment infrastructure | Encrypted customer data at rest and in transit | Not engaged; self-hosted is the default delivery |
Your rights
Wherever you are, and whichever regime applies to you, we will act on these:
- Know what we hold about you and why
- Get a copy in a portable format
- Correct it
- Have it deleted, where no legal retention obligation applies
- Object to a use, and withdraw a consent you previously gave
- Complain to a supervisory authority without going through us first
Write to privacy@4shock.xyz. We will ask enough to be sure you are you and no more, and aim to answer within thirty days. You will never be asked to create an account in order to exercise a right.
One distinction that matters for self-hosted deployments: the customer is the controller of the data in their own environment, and we have no access to it. Requests about that data go to them, not to us, and we will say so rather than pretend to a power we do not have.
Changes
Material changes to this page are announced in the newsroom with the reason, before they take effect where that is possible. The revision date is at the top of the page.