1. Controllers and contact
The Lumio operator must be identified for accounts, billing and platform operations. Your chosen accounting firm determines the purposes of its accounting or tax engagement. Contracts must define these roles and any processing on another party’s behalf. The reference contact supplied for this project is Contact@lynvia.ch, Avenue de Tourbillon 34, 1950 Sion. This contact alone does not establish the legal identity of the Lumio operator.
2. Data and purposes
Depending on the features used: identity, contact details, company, tax canton and municipality, accounting and tax documents, payroll data, messages, simulations, orders and payments. These support the requested service, communication with your firm, access management and billing. Supply only necessary data that you are authorised to share. Data may come from you, your company or your appointed firm.
3. Swiss framework
The Swiss FADP and its ordinance govern private-sector processing of natural persons’ data in Switzerland. Processing must be proportionate, transparent and limited to its purpose. Where consent is required it must be informed and freely given; viewing the site is not blanket consent. GDPR applies only when its territorial conditions are met. The Sion office location does not replace the client’s tax canton.
4. Access, providers and transfers
Recipients depend on the service: assigned firm and authorised staff, technical support, providers and authorities where required by law. The platform uses these service providers: Google Firebase (authentication and databases), Vercel (hosting and deployment), Cloudinary (file storage), Stripe (payments), Resend (transactional email), Anthropic, Claude (AI generation), Google, Gemini (embeddings and search) and Supabase (vector search storage and backups). Provider roles, recipient countries and safeguards require confirmation before publication. Exclusive Swiss hosting is not established. FADP articles 16 to 19 govern foreign disclosures and information about countries and safeguards.
5. Retention and deletion
Retention must be set by category and purpose, with deletion or anonymisation when no longer needed, subject to legal duties and disputes. Article 958f of the Code of Obligations requires ten years for the relevant accounting books, records and reports, starting at financial year end. It does not require ten years for every profile, conversation or statistic. Closing an account does not automatically delete legally required records. Backup retention and technical deletion periods must be documented.
6. Cookies, local storage and analytics
The platform stores language, audience selection, preferences and authentication information. Remember me keeps sign-in beyond the browser session. The code also sends visits to the server: path, referrer, browser, language and account ID when available. Analytics must be distinguished from essential functions; this notice does not claim there is no tracking. Storage periods, opt-out options and any required consent must be configured under applicable rules. Social links open sites with their own policies.
7. AI and decisions
Simulations and automated answers are aids to verify, not official tax decisions. Human review should precede a decision or filing that commits you. Data sent to AI services, their retention and possible reuse must be specified before confidential data is used. If automated individual decisions under FADP article 21 are introduced, information and rights to express your view and request human review must be provided, subject to statutory exceptions.
8. Your rights and security
You may request access and correction and, under statutory conditions, delivery or transfer of your data, object to processing or request deletion. Retention duties and third-party rights may limit a request. The controller must verify identity proportionately and explain restrictions. The final rights-request contact remains to be confirmed. You may contact the FDPIC or competent courts. Access controls, file protection and incident procedures require verification; no certification is asserted here.