Privacy policy
In force since 1 November 2026. The French version prevails in case of doubt.
Liturgies helps churches prepare their services. To do so, the app keeps information about people: accounts, and the names of those who serve. This page explains which, why, where and for how long, under the Swiss Federal Act on Data Protection (FADP) and the EU General Data Protection Regulation (GDPR).
1. Who is responsible
Liturgies is operated by [TO COMPLETE: name of the person or company], [TO COMPLETE: postal address] ("we"). For any question about your data: support@techvillage.ch.
Two situations should be told apart:
- A church's content (its services, its planning, the names of those who serve, its lists) is decided by the church. The church is the controller; we process it on its behalf and on its instructions, as a processor.
- Accounts, the security of the service and this site: we are the controller.
If you are named in a church's planning without having an account, please contact that church first; we will help it answer.
2. The data processed
| Category | Data |
|---|---|
| Account | Name, e-mail address, password (never in clear: only a hashed form), chosen language, churches and the role in each, person linked in the planning, personal calendar link. |
| Church content | Services (dates, titles, order of service, notes, technical needs), team planning with the names of those who serve, hymns, readings, series, templates, the church's details and logo, version history. |
| Invitations | Proposed role, the "for whom" note typed by the manager, date sent and accepted. |
| Technical data | IP address and request details, kept briefly for security (limits on attempts, error diagnosis). |
| Access requests | What you enter in this site's form: church, city, name, role, e-mail, message. |
We do not ask for any sensitive data. Serving in a church's service may however reveal a religious affiliation: this is why access is restricted to each church's members, and nothing is public unless you decide so (a service's public link, which the church can stop at any time).
3. Why, and on what basis
- Providing the service the church and its members use (performance of a contract; Art. 6(1)(b) GDPR).
- Protecting the service and accounts: limits on attempts, protection against robots, logs (legitimate interest; Art. 6(1)(f)).
- Sending the e-mails needed, such as a link to choose a new password (performance of a contract).
- Answering an access request sent from this site (pre-contractual steps; Art. 6(1)(b)).
We do not use your data for advertising, profiling or resale. No automated decision is taken about you.
4. What stays on your device
The app keeps in your browser's storage: your session, a copy of your church's data for offline reading, your unsaved drafts, and your language and theme. This is not tracking: nothing is sent elsewhere. The offline copy is erased when you sign out.
This site and the app use no advertising cookies, no audience measurement, and load no fonts or scripts from other sites.
5. Where the data is, and who can access it
The data is hosted in Switzerland. We use:
| Provider | Role | Location |
|---|---|---|
| Infomaniak Network SA | Server hosting the app, its data and its backups | Switzerland |
| Infomaniak Network SA (Swiss Backup) | Off-server copy of the backups | Switzerland |
| Infomaniak Network SA | Sending e-mails (forgotten password, access requests) | Switzerland |
| Google (only if your church turns it on) | Reading, read-only, a Google Sheet the church shares to import it into the app | Where Google hosts the sheet |
No data is passed to other third parties unless required by law.
Within a church, everyone sees what their role allows: a member sees their church's services and planning, a manager also sees the list of members and their e-mail addresses. A church never sees another church's data. On our side, access to the data is reserved for running the service (maintenance, support at a church's request).
6. How long
- Account: as long as it exists. Deleted on request; if it no longer belongs to any church, we may delete it after 12 months.
- A church's content: as long as the church uses Liturgies. On request, we send it a copy, then delete it within 30 days (90 days for backups).
- Backups: one per night, kept 30 days on the server and 90 days as a copy at Swiss Backup; deleted data therefore leaves the backups within 90 days.
- A service's history: the last 60 versions.
- Invitations: valid 14 days; then kept with the church.
- Technical logs: a few days.
- Access requests: 12 months at most, then deleted if no church was opened.
7. Security
Encrypted connections (HTTPS), passwords kept as hashes, strong passwords required, protection against robots and limits on attempts, strict separation between churches checked by the server, rights per role, daily backups copied off the server. No system is infallible: in case of a data breach that puts you at risk, we will inform the churches concerned and the competent authorities within the legal deadlines.
8. Your rights
You may ask to access your data, have it corrected or deleted, receive a copy in a common format, object to a processing or ask for it to be restricted. Some of this is done directly in the app (name, password, leaving a church); for the rest, write to support@techvillage.ch. We answer within 30 days.
You may also contact a data protection authority: in Switzerland, the Federal Data Protection and Information Commissioner (FDPIC); in the European Union, the authority of your country.
9. Access requests sent from this site
The "Request access" form sends us the church, city, your name, your role, your e-mail and your message. They are used only to reply to you and to open your church's space; they reach our e-mail inbox (Infomaniak) and are kept 12 months at most. To tell people from robots, your browser performs a small calculation; no third-party service is involved.
10. Changes
If this policy changes significantly, we will say so in the app and to the churches' managers. The date at the top of this page shows the latest version.