What you need to know before presenting it to the municipal council

As a rule, no. Depending on the edition and the size of the municipality, an annual Trennio licence costs between CHF 990 and 5'900 (up to 15'000 residents). Municipalities can usually award contracts of this size directly, without an invitation or open procedure.

What counts, however, is the law that applies to you: cantonal procurement law and your municipal regulations. Municipalities may set lower thresholds than the canton. It is worth checking your own regulations before you write the proposal.

No. Trennio is not a system that is installed on your premises. There is nothing to run, nothing to update and nothing to back up.

• No interface needed. Trennio does not have to be connected to your residents' register, your finance software or your website.
• No server, no installation. Neither on your side nor on your residents' devices.
• No user account for residents. So no passwords that someone has to reset either.
• No training needed to get started. We handle the initial set-up. After that, you decide what you maintain yourself.

This is by design. The biggest difficulty in digitalising municipalities is not a lack of motivation, but that every new system makes the landscape more complicated. Trennio is not meant to connect anything else, but to take care of one thing completely.

In the public sector, accessibility is not a nice-to-have. The Swiss standard eCH-0059 refers to WCAG 2.1 at level AA, the federal government has made it a binding requirement, and cantons and municipalities have committed under the framework agreement on e-government to apply eCH standards as binding as a rule, explicitly including in procurement.

What is in place today: full keyboard operation, labels for screen readers and Atkinson Hyperlegible, a typeface optimised for readability. Automated checks run with every release; the last measurement on 16 September 2026 found no contrast violations across four views of the residents' app.

Usually 48 hours after we receive all your data, on working days. An existing collection schedule as a PDF is all we need to start.

For complex calendars with several areas, we give you a firm date in advance, rather than promising a figure we then cannot keep.

Your effort: provide the data, tell us your logo and colour, approve.

The contract runs for one year and renews for a further year unless you cancel by email three months before it ends. Your content belongs to you: you can export it at any time during the term; after the end, we keep it available for export for 30 days, then delete it and confirm this in writing on request. The export is a file in the open JSON format containing dates, drop-off points, areas, news, events, the Local A–Z and reports. If we significantly restrict the service, you will be informed at least three months in advance and can cancel with effect from that date. There is no database on your side that would need dismantling, and no interface that would be missing afterwards.

We do this deliberately, because a municipality finds a decision easier to make when it can be reversed.

In our experience, these six points answer the questions raised in council:

• What: An app in our municipality's branding for collection dates, news, events and the Local A–Z.
• Cost: Annual licence depending on edition and number of residents, set-up free until the end of 2026.
• Procurement: Amount below our threshold for direct award (check regulations).
• Effort for the administration: Provide data, then maintain content in the browser. No IT department needed.
• Data protection: revised FADP, no resident accounts and no profiles; personal data only when someone uses a feature (such as issue reporting or reminders), details in the privacy policy.
• Exit: Annual contract, three months' notice, the content remains ours.

Everything you need for a proposal to the council or for review by your data protection officer:

• Price sheet: Editions, size bands, add-ons, support and contract terms.
• Fact sheet: What the app does, how the roll-out works, where the data is stored.
• Retention guidelines: Which data is stored for how long, and when it is deleted.
• Operations sheet: Responsibilities, incident reporting, availability and what applies in the event of an outage.
• Security sheet: Where the data is stored, who has access, how it is backed up and what we cannot prove.
• Exit sheet: What you can export yourself at any time and what happens if you cancel.

Always up to date online: Data protection · Terms and conditions · Data processing agreement · Accessibility.

Trennio is developed and operated in Switzerland. The provider is Sinew GmbH, based in Kienberg SO (UID CHE-293.157.044). Details in the legal notice, contact info@trennio.app.

We are a small team, not a corporation. That means you speak to the person who actually builds the app, and a query takes hours rather than weeks.