Security

Security built to hold the keys to your companies.

LtdPilot’s encrypted vault holds the details that let someone act as your company. That means Companies House authentication codes, Government Gateway logins and tax references. So the product is built in layers, starting with two-factor sign-in, rather than one lock.

Principles

  • Defence in depth

    Hosting security, application encryption, access control and auditing each assume the layer before it might fail.

  • Fewer parties, less risk

    No third-party database service, no analytics, no advertising or tracking scripts. Fonts and assets come from our own servers.

  • The same on every plan

    Two-factor, passkeys, encryption and the audit log are not upgrades. Every customer gets all of them.

The vault

Why authentication codes and personal codes do not belong in a spreadsheet

A company’s authentication code authorises filings in its name, so anyone who holds it can act for the company. In a spreadsheet or an inbox, everyone with the file can read it. It is copied into every backup, and nobody can tell who looked.

  • Each code encrypted on its own with AES-256-GCM, beside the company it belongs to.
  • Masked until you prove it is you again. The most sensitive need your authenticator or a passkey.
  • Every reveal in the audit log: which code, who and when, but never the value.
Revealing a stored authentication code asks for your authenticator code first; every other credential stays masked.

Controls

What protects your data, in plain English.

Six groups of controls protect your account and your companies.

Signing in

  • Passwords are never stored. Only a one-way scrypt hash is kept, with a unique random salt for each account.
  • Two-factor authentication with any authenticator app, with single-use recovery codes stored only as hashes.
  • Two-factor is always required for the administrator. Nobody can reveal a stored credential, manage users, change settings or restore a backup without it.
  • Passkeys: Face ID, Touch ID or Windows Hello, verified by the application itself rather than an outside identity service.
  • Continue with Google is optional. Two-factor authentication still applies when you use it, just as it does after a password.
  • Sign-up confirms your email address with a link that works only when you press its button. An email scanner cannot confirm an account for you.
  • Sign-in attempts are rate-limited, with a temporary lockout after repeated failures. Error messages don’t say which part was wrong.

Sessions

  • Server-side sessions: the browser holds only a random token in a secure, HttpOnly cookie that scripts cannot read.
  • Sessions end after one hour of inactivity, and after twelve hours regardless.
  • The session identifier is replaced at sign-in, so a token planted before sign-in is worthless after it.
  • Sign out of one device or every device; administrators can revoke sessions.
  • Sensitive actions require you to have proved who you are within the last five minutes.

Encryption

  • Every vault value is encrypted on its own by the application with AES-256-GCM. That covers authentication codes, Government Gateway logins, UTRs and personal codes.
  • Uploaded documents are encrypted too. Each is bound to its own company and record, so an encrypted file moved elsewhere will not decrypt.
  • Separate keys for separate purposes are derived from a master key kept outside the data store. The format supports key rotation.
  • Backups are encrypted archives, useless without the key. All traffic is served over HTTPS.

Access control

  • Each person sees only the companies they own or have been assigned, in every list, search, report, document download and calendar export.
  • A company outside your access is reported as “not found”, so its existence is never confirmed to someone who shouldn’t know.
  • Access to confidential values is a separate grant for each company.
  • Permissions, not job titles, decide what each role can do. They are checked on the server for every request.

Documents

  • Your filename is never used as a storage path. Files are stored under identifiers the application generates.
  • File type and extension must agree, and size is checked against the bytes actually received.
  • Downloads and in-app viewing go through a signed-in route that re-checks permission every time, and each access is logged.

Audit trail

  • An append-only record of sign-ins, failed sign-ins, changes, credential reveals, document downloads, permission changes and settings changes.
  • Audit records say which entry was revealed, by whom and when, but never the value itself.
  • Refused attempts to reach a company outside someone’s access are recorded too.

Privacy by default

Nobody else is watching.

The product contains no analytics, advertising pixels or session-recording tools. This website doesn’t either. It sets no cookies and loads nothing from anyone else’s servers.

  • Confidential values are kept out of logs, URLs, error messages and standard reports.
  • Reports exclude confidential fields unless an administrator chooses otherwise and confirms their identity.
  • WhatsApp alerts, if you switch them on, never contain credentials.
  • Strict browser security headers, including a content security policy, HSTS and protection against framing.

For your security reviewer

Security questions, answered plainly.

No system is impossible to break into, and we won’t claim otherwise. We never trade security for convenience, and we will tell you plainly how each part works.

Are you ISO 27001 or SOC 2 certified?

No. Thinkteq Technology is a small company and has not been through a formal security certification. We will answer your security questionnaire in writing and tell you plainly where we stand on each point.

Can staff see clients’ codes?

Only if you give them that permission for that company. Even then, they must confirm who they are again before a code is shown, and every reveal is written to the audit log.

Can Thinkteq staff see my data?

Only to help you, and never your vault or documents. LtdPilot staff can open a customer’s account for support only after recording a reason. Each support session is time-limited and appears in the customer’s activity log, and stored credentials and uploaded documents stay hidden from staff even then.

Our staff are bound by confidentiality, and Enterprise offers a dedicated instance if you need stronger separation.

Where is my data stored?

On infrastructure run by our hosting provider, inside the application’s own encrypted storage rather than a separate database service. If your firm or your clients need to know where the data lives, ask us. We will confirm the current hosting location and list of sub-processors in writing.

Is there a data processing agreement?

Yes. For the client data you put into LtdPilot, you are the controller and we are your processor. The processing terms required by UK GDPR are part of our terms of service.

What happens if Companies House or email is down?

The application keeps working. Your last good Companies House data is kept and marked as stale, and reminders that fail to send are retried rather than lost.

How do I report a vulnerability?

Email hello@ltdpilot.co.uk with the details, and please give us a reasonable chance to fix the issue before disclosing it. Our contact details are also published in /.well-known/security.txt.

Put your companies somewhere safer than a spreadsheet.

Use LtdPilot with your own companies for 3 days, with every Professional feature, for up to 5 companies and 2 users. The trial costs £1.

£1 for 3 days, then your chosen plan unless you cancel · Cancel any time in the app · Prices exclude VAT

We are here to help you!

Usually replies within a few hours

Hi there! How can we help you today?

Start chat (opens WhatsApp)