CAPITAL FLUERE← back

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

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

4. Encryption at rest and in transit

5. Vulnerability and patch management

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:

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.

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.