Terms of Service

Chai provides a calendar-connected meeting recorder that uses visible meeting bots to join supported Zoom, Google Meet, and Microsoft Teams meetings.

The service stores meeting metadata, transcripts, and audio files in Chai-controlled infrastructure so authorized users can review their meeting records.

You must sign in with an authorized identity provider and provide accurate account information. You are responsible for meetings connected through your calendar account.

You must use Chai only when recording is lawful, participants receive clear notice, and required consent or authority has been obtained. Recording requirements can depend on the locations of all participants and the circumstances of the meeting.

You agree that Chai may schedule and operate visible meeting bots for meetings on connected calendars. You must not hide the bot or misrepresent that recording is taking place.

For every meeting, you are responsible for notifying participants before recording and for using Chai only where you have the right to do so. Selecting an account country does not replace any notice, consent, or other requirement that applies to participants elsewhere.

By accepting these terms, you grant Chai a purpose-limited, withdrawable license to store, process, transform, anonymize, and license eligible meeting audio, transcripts, and metadata for the disclosed product improvement, compliance, and dataset licensing purposes, subject to the Privacy Policy and your explicit AI-training preference. Account creation alone does not constitute acceptance or participant consent.

Only eligible meeting data may be included in licensed exports, after consent, deletion, exclusion, and buyer export manifest checks. Participants can withdraw consent, and their data is not licensed under an unrestricted personal-data grant. Chai does not sell or license meeting content that remains personal data for third parties' independent use. Google user data and data derived from Google API scopes are excluded from dataset licensing and third-party AI model training.

Meeting-level opt-out removes that meeting from the licensing pool going forward. Consent withdrawal removes future eligibility for licensed exports, and permanent deletion deletes available Chai-controlled meeting objects and marks the meeting deleted in the product database.

The dashboard includes controls to exclude individual meetings from licensing and to delete recordings. Settings include calendar disconnect, data export, sign out, consent withdrawal, and account deletion controls. Participants can request deletion at /remove-me.

Deletion or withdrawal requests propagate to Chai-controlled future licensing eligibility and buyer export manifests. Chai will also record the request so downstream licensees can be notified where contractually or legally required.

Chai relies on WorkOS for authentication, Supabase for database and auth infrastructure, Recall.ai for meeting bots, Deepgram for Arabic, Hindi, Urdu, and Korean transcription through Recall, Cloudflare R2 for object storage, Groq for meeting chat, Sentry for error monitoring, and Vercel for hosting and cron execution.

Those providers may process data as needed to operate the service.

Chai may update these terms. If data-license terms materially change, users may be required to accept the new version before future recording continues.

Current terms questions, data rights requests, and Grievance Officer notices can be sent to janak@withspecific.com.