Meetora Company

Privacy at Meetora

Clear information about your data.

Audio and video

The current Meetora server has no meeting audio/video recording or upload pipeline. This does not mean that no meeting-related data is stored: room details, membership and messages are handled separately as described below.

Data this version stores

The service stores your account name, email, profile photo, preferences, room names and codes, membership, contacts, schedules, notifications and messages you submit. Account sessions, short-lived verification challenges and Google identity identifiers are also stored to support sign-in and access control. Room owners can see room participants and messages; administrators have administrative access.

Encryption and its limits

The public website and desktop API use HTTPS. HTTPS is transport encryption, not end-to-end encryption. Passwords are hashed with Argon2, not stored as readable passwords. This version does not implement end-to-end encryption for room messages or application-level encryption of its database and uploaded profile photos. Do not submit content that requires those protections.

Service providers

Google processes Google sign-in and provides the name, verified email and profile-photo information you authorize. Google access and refresh tokens are not stored by Meetora. Resend processes verification emails when email delivery is enabled. Our hosting and CDN providers handle network requests and may process IP addresses and operational metadata under their own policies.

Retention and your choices

You can edit your profile and remove supported content through the application. There is not yet an automated account-wide retention or deletion schedule in this version; stored data may remain until explicitly removed, and operational backups may require separate deletion. Requests about access, deletion or privacy can be directed to privacy@meetora.me. Mailbox availability must be confirmed by the service operator.

Managed demo participants

Administrators can add clearly labeled managed demo profiles to rooms. These profiles are not evidence that a person joined from a browser or desktop app. Their presence must not be represented as a real connection.