Privacy Policy

1. Who we are

MeetFlow AI (“MeetFlow,” “we,” “us”) is a software service that helps authenticated users turn meeting recordings into transcripts, summaries, decisions, action items, risks, and follow-up drafts.

Operator / legal entity: [Legal entity name — placeholder]. Contact: the support contact configured for this deployment.

2. Information we process

• Account information: name, email address, authentication identifiers, and profile details managed through Clerk.
• Workspace data: workspace membership and plan assignment used to authorize access and enforce usage limits.
• Meeting content: titles, descriptions, uploaded audio files, transcripts, AI analyses, action items, and export content you create or generate in the product.
• Technical data: basic application logs and operational events needed to run the service (for example request failures or processing status).

3. How we use information

We use the information above to:

• authenticate users and protect workspace access;
• store and process meeting recordings for transcription and analysis;
• display and export meeting insights inside your workspace;
• enforce plan usage limits;
• operate, debug, and improve reliability of the service.

We do not sell meeting content. We do not use your meeting audio or transcripts to train public foundation models as part of the MeetFlow application logic described in this repository.

4. AI processing and third-party providers

To provide the service, MeetFlow sends relevant data to infrastructure and AI providers under the buyer’s configured accounts, which may include:

• Clerk — authentication and account management;
• Neon — Postgres database storage;
• Vercel — application hosting and private Blob object storage;
• Deepgram — speech-to-text transcription of stored audio;
• Groq (and optionally Vercel AI Gateway) — structured meeting analysis.

Transcript text is processed on the server. Provider API keys are not exposed to the browser. Each provider processes data under its own terms and privacy policy.

5. Storage and access

Meeting audio is intended to be stored in a private object store. Application data (including transcripts and analyses) is stored in Postgres. Access to meeting resources requires an authenticated workspace member. Cross-workspace identifiers return not-found responses rather than revealing whether a resource exists.

6. Retention and deletion

Meeting data is retained while the workspace account remains active and the meeting record exists in the database. Self-service meeting deletion and full account deletion workflows may be limited in the current product version; contact the support contact configured for this deployment for deletion requests that the product UI does not yet support.

7. Security measures

MeetFlow uses authentication, workspace authorization checks, private object storage for audio, and server-side provider calls. No formal compliance certification (such as SOC 2, ISO 27001, HIPAA, or GDPR certification) is claimed by this product draft.

8. Children

MeetFlow is intended for business and professional use. It is not directed to children under 16.

9. Changes

We may update this policy as the product evolves. Material changes should be reflected on this page with an updated date.

10. Contact

Privacy questions: the support contact configured for this deployment. Mailing address: [Business address — placeholder].