Dōrvis

Sign in

Personal code GDPR rules: processing the Latvian personal code at login

When you process a Latvian personal code (personas kods) during authentication, GDPR requires a lawful basis, a clear purpose and only the data you need. Dorvis returns a verified first name, last name and personal code after login. The data is processed only in Latvia.

Dorvis team 12 October 2026 3 min read

In this article
  1. Provisions that apply to the personal code
  2. Why the personal code is used at login
  3. Good practice for handling the personal code
  4. Dorvis and data protection

Provisions that apply to the personal code

Sources: Regulation (EU) 2016/679 and the Latvian Personal Data Processing Law on likumi.lv, checked 12.10.2026.
ProvisionWhat it says
GDPR Article 4(1)Personal data is any information about an identified or identifiable person, for example by a name or an identification number. The personal code is personal data.
GDPR Article 5(1)(c)Data minimisation: data must be adequate, relevant and limited to what is necessary for the purposes.
GDPR Article 5(1)(e)Storage limitation: data is kept in identifiable form no longer than necessary.
GDPR Article 6(1)Processing needs a lawful basis, such as performance of a contract, a legal obligation or legitimate interests.
GDPR Article 28Where someone processes data on a controller's behalf, there must be a contract with the content the Regulation sets out.
GDPR Article 87Member States may set specific conditions for processing a national identification number; it may be used only with appropriate safeguards.
Personal Data Processing Law, section 3(1)The Data State Inspectorate is the supervisory authority within the meaning of the GDPR.

Why the personal code is used at login

Latvian e-identities (Smart-ID, eParaksts and bank login) identify a person by personal code. That lets you match a login reliably to an existing customer record, such as a contract or patient file, even if the customer has changed email or phone.

The lawful basis depends on your service: often it is performance of a contract or a legal obligation to identify the customer. Consent is usually not the best basis when you cannot provide the service without identification.

Good practice for handling the personal code

  • Request only what you need. Dorvis returns the personal code in the profile scope together with the first and last name. If you only need to know the person was verified, you do not have to store the code in your own system.
  • Do not keep it longer than needed. Set a retention period, and never use the personal code as a public identifier, for example in URLs or emails.
  • Limit access. Only staff and systems that need the personal code should see it, and access should be logged.
  • Tell your customers. State in your privacy notice that you receive the personal code at login, for what purpose and on what basis.
  • Put contracts in place. If an authentication service processes data on your behalf, agree the roles and terms (GDPR Article 28).

Dorvis and data protection

Dorvis infrastructure is in Latvia and personal data is not transferred outside Latvia. Dorvis does not store user passwords: the provider confirms the identity. Every login is recorded in an audit log, and keys are held in a separate secure vault.

Roles depend on the situation: for your customers' data in your portal you are usually the controller, while SIA Dativa is the controller for Dorvis account data. See the privacy policy for details, and email info@dorvis.eu about a data processing agreement.

Last reviewed:

Questions about data processing?

We will explain what data Dorvis receives, where it is stored and how to minimise it in your integration.

Loading complete

We use cookies to make this website easier to use. Read our Privacy and Cookie Policy.