๐ŸŽ™๏ธ Digital Front Desk

Data retention & deletion

Last updated: 2026-08-07 ยท Version 0.1 ยท Status: Draft for legal review โ€” not yet in force

What is kept, for how long, and what deleting actually deletes. Written from the scheduled job that does the deleting, not from an intention. Where the software keeps something after you have asked it not to, that is stated here rather than left for you to discover.

1. The automatic purge

A scheduled job runs daily and permanently deletes:

WhatAfter
Call records โ€” the transcript, caller number, timings, the generated summary, sentiment and action items 6 months
Operational diagnostic events 90 days

This is a hard delete, not an archive or a flag. Once the job has run, the row is gone and we cannot produce it again โ€” including for you.

2. What the purge does not touch

This is the section a template would omit. It is the one worth reading.

Review note โ€” remove before publishing. The shared, unpurgeable assistant memory is the most significant gap between what a customer will assume and what the software does. It should be resolved in the product โ€” by scoping memory per user, or by building a purge path โ€” rather than only disclosed. Until then this page must keep saying so, and no contract should promise deletion we cannot perform.

3. Asking us to delete something

If you are a business using the service, you can clear your saved business information from your own settings page at any time. For anything else โ€” a specific call record, a customer's data, or your whole account โ€” write to info@moneliautomation.com.

If you telephoned a business and want your information removed, ask that business: they decide what is collected and we act on their instructions. The call recording and AI disclosure page explains this.

We will tell you plainly which parts we can delete and which we cannot, including the assistant memory described above.

4. When an account closes

[ACCOUNT CLOSURE PROCESS AND TIMELINE]

Review note โ€” remove before publishing. The account-closure path is not implemented. Decide the timeline, whether an export is offered first, and whether the customer's dedicated machine is destroyed or wiped โ€” then write it here and build it.
This is not legal advice. This document was drafted from what the software actually does, by the people who built it, and it has not been reviewed by a lawyer. It must be reviewed by Canadian privacy counsel โ€” and, where a customer is a health information custodian or a law firm, by counsel familiar with PHIPA, the Alberta Health Information Act, Quebec's Law 25 and professional obligations of confidentiality โ€” before it is published or relied on by anyone. Highlighted [LIKE THIS] are facts we have deliberately not invented; they must be filled in before publication.