Skip to content
Moirova

Privacy

How Moirova erases a contact without breaking your books

A person can ask a business to delete their data. A business must keep its accounting records for years. Here is how Moirova does both at once, and why a restore from a backup never brings the person back.

By the Moirova teamPublished 8 min read

In short

  • Deleting a contact record is easy. Erasing a person from everything linked to them, while the books still balance, is the hard part.
  • Moirova decides record by record: delete it, or keep it for the books with the person's name, email and phone removed.
  • You see the full plan before anything changes, and a second admin approves it.
  • Backups are not edited; an erasure ledger re-applies every erasure to any restore.

Two rules that pull in opposite directions

Under the GDPR, a person can ask for their data to be erased, and US state privacy laws give a right to delete. At the same time, tax rules ask a business to keep invoices and payment records for years - in the US, typically three to seven. A CRM that deletes everything about a person breaks the books. A CRM that keeps everything ignores the request.

The answer is to separate the record from the person. An invoice is a record of a sale: its number, its date, its amounts. The person's name, email address and phone number on it are not needed to prove the sale took place.

A decision for every kind of record

Every collection in Moirova that can hold personal data has an entry in one register, with what an erasure does to it. There are four answers:

  • Delete: the contact record, activities, emails, notes, files and follow-up suggestions - things that exist only because of the person.
  • Keep without the person: invoices, payments, sent quotations, won deals and accounting entries keep their numbers, dates and amounts; the name, email and phone are removed.
  • Unlink: a company stays, but the link to the person goes, along with contact details that were the person's own.
  • Hash: an unsubscribe is kept only as a one-way hash of the address, so the person is never emailed again, without keeping the address.

Because the decisions live in one register, there is no record type the erasure forgets. Our tests fail if code writes personal data to a place the register does not know.

See the plan, then approve it

Nobody should erase a person on trust. Before anything changes, Moirova runs a check that lists every place holding the person's data, how many records each one has and what will happen to them. In a workspace with two or more admins, a second admin reads the same check and approves it; the approval is tied to that exact check, so if the records change, the check runs again.

Then the erasure runs in steps on the server, and keeps going if the admin closes the page. A long history is never cut short by a browser tab.

The part most systems skip: backups

A backup is a copy of the database from an earlier day. Editing every backup to remove one person is neither practical nor safe. But restoring a backup must not bring an erased person back.

Moirova keeps an erasure ledger: what each erasure removed, by record number, with no name, address or phone number in it - only one-way hashes. Every restore applies the ledger again before the workspace is used. Backups themselves age out within 98 days, so the old copies disappear on a fixed schedule.

What this means for you

When a client asks you to delete their data, you can say yes without calling your accountant. The request, the check, the approval and the result are all on record, and the register entry is kept - without the person's name - as proof that you answered.

The step-by-step guide is in our Help center: how to erase a contact.

A worked example: one client, five years of records

Take a consulting client who worked with you for five years. Their contact record has a phone number, two email addresses and notes from calls. There are forty emails in their conversation, three of them with signed documents attached. There are six quotations, four won deals, twelve invoices and the payments against them, plus a company record shared with two colleagues of theirs who are still your contacts.

When that person asks to be erased, the check lists each of these places and what will happen to it. The contact record, the notes, the call logs and the forty emails are deleted, and so are the files attached to those emails, the documents in the contact's own folder and the search copies the CRM keeps so you can find records quickly. The twelve invoices, the payments and the won deals stay, with their numbers, dates, amounts and taxes intact, but the person's name, email address and phone number are removed from them. The company stays too, because two other people still work there; only the link to this person and the details that were theirs alone are removed.

Your revenue reports for those five years show the same totals after the erasure as before it. The person, however, can no longer be found anywhere in the CRM.

Addresses that more than one person uses

Real data is messy. Two people at a small business often share one address such as office@ or accounts@, and a phone number can belong to a reception desk rather than a person. A careless erasure would remove those details from everyone who uses them.

Moirova checks every address and number against the other live contacts before it decides. An address another contact also uses is left as it is, because it is theirs too, and the check says so on screen. Phone numbers are compared in one standard form, so +1 512 555 0100, (512) 555-0100 and 5125550100 are recognized as the same number and no unrelated number is touched.

Deadlines, proof and the paper trail

Privacy laws set clocks. Under the GDPR a business normally has one month to answer a request, which can be extended in some cases. California's law gives 45 days, also extendable, and several other US states follow a similar pattern. Missing the deadline is a failure in itself, even if the erasure is done perfectly later.

Moirova keeps privacy requests in a register that shows each request's deadline from the day it was received, who is handling it and what was done. When the erasure finishes, the request keeps a record of the result - how many records were deleted, how many kept without the person and how many files were removed - without keeping the person's details. That record is what you show if a regulator or the person asks how you answered.

  • The request: when it arrived, how the person was identified, and its deadline.
  • The check: every place that held the person's data and the decision for each.
  • The approval: which admin approved which check, and when.
  • The result: what was done, kept as counts and record numbers, never as the person's details.

When you should not erase yet

Erasure is a right with limits. A business may keep data it needs to meet a legal obligation, or to establish or defend a legal claim. If you are in a dispute with a client, deleting their records halfway through can hurt you and may itself be wrong.

In Moirova, a hold pauses automatic deletion while a dispute or an audit is open, and the books keep the records the law needs under the legal-obligation exception. Erasure is a decision a person makes with the full check in front of them, not something that happens on its own when a form is filled in. If you are unsure whether an exception applies to you, ask a lawyer before you approve; the check will still be there.

What to look for in any tool that holds client data

Whatever software you use, these questions show whether it can honour an erasure without damaging your accounts:

  • Does it list every place a person's data lives, including files, logs and search indexes - or only the contact record?
  • Can it keep invoices and payments while removing the person's details from them?
  • Does it show you the plan before it acts, and keep a record of what it did?
  • What happens when a backup is restored after an erasure?
  • Does it treat an address shared by several people with care?

Questions

Questions and answers

Does erasing a contact change my revenue reports?

No. Invoices, payments, won deals and accounting entries are kept with their numbers, dates and amounts, so totals for every past period stay the same. Only the person's name, email address and phone number are removed from those records.

Are the files a client sent me deleted too?

Yes. Files attached to the emails that are deleted, the documents in the contact's own folder and the stored files linked only to that person are removed with the erasure. The check lists them before anything is deleted, and any file the CRM cannot reach is listed for you to delete yourself.

Can an erased person come back when a backup is restored?

No. Backups are not edited, but every restore re-applies the erasure ledger before the workspace is used again. The ledger records what was removed by record number and one-way hashes only, so it holds no name, address or phone number itself.

Who has to approve an erasure?

In a workspace with two or more admins, a second admin reads the same check and approves it before anything changes. The approval belongs to that exact check: if the records change in the meantime, the check runs again and needs a new approval.

How long do I have to answer a request to delete data?

Under the GDPR it is normally one month, and under California's law 45 days, with extensions allowed in some cases. The privacy requests register shows the deadline of each request from the day it arrived, so the team can see what is due.

What if the person shares an email address with a colleague?

An address or phone number that another live contact also uses is left in place, because it belongs to them as well. The check shows which details were left for this reason, so you can see exactly what was and was not removed.

Bring Moirova to your team.

Tell us a little about your business. A person on our team reviews every request and replies by email.