Privacy & cookies

What we don't do

• We ourselves set no tracking or advertising cookies. The hosting provider Lovable does, however, set its own measurement cookie. It and the other technical cookies are described in the section Cookies and technical requests.
• We have not added any cookie-based analytics tools of our own — neither Google Analytics, Matomo, Meta Pixel nor similar. The cookie-free measurement script and the hosting provider's built-in measurement are described below.
• We store no IP address, no user agent and no device fingerprint in our own tables. Abuse protection uses a salted cryptographic IP hash. A block lasts 30 days; expiry does not mean the block record has been deleted. The separate protection log has a configurable 90-day retention default. This is separate from saved pages and reading status.
• We do not sell personal data or share it for advertising. Technical processing for operation and delivery is described below.
• We have no ads and no ad networks.
• All open facts, search, comparisons and maps require no sign-in. New member accounts are paused for now. For accounts that already exist, the email address is stored, see the member account section below.

Personal data about MPs

SVERIGEFAKTA publishes personal data about Members of Parliament to provide accountable democratic information about public office and documented parliamentary activity. The primary sources are the Riksdag's open data and official documents.

Individual profiles contain name, party in the public role, constituency, status, roles, official portrait and documented motions, speeches and votes. Gender and year of birth are not published at individual level; verified Parliament-wide aggregates may be shown. Clearly labelled in-house calculations, such as shares, party medians and calculated remuneration levels, may also appear.

Recipients, history and reconsideration

The data is publicly available to the general public and may be indexed by search engines. The site's technical providers process the traffic and data required for operation and delivery. Visit measurement is separate from the published personal profiles and is described in the measurement section.

History is retained where needed to understand a dated public mandate or parliamentary session. Indexing and continued publication are reconsidered when the mandate has ended or after a reasoned request, taking account of accuracy, currency, public interest, intrusion and historical significance. There is neither an automatic blanket refusal nor a guarantee that accurate material will be deleted.

Journalistic purpose and other processing

The publication is assessed in light of its journalistic purpose and freedom of expression and information. Swedish data-protection law contains specific exemptions for processing for journalistic purposes. This does not mean that all processing on the website is automatically exempt. Accounts, contact cases, authentication and other service functions are assessed separately.

Correction, objection and requests

You may request correction, object to an item, or request deletion or de-indexing by emailing kontakt@sverigefakta.com. State the item, the page address and, if possible, supporting material, but do not send national identity numbers or sensitive private information. The same contact route accepts other personal-data requests. Each request receives a factual individual assessment.

kontakt@sverigefakta.com · You may also lodge a complaint with the Swedish Authority for Privacy Protection (IMY). · Read the method for Parliament pages

Cookie-free measurement script

sverigefakta.com loads Fathom Analytics as its external measurement script. It is cookie-free and used for aggregated visit statistics — it sets no cookies, builds no user profiles, is not used for ads, and nothing is sold or shared onward. The script is not loaded in previews or on internal pages under /intern.

We also measure the page's loading performance (Web Vitals), fully aggregated per day and page type, without IP address, user agent, ID or query parameters. The measurement respects the browser's Do Not Track and Global Privacy Control.

Cookies and technical requests

Besides the light and dark mode cookies, described further down, the following cookies and requests may occur when you visit the website:

• session-id — set by the visitor measurement of the hosting provider Lovable. The cookie lasts 30 minutes and contains a random id. The measurement sends the page address (including query parameters), referrer, the browser's user agent and language to Lovable. It currently does not honour Do Not Track.
• Lovable's event script — sends page views, client errors and loading times to Lovable. It sets no cookie; a session id exists only in memory while the page is open.
• __dpl — technical cookie from Lovable's hosting, valid for 24 hours. We do not read it.
• __cf_bm — Cloudflare's protection against automated traffic. The cookie lasts 30 minutes and cannot be read by the page's scripts.
• Maps — the maps load background tiles from Esri (services.arcgisonline.com, USA). Your browser then sends your IP address and the map area shown to Esri.
• Searches — when you search, the query is stored as free text (lower case, at most 80 characters) together with the date, language and whether the search had results. No IP address and no identifier is stored, and nothing is sent if Do Not Track or Global Privacy Control is enabled. Do not type personal data into the search box.
• Database — our own counters, the search log and the data for existing accounts are stored at Supabase.

What belongs to your member account

New accounts, municipality watch, the Ask SVERIGEFAKTA chat, web notifications and comments are paused for now. For accounts that already exist, the following applies.

Saved pages, read status and followed municipalities belong to your member account and are stored in our database, linked to your account id. They require sign-in, are visible only to you and are deleted when you delete the account. No IP address, no cookie-based visitor identity and no fingerprinting is used for this. Without an account nothing of this kind is stored, and all open facts, search, comparisons and maps still work.

What is stored locally in your browser

Everything below is stored only on your own device. None of it contains a user ID, is linked to your IP address or is sent to the server, and none of it follows you between browsers or devices. You can clear it all at any time via your browser's settings.

• Research Workspace — saved charts and excerpts live in the browser's IndexedDB on your device and never leave it.
• Light or dark mode — your choice is stored in localStorage and in two functional cookies sf-theme and sf-theme-explicit so the page can render in the right mode immediately. They contain only "light" or "dark" and identify nobody.
• Price base — the "Original prices ↔ 2026 prices" toggle is stored under invnetto.inflation with the value "original" or "today".
• Reading path, Save and Read — without an account, your saved pages, read markers and where you left off on the reading path are stored only in this browser's localStorage (sf:lokal-lista:v1 and sf:lasvag:v1), are never sent to us and can be cleared at any time via My list or your browser settings.
• Preferences and dismissed notices — e.g. recently searched municipalities, the map guides and the editorial note you already closed. Only yes/no markers and your own choices.
• Tab marker for the counting — sf.seen in sessionStorage with the value "1", so the counting knows whether a page view was the tab's first. It disappears when you close the tab.

External links

When you click links to PDF reports (e.g. Ruist's ESO report or the National Institute of Economic Research's special studies), these open with the respective sender. What they log is governed by their own privacy policies — we have no insight into or control over that.

How we count page views

We want to know which pages are actually read, so effort is put where it helps. Every page view is therefore counted in an aggregated table. It also underlies the "Most read pages, last 7 days" list in the footer. The only things stored per page view are these six fields:

• The path (e.g. /skattetrycket never a query string or fragment.
• Date (day, not time of day).
• Language — sv or en, derived from the path.
• Traffic class — one of five fixed strings: google, bing, social, direct, other. Den fullständiga hänvisningsadressen läses i minnet, reduceras till en av dessa och slängs. Den lagras aldrig.
• Country code — two letters from the hosting provider (e.g. se), or xx if unknown. No region, city or position.
• Landing flag — whether the page was the first in the tab. A plain yes/no flag.

What is not stored: no IP address, no user agent, no session identifier, no user ID, no device fingerprint, no geolocation beyond the country code, and no full referrer address. The IP address is used only in memory for a short-lived rate limit and is never written to disk. The rows are pure sums per page and day — they cannot be linked into a visitor trail and therefore cannot be used to follow an individual person.

The counting respects your browser's Do Not Track and Global Privacy Control: if either is enabled, nothing at all is sent.

How we count shares

Pages have share buttons (X, Facebook, Reddit, copy link and save as image). When you use one of them, the event is counted in an aggregated table, the same way as page views. The only things stored are four fields:

• The path to the page — never a query string or fragment.
• Block ID — which section or footer the button sat in.
• Action — e.g. link-copied or image-saved.
• Succeeded/failed plus date (day, not time of day).

No IP address, session identifier or referrer address is stored. The rows are pure sums per page and day and cannot be linked to an individual visitor. So we see that a page was shared — never who shared it. If you click through to X, Facebook or Reddit, their own privacy policies then apply; we have no insight into what they log.

So the same share isn't counted several times when the page re-renders or when you navigate back and forth, a technical marker is stored in your browser's sessionStorage (path, block ID and action). It never leaves your device, contains no identifier, and is deleted when you close the tab.

Hosting & server logs

The website is built and hosted at Lovable, with Cloudflare in front. Like all web hosting, the hosting services can technically log IP address, time and which page was requested — this is necessary to deliver the content and to protect against abuse. We do not use these logs to profile visitors, and we never link them to an identifiable individual.

Source code & transparency

All calculation happens in your browser, based on publicly available figures from Ruist (ESO 2018:3), the National Institute of Economic Research (Special Study 117) and Statistics Sweden. See Method and Sources for full documentation.

Purposes, consent and retention

Ändamålen hålls åtskilda och blandas aldrig ihop. Kontot lagrar e-postadress, internt konto-id, verifieringsstatus, språkval och ett frivilligt förnamn. Kommunbevakningen är en tjänst du själv startar och lagrar bara kommunkod och frekvens; den kan avslutas separat utan att kontot raderas. Ett redaktionellt nyhetsbrev kräver ett eget uttryckligt ja och följer aldrig automatiskt med kontot eller bevakningen — nyhetsbrevsutskick är ännu inte byggda. Betalabonnemang är inte aktiva. Donation kräver ingen anmälan; frivillig kontakt innebär behandling av de kontakt- och transaktionsuppgifter som skickas. Offentlig tacktext kräver uttryckligt önskemål och innehåller inte transaktions-id eller kontaktuppgifter.

Retention: accounts whose email is never verified have a 30-day default; inactive watches without a linked account 180 days, watch logs 365 days and the chat’s separate protection log 90 days. These are configurable defaults, not evidence that a particular deletion run has taken place. Consent records are retained while consent remains active and can be deleted after withdrawal.

You see and change all of this yourself under My SVERIGEFAKTA: account details, active watch, newsletter choice, export of your data and permanent deletion of the account.

GDPR & your rights

Cookie-free visit measurement stores aggregate totals without visitor identifiers. Separately from measurement, SVERIGEFAKTA processes personal data in published MP profiles, member accounts, the search log, contact cases and technical delivery as described in the relevant sections. Requests about published data or other personal-data processing can be made through the contact route above.

What the hosting services (Lovable and Cloudflare) can technically log for a request — IP address, time, path — is processed for delivery and abuse protection, and is not stored by us. If you have questions about this, contact us via /kontakt. For rights exercised against Lovable or Cloudflare, see their own policies.

Changes

The date of the latest change is shown in the page header ("Last updated") and mirrored in the page's metadata. A full trail is available in the changelog.