Frequently asked questions

These are the questions procurement teams, data-protection officers, and IT departments most often ask. For anything not covered here, reach out via the contact page.

About Clex

What is Clex?

Clex is a writing-support tool for municipal care documentation. It ships as a system keyboard on Android and iOS and as a browser extension on Chrome and Edge. It gives the care worker two things: care-domain word suggestions as the worker types, and sentence correction and rewrite on request. The suggestions come from a model trained on care documentation language, not the general vocabulary of a phone keyboard. When the note is down, two models on the device correct the spelling and rewrite it into fluent care-record language, and the worker accepts or rejects each change; pictograms mark the care concepts Clex recognises along the way. Care workers write notes directly into their existing record system.

Who is behind Clex?

Clex A/S is a Danish healthcare-technology company founded in 2016, headquartered in Copenhagen with offices in Kolding and Malmö. The team built Wizkids, the reading-support tool used across Danish schools for years, and applied that language-technology expertise to care documentation. On the Swedish market, the contracting entity is Clex Sweden AB (org.nr 559544-8001).

Who uses Clex today?

Clex is in daily use in municipalities across Denmark and Sweden, serving both home care and residential care settings. See the home page for a selection of named municipalities.

Data, privacy, and GDPR

What data does Clex send from the device?

All text the care worker types remains on the device. The writing features - word prediction, sentence correction and rewrite, speech to text, read-aloud, and translation - run locally, using language models stored on the device or in the browser. What Clex receives is a licence check and a daily count of how often features were used. It carries no text, no keystrokes, and no identifier for any person.

Where are your servers?

Production infrastructure is hosted at Hetzner Online GmbH in Falkenstein, Germany (EU). All server-side processing stays inside the EU.

Do we need a Data Processing Agreement with Clex?

Roles are assigned per activity. The text care workers write is processed on your organisation’s own devices and browsers and is never received by Clex, so for that processing your organisation is the controller and Clex is the software supplier, neither controller nor processor. For licence validation, the connection data it carries and the daily usage statistics, Clex A/S is an independent controller. Where Clex processes personal data on your documented instructions, for example diagnostic access during a support case, Clex acts as a processor and a data processing agreement is in place before that processing begins; when your data protection officer requests a data processing agreement for any other activity, Clex concludes one.

Are user keystrokes logged or monitored?

No. Clex collects only a daily count per feature (for example, how many sentence corrections were accepted that day) to keep the service stable. A report carries no identifier for any person, device, or installation, and on arrival its numbers are added into a total for the whole organisation. Keystrokes and free text are never collected or stored.

Can everything be deleted when we uninstall Clex?

Yes. On Android, iOS, and the Chrome or Edge extension, uninstalling removes all locally stored Clex data. The app also offers an in-app reset. On the server side, only aggregated counts that carry no identifier for any person are kept, deleted automatically 24 months after the day they describe.

Does Clex work offline?

Yes. Word prediction, sentence correction and rewrite, text-to-speech, speech to text, and translation all run on the device and work with no network connection. A connection is needed to download language models on first use and for licence checks; day-to-day writing does not depend on it.

Deployment

How does a rollout work?

On Android and iOS, Clex is pushed to the fleet through the municipality’s existing MDM (mobile device management). Care workers can also activate Clex on a personal device via BYOD using a code from the deployment portal. For Clex Web, the browser extension is deployed via GPO on managed Chrome and Edge fleets. Detailed deployment guides are available on request - contact Uffe Gorm Pal Hansen.

How does licensing work?

Licensing is managed per municipality. At startup, Clex exchanges the licence key for a short-lived access token (valid for around twelve hours) that identifies the customer organisation - not the individual user. The token carries no personal data.

Which record systems does Clex work with?

Clex works alongside the record systems Scandinavian municipalities already use, including Lifecare, Cura, Nexus, KMD Care, Treserva, Combine, and Procapita. Care workers write their notes directly into their record system; Clex does not replace it.

Security and documentation

Has a DPIA been conducted for Clex?

Clex has assessed its own processing (licence operation, connection data, aggregated usage statistics) and documented it; a vendor-side data protection impact assessment is not required for that processing.

Datatilsynet’s guidance treats the introduction of an AI-supported tool in care as new technology that normally calls for a data protection impact assessment (DPIA), so most organisations run one. Clex’s technical documentation contains the systematic description, data flows, categories of data, retention and measures that a DPIA needs, and Clex answers targeted questions from the DPIA author.

How is Clex classified under the AI Act?

Clex A/S has classified its products under the AI Act (Regulation (EU) 2024/1689). For its intended purpose - writing support for the employee who documents care - Clex is not a high-risk AI system under Annex III: it assesses no one, decides nothing about any citizen or employee, and has no interface to any decision system. The transparency duties in Article 50 are analysed function by function: correction, rewrite, dictation and read-aloud work on the employee’s own text, and the employee reviews and accepts every change before it enters the record. The reasoning, the human-oversight model and the support for your own AI-literacy duties are set out in the AI Act Classification and Transparency Memorandum, which is part of the customer document pack.

How do we get the full security and compliance documentation?

The customer document pack (security management, secure development, infrastructure, business continuity, data protection and sub-processors, SLA, and GDPR Questions and Answers) is available on request. Ask Flakron Sojeva for Danish customers, Ron Karlsson for Swedish customers, or Uffe Gorm Pal Hansen for technical follow-up.

What happens if we report a security or reliability issue?

Reports go to Uffe Gorm Pal Hansen. We acknowledge the report within two working days and respond with a scope assessment, severity rating, and remediation timeline. Formal incident-response procedures are covered in the Business Continuity, Incident Response and Disaster Recovery document in the customer pack.

For anything else, the contact page lists named contacts by market and topic.