Privacy
How we handle information
This page explains how we handle information on our website, in the three free tools and in Komplai app. We do not sell your information or use tracking cookies.
- Who we are
- komplai ApS, CVR DK40351981, Copenhagen. We are the controller for enquiries, website statistics and the information used to administer accounts and agreements. When we process your organisation’s material on its behalf, we follow its instructions and the agreed processing terms. Write to hej@komplai.dk with questions.
- The contact form
- You choose whether we should email or call you and give us your email address or phone number. Your message, organisation and role are optional. We send the enquiry to our inbox; if you choose email, we also send you a receipt. We do not create a contact profile in the website database or use the message for model training. Our basis is our legitimate interest in responding to an enquiry you sent us. We retain the email while it remains relevant to the conversation and any agreement. You can request deletion; information we must retain by law remains until that obligation ends.
- Statistics
- We run our own statistics on our servers. We count page views, referring pages and form events without sending the form’s contents to analytics. A code derived from IP address and browser distinguishes visits and changes daily and on restart. The IP address itself is not stored in analytics. Our basis is our legitimate interest in understanding website use and keeping it functioning.
- Cookies and browser storage
- We use no tracking cookies. Downloading a budget PDF sets a technical cookie that protects against forged and repeated requests. It expires after 15 minutes and creates no account. Your browser also remembers locally that you dismissed this site’s information box. Sign-in and document ownership use technical cookies on the relevant services, described below.
- Where it runs
- The website and statistics run at Hetzner in Falkenstein, Germany. Email is sent through Resend, a US company. Resend stores message content and delivery data in the United States even when email is sent from an EU region. Its standard terms describe 30-day email and log retention and transfers under Standard Contractual Clauses and the EU–US Data Privacy Framework. Resend and its subprocessors process information for delivery and security; content is not used for model training. Fonts load from Google Fonts, which sees your IP address.
- Your rights
- You can request access, correction and deletion and object to processing based on legitimate interest. You may also have rights to restrict processing and to transfer information to another service. Write to hej@komplai.dk. For material controlled by your organisation, contact it; we help it handle your request. You can complain to the Danish Data Protection Agency.
- Other services
- Townhall has its own privacy policy and contact address, applying to information you have shared there.
The free tools and Komplai app
Redact, Lens and Secret work without an organisation account. They handle information differently, as described below. Komplai app follows your organisation’s access rules and agreement. Public free use does not include a data processing agreement.
redact The PDF and replacement list stay in your browser. Smart detection sends text for processing.
- In your browser
- Pattern detection, manual marks, replacing details with placeholders and restoring them in an AI response happen in your browser. The replacement list is not saved in browser storage and disappears on reload or when the page closes.
- Smart detection
- Smart detection sends text to the selected detection service. Komplai’s name detection runs on our infrastructure in Germany and processes longer texts in multiple parts. Selecting AI sends the text to your selected AI service. This also applies to text extracted from a PDF.
- PDFs
- The PDF file itself stays in your browser, where the redacted PDF is built. Text extracted from the document may be sent for smart detection. Review the marks before exporting; automatic detection can miss details.
- AI and temporary processing
- AI on Komplai’s local infrastructure passes through an encrypted queue: input is deleted after processing and responses are held encrypted for one hour by default before subsequent cleanup deletes them. Operational metadata is used for load management and troubleshooting. The public editor does not create a document archive.
- External providers
- An external AI service is used only after active selection and its consent dialog. Text is then processed by that provider under its terms; a failure does not automatically authorise sending it elsewhere. Fonts are loaded from Google Fonts, which sees your IP address.
lens The PDF stays in your browser. AI questions and summaries send text for processing.
- The document
- The PDF file, highlights and text recognition (OCR) are processed in your browser, without a document library. Closing the tab loses the contents, highlights, OCR text and answers.
- Questions and summaries
- When you ask for an AI answer or summary, text passages from the PDF are sent to your selected AI service. The default is Komplai’s local infrastructure in Denmark. The PDF file itself stays in your browser. Answers can refer to the pages and passages used.
- Your own AI provider
- An external provider is used only when you actively select it with your own key and consent. The text is then sent to that provider and processed under its terms. A failure does not change your provider choice.
- Temporary AI processing
- On local infrastructure, text and responses pass through an encrypted queue. Input is deleted after processing; responses are held encrypted for one hour by default and deleted during subsequent cleanup. Operational metadata is used for load management and troubleshooting. lens does not create a document archive.
- Statistics and fonts
- Statistics can record a page visit and a document being opened without including its contents. Fonts are loaded from Google Fonts, which sees your IP address.
secret We cannot read what you send.
- The content
- It is encrypted in your browser before anything at all is sent. The key sits in the part of the link after the # character, and browsers never send that part to the server. So all we hold is an encrypted blob we cannot open.
- What we hold
- Encrypted content with the information required for decryption in the recipient’s browser, and an expiry time. The server has neither the content key nor any optional passphrase. We do not store the sender’s name, recipient’s name or a description of the contents.
- Once only
- When the recipient clicks to reveal the content, the server’s encrypted copy is deleted in the same database call that returns it. A mail scanner simply fetching the page does not consume the secret. An unopened link expires at the chosen time.
- Receipt
- The receipt holds sharing status and timestamps, without the secret’s contents, and is deleted during cleanup 30 days after the link’s chosen expiry time. Revealed text is cleared after five minutes, with an option to extend viewing; the service cannot delete copies in a clipboard or held by the recipient.
- What we can see
- Your IP address is used to limit how many can be created from the same place. It is not stored alongside the secret.
- Statistics and fonts
- Visit statistics contain no secret content. Fonts load from Google Fonts, which sees your IP address.
Komplai app Accounts, content and AI processing follow your organisation’s setup.
- Account and access
- We use your name, email address, organisation, role and assigned access to provide access. Your organisation or Komplai invites you; there is no public self-registration. Sign-in uses the Komplai account or your organisation’s connected identity provider. Email links and invitations are sent through Resend.
- Organisation material
- Text, documents, email and other files are processed in apps your organisation has assigned to you. Document-room material can be stored with extractions, comments, analyses and versions. Permissions determine who can view and share it; having an account does not grant access to all organisation material.
- AI and API
- Processing uses approved local infrastructure, EU cloud or your organisation’s agreed solution. The location, model provider and subprocessors follow the configuration and agreement. A provider key supplied by you also brings that provider’s data terms into scope. We do not use organisation material to train our models.
- Word and other tools
- Using Word or an external client with Komplai’s API sends the chosen text or request for the same approved processing. Access is tied to the user, organisation and key permissions. A register lookup can send the query to CVR, Retsinformation, Statistics Denmark or Parliament’s open data.
- Temporary processing
- Processing does not always mean document-room storage. Local AI uses an encrypted queue: input is deleted after processing; results normally remain encrypted for one hour and are then deleted during cleanup. File analysis can use temporary working files. Image and text analysis runs in memory; video can briefly use a private working directory cleared after completion, failure, cancellation or timeout.
- Logs and usage
- We record access, actions, refusals and usage against the user and organisation for security, audit, capacity management and the shared AI budget. Operational metadata and content are different information; retention follows the relevant processing and agreement.
- Retention, deletion and backups
- Organisation material, log and backup retention is defined in the agreement. Closing an employee account removes access but does not automatically delete organisation case material. Deleted information can remain in older backups until their agreed expiry.
- Apps you publish
- Komplai publish stores the app files and versions you publish. You choose public or organisation-only visibility. Public content is available to everyone; private apps use organisation access. The publisher determines the app’s content and any calls it makes to other services.
- Existing documents
- For documents created in the former document service, existing rules continue: documents without an account are deleted after 30 days without activity; account documents remain until the document or account is deleted. Existing link and membership permissions govern sharing. Ownership and sign-in cookies preserve access, and sign-in links are sent through Resend.
- Document cookies and backups
- The former document service’s ownership cookie lasts a year; sign-in uses a session cookie and technical cookies against forged forms and for sign-in return. The database has encrypted nightly backups. A deleted document can remain in older backups for up to 12 months. Existing impact assessments, comments and versions follow the same rules.
- Chosen third-party document AI
- If you actively choose a free third-party model in the document service’s consent dialog, only that request is sent through OpenRouter to the model provider. The processing country can vary and the provider may use content for training. This route is unsuitable for personal data. Errors never cause automatic forwarding.
Last updated:
Back to the front page