Skip to content

Compliance notes

A few constraints shape what you can do with Gungner data. None of these are things you need to build around — they’re enforced for you — but you should know they exist.

Person lookups in Sweden run under your own permit for the Swedish population register (SPAR), not something Gungner grants on your behalf. If your tenant has no active permit on file, a person-lookup call is rejected with a clear error rather than attempted or silently returning nothing.

Getting a permit is a real-world step you complete with the relevant Swedish authority. Gungner activates access to person data once that’s in hand — see the country coverage matrix, where this shows as “built, gated.”

Some people in the Swedish population register carry protected-identity status — for safety reasons, such as protection from stalking or threat. For these individuals, Gungner does not construct or return anything that would help locate them. This protection is enforced at the data layer: if a person has protected-identity status, nothing Gungner returns can be used to locate them. It isn’t something you need to detect or handle on your side.

Gungner’s own data licences — for registry data, sanctions and PEP list data, and so on — determine what can be re-shared or re-published downstream. Your contract with Gungner defines what you’re licensed to do with the data you receive: for example, some data may be usable only for your own risk decisions, not for re-publishing or reselling to a third party. Licence scope is a real constraint — check your own contract for the specifics that apply to you rather than assuming any particular use is covered.

Lithuania has no live connector yet. Some of the planned Lithuanian datasets are open data and need no agreement at all; others require your own data agreement with the relevant Lithuanian registry, with Gungner acting as processor on your behalf. See the country coverage matrix for exactly which datasets fall into which category and their current status.