Security Policy
Last updated: 11 October 2026 · Owner: the directors of FLUERE TERMINAL LTD · Reviewed at least yearly and after any incident
1. Scope
This policy covers Capital Fluere (the Fluere Terminal web application, its API and the data it holds), the company accounts used to run it, and the computers the directors work on. It applies to everyone who works on the service. The company has no premises, no servers of its own and no corporate network: the service runs entirely on Cloudflare's edge, and the two directors work from encrypted laptops.
2. Data classification and handling
- Public: market data, news and the pages of the website. No restrictions.
- Member: email address, handle, profile, layouts, notes, diary, watchlists, chat and direct messages, dispatches. Held only in the service's own storage, reachable only through the API with a valid session, shown to other members only as the privacy policy describes.
- Sensitive: password hashes, two-factor keys and recovery codes, session tokens, broker access tokens, and the secrets the service itself runs on. Never logged, never emailed, never placed in a URL, never held in the browser beyond the HttpOnly session cookie, never exported. Encrypted at rest as set out in section 4.
- Payment: card details are collected and held by Stripe. The service never sees or stores a card number.
Member data is used only to run the service. It is not sold, not shared with advertisers and not passed to the market-data providers. Exports from storage are made only to answer a member's own data-access request or a legal obligation, and are deleted once answered.
3. Access control and privileged access
- Access to production (Cloudflare, GitHub, Stripe, the email providers, the domain registrar) is limited to the two directors, each under a named account with two-factor authentication turned on. There are no shared logins.
- Administrative routes in the API are gated on a fixed list of administrator addresses checked on every call, on top of the ordinary session, and are rate-limited like everything else.
- Service secrets (session key, encryption keys, API keys, OAuth client secrets) are held as Cloudflare Worker secrets, set through the dashboard. They are not in the source code, not in the repository and not on any laptop in the clear. The worker source itself is kept out of the public repository.
- Access is removed on the day a person stops working on the service, and every secret that person could have seen is rotated.
- Members get optional two-factor authentication (authenticator app) with one-time recovery codes, and a list of remembered devices they can clear.
4. Encryption at rest and in transit
- In transit: every connection to the website and the API is HTTPS, with HSTS set so a browser will not fall back to plain HTTP. Calls from the service to its providers (market data, broker, email, Stripe) are HTTPS only.
- At rest: all stored data sits in Cloudflare's storage, which is encrypted at rest. On top of that, the service applies its own encryption to the most sensitive items: two-factor keys and broker access tokens are sealed with AES-GCM under keys derived from worker secrets, so a copy of the storage alone cannot read them. Passwords are stored as salted PBKDF2 hashes; recovery codes as one-way hashes.
- Sessions: an HttpOnly, Secure, first-party cookie. Rotating the session secret invalidates every session at once, which is the first step of any credential incident.
- Broker tokens: only ever opened inside an API handler, for the one call the member asked for, and never sent to the browser. Deleted when the member disconnects, the broker revokes, or the account closes.
5. Vulnerability and patch management
- There is no operating system, web server or database for us to patch: the runtime is Cloudflare Workers and Pages, which Cloudflare maintains and patches. Our exposure is our own code and its few dependencies.
- Dependencies are kept deliberately few. Third-party code served to members is vendored, version-pinned and self-hosted; a version bump is a reviewed change like any other.
- Every change runs an automated validation suite before it is deployed, including checks for the security properties above (no raw credential in a URL, sealed secrets, gated admin routes, rate limits present). A change that fails is not shipped.
- Every API route carries a per-caller rate limit and a request-body size cap, and public routes are limited per address, so an abusive client is throttled before it costs anything.
- Security reports can be sent to contact@capitalfluere.com. A confirmed vulnerability in our code is fixed and deployed with priority over all other work: within 24 hours where it exposes member data, otherwise within 7 days.
6. Incident response and disaster recovery
Incident response. An incident is any confirmed or suspected unauthorised access to member data, loss of a secret, or a defect that exposes one member's data to another. On discovery:
- Contain (immediately): rotate the affected secrets, which also ends every live session; revoke affected broker tokens at the broker; disable the affected route if needed.
- Assess (within 24 hours): establish what data, which members and what window, from Cloudflare's logs and the service's own records.
- Notify: the ICO within 72 hours where UK GDPR requires it; affected members without undue delay, in plain language, with what happened and what they should do; any partner whose integration is affected (for example a broker whose tokens were involved) at the same time.
- Review (within 14 days): a written account of cause, timeline and the change made so it cannot recur, kept with the company's records.
Disaster recovery. The service has no single machine to lose. The front end and all code are in version control and redeploy from the repository in minutes; the API and its storage are replicated across Cloudflare's network, with no region to fail over. Member layouts are also cached in the member's own browser, so a storage outage does not lose a workspace. Recovery objective: the service back within 4 hours of a platform outage ending; data loss limited to the replication window of the storage provider.
7. Physical security
There are no company premises, servers or network equipment. The physical controls that apply are those on the directors' computers: full-disk encryption on, automatic lock on a short idle, operating-system updates applied automatically, the built-in malware protection on, and no company credential kept on a shared or family machine. A lost or stolen laptop is treated as an incident under section 6: its sessions are revoked and the secrets it could have reached are rotated the same day. Cloudflare's and Stripe's own data centre controls cover the hosted side.
8. Vendor risk management
We use a small, fixed set of providers, each for one job. Before adding one we check what data it would hold, that it offers a data-processing agreement, and its own security attestations; we prefer providers with a current SOC 2 or ISO 27001 report, and every provider below that holds member data publishes one.
- Cloudflare: hosting, API runtime, storage, and the model behind the written summaries on some panels. Holds all member data.
- Stripe: payments. Holds card data; we hold none.
- Resend (account emails) and Brevo (marketing emails, opt-in only): hold email addresses.
- GitHub: source code of the front end. Holds no member data and no secrets.
- Market-data providers: receive the symbols the service requests, never who asked.
- A member's broker, if they link one: receives only the orders the member enters, over the broker's own OAuth, under the broker's terms.
The list is reviewed yearly. A provider is dropped if it loses its attestation, suffers a breach it does not disclose promptly, or changes terms in a way that would widen what it holds.
9. Contact
Security questions and reports: contact@capitalfluere.com, or FLUERE TERMINAL LTD, 37 Newton Road, Lewes, England, BN7 2SH.