Security

How we protect books, payroll and tax data.

Written plainly, and limited to what is true today. We do not hold a formal security certification yet. When we do, it will be listed here.

Security & compliance

Built-in security.

Records are encrypted, bank feeds are read-only, and every change is logged. The controls turn with the mark as you move.

In place today

FinanceBee is run by FINANCE BEE TECH LIMITED, company 17253067, VAT GB5266666074. This page complements the Privacy Policy.

Encrypted connections

Sites are served over HTTPS with TLS certificates, behind Cloudflare.

Encrypted secrets

HMRC, bank and connected-app tokens and filing passwords are encrypted before they are stored.

Two-step verification

Authenticator app, ten recovery codes, optional 30-day trusted device. Five wrong codes lock the step for 15 minutes.

Separated client data

In FinanceBee Accounts the database keeps each organisation's records apart. The service will not start if its login could bypass that rule.

Hosting

The platform and databases run on servers we operate at DigitalOcean.

New location alerts

If the account is signed in from an address it has not used, we email you.

HMRC, MTD and RTI

How your filings connect to HMRC, step by step.

  1. Step 1

    Sign in with HMRC

    You connect through HMRC's own sign-in. We never see your Government Gateway password for Making Tax Digital.

  2. Step 2

    HMRC issues a token

    HMRC gives us an authorisation token, which we encrypt.

  3. Step 3

    Fraud-prevention headers

    The headers HMRC requires are sent with each request. What is sent is listed in the Privacy Policy.

  4. Step 4

    Payroll RTI and CIS

    Government Gateway credentials used for payroll RTI and CIS are encrypted.

  5. Step 5

    Recorded in an audit log

    Each submission is recorded in an audit log.

Sub-processors

These companies process data so the platform can work. Some receive data only when you connect them yourself.

FinanceBee sub-processors
ProviderWhat it does
DigitalOceanHosting: the servers and databases the platform runs on.
CloudflareDNS, content delivery and protection against attacks. Web traffic passes through its network.
StripeSubscription billing. Card details go to Stripe, not to our servers.
ResendSending account emails such as sign-in links, security alerts and notices.
YapilyOpen banking bank feeds, with your consent. Only when you use or switch on this feature.
AnthropicReading uploaded documents and suggesting how transactions might be categorised.
WhatsApp (Meta)Receipts you choose to send to Receipt Sync by WhatsApp. Our WhatsApp gateway runs on our own server. Only when you use or switch on this feature.
Google AnalyticsWebsite usage statistics, only if you accept analytics cookies.

UK GDPR: for the business records you keep, you are the controller and we are your processor. Processing terms sit in the Terms.

Reporting a security issue

If you think you have found a weakness, send a report below. Include clear steps to reproduce it. We read every report.

  • Only test against your own account and data.
  • Do not run denial of service, spam or social engineering tests.
  • Give us a reasonable time to fix the issue before you tell anyone else.

Security report

Tell us what you found

Thanks. Your email app should open with the report ready for [email protected].

Opens email to [email protected]. Attach files there if you added any.