Skip to content

How MeetZaa protects your trade show data

Security is not a feature page. It is a list of what we do and what we do not do.

Hosting and infrastructure

MeetZaa is hosted on Supabase infrastructure. Database and authentication run on Supabase’s managed PostgreSQL. File storage (voice recordings, business card images, photos) uses Supabase Storage with private buckets. Supabase runs on AWS infrastructure.

Encryption

All data is encrypted in transit using TLS. Data is encrypted at rest by the hosting provider. Voice recordings and images are stored in private buckets that are not accessible via public URL.

Organisation isolation

Each organisation’s data is isolated at the database level using row-level security (RLS). One organisation cannot access another’s meetings, contacts, recordings or exports.

AI processing

Voice recordings are transcribed using OpenAI Whisper. Meeting summaries, lead scores and follow-up drafts are generated using OpenAI and Anthropic Claude. Content is sent only to produce the requested output. It is not used to train models. Both providers’ API terms state that API inputs and outputs are not used to train their models.

Authentication

Authentication is handled by Supabase Auth. Passwords are never stored in plain text. Session tokens are HTTP-only cookies. Team invites use single-use tokens that expire.

What we do not do

Data export and deletion

You can export your data at any time from the app as CSV or Excel. You can also request a full data export or complete deletion by emailing start@meetzaa.com. Exports are delivered within 14 days. Deletion is completed within 30 days.

Responsible disclosure

If you find a security issue, email start@meetzaa.com. We will acknowledge within 2 business days and provide a timeline for resolution.

Contact

start@meetzaa.com · MeetZaa Pvt Ltd, Pune, India.