Security at Basefund

Protecting your account

Most account takeovers start with a stolen or reused password. Basefund has neither.

• One person, one account. Each email address belongs to exactly one account, and a sign-in identity can never be re-linked to someone else’s account.
• Your email address cannot be changed from inside the app. A change goes through our support team, who verify the request with you and re-verify the new address before it takes effect.
• Invitations and sign-up links are single use and work only for the person they were sent to.
• We never ask for a sign-in code, and our email always comes from notifications@secure.basefund.com. The email guide shows how to recognize it.
• Automated attacks are stopped at the edge: Cloudflare challenges bots before they reach us, and requests that look like scanning or probing are blocked and their source temporarily banned.
• You can see every device you have trusted, and remove any you do not recognize, from your profile at any time.
• Every sign-in is recorded with the method used and the device and network it came from, so our team can investigate anything unusual with you.

Your organization stays in control

Your data belongs to your organization, not to any individual user, and your organization decides who can see and change it.

• Your organization’s administrators decide who has access and what each person can do, and can change that at any time.
• Access ends the moment someone is removed, and access can carry an end date that switches it off automatically, which suits contractors, auditors and seasonal staff.
• An organization can never be left without an administrator, so control of its data never rests with a single person who might leave.
• Every approval, edit and upload is attributed to the individual who made it, and a history of changes is kept.
• Sharing a transaction with another firm gives that firm read access only; nobody outside your organization can change your records.
• Basefund staff have no standing access to your workspace. When support needs to act inside it, they do so through an explicit, recorded access that is switched on for the task and off afterwards. Everything they do is recorded in an audit trail under their own name, and that record is kept after their access ends, so every action is attributed to a person, including our staff.

Network and infrastructure

Basefund runs on Google Cloud behind Cloudflare, and nothing reaches our servers without passing through Cloudflare first.

Every request to app.basefund.com and api.basefund.com is inspected at Cloudflare’s edge before it reaches us: managed web application firewall rules screen for known attack patterns, bot detection challenges automated traffic, and requests from countries where we have no customers are turned away. Our servers accept connections only from Cloudflare’s own network. Anything that tries to reach them directly, bypassing those checks, is dropped at the network edge.

Inside our environment, services are isolated from one another by default. Each part of the platform can talk only to the parts it needs, and the application reaches the production database over a private, encrypted link inside our cloud network, never across the public internet. Every connection to the database must be encrypted.

Everything is encrypted in transit with TLS 1.2 or later, and browsers are told to use HTTPS only. Our infrastructure is defined in code and deployed through a reviewed change process, so production is never changed by hand, and every change is recorded.

Compliance and transparency

Our security program is monitored continuously against the SOC 2 framework, and our controls, policies and progress are published at trust.basefund.com.

Independent penetration testing is performed annually. We review our network boundary and access rules on a fixed annual cycle, apply security updates frequently through the same reviewed change process as everything else, and run automated compliance checks against our cloud accounts every day.