Recording starts with informed participants
Hodar requires the user to confirm before every capture that participants have been informed.
Information the app may handle
- Meeting audio, timestamps, transcripts, summaries, decisions, questions, and action items.
- Participant names, roles, contact details, notes, and voice profiles supplied or confirmed by the user.
- Project labels, follow-up history, API credentials, and optional Microsoft account tokens.
- If the planned remote-capture pilot is enabled later: user-confirmed Zoom or Teams links and temporary coordinator session status.
What stays on your device
Meeting records and voice embeddings are stored in the app’s private Android storage.
External processing you choose to use
In the current private beta, audio is sent to Google Gemini for transcription.
Remote capture under preparation
Zoom and Teams capture is being prepared for production rollout and is not generally available.
Controls available to you
You can delete individual meetings, disconnect integrations, or erase local personal data and credentials.
Security safeguards
The Android app uses private storage and Keystore-backed credential protection.
The final policy must identify the legal operator and contact details and be reviewed for the intended markets and customer contracts.