Legal
Security
Last updated: 27 September 2026
Fun In Raising holds data about fundraisers, their performance, and sometimes where they work. We treat that data as sensitive. This page describes how we protect it.
Each organisation is kept separate
Every customer organisation has its own address. Its data is separated from every other organisation by row-level security in the database itself, so a mistake in application code cannot show one organisation's data to another. Our automated tests check this against a real database and fail if the separation is switched off.
Accounts and sign-in
- Passwords are stored with argon2id, a slow, salted hash designed to resist cracking.
- Two-step verification with an authenticator app is required for administrators, operations and campaign managers, and platform owners.
- Repeated failed sign-ins are rate limited per account and per network address.
- Session cookies hold a random value. We store only a keyed digest of it, so a copy of our database cannot be used to sign in.
- A suspension or role change takes effect on the person's very next page load.
- Sensitive actions, such as changing roles or suspending an account, ask for your password again if you last confirmed it more than 10 minutes ago.
Access inside an organisation
Access is based on roles and scope. A fundraiser sees their own data. A team leader sees their own team. Managers see their regions or campaigns. Charity client viewers see only their own campaigns and no staff data. Every change is written to an audit log that cannot be edited.
Our staff
Fun In Raising platform owners manage customer accounts but cannot read an organisation's staff or performance data. Their database access does not include it.
Location data
Location sharing is being rolled out. When an organisation turns it on, it runs only between clock-in and clock-out, pauses during breaks, and shows clearly on the phone while it is on. Every view of a person's location is logged, and raw location points are deleted after the period each organisation sets.
Infrastructure
- All traffic is encrypted in transit and passes through Cloudflare, which filters attacks.
- The database and cache listen only inside the server and are not reachable from the internet.
- Secrets are kept in files readable only by the service account, never in source code.
- Each release is built separately and switched in only after it passes a health check.
- We back up the database every night and keep backups for 35 days.
AI features
AI features are being rolled out. When an organisation turns them on, they run on our servers, never in your browser, and see only the data needed for the request. Answers about a charity come only from documents that organisation has approved, and show their source. AI never makes decisions about people.
Reporting a vulnerability
If you think you have found a security problem, email [email protected]with "Security" in the subject. Please give us a reasonable time to fix it before telling anyone else, and do not access data that is not yours. We will not take action against people who report issues in good faith.