Right to erasure under the FADP
Right to erasure under the FADP: a workflow for SMEs
Right to erasure under the FADP is a recurring task for owners and office staff in Swiss companies of about 20 to 250 people: a data subject can ask you to rectify or erase personal data where the law requires it (Art. 32 FADP). The Act also expects appropriate technical and organisational measures (Art. 8 FADP) and fair information at collection (Art. 19 FADP). This page describes an office workflow. It is orientation, not legal advice. Health data at work is covered separately in medical certificates and the employer.
Erasure is not the same as access
An access request delivers a copy of what you hold. Erasure removes or anonymises data where permitted. Process them separately. The data subject access request workflow is a separate topic; do not mix deadlines or content.
When someone writes “delete all my data”, clarify in plain language whether they want access, erasure, or both. Many SMEs can answer with two paragraphs instead of new software.
Rectification means fixing a wrong phone number or a typo in a name. Erasure means removing or anonymising an entry where no duty blocks it. Both can arrive in one email; still keep two tracks in your log so you can show later what you did.
Steps when someone asks for erasure
Log the request
Date, channel, and who owns the reply. Do not delete before the person is identifiable.
Check identity
Does the request come from the address you use for that customer? Otherwise use a secure channel or counsel.
Walk storage locations
CRM, ERP, debtors and creditors, shared mailboxes and personal archives (PST, local folders), newsletter, event and marketing lists, shared drives, USB sticks and old exports, plus processors who hold data in their tool. See also sharing files with personal data and sending personal data by email.
Test exceptions
Legal retention (invoices, open claims), legal defence, ongoing proceedings.
Write the answer
What you deleted, what you keep, until when, and why. Not “no, privacy” without a reason.
File a short record
Date, search locations, owner name. Helps the next case and any review.
Where SMEs forget data
A tick in CRM is not enough when exports sit on a shared drive or someone keeps the contact in an Excel sheet for trade fairs. Job applications have their own retention rules; see how long to keep job applications. Backups: you need not destroy every tape at once, but active systems and restorable copies you use in daily work belong in the deletion plan.
When a processor handles personal data for you, you remain accountable to the data subject. Instruct the processor in writing to delete its copy and keep the confirmation. That does not replace your own search in systems only your team uses.
Marketing lists and old campaigns
Separating “unsubscribe” from “delete the person” avoids disputes. Unsubscribe stops sending; erasure removes historical entries where no retention duty applies. Exports from Mailchimp, Brevo, or Excel lists on the server belong on the same checklist as CRM.
Employees, customers, and former applicants
Customer erasure differs from HR data. Someone who worked for you may ask for deletion while payroll and social records must still be kept. Unsuccessful applicants leave shorter trails; the neighbour article on job applications describes retention that can delay erasure.
A made-up example: a 40-person services firm in Aargau receives the same erasure request twice from a former customer. The admin deletes the CRM record, removes the address from the newsletter list, keeps mail only as far as invoice retention requires, and sends a half-page reply with the deadline for billing data. No new tool; a short record in the “privacy” folder.
Reply text without legal jargon
A clear reply names three things: what you deleted, what you keep for now and why (retention, open invoice), and when you will review again. Offer a contact for questions. Do not promise a fixed number of days your privacy notice does not support; plan enough internal time to search every location before you write “all done”.
Paper, scans, and archives
Paper files and scanned PDFs in “customer 2019” folders count. Deleting digitally while the box in the cellar remains is not erasure. Shredding rules for HR and sales should match deletion requests; see clean desk and disposing of files when physical stock builds up regularly.
A short internal record for the next request
After the first case, half a page internally pays off: search list, owner, template for “partly deleted”. That is not certification; it saves time when the same question returns next quarter. Leadership reads once a year whether the list still matches your tools.
When you refuse or delete partly
You may refuse or limit erasure when legal duties conflict, when data is needed to assert legal claims, or when identity is not plausible. Offer a secure channel instead of guessing.
Frequently asked questions
Do we need a lawyer every time?
Not for routine customer erasure with a clear file. Counsel helps with complaints, unusual categories, or cross-border cases.
Does GDPR apply as well?
EU contacts can trigger GDPR duties in addition to Swiss law. This text centres on the FADP; review borderline cases separately.
Must we overwrite every backup immediately?
You must clean reachable copies in active systems. Old backup tapes you do not use for restore are a separate IT topic; document what you deleted and when.
Team, roles, and training
One person should approve deletions (CRM, mail, marketing). Reception and support use the same ticket template so nobody “only deletes mail” and forgets CRM. IT helps with backups and cloud accounts; HR with personnel files.
A live data protection session walks through erasure, retention, and reply letters with your examples, in one to two hours. Details on Datenschutz awareness training.
Check whether statutory retention blocks erasure, for example in accounting. Delete in the systems you actually use, not only in the mailbox of the person who read the email.
Written by
Aurum Avis Labs
Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.
Related Articles
You might also be interested in these articles
Sending personal data by email in Switzerland
Sending personal data by email: when ordinary transport is enough, and when it is not. For Swiss SMEs.
How long to keep job applications in Switzerland
How long to keep job applications in Switzerland: retention after hire or rejection, talent pools, and deletion. FADP-oriented steps for HR in SMEs.
Sharing files with personal data in Switzerland
Sharing files with personal data: Excel, links, and USB sticks for Swiss SMEs. Channel choice, access rights, and first steps under the FADP.