For varje kategori av personuppgifter: vem ar personuppgiftsansvarig och vem ar personuppgiftsbitrade.
For each category of personal data: who is the controller and who is the processor.
Forenings- och foretagsdata (namn, adress, e-post, telefon), evenemang, rutter och allt annat innehall som registreras via kommunkoordinatorns administrationsgranssnitt.
| Roll | Part | Motivering |
|---|---|---|
| Personuppgiftsansvarig | Kommunen | Kommunen bestammer andamalet med registreringen och vilka uppgifter som ska samlas in |
| Personuppgiftsbitrade | HDS | HDS behandlar uppgifterna pa kommunens uppdrag och instruktion |
Medlemsnamn, e-post, medlemsnummer, anpassade falt och betalningsreferenser for foreningars Bli Medlem-funktion.
| Roll | Part | Motivering |
|---|---|---|
| Personuppgiftsansvarig | Foreningen | Foreningen bestammer vilka uppgifter som kravs for medlemskap |
| Personuppgiftsbitrade | HDS | HDS lagrar och behandlar uppgifterna pa foreningens uppdrag |
| Mellanliggande part | Kommunen | Kommunen har avtal med HDS och ansvarar for att foreningar inom kommunen behandlar personuppgifter lagligt |
Inloggningsuppgifter (e-post, hashat losenord), sessionstoken och kontoinstallningar for alla registrerade anvandare.
| Roll | Part | Motivering |
|---|---|---|
| Personuppgiftsansvarig | HDS | HDS bestammer andamalet med anvandarkonton (autentisering av plattformens anvandare) och behandlar uppgifterna for eget andamal |
Sidvisningar och anvandningsstastistik insamlade av Umami (sjalvhostad pa HDS-infrastruktur).
| Roll | Part | Motivering |
|---|---|---|
| Personuppgiftsansvarig | HDS | Umami samlar inte in persondata (ingen IP-lagring, ingen fingeravtryckstagning). HDS kontrollerar konfigurationen. |
Ingen extern analytiktjanst med persondata anvands. Google Analytics eller liknande forstar aldrig.
Association and business data (name, address, email, phone), events, routes, and all other content registered via the municipality coordinator admin interface.
| Role | Party | Rationale |
|---|---|---|
| Data Controller | Municipality | The municipality determines the purpose of registration and which data to collect |
| Data Processor | HDS | HDS processes the data on behalf of and under instruction from the municipality |
Member names, email, membership numbers, custom fields and payment references for associations using the Bli Medlem feature.
| Role | Party | Rationale |
|---|---|---|
| Data Controller | The Association | The association determines what data is required for membership |
| Data Processor | HDS | HDS stores and processes the data on behalf of the association |
| Intermediary | Municipality | The municipality contracts with HDS and is responsible for ensuring associations process personal data lawfully |
Login credentials (email, hashed password), session tokens and account settings for all registered users.
| Role | Party | Rationale |
|---|---|---|
| Data Controller | HDS | HDS determines the purpose of user accounts (authenticating platform users) and processes the data for its own purpose |
Page views and usage statistics collected by Umami (self-hosted on HDS infrastructure).
| Role | Party | Rationale |
|---|---|---|
| Data Controller | HDS | Umami does not collect personal data (no IP storage, no fingerprinting). HDS controls the configuration. |
No external analytics service with personal data is used. Google Analytics or similar will never be introduced.