Security overview
Last updated: 2026-09-22
This English version is a convenience translation — the Swedish version governs.
Version history
- — Counsel-reviewed final edition of the whole legal pack; effective on this date.
- — First consolidated edition of the legal pack (draft).
This page describes how Kursregistrering.se protects Course Organizers' and Course Participants' data. It covers where data is stored, how organizations are kept apart, how access is controlled, and how we handle incidents and vulnerability reports. More information about the security measures that apply when we process personal data on the Course Organizer's behalf is available in our Data Processing Agreement.
Hosting and data residency
Application data is stored within the EU. However, certain of our providers can also process or access data outside the EU/EEA. The complete sub-processor list, with data categories and information about the applicable transfer mechanisms, is available in the Data Processing Agreement.
| Sub-processor | Purpose | Region |
|---|---|---|
| Supabase (Opens in a new tab) | Database, authentication, and file storage | EU |
| Resend (Opens in a new tab) | Transactional email delivery | US |
| Stripe (Opens in a new tab) | Subscription and per-course billing (Kursregistrering.se's own billing of the organization) | EU/US |
| Vercel (Opens in a new tab) | Application hosting and content delivery | EU/Global |
| Sentry (Opens in a new tab) | Error monitoring (consent-gated in the browser) | EU |
| Upstash (Opens in a new tab) | Distributed rate limiting (Redis) | EU |
Tenant isolation
Kursregistrering.se is a multi-tenant service. Every database table holding organization data is protected by PostgreSQL row-level security (RLS). Queries are scoped to the requesting organization at the database layer, not only in application code. Tenant isolation is covered by automated tests that run on every change.
Access control and authentication
The Course Organizer's users sign in with individual accounts through our authentication provider. Every server operation that changes data passes through a shared authorization check. The check verifies the session and the user's membership and role in the Course Organizer's organization before any data is touched. Participant pages use personal single-purpose links instead of accounts, and all public endpoints are rate-limited.
Encryption
All traffic to and from the service is encrypted in transit with TLS. Data is encrypted at rest by our infrastructure providers, including database storage and backups. Secrets and API keys live in the hosting platform's encrypted configuration, never in the codebase.
Backups and continuity
The production database is backed up automatically by our database provider. The application layer is stateless and runs on managed, redundant infrastructure. It can therefore be redeployed or rolled back independently of the database.
Incident response
We have an internal incident response plan aligned with Articles 33 and 34 of the GDPR. A designated incident owner triages and contains incidents. Every incident is documented in an internal log and assessed against the notification duties in the GDPR and our Data Processing Agreement.
Customer notification commitment
We notify the affected Course Organizer without undue delay after becoming aware of an incident that affects the Course Organizer's data or use of the service. If the incident constitutes a personal data breach concerning personal data we process on the Course Organizer's behalf, the notification follows our Data Processing Agreement.
The Course Organizer is responsible for assessing whether the incident is subject to reporting or information duties under the GDPR, NIS2, or other applicable legislation. If it is, the Course Organizer is responsible for meeting the deadlines and other requirements that apply to the Course Organizer. We are correspondingly responsible for fulfilling the reporting and information duties that apply to us under applicable legislation.
Sub-processor management
We use a number of sub-processors, each bound by a data processing agreement with data protection duties corresponding to the duties under our Data Processing Agreement with the Course Organizer. The complete and current list of our sub-processors is available in our Data Processing Agreement. We inform the affected Course Organizer in advance of planned additions or replacements of sub-processors and give the Course Organizer the opportunity to object under the Data Processing Agreement.
Vulnerability disclosure
We welcome good-faith reports of security vulnerabilities in Kursregistrering.se.
Security contact: security@kursregistrering.se
This channel is also published in machine-readable form at /.well-known/security.txt (RFC 9116).
What to report
Report anything you believe affects the confidentiality, integrity, or availability of the service or its data. Examples: authentication or authorization flaws, tenant-isolation issues, or injection vulnerabilities. Include steps to reproduce. Do not access or modify data that is not your own.
What to expect
We acknowledge reports, investigate them, and keep you informed of the outcome where we can. We do not currently operate a bug-bounty program.
Safe harbor
Our starting point is not to take legal action in response to security research or vulnerability reporting carried out in good faith and in accordance with these guidelines. This requires, in particular, that you make reasonable efforts to avoid privacy intrusions, access to or modification of other people's data, and disruptions to the service. It also requires that you give us reasonable time to investigate and remediate the vulnerability before public disclosure.