Security

Most of the systems we build handle money, contracts and other people's details. This is how we treat that.

• Your cloud, not ours. Wherever practical, systems run in accounts that belong to you. You hold the keys. If we disappeared, you'd still have everything.
• The software never moves money. Nothing we build sends a payment. It prepares, checks and records. A person presses pay, in your bank, the way they do now.
• AI reads, it doesn't decide. AI can pull a figure off a document. It never works out what's owed or approves anything. Every amount is checked against a source and by a person before it's acted on.
• Bank details don't come from documents. Where a system holds payee details they're entered by a person and confirmed separately, not read off an invoice.
• Access. We use named accounts rather than shared logins wherever the platform allows, scoped to what the work needs. When the work ends we hand over and remove our access on request.
• Credentials. Keys and passwords are stored in secret managers, never in code or documents. We ask that anything we've handled is rotated at handover.
• Backups. Systems are designed so nothing is deleted outright. Backups depend on the platform you're on and are agreed per project.
• Before go-live. A system typically gets a review of who can reach what before it goes live, and fixes go in first.
• If something goes wrong. Tell us. If we find a problem on our side that affects your data, we tell you without undue delay so you can meet your own reporting duties, and we say what we're doing about it.
• Other people's services. Systems we build usually rely on third-party providers: hosting, email, and AI models from companies such as Anthropic, OpenAI or Google. We tell you which ones your project uses and where they process data before it goes live.

This page describes how we work. Specific commitments for your project are in your written agreement.

Trading

Edward Togher, trading as Highcroft Digital

Based

Surrey, UK

Email

edward@highcroftdigital.com