The one-pager procurement asks for
No participant personal data.
By design, not by policy.
Most impact tools ask you to trust their safeguards. Owl Impact removed the risk at the design stage instead.
What we hold about the people you work with
Nothing identifying. No names, no dates of birth, no addresses, no contact details of any participant, ever. Outcomes and distance-travelled measures are recorded against an anonymous participant code that only your own team can connect to a person. There is no participant register in the system to breach.
What the system does hold
- Logged records — hours, session types, outcome events and measures, each dated and rate-stamped when logged.
- Account details — the name and email of your logging staff, for sign-in and reports. Nothing else.
Who sees what
- Your loggers see their own logging tools.
- Your dashboard holders see your organisation's records and reports. Viewer access is read-only — viewers cannot change anything.
- An umbrella or funder sees aggregate reports only — never a member's raw records without that member's part in it.
- We see what's needed to run the service, and nothing is sold or shared with anyone. No advertising, no tracking of the people you serve.
Where it lives
Data is held with established UK/EU-serving providers under UK GDPR. Passphrases are stored only as salted cryptographic hashes — we cannot read them. Reports are sent to the addresses your account names, and nowhere else.
How the numbers stay honest
- Every rate is published with its source and year on the methodology page — on the report itself, too.
- Cost, social value and in-kind are reported side by side, never summed — so no figure is counted twice.
- Reach is counted, never costed. Distance travelled carries no £ — a shift in a measure is not a price.
Questions a procurement or safeguarding lead wants answered in writing? Ask us — we answer in plain language.