# Verify API key or OAuth token Source: https://docs.lyra.so/api-reference/authentication/verify-api-key-or-oauth-token https://app.lyra.so/openapi.json post /auth Validates a Lyra API key or OAuth access token and returns associated user and org identifiers. # Create a Lyra meeting Source: https://docs.lyra.so/api-reference/meetings/create-a-lyra-meeting https://app.lyra.so/openapi.json post /meeting Creates a meeting and optional participants, returning a video call payload. # Delete a webhook endpoint Source: https://docs.lyra.so/api-reference/webhooks/delete-a-webhook-endpoint https://app.lyra.so/openapi.json delete /webhook Removes a webhook subscription by ID. # List webhook endpoints Source: https://docs.lyra.so/api-reference/webhooks/list-webhook-endpoints https://app.lyra.so/openapi.json get /webhook Returns all webhook subscriptions for the authenticated user's organization. # Register a webhook endpoint Source: https://docs.lyra.so/api-reference/webhooks/register-a-webhook-endpoint https://app.lyra.so/openapi.json post /webhook Creates a new webhook subscription for the specified events. Returns a signing secret (shown once). # Product Updates Source: https://docs.lyra.so/changelog Product updates and announcements # Webhooks, agent improvements and a new sharing domain A few meaningful improvements this week as we wrap up an upcoming release we're excited to share with you! **Trigger API endpoints when meetings end** We've updated our API to enable triggering webhooks when a meeting ends. This makes it simple to trigger anything downstream the moment a meeting finishes, whether that's updating your CRM, notifying your team, or kicking off any custom process in your stack. Screenshot 2026-03-04 165850.png **Agent chat improvements** We've improved formatting and readability in responses — they should look and feel better. You can now also upload files directly into the chat, giving the agent additional context when taking action across your meetings. Screenshot 2026-03-04 170253.png **Public meeting links now live at [share.lyra.so](http://share.lyra.so)** Public share pages now live at share.lyra.so instead of app.lyra.so. This makes it immediately clear to anyone receiving a link that they're viewing a shared meeting. Screenshot 2026-03-04 170809.png **Other improvements across the app** * Sound effects now play through your selected audio output device * Global search can now find people and companies by name * Automatic recording only begins once participants have joined the call # Global search, agent rework, performance dashboard After this week Lyra should feel significantly more intelligent, platform wide. We've doubled down on our power users and focused on improving the most common core user journeys. **Complete AI rework** Over the past months, we completely rebuilt our agent pipeline from the ground up — new tooling, chat interaction and more. You should notice the agent respond at least 3x faster in most cases and perform actions with more accuracy. This feeds into almost all our features. **Removing artifacts (for now)** We're rethinking how artifacts work and have temporarily removed them while we build a better version. Stay tuned. **Search across the entire app (cmd + k)** You can now search across Lyra for meetings, people and companies in one place. Press CMD + K to trigger the search. image.png **Track your performance** Lyra at its core was built to help GTM teams perform. We’ve introduced a new performance tab that provides key metrics across your entire organization. image.png **Smaller improvements across the app** 1. Background blur persistence 2. Faster AI chat 3. Migrate events when participating as a guest 4. Users can reorder meeting types # Custom research instructions, meeting templates and a new camera grid We’re continuing to implement feedback as fast as possible with new features and usability this week. **Customize your pre-research to your business** Within the new agents page you can now provide Lyra with direct instructions on what to research and how to present the information before a meeting starts. Examples include telling Lyra to focus on if they live in NYC or use Google Calendar. You can also provide Lyra information on your business such as pricing, custom vernacular you use in sales calls so Lyra understands the real time conversation better. Lyra will combine this research with a summary of all your previous engagements to date. image.png **Unique meeting URLs** Every Lyra user now gets a unique meeting URL that can be used to start an instant meeting with them. Useful for adding to scheduling tools like Calendly etc or websites that need to be permanent. URLs never expire. image.png **Share meetings with teammates** Within Lyra you can now share meetings with specific teammates with more granular permissions coming soon. image.png **Meeting types** Within Lyra you can now create specific meeting types such as Demo Calls, user interviews etc. For each type you can provide specific instructions on what the agent should look for and how you want summaries presented. This also makes the agent significantly more intelligent within real time calls because it has contextual understanding of why the conversation is taking place. image.png **Full camera grid matching Google Meet** After testing we’ve ditched the square camera grid layout and gone back to full screen grids, think Google meet style. image.png **Minor** 1. View company logos & names from research 2. Fixed transcript ordering issue 3. Design refinement throughout the main app # Custom agents, public share pages, API docs and meeting filters This week we refreshed some of our core UI and massively improved the customization and extensibility of our core features. **Save custom instructions for your agents** The agents page now lets you customize and manage your Lyra agent experience from a single, centralized view. You can provide agents with general knowledge (such as your pricing), give detailed instructions for performing research (such as identifying if they’re a YC business) and write long detailed prompts that can be saved as skills and accessed with /skill in any chat. Our agents now operate contextually to your business, massively improving their output relevance. Screenshot 2026-02-10 at 6.24.25 PM.png **Public share pages** Meetings can now be shared publicly once the call ends, making it easy to send recordings or summaries to anyone who needs access. This is convenient for collaboration, follow-ups, and sharing context without requiring a Lyra account. Viewers get the full power of AI chat to ask questions across the meeting transcript and artifacts. image.png **Filter meetings by people & companies** You can now filter completed meetings by specific people or companies for faster searching and organization. This makes it much easier to find past conversations and relevant context without scrolling through long meeting lists. Screenshot 2026-02-10 at 6.02.25 PM.png **API docs are live** Lyra’s API documentation is now available at [https://docs.lyra.so](https://docs.lyra.so/), providing clear guidance on how to integrate with our platform. This makes building, testing, and shipping integrations faster and more straightforward. image.png **Smaller improvements across the app** * Agents can now search the web * View meetings / folders by clicking on inline references inside the AI chat * Directly unsubscribe from midnight summary emails in notification settings * All participants must go through the waiting room even if they were added through Google Calendar * Warning for hosts before closing the meeting # Google extension, meeting interface, agent skills, automated research In the last few weeks we’ve shipped major updates that make Lyra even more useful when taking your meetings and continued to improve the core experience across the app. **Google workspace extension** You can now schedule meetings directly from your Google calendar the same way you would Zoom meetings. Invitees will receive an invite containing the Lyra meeting URL and joining instructions. CleanShot 2026-01-28 at 18.50.12@2x.png CleanShot 2026-01-28 at 18.50.51@2x.png **Improved meeting interface** We've streamlined meeting controls, chat and participant management panels within the meeting itself. We've also updated the agent chat to be more responsive and delightful. Several UI/UX improvements enhance the overall meeting experience. We've also refined picture-in-picture so you can see attendees while navigating other tabs or sharing your screen. CleanShot 2026-01-28 at 18.55.07@2x.png **Agent with Hubspot, Slack & Gmail** Lyra agent can now search your favorite tools for answers or take action within them. Without leaving Lyra you can update HubSpot records, send emails or Slack messages all based on real-time transcription. You can also ask questions and surface insights across all the conversation history in your entire workspace. CleanShot 2026-01-28 at 19.18.47@2x.png **Automatic research prep before your meetings** Lyra automatically runs deep research on all your meetings and gives you a helpful summary before the call starts along with any important insights from previous conversations that you need to take into the meeting. CleanShot 2026-01-28 at 19.09.28@2x.png **Smaller improvements across the app** * Calendar sync is significantly more reliable and consistent * Meeting recordings now play in a custom Lyra player and load instantly * Meeting prep emails that send at midnight have been improved and are more actionable * Lyra agent explicitly asks for confirmation before taking external actions like sending emails * Artifacts generate faster and have improved visual representation # Hosting Meetings Source: https://docs.lyra.so/hosting-meetings # Introduction Source: https://docs.lyra.so/introduction Programmatically create meetings and manage webhooks with the Lyra REST API ## Overview The Lyra API lets you programmatically create meetings, manage webhook subscriptions, and verify authentication tokens. The API follows REST conventions and uses JSON for request and response bodies. All requests are authenticated via `Bearer` tokens — either an **API key** or an **OAuth access token**. ``` https://app.lyra.so/api/v1 ``` ## Quick Start Navigate to **Settings → Developers → API Keys** in your Lyra dashboard and click **Create API Key**. Give your key a descriptive name, then copy the generated key immediately — it will only be shown once. API Keys settings page Store your API key securely. Lyra only stores a hash of the key — if you lose it, you'll need to create a new one. Test your API key by calling the authentication endpoint: ```bash theme={null} curl -X POST "https://app.lyra.so/api/v1/auth" \ -H "Authorization: Bearer lyra_your_api_key" ``` You should see a successful response: ```json theme={null} { "valid": true, "userId": "user_abc123", "orgId": "org_xyz789" } ``` Use the [Create Meeting](/api-reference/meetings/create-meeting) endpoint: ```bash theme={null} curl -X POST "https://app.lyra.so/api/v1/meeting" \ -H "Authorization: Bearer lyra_your_api_key" \ -H "Content-Type: application/json" \ -d '{ "title": "Customer kickoff", "start": "2026-04-01T15:00:00.000Z", "attendees": ["alex@acme.com", "sam@acme.com"] }' ``` The response includes a join URL for the meeting: ```json theme={null} { "type": "lyra_video", "id": "meeting_123", "password": "", "url": "https://app.lyra.so/meeting/abc-def-ghi" } ``` ## Authentication All API requests require an `Authorization` header with a Bearer token. ``` Authorization: Bearer ``` Lyra supports two types of tokens: | Type | Prefix | Scopes | Best for | | --------------- | ------------- | --------------------------- | ------------------------------------------ | | **API Key** | `lyra_` | Full access (all endpoints) | Server-to-server integrations | | **OAuth Token** | `lyra_oauth_` | Limited by granted scopes | Third-party apps acting on behalf of users | API keys have unrestricted access to all endpoints. If you need scoped permissions or are building an integration for other Lyra users, use [OAuth](/oauth) instead. ## Error Handling The API uses standard HTTP status codes. Error responses include an `error` field with a human-readable message. | Status | Meaning | | ------ | -------------------------------------------------------- | | `400` | Invalid request body or parameters | | `401` | Missing or invalid authentication token | | `403` | Token is valid but lacks the required scope (OAuth only) | | `404` | Resource not found | | `500` | Internal server error | ```json theme={null} { "error": "Insufficient scope. Required: meeting.create" } ``` ## Need Help? Set up OAuth for third-party integrations with scoped permissions Reach out to the Lyra team for assistance # OAuth Source: https://docs.lyra.so/oauth Build integrations that act on behalf of Lyra users with OAuth 2.0 ## Overview Lyra implements the [OAuth 2.0 Authorization Code](https://datatracker.ietf.org/doc/html/rfc6749#section-4.1) flow. This lets third-party applications request permission from Lyra users and receive scoped access tokens to call the API on their behalf. Use OAuth when you're building an integration that other Lyra users will authorize — for example, a scheduling tool that creates Lyra meetings for its customers. If you only need to access your own workspace programmatically, an [API key](/introduction) is simpler and provides full access without scopes. ## Create an OAuth Application Navigate to **Settings → Developers → OAuth Clients** in your Lyra dashboard. OAuth Clients settings page Click **Create OAuth Client** and fill in the required fields: | Field | Description | | ---------------- | ---------------------------------------------------------------------------------- | | **Name** | A display name shown to users during the consent screen | | **Redirect URI** | The URL where Lyra will send the authorization code after user consent | | **Scopes** | The permissions your application needs (see [Available Scopes](#available-scopes)) | Create OAuth Client dialog After creating the application, you'll receive a **Client ID** and **Client Secret**. The Client Secret is only shown once. Store it securely — Lyra only keeps a hash of the secret. ## Available Scopes Scopes control what your application can do on behalf of the user. Request only the scopes you need. | Scope | Description | | ---------------- | ------------------------------------ | | `meeting.create` | Create meetings on the user's behalf | | `webhook.create` | Register webhook endpoints | | `webhook.read` | List webhook endpoints | | `webhook.delete` | Delete webhook endpoints | ## Authorization Flow The OAuth flow has three steps: redirect the user, receive the authorization code, then exchange it for tokens. ### 1. Redirect the User to Lyra Send the user to the Lyra authorization page with your application's parameters: ``` https://app.lyra.so/oauth/authorize ?client_id=YOUR_CLIENT_ID &redirect_uri=https://yourapp.com/callback &scope=meeting.create webhook.read &response_type=code &state=RANDOM_STATE_VALUE ``` | Parameter | Required | Description | | --------------- | ----------- | ---------------------------------------------------------------------------- | | `client_id` | Yes | Your application's Client ID | | `redirect_uri` | Yes | Must exactly match the redirect URI registered with your application | | `scope` | Yes | Space-separated list of requested scopes | | `response_type` | Yes | Must be `code` | | `state` | Recommended | An opaque value to prevent CSRF attacks. Returned unchanged in the callback. | The user will see a consent screen showing your application name and the requested permissions. OAuth consent screen ### 2. Receive the Authorization Code After the user approves, Lyra redirects to your `redirect_uri` with an authorization code: ``` https://yourapp.com/callback?code=AUTHORIZATION_CODE&state=RANDOM_STATE_VALUE ``` If the user denies the request, the redirect includes an error: ``` https://yourapp.com/callback?error=access_denied&state=RANDOM_STATE_VALUE ``` Authorization codes expire after **10 minutes** and can only be used once. ### 3. Exchange the Code for Tokens Make a server-side `POST` request to the token endpoint to exchange the authorization code for an access token and refresh token. ```bash cURL theme={null} curl -X POST "https://app.lyra.so/api/oauth/token" \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "grant_type=authorization_code" \ -d "code=AUTHORIZATION_CODE" \ -d "client_id=YOUR_CLIENT_ID" \ -d "client_secret=YOUR_CLIENT_SECRET" \ -d "redirect_uri=https://yourapp.com/callback" ``` ```json JSON Body (alternative) theme={null} POST https://app.lyra.so/api/oauth/token Content-Type: application/json { "grant_type": "authorization_code", "code": "AUTHORIZATION_CODE", "client_id": "YOUR_CLIENT_ID", "client_secret": "YOUR_CLIENT_SECRET", "redirect_uri": "https://yourapp.com/callback" } ``` The response includes both tokens: ```json theme={null} { "access_token": "lyra_oauth_abc123...", "refresh_token": "lyra_rt_def456...", "token_type": "bearer", "expires_in": 3600, "scope": "meeting.create webhook.read" } ``` | Field | Description | | --------------- | --------------------------------------------------------------- | | `access_token` | Use this as a Bearer token to call the Lyra API | | `refresh_token` | Use this to get a new access token when the current one expires | | `expires_in` | Access token lifetime in seconds (1 hour) | | `scope` | The scopes granted by the user | ## Using OAuth Tokens Pass the access token as a Bearer token in the `Authorization` header, just like an API key: ```bash theme={null} curl -X POST "https://app.lyra.so/api/v1/meeting" \ -H "Authorization: Bearer lyra_oauth_abc123..." \ -H "Content-Type: application/json" \ -d '{"title": "Team standup"}' ``` If the token lacks a required scope, you'll receive a `403` response: ```json theme={null} { "error": "Insufficient scope. Required: meeting.create" } ``` ## Refreshing Tokens Access tokens expire after **1 hour**. Use the refresh token to obtain a new access token without requiring the user to re-authorize. ```bash theme={null} curl -X POST "https://app.lyra.so/api/oauth/token" \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "grant_type=refresh_token" \ -d "refresh_token=lyra_rt_def456..." \ -d "client_id=YOUR_CLIENT_ID" \ -d "client_secret=YOUR_CLIENT_SECRET" ``` The response has the same format as the initial token exchange, including a **new refresh token**: ```json theme={null} { "access_token": "lyra_oauth_new_token...", "refresh_token": "lyra_rt_new_refresh...", "token_type": "bearer", "expires_in": 3600, "scope": "meeting.create webhook.read" } ``` Lyra uses **refresh token rotation** — each refresh token can only be used once. Always store the new refresh token from the response, as the previous one is immediately revoked. ## Token Lifetimes | Token | Lifetime | | ------------------ | ---------- | | Authorization code | 10 minutes | | Access token | 1 hour | | Refresh token | 30 days | ## Error Responses The token endpoint returns standard OAuth error codes: | Error | Description | | ------------------------ | ----------------------------------------------------------- | | `invalid_request` | Missing required parameters | | `invalid_grant` | Authorization code is invalid, expired, or already used | | `invalid_client` | Client ID or secret is incorrect | | `unsupported_grant_type` | Only `authorization_code` and `refresh_token` are supported | | `invalid_scope` | Requested scope is invalid or not allowed for this client | | `access_denied` | The user denied the authorization request | # Privacy Policy Source: https://docs.lyra.so/policies/privacy-policy *Last updated: January 26, 2026* This Privacy Notice describes how Seeking Sigma Inc. dba Lyra ("Lyra", "we", "us", "our") collects, uses, and shares your personal information and explains your privacy rights. ## 1. Scope This Privacy Notice applies to personal information processed on our websites, mobile applications, and other offerings (collectively, the "Services"). ## 2. Personal Information We Collect We collect information you provide, information collected automatically, and information from third-party sources. ### (a) Information You Provide **Account Creation:** Name, email address, and username. **User Content:** Text, files, documents, graphics, images, audio, video, meeting recordings, transcriptions, and AI-generated summaries. **Meeting Recordings and AI Features:** When you use recording, transcription, or AI summary features, we collect audio, video, transcripts, and meeting content. You are responsible for obtaining required consent from all meeting participants before enabling these features and for complying with applicable laws. By enabling these features, you authorize Lyra and our service providers to process this content. **Purchases:** Purchase details and payment information. Payments are processed by third-party processors; we do not store payment card information. **Communications:** Email, phone, or mailing address when you contact us, request support, or apply for jobs. **Surveys:** Information provided when participating in surveys. **Interactive Features:** Information submitted through messaging, chat, collaboration, commenting, forums, blogs, and social media. Public sharing features make information "public" unless otherwise required by law. **Sweepstakes/Contests:** Information provided for sweepstakes or contests we offer. **Events:** Information collected at conferences, trade shows, and events. **Business Development:** Information collected to assess business opportunities. **Job Applications:** Applications, CVs, cover letters, and related information. ### (b) Information Collected Automatically **Automatic Data Collection:** IP address, user settings, MAC address, cookie identifiers, mobile carrier, mobile identifiers, browser/device information, approximate location, Internet service provider, pages visited, links clicked, content interactions, activity frequency/duration, and information others provide about you. **Cookies and Tracking:** We and third parties use cookies, pixel tags, local storage, and other technologies to collect information automatically. **Cookies:** Small text files that store preferences. **Pixel Tags/Web Beacons:** Code that collects engagement data. We use Meta Pixel and email beacons. See Meta's Privacy Center for opt-out information. These technologies are used for: (1) operational necessity (access, security, fraud prevention), (2) performance assessment, (3) enhanced functionality, and (4) personalized advertising. **Analytics:** We use Google Analytics and other tools. See Google Analytics' Privacy Policy for opt-out options. ### (c) Information from Other Sources **Third-Party Services:** Information from social networks, login services, and other applications based on your privacy settings. **Public Sources:** Information from LinkedIn, business directories, and online sources. **Referrals:** Information provided through referral and sharing features. ## 3. Google User Data When you connect your Google account, we access and store Google user data to provide our Services. **Information Collected:** Calendar events and meeting details (titles, descriptions, participants, times, locations), meeting metadata, email addresses, and related information for meeting intelligence features. **How We Use It:** Display your calendar/meetings, automatically join meetings, provide AI summaries and insights, enable collaboration features, and improve our Services. **Storage and Retention:** Stored on US servers while your account is active and integration is connected. You may disconnect or request deletion anytime via [support@lyra.so](mailto:support@lyra.so) or account settings. We delete your Google data within 30 days of your request, except where required by law. **Limited Use Compliance:** Our use of Google API data adheres to the [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy), including Limited Use requirements. We only use your Google data for authorized features, not for advertising. We don't allow human access unless you consent, for security, or as required by law. We don't transfer your Google data to third parties except as necessary for Services, legal compliance, or corporate transactions (with notice). ## 4. How We Use Your Information **Provide Services:** Manage accounts, provide access and features, process recordings/transcriptions/AI summaries, handle support requests, process payments, process job applications, and enable event registrations. **Administrative Purposes:** Direct marketing, research and development, security, fraud prevention, measure engagement, improve Services, develop new products, quality control, verify identities, debug, audit, share with service providers, enforce agreements, comply with legal obligations, and train AI models for transcription and summary quality. **Marketing:** Tailor and deliver content and advertisements via email campaigns, text messages, custom audiences, and personalized advertising including cross-device tracking. Contact us to opt out of marketing. **With Your Consent:** Other purposes disclosed when you provide information or with your consent. **De-identified/Aggregated Data:** Create de-identified or aggregated information that does not identify individuals. ## 5. How We Disclose Information **Service Providers:** IT support, hosting, payment processing, customer service, transcription, AI/machine learning services, and related providers. **Business Partners:** Partners who provide joint products/services. **Affiliates:** Our company affiliates. **Advertising Partners:** Third-party advertisers who use tracking tools to deliver personalized ads. **APIs/SDKs:** Third-party APIs and SDKs as part of Service functionality. **Legal/Safety Disclosures:** To comply with law enforcement, legal process, court orders, or subpoenas; protect rights, property, or safety; enforce policies; collect debts; or assist with investigations. **Corporate Transactions:** In connection with mergers, acquisitions, financing, reorganizations, bankruptcies, or asset sales, your information may be transferred as permitted by law. ## 6. Your Privacy Choices and Rights **Email Communications:** Unsubscribe via link in emails. You'll still receive transaction-related and service communications. **Text Messages:** Opt out via instructions in messages or by contacting us. **Mobile Devices:** Adjust settings to control push notifications and location collection. **Do Not Track:** We do not respond to DNT browser signals. **Cookies and Advertising:** Adjust browser/device settings to control cookies. Mobile opt-outs: follow device instructions for Android/iOS. Visit Network Advertising Initiative, Digital Advertising Alliance, European Digital Advertising Alliance, and Digital Advertising Alliance of Canada for targeted ad opt-outs. Opt-outs are device and browser-specific. ### Your Rights (where applicable by law) **Access:** Confirm we're processing your information, obtain copies, or request portable electronic copies. **Correction:** Request correction of inaccurate/incomplete information. **Deletion:** Request deletion of your information. **Restriction/Objection:** Request restriction or object to processing, including for direct marketing. **Withdraw Consent:** Withdraw consent (future processing only; doesn't affect prior lawful processing). Contact us per Section 14 to exercise rights. We'll process requests per applicable law. ## 7. Security We use technical and organizational measures to protect your information. No system is 100% secure; we cannot guarantee security. We may communicate electronically about security, privacy, and administrative issues. If we learn of a breach, we may notify you electronically, by mail, or via email. ## 8. International Data Transfers Information may be transferred, processed, and stored anywhere in the world, including the United States, which may have different data protection laws. We safeguard your information consistent with applicable law. ## 9. Data Retention We store personal information as long as you use our Services or as necessary to fulfill collection purposes, provide Services, resolve disputes, establish legal defenses, conduct audits, pursue legitimate business purposes, enforce agreements, and comply with applicable laws. ## 10. California Residents This section applies to personal information subject to the California Consumer Privacy Act ("CCPA"). The CCPA requires us to disclose the categories of personal information we collect and the categories of third parties to whom we disclose that information. Over the past 12 months, we have collected and disclosed the following categories: **Identifiers** (such as name, email, IP address). Disclosed to: Service providers, business partners, affiliates, advertisers. **Personal information under California Customer Records statute** (such as contact details, payment information). Disclosed to: Service providers, affiliates. **Protected classification characteristics** (such as age, gender). Disclosed to: Service providers. **Commercial information** (such as purchase history, preferences). Disclosed to: Service providers, business partners. **Internet or network activity** (such as browsing history, interactions with our Services). Disclosed to: Service providers, advertisers. **Geolocation data.** Disclosed to: Service providers. **Audio, visual, or similar information** (such as meeting recordings, transcriptions). Disclosed to: Service providers, AI/transcription providers. **Professional or employment information** (such as job title, employer). Disclosed to: Service providers. **Inferences** (such as profiles reflecting preferences or characteristics). Disclosed to: Service providers, advertisers. See Sections 2 and 4 above for the sources from which we collect personal information and our business and commercial purposes for using personal information. **No "Sales" Under CCPA.** We do not "sell" personal information as defined by the CCPA, nor do we have actual knowledge of any "sale" of personal information of minors under 16 years of age. ### Additional Rights for California Residents **Right to Opt-Out of Sharing:** You have the right to opt out of our disclosure of personal information to third parties for their direct marketing purposes. To make such a request, contact us as set forth in Section 14 below with "California Privacy Rights" in the subject line. **Right to Non-Discrimination:** You have the right not to receive discriminatory treatment for exercising your rights under the CCPA. ## 11. Nevada Residents Nevada residents may opt out of the "sale" of certain personal information. We do not currently sell personal information as defined under Nevada law. ## 12. Children's Information Services are not directed to children under 13. We don't knowingly collect children's information. Contact us if your child provided information without consent. We'll delete children's information collected in violation of law. ## 13. Other Provisions **Third-Party Sites/Apps:** Our Services may link to third-party sites/apps not controlled by us. Read their privacy policies. We're not responsible for third-party privacy practices. Providing information to third parties is at your own risk. **Supervisory Authority:** EEA, Switzerland, and UK residents may lodge complaints with supervisory authorities if you believe our processing violates applicable law. **Changes to Privacy Notice:** We may revise this Notice and will notify you as required by law. Continued use after changes take effect constitutes acceptance. ## 14. Contact Us For questions about privacy practices, this Notice, or to exercise your rights: Email: [support@lyra.so](mailto:support@lyra.so) # Terms of Service Source: https://docs.lyra.so/policies/terms-of-service *Last updated: January 26, 2026* Please read these Terms of Service (the "Terms") and our Privacy Notice ("Privacy Notice") carefully because they govern your use of the website located at [https://lyra.so/](https://lyra.so/) (the "Site") and the services accessible via the Site and corresponding web application ("App") offered by Lyra ("Lyra"). To make these Terms easier to read, the Site, our services offered including our AI meeting platform and App are collectively called the "Services". ## 1. Agreement to Terms By using our Services, you agree to be bound by these Terms. If you don't agree to be bound by these Terms, do not use the Services. If you are accessing and using the Services on behalf of a company (such as your employer) or other legal entity, you represent and warrant that you have the authority to bind that entity to these Terms. In that case, "you" and "your" will refer to that entity. ## 2. Changes to these Terms or the Services We may update the Terms from time to time in our sole discretion. If we do, we'll let you know by posting the updated Terms on the Site, to the App and/or may also send other communications. It's important that you review the Terms whenever we update them or you use the Services. If you continue to use the Services after we have posted updated Terms it means that you accept and agree to the changes. If you don't agree to be bound by the changes, you may not use the Services anymore. Because our Services are evolving over time we may change or discontinue all or any part of the Services, at any time and without notice, at our sole discretion. ## 3. Who May Use the Services? ### (a) Use of the Services You may use the Services only if you are 18 years or older and capable of forming a binding contract with Lyra, and not otherwise barred from using the Services under applicable law. ### (b) Account Registration For certain features of the Services, you'll need an account. It's important that you provide us with accurate, complete and current account information and keep this information up to date. If you don't, we might have to suspend or terminate your account. To protect your account, keep the account details and password confidential, and notify us right away of any unauthorized use. You're responsible for all activities that occur under your account. ### (c) Authorized Users You will only allow the Services to be accessed and used by your employees or contractors who have been designated and authorized by you to be granted such access (each an "Authorized User") for the sole purpose of performing their job functions for you. Each account for the Services may only be accessed and used by the specific Authorized User for whom such account is created. The account credentials are confidential and cannot be shared or used by more than one person. You are responsible and liable for: (i) all actions taken under an Authorized User's credentials, whether or not such action was taken or authorized by the Authorized User; and (ii) all uses of the Services resulting from access provided by Lyra, directly or indirectly, whether such access or use is permitted by or in violation of these Terms. Lyra may process personal data about you and your Authorized User's use of the Services ("Account Data") in accordance with its Privacy Notice. Account Data is not Customer Files (as defined below) or Output. ### (d) Recording and Consent Requirements You must obtain consent prior to communicating with any person who is not a user of the Services ("Recipient"). By connecting your calendar to the Services, you represent and warrant that you will: (1) inform all Recipients that the meetings, calls or text messages may be recorded and transcribed by us or our service providers for the provision of the Services in compliance with applicable laws and regulations, including but not limited to the federal Electronic Communications Privacy Act and similar state-level laws related to wiretapping, interception of electronic communications, and the tracking and monitoring of online activity, and (2) obtain consent from all Recipients for us to use the Recipient's information for marketing purposes. Your failure to comply with these requirements may result in the termination of your rights to use the Services and potential legal action. We are not liable for any non-compliant meetings, calls or text messages, and you acknowledge that you are solely responsible for ensuring that all communications adhere to applicable regulations. ### (e) Customer Files You retain full ownership of any files, documents, data, or other content that you upload to the Services (collectively, "Customer Files"). Lyra does not claim any ownership rights over your Customer Files. However, by uploading Customer Files, you grant Lyra a non-exclusive, worldwide, royalty-free license to such Customer Files solely for the purpose of providing the Services to you. You are solely responsible for the legality, reliability, and appropriateness of your Customer Files and you must ensure that you have the necessary rights to upload and use these files in connection with the Services. ### (f) Service Availability Lyra aims to provide continuous availability of the Services; however, there may be occasions where the Services are unavailable due to maintenance, downtime, or other unforeseen circumstances. Lyra will strive to provide advance notice of any expected downtime, but this may not always be possible. You acknowledge that interruptions may occur and agree that Lyra is not liable for any losses or damages resulting from the unavailability of the Services. ### (g) Termination Either party may terminate this agreement with notice if the other party breaches any material term of these Terms and fails to cure such breach within thirty (30) days of receiving written notice of the breach. Upon termination, your access to the Services will cease, and you will no longer have the right to use any of the Services. You are responsible for retrieving any Customer Files that you wish to keep prior to termination, as Lyra may delete all of your Customer Files after the termination date. ## 4. Contact Us To resolve a complaint regarding the Services or to receive further information, please contact us at: [support@lyra.so](mailto:support@lyra.so) # Quickstart Source: https://docs.lyra.so/quickstart Get setup in Lyra asap * integrate your scheduler * teach lyra about your business * customize your research