There's no server holding a second copy of this meeting for you.

A cloud notetaker's recordings live on somebody else's infrastructure, which comes with a real cost — the audio had to leave your Mac to get there — but it also means a dead laptop doesn't erase the archive. Coii AudioNotes trades that upload away, which means the files it produces exist in exactly one place until you decide otherwise. That's not a gap in the product; it's the same tradeoff as any other file on the Mac, and it has the same fix: a backup routine that doesn't depend on remembering to run it.

What actually needs protecting

A single recorded meeting isn't one file — it's three, kept together as one entry in the app's archive: the audio recording itself, the transcript built from it, and the minutes generated once the call ends. A backup that catches the audio but misses the transcript still loses the thing most people actually go looking for later, since a transcript is what gets searched and a summary is what gets skimmed; the raw audio is usually the one file nobody reopens.

That example is the ordinary shape of why this matters: nobody backs up a meeting archive because of the meeting that just happened. They do it because of the one a client, a manager or a lawyer asks about eight months from now, after the laptop that made the original recording has since been replaced, dropped, or simply full — the same reason searching an old archive only works if the archive being searched still exists.

Step 1 — find out where the archive actually sits

Before backing anything up, it's worth knowing what's being protected. The app keeps its recordings, transcripts and minutes in its own data folder on the Mac rather than scattering them across the Desktop or Documents — that's a deliberate choice, since a backup routine that already covers "everything on this Mac" needs to actually include that folder, not just the ones a person happens to save things into by hand. If a backup tool is configured to skip certain folders — some people exclude anything that looks like an app's internal storage — it's worth checking that this one isn't caught in that exclusion by accident.

Step 2 — turn on Time Machine, or confirm it's already running

For most people, the entire answer to "how do I back this up" is Time Machine, macOS's own backup tool, pointed at an external drive or a network volume. It's not something Coii AudioNotes has to integrate with specially — it works the same way for a meeting archive as it does for a photo library or a folder of tax documents, because both are just files on the same disk. The part people actually get wrong isn't turning it on; it's not noticing when the backup drive stopped being plugged in three weeks ago and quietly stopped protecting anything since.

Step 3 — add a copy somewhere other than the same room

Time Machine on a drive sitting next to the Mac protects against a failed disk, not against a fire, a theft, or a laptop and its backup drive going missing from the same bag at once. A second copy somewhere physically separate closes that gap — a drive kept at a different address, or a personal cloud-storage folder (iCloud Drive, Dropbox, whatever's already in use) that the archive folder is deliberately copied into on a schedule. That's a choice made by the person who owns the files, on their own account, not something the app does on its own — nothing here is Coii AudioNotes syncing anywhere by default, which is the whole point of how it handles recordings in the first place.

Step 4 — for higher-stakes recordings, rotate an external drive

Anyone whose recordings are the kind a client, a compliance policy or opposing counsel might one day ask for benefits from a stricter routine than "Time Machine, eventually." A second external drive, kept unplugged except when it's updated and stored somewhere other than the desk the Mac sits on, is the simplest version of that — a monthly or weekly copy, rotated between two drives so a single failure during the copy itself never leaves zero good backups. It's more manual than Time Machine and it's also the version people actually trust when something goes wrong, because it was checked by hand rather than assumed to be running.

Step 5 — check that a backup can actually restore something

The same logic applies to exporting a transcript out to somewhere else entirely — a second location a backup doesn't even need to know about, but a useful option for the one file that matters most. A backup that has never been tested, meanwhile, is a belief, not a fact. Once a routine is in place, it's worth deliberately restoring one old recording from it — not because anything is wrong, but because the first time most people discover a backup was silently failing is the day they need it, and that's the worst possible time to find out. Ten minutes spent restoring one file from a drive is cheap insurance against a much longer conversation later.

What a lost or stolen Mac actually means for this archive

Because everything lives as files on the Mac rather than behind a separate cloud login, the meeting archive is exactly as exposed as anything else stored there — someone who can unlock the machine can open the recordings on it, the same as any other document. Turning on FileVault, Apple's built-in full-disk encryption, means a lost or stolen Mac that's locked stays that way for whoever finds it; it's a macOS setting rather than anything specific to this app, and it's worth having on regardless of whether meeting recordings are part of what's at stake.

Retiring or selling the Mac these recordings are on

Files stay exactly where they were written until the drive that holds them is erased — nothing about the app quietly removing itself takes the archive with it. Before wiping a Mac for resale, trade-in or handoff, the practical order of operations is: confirm a current backup exists, then erase. That's the step people skip when they're in a hurry to get a trade-in processed, and it's the one that turns "the old laptop is gone" into "the old laptop is gone and so is a year of meeting notes," which a five-minute check the same afternoon would have prevented.

How this differs from trusting a cloud tool's "backup"

A cloud notetaker's servers hold the only copy of a recording too, in a different sense — the vendor's infrastructure is doing the job Time Machine does here, which sounds like less to think about until the thing that goes wrong isn't a failed drive but a company shutting down, getting acquired, or changing its retention terms. Either way, one copy sitting in one place is one copy, whether that place is a vendor's data center or a Mac on a desk — the difference is who controls when it disappears and whether there's any warning first.

How big this archive actually gets

It's worth sizing the problem before deciding how seriously to take it. A transcript and a set of minutes are both plain text, small enough that a year of them barely registers on a modern drive. The audio recordings are the part that adds up — an hour of meeting audio a day, most weekdays, across a year, is a meaningful chunk of storage, though still well within what an external drive handles without strain. Knowing that in advance matters for choosing a backup drive with enough headroom rather than discovering six months in that the one bought for "some documents" is already full of a year of recordings it wasn't sized for.

What a partial backup actually protects against

Not every backup failure is total. A Time Machine drive that's been unplugged for three weeks still has three weeks of backups sitting on it — old, but not nothing. The risk worth planning for specifically is the gap between "the last time this actually ran" and "right now," because that gap is exactly the set of recordings with no backup at all. Checking, occasionally, how recent the last successful backup actually was is a more useful habit than assuming a backup routine set up once is still running the way it was configured to.

Deciding what's worth keeping forever versus what isn't

Not every recording deserves the same backup treatment. A weekly internal status sync six months from now is probably not something anyone will go looking for; a signed-off client scope call, a board meeting, or an interview that ended up in a published piece might be referenced for years. Rather than backing up an entire undifferentiated archive with equal care, it's worth periodically deciding which specific recordings are worth a more durable, off-site copy and which ones can simply age out of a rolling Time Machine window without anyone noticing.

A routine that doesn't ask you to remember much

The backups that actually work long-term are the ones that don't depend on remembering to do them. Time Machine, left running against a drive that stays connected, covers the everyday case without anyone thinking about it again. On top of that, a monthly reminder to check the drive is still plugged in and the backup still current takes less time than writing this sentence took to read, and it's the single habit most likely to matter the one time it's actually needed. Everything past that — the off-site copy, the rotated external drive — scales with how much a specific recording would cost to lose, not with how many meetings happen in a week.

Who ends up caring about this the most

Anyone recording client work, board meetings or anything that might get referenced months later has more riding on this than someone using the app for their own weekly team sync. A private practice's session notes and a board secretary's minutes archive are both examples of a folder that starts mattering more the longer it's been since the meeting happened — the exact moment a backup routine either paid for itself or didn't exist. The same reasoning is why a local-first archive puts backup ownership back on the person who made the recording in the first place, rather than a vendor's own retention schedule.

A short checklist worth revisiting once a quarter

Backup routines tend to be set up carefully once and then never looked at again, which is exactly how a silently broken one goes unnoticed for months. Once a quarter, three quick checks cover most of what actually matters: confirm the backup drive was connected recently enough to have run, confirm the off-site or cloud copy — if one's in place — is current rather than months stale, and open one recording at random from the backup itself to confirm it plays and reads correctly rather than assuming the file made it across intact. None of those take more than a few minutes, and together they're the difference between a backup that exists in theory and one that would actually work the day it's needed.

Backing up more than one Mac on the same licence

A licence covers up to three Macs, and each one keeps its own independent archive rather than a shared one — a recording made on a laptop doesn't automatically appear on a desktop also running the app under the same licence. That means backup is a per-Mac responsibility too: a routine set up on one machine doesn't extend to the others just because they share a licence, and it's worth confirming each Mac actually in use for recording has its own backup covering it, rather than assuming the work done on one covers all three.

What it costs, what it runs on

None of this backup routine is a feature of Coii AudioNotes specifically — it's the ordinary responsibility that comes with an app that costs $19 once, runs entirely on the Mac, and never uploads a recording anywhere on its own. The trial is 30 days, no card, no account, the same terms as the finished product, and it runs on macOS 13 Ventura or later, on Apple Silicon or Intel. What the app actually does day to day covers the rest of it beyond keeping the archive safe once it exists.