{"id":2491,"date":"2026-09-22T03:16:17","date_gmt":"2026-09-22T03:16:17","guid":{"rendered":"https:\/\/daxs.com\/data-protection-secure-digitalisation\/"},"modified":"2026-09-22T17:31:46","modified_gmt":"2026-09-22T17:31:46","slug":"data-protection-secure-digitalisation","status":"publish","type":"page","link":"https:\/\/ticketsystem.wesupport.at\/en\/data-protection-secure-digitalisation\/","title":{"rendered":"Data protection &#038; secure digitalisation"},"content":{"rendered":"<!-- daxs-change: 1790056200 source=git -->\n<style>\n.daxs-privacy{--o:#f23c13;--i:#10191c;--p:#f4f3ef;--l:#d5dbd8;font-family:Inter,Arial,sans-serif;color:var(--i);overflow:hidden}.daxs-privacy *{box-sizing:border-box}.daxs-privacy .w{width:min(1160px,calc(100% - 48px));margin:auto}.daxs-privacy h1,.daxs-privacy h2,.daxs-privacy h3{letter-spacing:-.035em;line-height:1.06}.daxs-privacy h1{max-width:900px;font-size:clamp(44px,6vw,78px)}.daxs-privacy h2{font-size:clamp(32px,4vw,56px)}.daxs-privacy h3{font-size:24px}.daxs-privacy p,.daxs-privacy li{font-size:17px;line-height:1.65}.daxs-privacy .hero{padding:108px 0 84px;background:#070d10;color:#fff}.daxs-privacy .lead{max-width:820px;color:#d4dddd;font-size:23px}.daxs-privacy .ey{color:var(--o);font-size:12px;font-weight:800;letter-spacing:.16em;text-transform:uppercase}.daxs-privacy .s{padding:82px 0}.daxs-privacy .paper{background:var(--p)}.daxs-privacy .dark{background:var(--i);color:#fff}.daxs-privacy .dark p{color:#c6cfcd}.daxs-privacy .split{display:grid;grid-template-columns:.82fr 1.18fr;gap:7vw}.daxs-privacy .grid{display:grid;grid-template-columns:repeat(3,1fr);gap:16px;margin-top:34px}.daxs-privacy .card{padding:28px;background:#fff;border:1px solid var(--l)}.daxs-privacy .card:before{content:\"\";display:block;width:30px;height:3px;margin-bottom:22px;background:var(--o)}.daxs-privacy .steps{counter-reset:step;display:grid;grid-template-columns:repeat(4,1fr);gap:1px;margin-top:36px;background:#334047}.daxs-privacy .step{counter-increment:step;padding:26px;background:#142228}.daxs-privacy .step:before{content:\"0\" counter(step);display:block;margin-bottom:20px;color:var(--o);font-weight:800}.daxs-privacy .visual{display:block;width:100%;height:auto;margin-top:36px;border:1px solid #314047}.daxs-privacy .note{padding:24px;border-left:4px solid var(--o);background:#fff}.daxs-privacy .links{display:flex;flex-wrap:wrap;gap:12px;margin-top:28px}.daxs-privacy .btn{display:inline-block;padding:15px 20px;background:var(--o);color:#fff!important;font-weight:800}.daxs-privacy .btn.alt{background:transparent;border:1px solid #697678}.daxs-privacy .cta{padding:72px 0;background:var(--o);color:#fff}.daxs-privacy .cta .btn{background:var(--i)}.daxs-privacy a{color:var(--o)}\n@media(max-width:900px){.daxs-privacy .grid{grid-template-columns:1fr 1fr}.daxs-privacy .steps{grid-template-columns:1fr 1fr}}@media(max-width:700px){.daxs-privacy .w{width:min(100% - 32px,1160px)}.daxs-privacy .split,.daxs-privacy .grid,.daxs-privacy .steps{grid-template-columns:1fr}.daxs-privacy .hero,.daxs-privacy .s{padding:60px 0}.daxs-privacy .lead{font-size:20px}}\n.page-id-2491 .entry-title.main_title,.page-id-2491 #sidebar{display:none!important}.page-id-2491 #main-content>.container,.page-id-2491 #left-area,.page-id-2491 #content-area{width:100%!important;max-width:none!important;margin:0!important;padding:0!important;float:none!important}.page-id-2491 #main-content>.container:before{display:none!important}\n<\/style>\n<main class=\"daxs-privacy\"><section class=\"hero\"><div class=\"w\"><p class=\"ey\">Data protection &amp; secure digitalisation<\/p><h1>Use data deliberately.<br><span style=\"color:var(--o)\">Set clear technical boundaries.<\/span><\/h1><p class=\"lead\">DAXS implements agreed legal and operational requirements in technology: from forms and access rights to cloud services, integrations and AI tools. The central question is which system may use which data for which purpose.<\/p><\/div><\/section>\n<section class=\"s\"><div class=\"w split\"><div><p class=\"ey\">Clear responsibilities<\/p><h2>Data protection is not a single product setting.<\/h2><\/div><div><p>Legal and data-protection advisors establish the applicable requirements. The organisation decides on purposes, workflows and approvals. DAXS translates those requirements into technical configuration, roles, data flows, logging and secure operating processes.<\/p><div class=\"note\"><strong>Important:<\/strong> DAXS does not replace legal advice. Technical implementation is documented so it can be coordinated with data protection officers, legal advisers and the responsible teams.<\/div><\/div><\/div><\/section>\n<section class=\"s paper\"><div class=\"w\"><p class=\"ey\">Services<\/p><h2>From requirements to day-to-day operation.<\/h2><div class=\"grid\"><article class=\"card\"><h3>Map data flows<\/h3><p>Make sources, recipients, integrations, storage locations and access visible across forms, email, files, CRM, ERP and other business systems.<\/p><\/article><article class=\"card\"><h3>Implement access rules<\/h3><p>Configure users, roles, sharing, MFA and administrative responsibilities to match the actual workflow.<\/p><\/article><article class=\"card\"><h3>Secure forms<\/h3><p>Consider necessary required fields, TLS, secure uploads, permitted file types, spam protection, recipients, logging and retention together.<\/p><\/article><article class=\"card\"><h3>Review cloud and SaaS<\/h3><p>Define which data may enter Microsoft 365, Google Workspace, business applications or other services and how it can be recovered or removed.<\/p><\/article><article class=\"card\"><h3>Use AI in a controlled way<\/h3><p>For Copilot, Gemini, OpenAI\/ChatGPT services or API integrations, clarify per process which content may be processed, retained or excluded.<\/p><\/article><article class=\"card\"><h3>Operate the lifecycle<\/h3><p>Connect retention, deletion, backup, recovery, logging and recurring controls in the technical design.<\/p><\/article><\/div><\/div><\/section>\n<section class=\"s dark\"><div class=\"w\"><p class=\"ey\">Data approval<\/p><h2>A clear decision comes before configuration.<\/h2><p>System access is not appropriate simply because it is technically possible. Purpose, data type, sensitivity and agreed requirements determine whether data is allowed, limited or excluded.<\/p><img decoding=\"async\" class=\"visual\" src=\"https:\/\/daxs.com\/wp-content\/uploads\/2026\/09\/daxs-datenschutz-datenfreigabe-workflow-2026-09.jpg\" alt=\"Data approval workflow from data source, purpose, data type and requirements through technical approval to target system, retention, deletion and control\" title=\"\"><\/div><\/section>\n<section class=\"s\"><div class=\"w split\"><div><p class=\"ey\">Web forms<\/p><h2>Consent is not automatically the right answer.<\/h2><\/div><div><p>An extra checkbox does not automatically make a data process compliant. Purpose, necessary fields, legal basis and recipients must be established first. Only then can the required notice or consent be determined.<\/p><p>DAXS implements the agreed workflow and considers uploads, file formats, transport encryption, logs, deletion periods and spam protection.<\/p><\/div><\/div><\/section>\n<section class=\"s paper\"><div class=\"w\"><p class=\"ey\">Related topics<\/p><h2>Connected, but kept distinct.<\/h2><div class=\"steps\"><article class=\"step\"><h3>Data protection<\/h3><p>Requirements, purposes and permitted processing.<\/p><\/article><article class=\"step\"><h3>IT security<\/h3><p>Protection of systems, identities and access.<\/p><\/article><article class=\"step\"><h3>Backup<\/h3><p>Data protection and tested recovery.<\/p><\/article><article class=\"step\"><h3>AI governance<\/h3><p>Approval, use and control of specific AI processes.<\/p><\/article><\/div><div class=\"links\"><a class=\"btn\" href=\"https:\/\/daxs.com\/en\/cloud-saas\/\" target=\"_blank\" rel=\"noopener\">Cloud &amp; SaaS<\/a><a class=\"btn\" href=\"https:\/\/daxs.com\/en\/backup-recovery\/\" target=\"_blank\" rel=\"noopener\">Backup &amp; recovery<\/a><a class=\"btn\" href=\"https:\/\/daxs.com\/en\/it-support\/\" target=\"_blank\" rel=\"noopener\">IT support<\/a><a class=\"btn\" href=\"https:\/\/docs.daxs.com\/books\/datenschutz-sicherheit\/page\/datenschutz-und-informationssicherheit\" rel=\"noopener\" target=\"_blank\">Data protection documentation<\/a><\/div><\/div><\/section>\n<section class=\"cta\"><div class=\"w\"><h2>Which data may go where?<\/h2><p>We capture the technical baseline, map data flows and implement agreed requirements in a traceable way.<\/p><a class=\"btn\" href=\"https:\/\/daxs.com\/en\/contact\/\" target=\"_blank\" rel=\"noopener\">Discuss secure digitalisation<\/a><\/div><\/section><\/main>","protected":false},"excerpt":{"rendered":"","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"inline_featured_image":false,"footnotes":""},"class_list":["post-2491","page","type-page","status-publish","hentry"],"featured_image_src":null,"_links":{"self":[{"href":"https:\/\/ticketsystem.wesupport.at\/en\/wp-json\/wp\/v2\/pages\/2491","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ticketsystem.wesupport.at\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/ticketsystem.wesupport.at\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/ticketsystem.wesupport.at\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/ticketsystem.wesupport.at\/en\/wp-json\/wp\/v2\/comments?post=2491"}],"version-history":[{"count":4,"href":"https:\/\/ticketsystem.wesupport.at\/en\/wp-json\/wp\/v2\/pages\/2491\/revisions"}],"predecessor-version":[{"id":2574,"href":"https:\/\/ticketsystem.wesupport.at\/en\/wp-json\/wp\/v2\/pages\/2491\/revisions\/2574"}],"wp:attachment":[{"href":"https:\/\/ticketsystem.wesupport.at\/en\/wp-json\/wp\/v2\/media?parent=2491"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}