In short
- Accounting records must be kept for years; the personal details on them usually do not need to be.
- Logs and history pile up quietly: sign-ins, email events, briefings. Each kind needs its own period.
- Minimums matter as much as maximums: proof of how you answered privacy requests must stay for at least two years.
- A good default is to preview first, then delete on a schedule you can see.
The problem with keeping everything
A CRM collects personal data in places nobody looks at: a sign-in log with network addresses, a record of every email that was opened, a morning briefing from two years ago that lists the clients someone was asked to call. None of it is wrong to collect. Keeping it forever is.
The GDPR calls this storage limitation: personal data should be kept no longer than needed for its purpose. US state privacy laws, including those of California and Texas, carry the same idea of data minimization. And every record you keep is a record that can leak.
Records the business needs
Some records exist for the business, not for the person: invoices, payments, quotations that were sent, the books. They must be kept for tax periods and audits. What they rarely need is the person's name, email and phone once the person has asked to be erased - the sale, its number and its amounts are what count.
So in Moirova, an erasure keeps these records and removes the person's details from them. The books still balance, and the person is gone. Our post on erasing a contact without breaking your books explains how.
Data that should age out
Logs and history are the opposite: useful for a while, then just risk. Moirova has a retention rule for each kind, with a default and limits you can choose within:
- Sign-in history: 13 months by default - long enough to look into a security problem.
- Email delivery and engagement events: 25 months - two full years to compare.
- Morning briefings: 3 months - a briefing is about one day.
- Follow-up suggestions: 6 months - the contact's own history stays.
Each rule shows on screen why its period was chosen.
Minimums, not just maximums
Deleting too soon can be as wrong as keeping too long. California's privacy regulations ask businesses to keep records of how they answered privacy requests for at least 24 months. So the audit trail and closed privacy requests in Moirova can never be set below two years, whatever the workspace chooses.
Preview first, then delete on a schedule
Automatic deletion should never be a surprise. In Moirova, retention rules start in Preview: each night the CRM counts what would be deleted and deletes nothing. Turning deletion on waits 24 hours, and so does choosing a shorter period, so every change is on record a day before it takes effect. A hold pauses everything during a dispute, and records about a person with an open privacy request are kept until it is closed.
If you run a Moirova workspace, the steps are in how to set data retention rules.
A worked example: what five years of CRM data looks like
Picture a twelve-person agency after five years on one CRM. It has about four thousand contacts, most of them leads that never bought. Behind them sit years of email delivery events, a sign-in log for every member of the team, hundreds of morning briefings and a long trail of follow-up suggestions that were acted on or ignored long ago.
Almost none of that history is needed today. The sign-in log from four years ago cannot help with a security question now. A briefing from last spring describes a day that is over. Delivery events from campaigns three years old do not change how next month's campaign should be written. Yet all of it can still be read, exported or leaked, and every record that mentions a person is one more place a privacy request has to reach.
With retention rules in place, the same agency keeps its clients, its deals, its invoices and its books, and lets the logs age out on a schedule it chose. The CRM gets lighter, faster to search, and far simpler to keep within the law.
How to choose a period for each kind of data
A retention period is a business decision with a reason behind it. Ask three questions for each kind of record:
- What is it for?. A sign-in log exists to investigate a security problem. An email event exists to measure a campaign. The purpose sets the period.
- When does that purpose end?. Most security reviews look back months, not years. Most campaign comparisons look back one or two years.
- Does a law require a minimum?. Tax records, and records of how you answered privacy requests, have minimums that you cannot go below.
Write the reason down. In Moirova each rule shows its reason on screen, so the next person who opens the settings understands why a period was chosen and does not change it on a guess.
Files are personal data too
Attachments are easy to forget. A client's signed contract, a scanned ID they sent with an application, a photo of a site visit - each one can hold more personal data than the contact record itself.
Moirova keeps the files clients attach to their emails with the email, on the client's page, so the team can find them. Those files count toward your workspace's storage, which keeps their growth visible. When a person is erased, the files of their deleted emails and the documents in their folder are removed with them, and the check lists each one before anything is deleted.
What minimization means for your team day to day
- Collect what you use. A field nobody reads is a field nobody needs to fill in.
- Write notes about the work, not about the person's private life.
- Keep personal files in the CRM rather than in downloads folders and laptops, where no rule reaches them.
- When a client leaves, let the history age out on its schedule instead of exporting it to a spreadsheet.
None of this slows a team down. It removes clutter, and it means a privacy request takes minutes, not a week of searching through inboxes and shared drives.
Questions to ask before you keep anything
When a new field, log or report is added to a CRM, three questions keep it honest. Who will read this, and when? What would go wrong if it were deleted after a year? Would the person it describes expect us to keep it? A field that fails all three is clutter today and a liability tomorrow. Asking them at the start costs a minute; finding the same data in an export during a privacy request costs far more.
Exports deserve the same care. A spreadsheet downloaded for one report and left on a laptop is a copy no retention rule will ever reach. Export what you need, use it, and delete it when the job is done.

