Security at TradersFlow

Security is treated as an engineering discipline, not a checkbox. Every change to TradersFlow goes through code review with security considerations. We follow the principle of least privilege across our codebase and infrastructure.

• Secure-by-default configuration for every new service and table.
• Automated dependency scanning to catch vulnerable libraries early.
• Secrets stored in a managed vault — never in code, never in logs.
• Role-based access controls on all internal admin tooling.

TradersFlow uses managed application hosting plus managed database, authentication and file-storage services configured in a European region. Those providers operate the underlying infrastructure and may use their own infrastructure sub-processors.

Application traffic uses HTTPS/TLS. Precise protocol versions, headers, edge protections, certifications and monitoring coverage depend on the current production hosting configuration and provider controls; contact us if you require current assurance evidence.

Customer data is protected in transit using HTTPS/TLS and by provider-managed encryption at rest. Database row-level security and account-scoped server checks are designed to isolate each account's records; no technical control can be represented as eliminating all risk.

Uploaded photos and documents are stored in isolated, per-account buckets with signed URLs that expire automatically. Passwords are never stored in plain text — only as salted, modern cryptographic hashes.

Every request to a protected resource is checked on the server against the authenticated session — we never rely on hiding UI as a security measure. Database row-level security and server-side permission checks both have to pass before any read or write is allowed.

Optional sign-in with Google delegates authentication to a provider with a strong, mature security model, including support for hardware-backed multi-factor authentication. Suspicious sign-in attempts are rate limited by our authentication provider. You can sign out from your account settings at any time, and you can permanently delete your account and data from Settings → Account & Data.

Subscription billing is powered by Google Play Billing, with RevenueCat, Inc. as our subscription management layer. Card details are entered directly into Google Play — they never touch our servers. We only store a Google Play purchase reference and a high-level subscription status.

Subscription state — active, trialing, past-due, cancelled — is reconciled from Google Play and RevenueCat via signed webhooks (see next section), so what you see in the app reflects what Google Play holds. Invoice payments to you are made by your customers directly by bank transfer; TradersFlow never holds or processes customer funds.

TradersFlow processes webhook events from Google Play and RevenueCat for subscription updates. Every incoming webhook is verified against its signing secret before any business logic runs. Unsigned, expired or tampered events are rejected. Processed events are logged so we can reconcile any discrepancy and detect duplicates.

The TradersFlow admin area uses server-side role and permission records. Access is checked on the server rather than relying on hidden interface controls, and the implementation deliberately avoids hardcoded owner-email privileges.

In limited support cases, an authorised TradersFlow administrator can sign in to your account as you, using a temporary single-use link, to investigate a problem you have reported. This gives the same access you have. It requires a specific admin permission and explicit confirmation, cannot be used on owner accounts by other staff, and every session is recorded in our audit log and can be ended at any time.

Sensitive admin actions — generating a temporary sign-in link, issuing a refund, suspending or reinstating an account, extending a trial, exporting reports — are protected behind explicit confirmation and recorded in the audit log described below.

Each agreement sent to a customer has its own random, non-guessable link code, separate from quote and portal links. The link expires after 30 days, can be renewed (the old link then stops working) or cancelled, and only ever opens that one agreement. Once sent, the wording is locked and fingerprinted; acceptance is only recorded against that exact wording, and accepted agreements cannot be edited. Drawn signatures are stored in a private storage area and shown only through short-lived signed links. Customer IP addresses are not stored with acceptances.

Supported administrative actions are written to a restricted audit log recording the actor, action, affected account or resource and timestamp. Separate service and subscription records may also support investigation. We do not describe every record as permanent or technically immutable.

Transactional emails are logged with the template, recipient, send status and available delivery or engagement events. We use these records to prevent duplicates, investigate delivery and respect available suppression or unsubscribe signals.

Application errors, webhook outcomes, email delivery records and security-relevant events are logged where the relevant service exposes them and reviewed as part of operating the Service. We aim for high availability but do not offer a contractual uptime guarantee or service-level agreement.

We investigate reported security incidents and take proportionate containment, recovery and review steps. Where data-protection law requires notification, we will notify the relevant parties within the legally required period.

If you're a security researcher and have found a vulnerability, we'd like to hear from you. Please email security@tradersflow.co.uk with details and we aim to acknowledge within 5 working days.

We commit to: investigating in good faith, keeping you updated, and not taking legal action against researchers who follow this policy and act in good faith. Please don't access data that isn't yours and don't disrupt the Service for other users.

For anything security-related — questions, concerns, vulnerability reports — email security@tradersflow.co.uk.