MeetStream Privacy Policy

MeetStream Corp. (“MeetStream,” “we,” “us,” or “our”) provides meeting bot infrastructure: an API that joins, records, streams and analyses meetings on Zoom, Google Meet and Microsoft Teams. This Privacy Policy explains what we collect, why, how we store it, and the choices you have.

It covers meetstream.ai, the MeetStream dashboard, and the MeetStream API. If you use MeetStream through a customer who built on our API, that customer’s own privacy policy governs their product; this policy governs our handling of data as their infrastructure provider.

1. Information we collect

Account information

When you create a MeetStream account we collect your email address, name, and authentication identifiers. If you sign up with Google, see section 4. Billing is handled by Stripe; we receive your email and a customer identifier, and we do not store full payment card numbers.

Meeting data you direct us to capture

When you or your application instructs a MeetStream bot to join a meeting, we process what that bot is configured to capture, which may include audio, video, per-participant media streams, transcripts, participant lists and join/leave events, in-meeting chat, and screenshots. You control which of these are enabled per bot.

Usage and technical data

We collect API request logs, bot run records, error and diagnostic data, and standard web analytics on meetstream.ai, used to operate, secure and improve the service.

2. How we use information

• To provide the service: run bots, deliver recordings, transcripts and streams to you
• To authenticate you and operate your account and billing
• To maintain security, prevent abuse, debug problems, and monitor reliability
• To communicate with you about the service, including changes and incidents
• To comply with legal obligations

We do not sell personal data, and we do not use meeting content or Google user data for advertising or to train advertising models.

3. Sharing and subprocessors

We share data only with service providers that help us run MeetStream, under contract and with appropriate safeguards. These include cloud infrastructure (Amazon Web Services and Google Cloud Platform) and payment processing (Stripe).

If you configure your own third-party providers (for example a bring-your-own-key speech-to-text or LLM provider), meeting content you route to them is governed by your agreement with that provider.

We may disclose information where required by law, to protect rights and safety, or in connection with a merger, acquisition or sale of assets, subject to applicable law and, for Google user data, the consent requirements described below.

4. Google Account Sign-In and Google user data

MeetStream offers users the ability to create and sign in to a MeetStream account using Google Sign-In (OAuth 2.0 / OpenID Connect), and may request additional Google API access when a user chooses to connect Google-related features such as Google Calendar.

MeetStream’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

4.1 What Google user data we access

Google Sign-In (account authentication). When you sign up or sign in with Google, we may receive your Google account email address, your name and basic profile information (for example given name, family name, and profile picture URL where provided by Google), and a unique Google account identifier used to authenticate you and link your Google identity to your MeetStream account. We use this to create and authenticate your account, prevent duplicate accounts, and communicate with you about the service.

Google Calendar (only if you connect Calendar). If you connect a Google Calendar account, we may access your Google account email and basic profile information to identify the connected account, and calendar list metadata and calendar events needed to detect meeting links and schedule meeting bots, including event title, start and end times, attendees, conference links, recurrence and related event metadata.

We request only the scopes needed for these features, typically read-only calendar access together with basic profile and email scopes. We do not request access to Gmail content, Google Drive file contents, or Google Contacts. If that ever changes we will update this policy and obtain new consent first.

4.2 How we use Google user data

We use Google user data solely to authenticate you and operate your MeetStream account; to provide the user-facing features you choose to use, such as joining meetings with bots and calendar-based scheduling; and to maintain security, prevent abuse, troubleshoot issues and comply with law.

We do not sell Google user data; use it for advertising, retargeting or personalised ads; use it to determine creditworthiness or for lending purposes; or transfer it to data brokers or information resellers.

4.3 How we store Google user data

Identity data from Google Sign-In, such as your email and account identifiers, is stored in our secure cloud systems as part of your MeetStream user record. If you connect Google Calendar, OAuth credentials such as refresh tokens (and, in our bring-your-own-key model, customer-provided OAuth client credentials) are stored encrypted using AWS Systems Manager Parameter Store (SecureString) and related AWS services. Access tokens are obtained as needed for API calls and are not retained as long-lived secrets. Synced calendar and event data used for scheduling may be stored in our databases and object storage to power MeetStream features. We apply security controls appropriate to the sensitivity of the data, including encryption in transit and at rest where supported by our cloud providers.

4.4 How we share Google user data

We do not share Google OAuth tokens, or Google profile or calendar data, with third parties for their own purposes. We may process Google user data using trusted subprocessors that help us operate the service, such as Amazon Web Services, under contractual and technical safeguards.

Meeting content generated through MeetStream, such as recordings and transcripts, is separate from Google Sign-In profile data and is handled according to your configuration and the rest of this policy.

4.5 Human access to Google user data

MeetStream personnel are not permitted to read Google user data obtained through Google APIs except where you give affirmative consent for a specific support case; where it is necessary for security, abuse investigation or debugging; where it is required to comply with applicable law; or where the data has been aggregated or anonymised for internal operations, consistent with applicable law and Google’s Limited Use requirements.

4.6 Disconnect, revoke and delete

• Revoke MeetStream’s access from Google: visit Google Account permissions and remove MeetStream or the relevant OAuth client.
• Disconnect Calendar inside MeetStream: use the calendar disconnect controls or the connection-delete API. Disconnecting removes the stored Google credentials for that connection and stops calendar sync; you can optionally purge the associated synced events and scheduled bots.
• Account deletion and data requests: contact us at info@meetstream.ai to request deletion of your account and the Google-linked data we control, subject to legal retention requirements.

After you revoke access, MeetStream can no longer obtain new Google user data for that grant. Previously stored data is deleted or retained only as required by law or to complete a deletion workflow you have already requested.

5. Security

MeetStream is ISO 27001 certified and GDPR compliant, and is currently undergoing a SOC 2 Type 2 audit. We use encryption in transit and at rest where supported by our cloud providers, scoped access controls, and audit logging. No system is perfectly secure, and we encourage you to report suspected issues to info@meetstream.ai.

6. Retention and deletion

Meeting recordings, transcripts and related artefacts are retained according to your account configuration and any retention settings you choose, including bring-your-own-bucket arrangements where the data is stored in your own storage. Account records are retained while your account is active. On deletion we remove or anonymise data we control, except where retention is required by law or to resolve disputes.

7. Your rights

Depending on where you live, you may have rights to access, correct, export or delete your personal data, and to object to or restrict certain processing. To exercise these rights, contact info@meetstream.ai. If you are in the EEA or UK, you also have the right to lodge a complaint with your local supervisory authority.

Meeting participants

MeetStream acts as an infrastructure provider to the customer who deploys a bot. If you were a participant in a meeting recorded through MeetStream and want your data addressed, contact the organisation that recorded the meeting; we will support them in responding.

8. Children

MeetStream is not directed to children. No one under 13 may create an account. If you are under 18 you may only use MeetStream with the involvement of a parent or guardian.

9. Changes to this policy

We may update this policy as the product changes. Material changes affecting Google user data will be reflected here before the corresponding change takes effect, and where required we will seek fresh consent. The date at the top of this page shows when it was last revised.

10. Contact

MeetStream Corp.
1007 N Orange St, 4th Floor, Ste 1382, Wilmington, DE 19801, United States
Email: info@meetstream.ai
Web: https://meetstream.ai

READ THE TERMS OF USE