Skip to content
KUHNIA Studios

Security

How Kuhnia Studios protects its services and its users' data, and how to report a vulnerability you have found.

Updated (version 1.3)

Principles

The best protection for personal data is not to collect it. That is why we design our apps to collect as little data as possible:

  • DIN Calculator does not send the data you enter anywhere.

How the services are protected

  • Encrypted connections: all traffic to the servers is encrypted (HTTPS/TLS).
  • Access control: server administration is only possible through a closed, encrypted network. Administrator accounts use two-factor authentication where the service supports it.
  • Server protection: a firewall and automatic attack detection block known attack attempts.
  • Updates: the operating system, software libraries and apps are kept up to date. Dependencies are checked for known vulnerabilities.
  • Data minimisation: query parameters and other unnecessary information are not stored in logs, and old data is deleted automatically according to retention periods.
  • Security headers: kuhnia.fi uses a strict Content Security Policy and does not load anything from third parties.

Personal data breaches

If a personal data breach occurs, we will act as follows:

  • We will investigate what happened and contain the damage without delay.
  • We will notify the Office of the Data Protection Ombudsman of the breach within 72 hours where the law requires it.
  • Where the breach is likely to result in a high risk, we will also notify those affected.

Reporting vulnerabilities

We appreciate reports of security issues. If you find a vulnerability in any Kuhnia Studios service, send a report to support@kuhnia.fi. Use “Security” as the subject line.

A good report includes:

  • which service and address the issue concerns
  • how the issue can be reproduced
  • your assessment of its impact.

What we promise:

  • We will acknowledge receipt of your report.
  • We will tell you how the matter is progressing, and fix confirmed issues.
  • We will not take legal action against a reporter who acts in good faith in accordance with these guidelines.
  • We will credit the reporter in our acknowledgements if they wish.

We ask that you:

  • do not exploit the issue beyond what is needed to demonstrate it
  • do not view, modify or delete other users' data
  • do not degrade the service's operation or carry out denial-of-service attacks, social engineering or physical intrusion attempts
  • give us a reasonable amount of time to fix the issue before disclosing it publicly.

We do not pay rewards for findings (there is no bug bounty programme).

Machine-readable contact information is also available at /.well-known/security.txt.