At a glance
- A correction is checked first: Moirova lists every record that still holds the old name, email or phone, then corrects the live ones.
- Issued documents and history keep the details they were made with - an invoice you sent stays as it was sent.
- A restriction stops email, campaigns, journeys, AI and automated follow-up for the contact, and keeps their data.
- Only an admin can lift a restriction, with a reason that goes in the audit trail.
Before you start
- Who can do it
- Admins, and people given "Handle privacy requests".
- Where it is
- Admin, Privacy, Requests: a request of the type "Correct their data" or "Stop using their data for now".
- What you need
- A recorded request with the identity check done.
Correct a name, email or phone
Editing a contact changes the contact record. But the old details also live in copies: the name on a deal, the email a journey sends to, the phone on an open quotation. A guided correction finds those copies so nothing is missed.
- Open the request. Open the "Correct their data" request and record the identity check if it is not done.
- Enter the right details. Type the corrected first name, last name, email or phone.
- Check what changes. Choose Check what changes. Moirova lists every place that still holds the old details and what it will do with each one: correct it, or keep it as it was and why.
- Apply the correction. Choose Apply correction. The live records are corrected and the request's log records what changed.
What a correction keeps as it was
- Issued documents, such as an invoice or quotation that was sent: they record what was sent and when.
- The audit trail and the activity history: they record what happened at the time.
- Notes and message texts written earlier: they are not rewritten.
- Records found only because they share an email address with the contact, such as a shared office inbox: they are shown so you can check them by hand, never changed.
This matches what the GDPR asks: correct the data you use, without rewriting the record of what happened.
Restrict the use of their data
A person can ask you to stop using their data for now - for example while they dispute whether it is accurate. Restricting keeps the data and stops every automatic use of it.
- Open the request. Open the "Stop using their data for now" request and record the identity check.
- Restrict. Choose Restrict the use of their data and give the reason.
- See it on the contact. The contact page shows a banner while the restriction is on, so everyone on the team knows.
While a contact is restricted:
- No email is sent to them from Moirova, and no campaign or journey includes them.
- They are left out of audiences.
- No AI feature and no automated follow-up uses their record.
- Their data stays exactly as it is.
Lift a restriction
When the reason is resolved, an admin chooses Lift the restriction and gives the reason. The change is in the audit trail and the request's log. Other team members cannot lift it, so a restriction cannot be removed by accident.
Tip
Close the request once the restriction is in place: the restriction stays on after the request is closed, until an admin lifts it.

