Security Policy
1. Scope
This Security Policy describes how Puraderi AB protects Kungora and the data processed in the service: organisations’ content and private workspaces, user accounts, followers, journalist accounts and logs. It supplements clause 18 (Annex 2) of the Data Processing Agreement.
2. Organisation and responsibility
2.1 Responsibility
We have an appointed security officer who is responsible for the policy being followed and kept up to date. Our information security management system follows the principles of ISO/IEC 27001 Annex A and Article 21 of Directive (EU) 2022/2555 (NIS 2), although we are not certified today.
2.2 Staff
All staff with access to systems or data have signed a confidentiality undertaking, receive training in information security and data protection, and have only the permissions their work requires. Permissions are reviewed regularly and removed when no longer needed.
3. Hosting and storage
3.1 Within the EU
The service runs on servers at Hetzner Online GmbH in Germany. Databases and files are stored at Hetzner in Germany, and the backups at Backblaze in the Netherlands, so with another provider. Everything is stored within the EU. Hetzner is certified under ISO/IEC 27001.
3.2 Suppliers
We use as few suppliers as possible. The current list is on the Sub-processors page.
4. Encryption
4.1 In transit
All traffic to the service is encrypted with TLS 1.2 or 1.3. Our domains use HTTP Strict Transport Security. Certificates for organisations’ own domains are issued and renewed automatically.
4.2 At rest
The database’s storage volumes are encrypted. Backups are encrypted before they leave the server. Secrets such as keys and service passwords are stored encrypted, and sensitive fields, for example webhook secrets, are encrypted in the database.
5. Access control
5.1 Organisations’ users
- Passwords must be at least 12 characters long and are checked against known breached passwords with a method in which the password never leaves us.
- Passwords are stored only as salted hashes.
- Two-factor authentication with an authenticator app and passkeys is available to everyone, and an organisation’s owner can require two-factor authentication for all users.
- Recovery codes are stored encrypted.
- Sensitive actions, such as creating API keys and webhook signing secrets, transferring ownership, closing the account, deleting a newsroom and exporting the organisation’s data, require a recent sign-in.
- Invitations are valid for 48 hours.
5.2 Our staff
- Staff tools are reachable only over an encrypted private network and have their own sign-in, separate from customers’.
- Sign-in requires a password and a passkey; a code from an authenticator app is used only as a fallback. Sessions last at most eight hours.
- Staff have no direct access to organisations’ contact lists. Every time staff view an organisation’s data a reason is given, and the access is logged.
6. Separation of data
6.1 Per organisation
Each organisation’s data is protected in the database by row-level access control, so that one organisation can never read another organisation’s data, even if an error occurred in the application.
6.2 Private and public data
Drafts, scheduled publications and embargoed material are stored separately from published content. Unpublished files are stored privately at random addresses and are shown only through signed links valid for five minutes.
6.3 Separate roles
The servers that show public pages have no access to private data, files or sign-in secrets. Each part of the service uses its own database role with least privilege, and the permissions are checked by automated tests.
6.4 Contact lists stay put
Organisations’ contact lists and sends never leave the primary database and are never part of statistics, exports to third parties or our company-information service.
7. Logging and traceability
7.1 Audit log
Important events, such as sign-ins, changed roles, publications, exports, API keys and staff actions, are written to an audit log that cannot be changed afterwards and is deleted only as a whole, month by month, after 12 months. Every night the previous day’s log is sealed with a chain of hashes, and the seal is kept on separate storage, so that later changes are detected.
7.2 Access logs
Our servers write access logs in which IP addresses are shortened and one-time links are masked before anything is stored.
8. Backups and recovery
The database is backed up continuously by archiving its transaction log and by regular full copies. The copies are encrypted, stored in another location within the EU and kept for 30 days. We test restoring regularly and document every test.
9. Secure development
- All code is reviewed by another person before it goes into production, and the main branch is protected.
- Automated tests run for every change, including tests of database permissions and of unpublished content never being visible publicly.
- Dependencies are updated continuously and checked against known vulnerabilities, and the code is scanned for leaked secrets.
- All content organisations enter is cleaned of dangerous code before it is shown, and public pages are protected by a strict Content Security Policy.
- Outgoing requests to addresses users provide, for example webhooks, go through a protection that prevents requests to internal networks.
- The service is scanned automatically for vulnerabilities. We plan to have an external party carry out penetration tests at least once a year.
10. Protection against misuse
Public forms are protected by a self-hosted check against bots that does not ask you to solve puzzles, and by rate limits. Uploaded files are scanned for malware, and location data is removed from published images. Publications are checked against our Content Policy.
11. Email
Our email is sent with SPF, DKIM and DMARC and with a one-click unsubscribe link. The sender’s identity is always stated in the email.
12. Incident response
12.1 Procedure
We have a documented procedure for detecting, containing, investigating and remedying security incidents, and a register of all personal data breaches.
12.2 Notifications
For a personal data breach where we are the controller, we notify the Swedish Authority for Privacy Protection within 72 hours where required, and inform the people concerned when the breach is likely to result in a high risk to them. Where we are a processor, we notify the customers concerned within 48 hours.
13. Continuity
We monitor the service’s availability around the clock from a separate server and have plans for restoring the service after a serious outage.
14. Reporting vulnerabilities
If you find a vulnerability, we would like to hear from you at security@kungora.com. Please read our Vulnerability Disclosure Policy first. The contact details are also in https://kungora.com/.well-known/security.txt.
15. Review
We review this policy at least once a year and whenever the service or the threat landscape changes significantly.