Express courier. Direct.
Also overnight.
x25pronto Switzerland takes goods direct to the destination. Small loads go by car. Larger loads go by van or Van XL. Direct, express and overnight trips run Monday to Sunday when a slot is free. Free times are shown in the booking calendar. This keeps the plan clear.
Retention and deletion policies for courier data: rights and processes
Practical guide for Swiss SMEs and pharmacies: set retention and deletion policies for courier data that are compliant, auditable and automatable.
Quick answer
SMEs and pharmacies should define clear retention and deletion rules for courier data and implement them technically. Start with a data inventory, assign retention periods per data category (e.g. tracking IDs, recipient addresses, signatures) and create automated workflows to delete or archive data when periods expire. Add written processes, access controls, audit logs and regular reviews to ensure compliance and traceability.
Why a deletion policy matters
Courier records contain personal and business data. Pharmacies may also handle data with health links. Legal requirements and data minimisation mean you must keep data only as long as necessary. A deletion policy reduces risk, protects customers and simplifies audits.
Create a data inventory
List all courier data you process: shipment IDs, sender/recipient details, phone numbers, delivery windows, signatures, status logs and photos. Categorise by purpose (billing, tracking, customer contact) and sensitivity. Record storage locations (TMS, CRM, backups, cloud) and responsible owners.
Define retention periods
Set a retention period for each category. Examples: tracking logs 30–90 days, signed delivery notes 2–5 years (accounting needs may apply), customer messages 6–24 months. Check sector rules for pharmacies and accounting retention obligations. Record the legal basis or purpose for each period.
Implement automated workflows
Use rules in your TMS or CRM. Examples: scheduled jobs that delete old logs; archive processes that move signatures to encrypted long‑term storage; or a delete trigger after X days. Use status flags rather than manual deletions. Test workflows in a sandbox before deploying.
Technical and organisational controls
Restrict access using need‑to‑know. Enable encryption at rest and TLS in transit. Keep audit logs that record deletions, users and timestamps. Assign data stewards and schedule periodic reviews. Train staff on processes and incident reporting.
Audit, proof and recovery
Run regular checks and spot audits. Keep deletion proofs (logs) to show authorities or partners. Plan a short recovery window for accidental deletions. Document exceptions, such as legal holds or ongoing disputes.
Frequently asked questions
Which courier data should pharmacies protect most?
Addresses, phone numbers and any information that could imply health conditions are most sensitive. Treat these data types more strictly: encrypt storage and limit access.
How do I automate deletions technically?
Set rules in your TMS/CRM, use scheduled jobs (e.g. cron) or cloud lifecycle policies. Tag records with expiry and test processes in a development environment.
What matters for audit logs?
Logs should be tamper‑resistant, timestamped and include user IDs. Store them separately from operational data and protect them against modification.
How to handle legal retention obligations?
Identify accounting or sector‑specific rules. Mark affected records as exceptions and manage legal holds with documented reasons and end dates.