The category is called "meeting bot" and carries baggage
Many AI note tools follow one pattern: a bot joins your Zoom/Meet/Teams from your calendar, records every participant, transcribes and delivers notes. Others capture the device audio while you are in the meeting, without adding a bot to the call.
AudioMap is neither. And the difference matters more than it seems.
The bot model has two structural problems
1. Ambiguous consent. When a bot enters a call, European case law (STC 114/1984, STS 22-04-2002) and the AEPD April 2026 guidance require explicit consent from each participant. Most organizations sidestep it with generic clauses in the calendar invite. The AEPD has started to audit this.
2. Responsibility stays with whoever invites it. The other participants' consent is still the host's to obtain, and the invitee only has the bot's visible presence as a cue to ask.
The bot-free system-capture model
No bot in the call, no visible list to the rest of participants. Better than a visible bot, but it retains an uncomfortable property: the host still records without invitees having any reason to know. Operating system capture is invisible. Case law and the AEPD apply equally to the host, but the invitee loses the visual cue that would let them ask.
AudioMap's upload-first model
AudioMap chose another vector: you upload what you decide to upload, and you are responsible for the consent you have obtained. No bot in your meetings, no silent system capture, no surprise for anyone in the call.
Does it imply that you have to record manually and upload? Yes. Is it less elegant than a bot that appears on its own? Yes. Is it much more defensible under AEPD April 2026? Yes, and that is why your DPO sleeps well.
Furthermore, AudioMap provides infrastructure for the invitee to exercise their rights directly without asking favors of the host: - Public deletion endpoint [/legal/request-deletion](/legal/request-deletion): a third party fills the form, we validate, we delete their voice and transcript. - Publicly documented sub-processors at [/legal/subprocessors](/legal/subprocessors). - Public DPIA + TIA at [/legal/dpia](/legal/dpia) and [/legal/tia](/legal/tia).
What about the "wow factor" of the bot?
We say this without rhetoric: the bot that appears on its own in your call is a wow factor that lasts 2 weeks and then becomes debt. Legal debt (consent), privacy debt, relational debt (some participants leave the call as soon as they see the bot).
The upload-first model has a higher initial friction (90 seconds to upload a file). But that friction is what gives you control over consent. And if "90 seconds of uploading" stops you, AudioMap includes: - Persistent web recorder in your dashboard (with offline + auto-upload when connection returns). - Native Flutter iOS and Android apps to record from mobile. - URL ingestion (Phase B): paste a YouTube/Spotify/Instagram link and it ingests. - REST API + MCP server to automate uploading from your CRM or flow.
The category coming
While the bot model takes consent for granted, AudioMap builds the opposite case: the invitee has rights, the host has responsibilities, and the tool facilitates both. It's not "meeting notetaker". It's "European augmented memory", and the categorical difference is in who decides what gets recorded and who can request its deletion.
What we are NOT
To make it clear: - We are NOT a meeting bot. We don't join your calls. - We are NOT a silent desktop notetaker. We don't capture system audio without your interaction. - We are NOT an always-on pendant. We don't run all the time. - We are NOT a meta-AI agent. We don't execute actions in other systems on your behalf without you seeing what we did.
What we ARE
- AudioMap is augmented memory for Spanish-speaking professionals who record responsibly (consent obtained), upload (web/mobile/URL), transcribe in Spanish, generate deliverables (emails, docs, slides) and maintain semantic search across their entire library. All in Europe, with no surprises for anyone on the call.
If this sounds less "wow" than a magical bot, it's because it's less risky. And in 2026, with the AEPD starting to audit, that difference is going to show.