Recording without the risk

For the meetings where a recording would be worth the most, you would never trust it to someone else's server.

You know the meetings. A board conversation where the numbers are not final. A legal review where every sentence might count against you later. A one-on-one where someone tells you the real reason they are leaving. There an accurate record would be worth the most, and a bad one would cost the most.

So you do not record. You scribble half a page of shorthand, and the most important meeting of the week is the worst captured. The value is real, the risk is real, and the risk wins.

The question is not whether transcription works. The question is: if you record a meeting like that, where does the recording rest afterwards, and who can open it?

A recording's path

You upload the audio. The file arrives on the readme server, is brought into a uniform format, and is stored in S3-compatible object storage, assigned to your workspace alone.

Then readme processes the recording. It turns the spoken word into text, attributes it to the speakers, and derives the results you read later. From one hour of audio come a faithful transcript, the decisions, and the action items.

The audio stays in object storage, in one place, in your workspace, for as long as you keep it. You can view it and you can delete it.

The results live in the readme database, assigned to the same workspace as the recording they came from.

A privacy promise is a sentence. A path you can follow step by step.

So the path is: upload, process, store, derive. What remains, the recording and everything from it, rests in your workspace. Whoever is a member there can open it.

Who can open it

Access to a stored recording and to everything derived from it is limited to your workspace. Anyone who is not a member there cannot open the file. It is the same boundary that governs the rest of your work. There is no second one for the audio.

This is what "we treat it as sensitive" looks like when it counts for something. It is a boundary you can check before you upload a file.

The decision stays with you. Delete a recording, and readme removes the stored audio and the results derived from it. Whether the upload stays or goes is your call.

You do not have to take our word for any of it. You see where your recording rests and who can open it, and you decide for yourself whether that is right for your organisation.

Record the meeting that counts

Think of the meeting you did not dare record. What held you back was the worry about where your recording would rest and who could reach it. There is now an answer to that. It rests in your workspace, only its members can open it, and you can delete it whenever you want.

Audio, transcript, and summary rest within the same boundary, and only the people involved in the work have access. That is exactly how the sensitive meeting, the one where an accurate record counts the most, becomes the one most worth recording.

Record the meeting you would otherwise keep under wraps, and run it through readme.