Account sign-in
Meeting workspaces and saved recordings require a signed-in account. Sign-in uses email verification links, and account sessions are managed by Melanam.
Security
Melanam uses account sign-in, room access checks, host controls, and plan-based limits to help protect meetings and recordings. Here is how those controls work and which service providers process data.
Contact supportMeeting workspaces and saved recordings require a signed-in account. Sign-in uses email verification links, and account sessions are managed by Melanam.
Meeting rooms use invite links and access checks. A room must exist and be started by its host before participants can join. Private rooms use signed access tokens, and participant limits are enforced according to the host plan.
Only the meeting host can start or stop server recording. The host controls whether a recording is shared with the meeting group and can delete their recording. Some tools and limits depend on the account plan.
Meeting recordings are stored in the configured Supabase storage account and are subject to plan-based storage, recording-time, and retention limits. When a recording reaches its retention date, it is marked expired and removed from normal playback and sharing. See Pricing for the current limits on each plan.
Some Melanam features send data to service providers to work. Live meeting audio/video uses the configured Jitsi service. Captions and transcription use AssemblyAI. AI-generated meeting notes use AssemblyAI and OpenAI. Server recordings are stored in the configured Supabase storage account. Account and meeting records are stored in MongoDB.
Use Melanam thoughtfully and let participants know when recording or transcription is active.
Melanam does not currently hold an independent security certification. We do not claim SOC 2 or ISO 27001 certification.
For security questions or to report a concern, contact gmnnetwork@gmail.com.