By Raphael Schwirtlich · Published Thu Nov 19 2026 · Last updated Sat Oct 20 2018
Risky Vibes pt. 02
Data At Risk
Disclaimer
This article is general information and my personal opinion, not legal, tax or insurance advice. Laws differ by country and state/canton, change over time, and depend on the facts of each case. Before you replace a business system, ask a qualified lawyer, tax adviser or data protection specialist about your own situation.
Three kinds of data, three rulebooks
When I started looking at what people actually replace, I realised that "business software" is a lazy phrase. A tool that tracks project tasks and a tool that runs payroll can both be called internal software, but they sit under very different rules, and the fallout differs a lot if they fail.
Start with an inventory
Before you cancel any of your current tools, write down which data each of them holds.
A table like this takes twenty minutes and may save weeks of headaches:
| Tool | What data it holds | Who can access it | Who else receives the data | Notes |
|---|---|---|---|---|
| Example: CRM | Customer names, emails, notes | Sales team | Hosting provider, email service | Contains contact persons |
The fourth column surprises most people. A homemade app rarely stands alone:
- It runs on a hosting platform,
- may send email through another service,
- and was probably built with an AI assistant that saw some of your data.
Family 1: Customer Data (CRM)
Names, email addresses, phone numbers, notes, deal values. Contact persons at business customers count too, because they are people. Data-protection laws such as Switzerland's revised data protection act (nDSG) and the EU's GDPR are generally concerned with personal data, and both expect appropriate security. Article 3 goes into this.
Family 2: Financial Data (invoices and books)
Invoices, ledgers, VAT records, bank details. There are two layers. The first is record-keeping: in Switzerland, commercial law sets a retention period of ten years and expects records to be reliable and not alterable without trace. In the EU, national rules apply, and a growing number of countries are introducing mandatory e-invoicing. The second layer is data protection, because invoices contain personal data. See article 4.
Family 3: HR Data (payroll, absence, contracts, pension funds)
Salaries, bank details, ID and social-insurance numbers, absence records, reviews, pension-fund information. This is often the most protected category. Employment law can limit what an employer may collect and process, pension-fund data can carry its own secrecy rules in Switzerland, and payroll connects to social-insurance and tax reporting. See article 5.
A rough traffic light
- Red: the ledger, invoicing, payroll, HR files, pension data.
- Orange: the CRM. It depends on how much customer data it holds and how sensitive the notes are.
- Green: dashboards and workflow helpers that don't touch personal data.
These colours are my personal rule of thumb, not rules of law. Your case may differ.
Which country's rules?
A Swiss company may be subject to Swiss rules and, if it has customers or staff in the EU, possibly EU rules as well. Cantonal matters, such as certain tax questions, can add another layer. Which rules apply depends on the facts. That is a question for a lawyer, not for a blog post.
Mixed tools and quiet scope creep
An all-in-one tool inherits the strictest rules of anything it holds. Homemade tools also grow. Someone adds an invoice export, then a salary column, and a "simple internal tool" becomes a system of record without anyone actively deciding that it should.
A simple rule helps:
Whenever a new type of data enters the tool, re-rate it.
Questions to bring to your adviser
- Which laws and duties apply to each of my data families, given where my business and my customers and staff are?
- Are there data types I should never put in a homemade tool?
- Do my contracts with customers, insurers, my pension fund or my payroll provider limit where or how data can be processed?