Skip to content

Security

Version of November 11, 2026

1. In short

  • The data in the app is stored and processed in the EU, in data centres in Frankfurt am Main. We make invoices for annual packages on invoice in Fiken, in the EEA.
  • Luentis only reads public pages, as a visitor does. We put no code, widget or overlay on your website, and we change nothing there.
  • The data belongs to your team. No other customer can see it.
  • You can delete scans and websites yourself, and download the reports as PDF and CSV.

This page describes the measures as they are today. What we have committed to is in the data processing agreement.

2. Where the data is

The app, the database and the queues run at Laravel Cloud, the scanner at Fly.io and the monitoring at Laravel Nightwatch, all in Frankfurt. Scan results and PDFs are in object storage at Cloudflare in the EU. The full list, with what each provider processes, is on the page Subprocessors.

3. What the scanner does and does not do

  • The scanner calls itself "LuentisBot" and only opens publicly available pages, at most one page a second. It follows robots.txt, except for the start page you gave yourself.
  • It does not fill in forms or submit anything. It only signs in when you have added a test user, cookies or a header for the website, and then it does not follow links that look like signing out.
  • Sign-in details are stored encrypted with the app's key and never shown again. They reach the scanner only in the signed job, and the scanner neither logs, stores nor returns them. A header is only sent to the website's own address.
  • It does not open internal or private network addresses, not even after redirects.
  • It runs separately from the app. Jobs for the scanner and its answers are signed with HMAC-SHA256, and answers without a valid signature are rejected.
  • Luentis never changes your website automatically. We offer no overlay or widget.

4. Sign-in and access

  • Passwords are only stored as a hash. In production, passwords need at least 12 characters with upper and lower case letters, numbers and symbols, and they are checked against known breaches.
  • You can turn on a second factor from an authenticator app, or sign in with a passkey.
  • Sign-in, the second factor and passkeys have limits on the number of attempts.
  • Everything in Luentis belongs to a team. Only members of the team can see its websites, scans, answers and statements.
  • Each member has a role: admins manage the team, members and purchases, editors scan and write the statements, and readers can only look. New members are invited by email with a link that works for seven days.
  • A team can require two-factor sign-in or a passkey for all members.
  • Organisations with Microsoft Entra ID can let their members sign in with Microsoft. The account is linked to the tenant and object ID from Microsoft, never to the email address alone, and only for the tenant the team has registered itself.
  • A shared report can only be opened with a link of 40 random characters, and you can withdraw it at any time. The links that make PDFs are signed and valid for a few minutes.

5. Encryption

All traffic to the website, the app and the scanner goes over TLS. Storage at the providers follows their own measures and certifications.

6. Logs and monitoring

The hosting provider keeps technical logs for at most 30 days. We monitor errors and performance with Laravel Nightwatch. It gets the addresses of pages without signatures, sharing links, reset links and email addresses, no IP addresses, and only the ID of the signed-in user, not their name or email.

7. Retention and deletion

  • Scans, answers and statements are kept for as long as the account exists, until you delete them.
  • You can delete a scan or a whole website in the app. When you delete your account, the websites and scans of teams you are the only member of are deleted at once.
  • Free scans without an account are deleted at the latest twelve months after the scan. Email addresses that are not confirmed are deleted after 30 days.
  • Database backups are made at the hosting provider and overwritten in the normal cycle.

8. Incidents

If we discover a personal data breach, we tell you without undue delay and at the latest 48 hours after we became aware of it, as the data processing agreement says.

9. Development and updates

The code is in a private repository, and every change runs through automated tests. We update the framework and packages and fix known vulnerabilities in them.

10. Contact

For questions about security, or if you have found a vulnerability, write to [email protected]. We answer in English, German and Norwegian.