Private persons and population registersCopy Anchor Link

When you add a private person to Strise with a national identity number, Strise keeps the person's register data up to date for as long as the person is stored and subscribed to register updates. This happens whether or not the person is in monitoring. Monitoring and register updates are two separate things: removing a person from monitoring does not stop register updates. To stop them, unsubscribe the person or delete them. To start them again, subscribe the person.

Keeping the two apart lets you match what Strise does to what you need for each person:

• Monitoring without register updates — keep screening a person daily against PEP and sanctions lists, but stop Strise from updating their name, address and other details from the register. For example, when you only need sanctions and PEP screening for the person, or when you do not want Strise to hold an ongoing register subscription for them.
• Register updates without monitoring — keep the person's register data current, for example for a person you hold on record but do not need monitoring alerts for.

See Private Persons Monitoring for what monitoring covers.

What happens when you add a personCopy Anchor Link

Which register Strise uses depends on the person's country:

Register lookups and updates need access to the register:

• Denmark — CPR is available only to organisations with a CPR agreement through Strise. Contact support@strise.ai to find out whether it applies to you.
• Norway — Strise uses the Folkeregisteret access your team has delegated to Strise. See Norwegian Folkeregister Access.

If you create a person through the Connect API with privatePersonCreateNoEnrich, Strise does not look the person up in the register, and the person is created without a register subscription. Strise does not keep the person's data up to date from the register in any country, and in Denmark it does not subscribe to the person's CPR number, until you subscribe the person with privatePersonSubscribe.

Danish CPR subscriptionsCopy Anchor Link

In Denmark, register updates rely on a subscription that Strise registers with CPR for each person's CPR number. A person can see which organisations subscribe to their CPR number through CPR's own self-service.

If CPR has registered name and address protection (navne- og adressebeskyttelse) for a person, CPR does not disclose the person's name or address to Strise. Strise then keeps whatever name and address you provided when you added the person.

Monitoring is separate from register updatesCopy Anchor Link

Adding a person to monitoring, or removing them, only controls Strise monitoring of that person — whether alerts are raised for them in your monitoring workflow. See Monitoring System. PEP or sanctions hits a person already has when you add them to monitoring don't alert, unless your team has turned on Alert on hits found when an entity is added to monitoring.

It has no effect on register updates. Four actions control what happens to a stored person:

Unsubscribing also removes the person from monitoring, unless you clear Also remove from monitoring in the app or pass removeFromMonitoring: false to privatePersonUnsubscribe. A person you keep in monitoring is then monitored on the data Strise already holds for them.

Subscribing starts register updates again for a person who was unsubscribed or created with privatePersonCreateNoEnrich. It also adds the person to monitoring, unless you clear Also add to monitoring in the app or pass addToMonitoring: false to privatePersonSubscribe. Strise does not look the person up in the register when you subscribe them; it applies register updates from then on. If the register cannot be reached, subscribing fails and the person stays unsubscribed, so you can try again. Calling privatePersonSubscribe for a person who is already subscribed does not subscribe them again.

In the app, Stop register updates is shown only for a person who receives register updates, and Resume register updates only for an unsubscribed person. Both need the same permission as Edit.

Deleting a person also removes them from monitoring. In Denmark, unsubscribing or deleting a person makes Strise end its subscription to the person's CPR number, unless another Strise team still keeps the same CPR number subscribed. This is processed shortly afterwards, not at the same moment. In the app, deleting a private person requires the Delete private persons permission.

Check whether a person receives register updatesCopy Anchor Link

In the app, the person's page shows a Register updates badge while Strise applies register updates, and a No register updates badge for an unsubscribed person; hover over it to see when they were unsubscribed. No badge is shown when register updates are not available for the person.

In the Connect API, the registerSubscription field on a private person returns a status and, for an unsubscribed person, unsubscribedAt — when they were unsubscribed:

UNAVAILABLE takes precedence: an unsubscribed person whose register updates are not available reports UNAVAILABLE, not UNSUBSCRIBED. unsubscribedAt is still set for them.

Which action to useCopy Anchor Link

Delete the person when you no longer need to process their data — for example when a customer relationship ends. Removing them from monitoring alone keeps the person stored in Strise and keeps their register data, and in Denmark their CPR subscription, active.

Unsubscribe the person when you need to keep them in Strise but no longer want Strise to update their data from the register — for example when you keep a record for a retention period after the relationship ends.

Remove a person from monitoring only when you still need to keep them in Strise with up-to-date register data, but no longer want monitoring alerts for them.

RelatedCopy Anchor Link

• Norwegian Folkeregister Access — how to delegate Folkeregisteret access to Strise.
• Monitoring System — how monitoring and alerts work.
• Data Sources — the registers and data providers Strise uses.