For public bodies
Public money is spent in public
Councils, sports departments, venue operators and tourism boards sell sponsorship like any other rights holder, then have to answer for it in a way a private seller never will. Zephlo keeps the evidence that answers it.
The same job, under more scrutiny
Public bodies sell the same things every other rights holder sells. Four things make the job harder.
Someone will ask what the sponsor got
A festival that can't answer has an awkward conversation. An authority has an auditor, a councillor, or a freedom-of-information request. Zephlo attaches a dated photo to every promise as it's delivered, so answering is a lookup rather than a search through three people's phones.
The inventory is scattered across departments
One venue has one set of assets to sell. A city has venues, events, programmes and teams, each sold by whoever owns that budget. Zephlo puts the whole inventory on one pipeline, which is usually the first time anyone can see what is still unsold.
The relationship has to outlive the post-holder
Election cycles and staff rotation move people. When the sponsorship officer leaves, the history of who agreed what tends to leave with them, sitting in an inbox nobody else can open. One shared record survives the handover.
Reporting is an obligation, not a courtesy
The report that shows a sponsor what they received is the same artefact that answers a transparency request or an internal audit. Zephlo builds it from the record instead of asking someone to reconstruct the year from memory.
Who this is for
Any public body that sells its own assets: naming rights, hoardings, shirt space, event partnerships, programme sponsorship.
City and municipal councils
Selling across venues, teams and civic events.
Sports and leisure departments
Municipal clubs, facilities and participation programmes.
Public venue operators
Stadiums, arenas, pools and leisure centres in public ownership.
Tourism and destination bodies
Festival, campaign and event partnerships.
Public event organisers
City marathons, cultural programmes, seasonal events.
Development agencies
Partner and sponsor programmes that run for years and cross borders.
Where we actually stand
Public procurement asks harder questions than a private buyer does, and the honest answers matter more than the flattering ones. This is where Zephlo is today, region by region. It will change, and this page changes with it.
European Union
In place
- Data stays in the EU: database in Ireland, application in Dublin.
- Row-level tenant isolation, encryption in transit and at rest, and a restore drill we have actually run.
- An Article 28 data processing agreement, available on request.
- An accessibility audit against WCAG 2.1 AA, done in August 2026. Dialogs now trap focus and close on Escape, mislabelled form controls were corrected, and text contrast was raised from 2.52:1 to 4.80:1 on the app's main surface.
Not yet
- No formal conformance statement against EN 301 549, broadly WCAG 2.1 AA. The August audit left real gaps: around 75 form controls still have no accessible name, and neither screen-reader testing nor a full keyboard walkthrough has been done. Until those are closed we will not claim conformance. Public bodies are required to meet the standard, and the requirement reaches internal tools they procure.
- No Esquema Nacional de Seguridad declaration for Spain. The Basic category is a self-declaration and is our realistic first step.
- The processing agreement has not been through external legal review.
Worth knowing: in Spain a services contract under €15,000 excluding VAT is a contrato menor and can be awarded directly, with no tender. Most low-value routes across the EU work similarly, and Zephlo's pricing sits well inside them.
North America
In place
- The same product, with the same tenant isolation and encryption.
Not yet
- Hosting is in the EU. A US or Canadian body that requires in-country residency would need us to run a second region, which is a project rather than a setting.
- No accessibility conformance statement yet. The same August 2026 audit and fixes apply here, and Title II sets the same WCAG 2.1 AA bar, but the remaining testing is the same too.
Worth knowing: the Department of Justice's Title II rule sets WCAG 2.1 AA for state and local government, with deadlines of 26 April 2027 for populations over 50,000 and 26 April 2028 for smaller bodies and special districts. Authorities are working through this now, and will expect the tools they buy to help rather than hinder.
Africa
In place
- The same product, and nothing shared beyond the sub-processors named on our security page.
Not yet
- Nigeria's Data Protection Act restricts cross-border transfers unless a lawful route applies, and NITDA's cloud policy pushes government workloads towards onshore hosting. With EU hosting, that has to be worked through case by case rather than assumed.
- No accessibility conformance statement yet, on the same footing as the other two regions.
Zephlo is a single product, and a public body gets all of it rather than a stripped-down version. Accessibility is being worked on rather than waved at, and the specifics are above. What it does not have yet is a conformance statement or an ENS declaration. We would rather say so here than have you find it at procurement stage.
The full detail on hosting, encryption and sub-processors is on the security page.
Talk to us before you write a spec
Tell us what your authority is required to produce, and we will tell you straight whether Zephlo can produce it today.