New South Wales, Australia
The recording is temporary. The note is what you keep.
Amara AI does one thing. You talk your way through a meeting, a structured note comes back in your own system, and the audio is destroyed the moment the note exists. Below is the whole path a recording takes, step by step, with the retention clock that governs each one.
A person reads that mailbox and answers within five business days. Security reports get the same or the next business day.
There is an established and unrelated company trading as AmaraAI at amaraai.com. It came first, it is not us, and we are not connected to it in any way. No shared ownership. No shared directors. No shared staff. No partnership, no licence, no reseller arrangement and no common investor.
If you arrived here looking for them, you are on the wrong site and should go to amaraai.com. This site belongs to AMARA AI PTY LTD, an Australian proprietary company registered in New South Wales under ACN 696 682 827.
The whole path, five steps
What happens to one recording
Every design argument on this page is really an argument about how short this rail should be. Ours ends in deletion rather than in storage.
- 01 Capture One meeting, started by hand, with the room told first.
- 02 Transcribe Speech becomes text. This is the only step that needs a machine larger than a phone.
- 03 Structure Text becomes a note with headings, decisions, actions and open questions.
- 04 Hand over The note lands in the place you already keep notes, in a format you can read without us.
- 05 Erase The audio is destroyed. The default retention period for a recording is zero once the note exists.
The rail scrolls sideways on a narrow screen. Every step is described in full below.
Stage by stage
The five steps, in detail
A process flow is only honest if each step says what it costs as well as what it does. These do.
01
Capture
Recording starts because a person pressed something. There is no always listening mode, no background capture, no calendar integration that arms a microphone before you arrive, and no wake word. A design that quietly starts recording is a design that will eventually record something it should not have, and the failure will be silent.
While capture is running the interface says so in a way you cannot miss and cannot dismiss. Stopping is one action and takes effect immediately rather than at the end of a buffer.
- One meeting at a time. Capture is scoped to a session you started and ends when you end it.
- The room comes first. The other people in a meeting have not agreed to anything. Telling them is your job, and the product is designed to make that easy rather than to make it skippable.
- Recording law is not uniform. Whether every party has to consent depends on which Australian state or territory you are in. The privacy policy sets out the governing statute for each of them.
- No covert mode. No setting hides the fact that recording is happening, and none will ever be added.
02
Transcribe
Turning speech into text is the one part of this that needs more computing power than sits in a pocket. It is therefore the one part where audio would leave the device, and it is the part that has to be described precisely rather than waved at.
The commitment is narrow and specific. Audio is sent for one purpose, which is producing a transcript of that recording. It is processed and then destroyed. It is not pooled, not retained for quality review, not listened to by a person, and not used to train anything. Where the processing happens in a country other than Australia, that country is named in the privacy policy rather than described as a region.
- No voiceprint. No speaker embedding, biometric template or voice signature is created, stored or compared. Telling two speakers apart within a single meeting is a different and much narrower operation, and anything of that kind is discarded with the recording.
- No training on your speech. Not by default, not buried in a setting, not as a condition of the free tier. If we ever want to, we will ask separately and you will be able to say no and change your mind later.
- No accuracy claim. We have not measured word error rate against any published benchmark and will not print a percentage we cannot defend. Accents, crosstalk, jargon and bad rooms all degrade transcription, and no vendor who tells you otherwise is describing your meetings.
03
Structure
A transcript is not a note. It is a wall of speech with the useful parts scattered through it, and reading one takes about as long as sitting in the meeting again. The product exists for the step after transcription, which is turning that wall into something with parts.
A note has a short summary, the decisions that were actually made, the actions with the person who took them, the questions nobody answered, and a small number of quoted lines where the exact wording matters. Everything else is dropped on purpose. A note that keeps everything is a transcript wearing a hat.
- Quotes are marked as quotes. Where the note claims somebody said something, it says so, and the rest of the note is clearly a summary rather than a record.
- It will get things wrong. Summarisation invents emphasis that was not there and misses points that were. The note is a draft for a person who was in the room, and it is not evidence of what was agreed.
- No scoring of people. No talk time league table, no sentiment rating, no coaching metric, no engagement score. Turning a meeting into a performance measure changes how people speak in meetings, and we do not want to be the reason for that.
04
Hand over
The note is yours the moment it exists, and it lands wherever you already keep written things. Plain text and Markdown come first because they can be read in thirty years by software that has not been written yet.
There is no archive on our side that you have to come back to. A hosted library of everything you ever said is a convenient feature and a permanent liability, and it is the specific thing this design is arranged to avoid.
- Export is the product, not an upsell. Getting your notes out will never sit behind a paid tier.
- No lock-in by format. If the only way to read your notes is our reader, we have built the wrong thing.
- Leaving is deleting. Removing us from the picture should mean uninstalling something and deleting a file, with nothing of yours left behind that you have to ask us for.
05
Erase
This is the step the rest of the design exists to protect. Once the note has been produced the recording has no remaining purpose, and information kept without a purpose is only ever a liability waiting for a bad week.
The default retention period for captured audio is zero once the note exists. The transcript goes with it unless you deliberately turn on keeping it, in which case it is kept where you chose to put it rather than with us. Deletion means the data is removed from live systems immediately and falls out of any backup on that backup rotation rather than lingering somewhere with a longer clock.
- No quiet exception. There is no debug copy, no sample retained for quality, and no research set built out of what people said.
- No resurrection. Because the audio is gone, we cannot re-run a better model over your old meetings later. That is a real cost of this design and we accept it rather than hiding it.
- Nothing to hand over. A subpoena, a hostile acquirer or an attacker can only reach what still exists.
The audit view
Every artefact, and how long it lives
The same five steps expressed as the thing an auditor would actually ask for, which is a list of what exists and for how long.
| Artefact | Where it would exist | How long | Who could reach it |
|---|---|---|---|
| Live microphone buffer | Device memory only | Seconds, overwritten continuously | Nobody. It never becomes a file |
| Audio segment in transit | Encrypted connection to the transcription service | The length of the request | Automated processing only |
| Audio at the transcription service | The processing country named in the privacy policy | Destroyed once the transcript exists. Default retention zero | Automated processing only |
| Transcript | Your device, unless you send it somewhere | Destroyed with the audio unless you switch on keeping it | You |
| The note | Wherever you export it | Yours to keep or delete | You |
| Voiceprint or biometric template | Never created | Not applicable | Nobody |
| Training corpus built from your speech | Never created without separate opt in consent | Not applicable | Nobody |
| Meeting index or searchable archive on our side | Not built | Not applicable | Nobody |
These are the retention rules this company holds itself to, published with a version number against them in the privacy policy. A retention rule that only lives in a slide can be softened the first time a customer asks for the feature that breaks it. One published like this cannot be softened quietly.
The company behind it
The commitments in short, and who is bound by them
Four lines you can hold us to, then the identifiers that let you check the company for yourself.
Nothing here is offered for use where a mistake is expensive. A note produced by a language model is not a medical record, a legal transcript, a board minute or a record of a regulated conversation.
- Registered name
- AMARA AI PTY LTD
- Company type
- Proprietary company limited by shares
- ACN
- 696 682 827
- ABN
- 73 696 682 827
- Home state
- New South Wales
- GST
- Registered
- Short form
- Amara AI is a contraction of the registered name, used here and in correspondence, rather than a separately registered business name
- Checking it yourself
- Both numbers resolve on public registers without an account or a fee. Look the ABN and its GST status up at abr.business.gov.au; the ACN sits on the company register kept by ASIC (Australian Securities and Investments Commission)
- Formal service
- Documents needing formal service go to the registered office held on file for ACN 696 682 827 by ASIC. That record is what governs, and a street address typed into a footer would not be
One way in
Email, and nothing else
This site carries no form at all. A mailbox that somebody actually opens beats a set of fields that quietly discards whatever you typed into them.
Write to hello@amaraai.cc. Questions about the design, disagreement with the retention model, privacy requests and press all reach the same place, and the contact page explains what to put in the subject line so the right thing happens quickly.
If you want to report a problem, describe it. Do not attach audio of a meeting, because everybody else in that meeting agreed to be recorded by you rather than by us. Unsolicited recordings are deleted rather than listened to.