The meeting we accidentally lost

It was a Thursday morning in March when a Scribr user - a therapist based in Manchester - sent us a message that stopped me mid-coffee. She'd accidentally deleted three months of session notes. Not maliciously. Not through negligence. She'd simply tapped the wrong button, and they were gone. Within minutes, she'd lost what amounted to years of clinical context, trust-building, and care.

What she asked for wasn't a recovery feature

I assumed she wanted an undo button or a trash bin. We could build that. But her follow-up email said something different. She didn't ask for recovery. She asked: "Could you make it so that even I can't accidentally delete something sensitive? Something I'd have to really think about before I could touch it?"

That question haunted me for a week. Because it revealed something we'd been building around the edges but never made central: people don't just want their data safe from hackers. They want it safe from themselves. From a tired Friday afternoon tap. From the coffee-spill moment. From the "oh God, what have I done" panic.

We looked at our usage data and realised this wasn't isolated. Consultants were asking if they could password-protect client notes. Lawyers wanted a way to lock sensitive case files. Researchers were asking if there was a way to isolate their most important recordings from casual deletion.

The pattern was clear. They weren't paranoid. They were responsible.

We built Vault Mode because trust isn't just technical

Vault Mode arrived in Pro last year. It's AES-GCM encrypted - military-grade, the same standard that secures everything from banking to classified communications. But the feature itself isn't really about cryptography. It's about intention.

When you lock a note into Vault Mode, it doesn't disappear. You still see it. You can still read it, replay it, search it. But you can't edit it, move it, or delete it without unlocking it first. Unlocking requires biometric verification (face or fingerprint) or a passphrase you've set yourself.

For the therapist in Manchester, it meant her notes from that day forward stayed exactly as recorded. If she needed to access them, a single Touch ID tap. But that moment of friction - that deliberate pause - meant she'd never lose something in a moment of distraction again.

I watched a sales team at a fintech company adopt it differently. They used Vault Mode for recordings of client calls where they'd quoted specific fees or terms. Locked them in, date-stamped, unhittable. Not because they were hiding anything from their customers. Because they wanted a clean record they couldn't accidentally tamper with.

Why this mattered more than we expected

Here's what surprised us: the people who cared most about Vault Mode weren't paranoid. They were the opposite. They were people whose work lived inside relationships. A therapist. A consultant. A researcher interviewing vulnerable populations. A legal aid solicitor handling asylum cases.

They didn't want encryption because they thought we'd spy on them. They wanted it because their work demanded it. Because their clients had trusted them, and that trust needed infrastructure. And because sometimes, the best security feature isn't one that keeps the world out. It's one that keeps you honest with yourself.

The therapist wrote back after a month. She'd locked about 40 notes into Vault Mode. She told us it changed how she thought about record-keeping, not because she was suddenly more secure, but because she was suddenly more deliberate. Each lock was a small ceremony. A commitment to the person in that session.

What we learned we still needed to get right

Building Vault Mode taught us something that doesn't fit neatly into a product roadmap: security is boring when it works. Nobody celebrates an encrypted note. They celebrate a recovered file, a fixed bug, a new feature that saves time. Encryption is just the thing that should already be there.

But it also meant we had to get the unlock experience right. Too hard, and people abandon the feature. Too easy, and it's a false comfort. We settled on biometric as default - fast enough that you don't resent using it, secure enough that casual thumb-scrolling won't open locked notes. And if biometric isn't your thing, you set your own passphrase.

We also built in the GDPR Compliance Mode for Team plan users, which adds an audit log. So if someone ever asks "who accessed this note and when," you have a clean record. Not because we assume you'll abuse it. Because some industries need to prove they didn't.

The real lesson: listen to what people don't ask for

If that therapist had asked us to "implement end-to-end encryption," we probably would have built something that looked right but felt wrong. Instead, she asked us to solve a human problem. She wanted safety from her own moment of carelessness. She wanted her notes to demand respect.

That's what Vault Mode actually does. It forces a pause. It says: these words matter enough to protect deliberately. Not hidden, not secret, just deliberate.

Every person using Scribr - whether they're on the free tier with on-device transcription that never leaves their phone, or Pro with Vault Mode encryption - is trusting us with conversations. With sales calls and client sessions and research interviews. With the specific words they used when it mattered.

The feature list gets the job done. But the story is what makes you believe it's actually safe.

That Thursday morning email taught us that the best security features aren't flashy. They're the ones that feel like someone actually understood what you were worried about. Do you build tools that matter to people? What would you ask for if you could ask developers to solve the problem you didn't even know how to describe?

Ready to try Scribr by MRVL?

One tap to download. No sign-up wall.

Get it on the App Store

Want to try Scribr?

Visit Scribr →